weichen 4561bcbd6b Record the RDM status review and repoint documents ...

Why: The planning index registered the stale RDM snapshot as an open
reconciliation item; the review re-verdicts the baseline and audits the
seven MS1 acceptance clauses so P1 scheduling rests on evidence.

Evidence: Documents PR #47 merged as 9505c7e (plan SS2.3 review, MS1
audit, six registered gaps, index sync, seven SELF receipts under
docs/records); replays run in an isolated clone at RDM 4feb2f0 with
pins=v0.1.0; the private minutes receipt stays local by decision.

Impact: documents gitlink -> 9505c7e; task card records authorization,
requirements R1-R5, increments, and next-task candidates; no code
changes; review is not milestone acceptance.

Refs: Documents #47; task feature/rdm-status-review.

2026-10-08 09:24:50 +00:00

..

backend @ fe7c245f5c

Advance the cascade pins after the nested pin-alignment PRs

2026-10-08 04:03:42 +00:00

core @ a253a40b8e

Point the core and ui pins at the contract authority update

2026-10-07 17:44:24 +00:00

documents @ 9505c7eadc

Record the RDM status review and repoint documents

2026-10-08 09:24:50 +00:00

frontend @ 84b73ab328

Take the WP6 pins and record the usage/retry increment on the task card

2026-10-07 17:31:08 +00:00

ui @ 76d6633736

Point the core and ui pins at the contract authority update

2026-10-07 17:44:24 +00:00