postmergelisted

`totem wrap` is retired pending mmnto-ai/totem#1361 (it silently overwrites hand-crafted committed docs via the `totem docs` step). Run the post-merge steps directly instead. After merging PRs, run the following sequence. Replace `$ARGUMENTS` with the merged PR numbers (space-separated, e.g. `1345 1347 1348`). 1. Extract lessons from the merged PR(s): `pnpm exec totem lesson extract $ARGUMENTS --yes` 2. Sync the semantic index (usually already handled by the post-merge git hook, but running it explicitly is cheap and safe): `pnpm exec totem sync` 3. Compile new rules locally and export to AI tool configs. Do NOT pass `--cloud`; the cloud worker is Gemini-only (migration to Claude declined — mmnto-ai/totem#1221, closed not-planned). Local compile routes to the `orchestrator.overrides.compile` role in `totem.config.ts` (currently Claude Sonnet 5): `pnpm exec totem lesson compile --export` 4. Review the newly compiled rules. Step 3's output prints a count like `N/M (100%) ... X compiled, Y skipped, Z failed`. For each of the X newly compiled rules, inspect them in `.totem/compiled-rules.json` and verify: - The `astGrepPattern` or `pattern` is not over-broad (does it fire on legitimate code the rule is not trying to flag?) - The pattern does not reference hallucinated package names, type names, or file paths that do not exist in the repo - The `lessonHeading` accurately describes the rule's behavior For any rule that fa