Repository navigation
2.0.2 — a drifted procedure doc can heal, and doctor stops promising
Two defects found by upgrading a real repo on published 2.0.1 — the kind
only a live walk surfaces.
- A drifted procedure doc can now heal.
refresh_procedure_doctriggered on
the config stamp rather than on the doc's own version. A repo whose
docs/gameplans/GAMEPLAN-PROCEDURE.mddrifted while its stamp stayed current
could never recover: the stamp matched the engine, so nothing refreshed, and
doctorfailed its MAJOR check forever on a file the engine owns. The trigger
is now the doc's version — which_procedure_doc_version()had been computing
all along with no caller consulting it. Bites any repo touched by the
withdrawn 3.0.0, whose procedure doc was left at 2.0.0. doctorno longer advertises an actionupgradedoes not perform. With
the docs-layout separation dormant in 2.0.1, doctor still told you to run
clauderize upgradeto separate your docs — and upgrade reported0 mechanical update(s). A shipped instruction that no-ops is the dangling-claim
class this project keeps building detectors for. The split-layout branch
stays, since it reports real state and forked stubs.
Suite 1622 → 1623. Procedure stays 1.13.0; the separation remains dormant.