Auto-Improvements Tracker - Growth: Dedup Against Canon

[missingbulb]

Standing tracker for the growth dedup phase (phase 3): prunes of this repo's local dev/procedures/ docs against the currently-merged Claudinite canon. Each run that changes a doc logs a dated comment naming what was pruned and the covering canon line/check id. Runs that prune nothing log nothing.

[missingbulb]

2026-07-08 — dedup run (PR #77, branch claude/compassionate-babbage-vnp4yf)

Pruned local items the merged canon now owns in full; kept all stronger-narrower items.

• chrome-extension.md — removed: ID-token-via-launchWebAuthFlow-not-getAuthToken, MV3-ES-modules-no-bundler, silent-refresh-prompt=none. Covered by packs/chrome-extension/RULES.md (the launchWebAuthFlow/id_token/not-getAuthToken line; the "MV3 loads ES modules natively — don't add a bundler" line; the "silent token refresh … must request prompt=none" line).
• aws-sam.md — removed: esbuild-Handler-path-flatten, esbuild-regular-dependency, CloudFront-custom-policy-Authorization, cache-key-vs-origin-forwarding-independent. Covered by packs/aws-sam/RULES.md lines 1–3 + checks aws-sam/handler-path, aws-sam/esbuild-dependency, aws-sam/cloudfront-authorization.
• ci-cd.md — removed: gate-optional-job-on-variable-not-secret (canon git-github-advanced §"Gate an optional CI job on a repo variable, not a secret" + check gha/secrets-in-job-if); read-PR-CI-via-check-runs-not-listing-tools (canon git-github-advanced §"To read a PR's CI result … Target the head SHA directly rather than actions_list-ing the repo's runs — that returns every run, its output is huge").
• testing.md — removed the file + its routing pointer: "teach every double a new use of a multi-faked boundary" is covered verbatim (incl. the far-away DOM-snapshot pixel-diff failure mode) by the canon writing-tests skill; only TLDR file names remained as illustration.

Kept: chrome multi-account login_hint, interactive-escalation guard, CORS-so-skip-host_permissions install warning, optional_host_permissions+dynamic content-scripts; aws-sam deploy-role IAM scope, new-account CloudFront verification, failed-CREATE cleanup; ci-cd OIDC sub casing, MCP-not-curl+status-workflow, workflow_dispatch-only-on-default-branch — the canon states these too generally (or not at all).

---

Generated by Claude Code