Delete the tests and the taste packs

.github/workflows/ci.yml

@@ -40,9 +40,6 @@ jobs:
       - name: Format
         run: bun run fmt:check
 
-      - name: Test
-        run: bun test
-
       - name: Smoke the CLI
         run: bun src/cli.ts --help
 

.github/workflows/release.yml

@@ -38,9 +38,6 @@ jobs:
       - name: Typecheck
         run: bun run typecheck
 
-      - name: Test
-        run: bun test
-
       - name: Smoke the CLI
         run: bun src/cli.ts --help
 

README.md

@@ -16,7 +16,7 @@ _actual issues, tells the coding agent exactly how + what to fix_ **[more catche
 
 ### What you get
 
-- **Your taste, not the model's.** Code is judged against a `CORPUS.md`: a [taste pack](#taste-packs) ("code like dtolnay / DHH / antirez …") or your own best files
+- **Your taste, not the model's.** Code is judged against a `CORPUS.md` of your own best files
 - **On your personal Codex plan.** stupify reviews with [Codex](https://github.com/openai/codex), running on the $20-$200/month plan. API usage is roughly 50x more expensive, enjoy the subsidized tokens while they last
 - **Slop, named.** Code review is cheap. Taste is expensive. Codify the goodies, let the LLM pattern match
 
@@ -59,18 +59,9 @@ The reviews run on Codex. On exe.dev that's a keyless **LLM integration**: it fr
 the VM holds no API key and your plan is billed instead. Link one once at [exe.dev/integrations](https://exe.dev/integrations)
 and provisioning attaches it for you
 
-## Taste packs
+## Your taste
 
-Don't have a corpus yet? Borrow one. Pick a programmer whose code you'd point a new hire at and review and write like them, or compose several:
-
-[dtolnay](packs/dtolnay.md) · [DHH](packs/dhh.md) · [antirez](packs/antirez.md) ·
-[Sindre Sorhus](packs/sindre-sorhus.md) · [Rich Harris](packs/rich-harris.md) ·
-[zod](packs/zod.md) · [Mitchell Hashimoto](packs/mitchell-hashimoto.md) ·
-[Tanner Linsley](packs/tanner-linsley.md) · [Simon Willison](packs/simon-willison.md) ·
-[devshorts](packs/devshorts.md) · [Jarred Sumner](packs/jarred-sumner.md) · [browse all →](packs)
-
-Each pack is concrete principles plus commit-pinned exemplar files. Or **bring your own**: point stupify at the
-files you _wish_ all your code looked like, and it scaffolds a `.review/` in your repo:
+Point stupify at the files you _wish_ all your code looked like, and it scaffolds a `.review/` in your repo:
 
 ```bash
 npx @stupify/cli init src/best.ts src/clean-service.ts   # inlines them; you add one line of "why" each

docs/ARCHITECTURE.md

@@ -16,7 +16,7 @@ generic engines, and the taste they read.
 
 A `.review/` _inside the repo being reviewed_ is version-controlled with the code it judges, visible in code
 review, and tuned through a normal PR, the same way you'd change a lint config. When a repo has none, both
-engines fall back to `~/.stupify/.review`, which the CLI assembles from [taste packs](../packs). The reviewer
+engines fall back to `~/.stupify/.review`, a global taste you place by hand. The reviewer
 reads it fresh from `origin/main` on every sweep, so a merged rubric change is live immediately.
 
 ## Two ends of the loop: prevent, then detect

package.json

@@ -30,7 +30,6 @@
     "src/hand-written-prompts.ts",
     "src/sweep",
     ".review",
-    "packs",
     "README.md",
     "LICENSE"
   ],
@@ -41,7 +40,6 @@
   },
   "scripts": {
     "typecheck": "tsc -p tsconfig.json",
-    "test": "bun test",
     "lint": "oxlint",
     "fmt": "oxfmt",
     "fmt:check": "oxfmt --check",