chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-08-08:
  - update .custodian-brief.md for rein-aharness

.custodian-brief.md

@@ -2,12 +2,16 @@
 # Custodian Brief — rein-aharness
 
 **Domain:** agents  
-**Last synced:** 2026-08-08 19:09 UTC  
+**Last synced:** 2026-08-08 19:25 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-*(none — repo may need first-session setup)*
+### Binky weekly founder-review ops-run approach
+Progress: 2/3 done  |  workplan_id: `4a7ab4e1-5b34-461b-8532-38dd95b3b941`
+
+**Open tasks:**
+- ! Deploy and prove one production cycle  `cd6b0f33`
 
 ---
 ## MCP Orientation (when available)

workplans/REIN-A-0003-binky-weekly-review-approach.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Binky weekly founder-review ops-run approach"
 domain: agents
 repo: rein-aharness
-status: proposed
+status: active
 owner: codex
 topic_slug: rein-aharness
 priority: medium
@@ -14,6 +14,7 @@ origin: residual
 origin_ref: REIN-A-0002
 related:
   - REIN-A-0002
+  - AWQ-011
 state_hub_workstream_id: "4a7ab4e1-5b34-461b-8532-38dd95b3b941"
 ---
 
@@ -38,7 +39,7 @@ weekly founder-review ops run, including its domain completion event.
 
 ```task
 id: REIN-A-0003-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "fec71480-b8c1-48f7-ab4a-8e3ac918cf7e"
 ```
@@ -47,11 +48,21 @@ Inspect the activity-core definition and Binky weekly-review contract. Decide
 whether an existing deterministic command can satisfy it or a new structured
 executor is required. Record required inputs, output, and completion event.
 
+**Decision (2026-08-08):** implement `brief-weekly` as structured llm-connect
+generation plus a deterministic markdown applier; never use a host coding-agent
+session. Inputs are the review week's daily briefs, `SuccessMilestones.md`,
+`DecisionQueue.md`, `RiskRegister.md`, `WORK-RECORDS.md`, the previous weekly
+review, and recent git history. Output is
+`briefs/YYYY-MM-DD-weekly-founder-review.md`, committed idempotently, followed
+by a `binky_weekly_review` progress event. Code derives milestone movement and
+the RISK-005 `clear|watch|escalate|quiet` state; model output cannot override
+those facts. Binky residual intake `AWQ-011` is the upstream work record.
+
 ## Implement and test the registry entry
 
 ```task
 id: REIN-A-0003-T02
-status: wait
+status: done
 priority: high
 state_hub_task_id: "f23de6a4-3bda-4927-b758-8acfd2c1d035"
 ```
@@ -61,6 +72,11 @@ Binky. Cover execution success, domain completion, and explicit failure.
 
 **Depends on:** REIN-A-0003-T01.
 
+**Implemented 2026-08-08:** `brief_weekly` structured generation,
+deterministic milestone/RISK-005 signals, idempotent markdown apply + commit,
+CLI `brief-weekly`, approach registry dispatch, completion event, and tests.
+Full suite: 87 passed.
+
 ## Deploy and prove one production cycle
 
 ```task