From bbcee47afd3f23e8277a56f431859b6c819e6761 Mon Sep 17 00:00:00 2001 From: type-two Date: Fri, 17 Jul 2026 18:01:54 +1000 Subject: [PATCH] CR-5 ratified at merge (coordinator) Co-Authored-By: Claude Fable 5 --- plan/CHANGE_REQUESTS.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/plan/CHANGE_REQUESTS.md b/plan/CHANGE_REQUESTS.md index a72d222..1232c93 100644 --- a/plan/CHANGE_REQUESTS.md +++ b/plan/CHANGE_REQUESTS.md @@ -108,4 +108,6 @@ Instead append an entry here and work around it locally; the integration agent a - **Workaround in place:** applied the minimal edit directly per the CR-1/CR-4 precedent (test file, not a frozen contract file; `api.py`/`cli.py` byte-for-byte unchanged), including the merge reconciliation with CR-4's side of the same loop. Suite green on the merged tree. -- **Decision:** (pending — coordinator/integration2) +- **Decision:** **APPLIED — RATIFIED by coordinator at merge** (2026-07-17). Same + supersession pattern as CR-1/CR-4; the shape-locked director test is stronger than the + stub assertion it replaces. Suite 169 → **189** on the merged tree.