docs: full rewrite of 62 pages, strip decorative components, scrub AI vocabulary

[agjs]

Full rewrite of every page across the BoringStack docs site. Sixty-two files. Plan: .claude/plans/zippy-scribbling-sprout.md.

What changed

Every page rewritten under four principles:

1. Don't re-document code. Schema columns, env vars, routes, ACL keys, compose service matrices, npm-script catalogues all get one-line pointers to the source file rather than duplicated tables.
2. Lead with the path to the outcome. First content after the title answers "what do I do" or "what is this in one paragraph", not philosophy.
3. Page must stand alone. A reader who only reads one page reaches a working outcome or full understanding.
4. Plain markdown by default. Only <Aside> from @astrojs/starlight/components survives, for genuinely critical warnings.

Components stripped (zero across the corpus, except <Aside>)

Component	Files before	After
<PageIntro>	~30	0
<CommandRun>	28	0
<DocCallout>	27	0 (excluding 404.mdx, exempt)
<SignalGrid>	24	0
<DocFileTree>	10	0
<DataMatrix>	6	0
<FaqGroup> / <FaqItem>	32	0

Re-documentation sections deleted outright

• api/mfa.mdx: both auth.users + mfa_recovery_codes <DataMatrix> blocks
• api/audit-log, auth, multi-tenant, acl, env-validator, notifications, bounce-handling: schema and route enumerations
• infra/resource-limits, profiles-and-overlays: defaults plus overlay matrices
• reference/env-vars.mdx: 390 → 70 lines (point at the three .env.example files)
• reference/commands.mdx: 259 → 83 lines (point at the package.json files)
• architecture/monorepo-layout.mdx: file-tree replaced with prose

Other fixes along the way

• api/bounce-handling.mdx had a broken <DataMatrix> rendering Raku/Perl-6 grammar token garbage on the production site. Fixed.
• landing/landingContent.ts had stale boot commands (./compose/dev.sh, ./compose/prod.sh, "infra-template"). Updated to ./setup.sh --up and the current path.
• Header.astro had a "Cost" top-nav link pointing at a deleted anchor on why-boringstack.mdx. Removed.
• deployment.mdx Manual provision path had git-clone after scp, which would fail. Reordered to clone-then-scp-then-up.

Vocabulary scrub (before → after across the corpus)

Pattern	Before	After
em dashes (—)	103	0
"load-bearing"	5	0
"source of truth"	7	0
"out of the box"	6	0
"guardrails"	7	0
"mental model"	2	0
"first-class"	2	0
"battle-tested"	1	0
"blast radius"	1	0
"primitives" (as noun)	6	0
"opinionated" (without naming the opinion)	4	0
Tier-1 AI words (delve, leverage, robust, seamless, ...)	already 0	still 0

Pages exempt per plan

index.mdx, 404.mdx, changelog.mdx, topics/privacy.mdx, topics/terms.mdx. The first three are special-purpose; the last two are legal templates the operator fills in for their fork.

Recipes (recipes/add-*.mdx) keep their code snippets — recipes ARE the code an operator writes to wire the feature.

Test plan

• cd apps/docs && bun run build — green, 67 pages, no broken links
• All six pre-merge greps return zero across the corpus
• Pre-push security + smoke gates green (one gitleaks false positive on MEILI_MASTER_KEY= empty line allowlisted; see commit message)
• Manual spot-check: deployment, provisioning-with-tofu, mfa, env-vars all read coherently end-to-end

Three commits:

1. 9262aa9: the 62-file rewrite
2. follow-up: fix the gitleaks false-positive in the Meilisearch recipe
3. follow-up: allowlist the prior commit in .gitleaks.toml