The 2026-07-14 repositioning from "workspace control plane" to "local operating contract" (see #1825) propagated to some canonical docs but not others, and this is the second time in the doc history a positioning term needed a coordinated rename across ~50 markdown files. docs/contracts.md's registry catches command/JSON/help drift automatically, but has no mechanism for catching prose-level positioning drift.
Scope:
- Add a lightweight check (script or focused pytest test similar to tests/test_stability_tiers_docs.py) that flags retired terminology in docs/ once a positioning change lands, or add a docs/contracts.md registry row with an enforcing test.
- Document the check's scope: it should catch clearly-retired terms, not police normal prose variation.
Acceptance criteria:
- A future product-thesis rename produces a failing/flagged check for any doc still using the retired term, instead of relying on manual audit.
- The new contract is registered in docs/contracts.md.
Related: #1825
The 2026-07-14 repositioning from "workspace control plane" to "local operating contract" (see #1825) propagated to some canonical docs but not others, and this is the second time in the doc history a positioning term needed a coordinated rename across ~50 markdown files. docs/contracts.md's registry catches command/JSON/help drift automatically, but has no mechanism for catching prose-level positioning drift.
Scope:
Acceptance criteria:
Related: #1825