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

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

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06ba0-10aa-7ea0-b20a-4f3fac39efe9

docs/adr/ADR-001-agent-harness-architecture.md

@@ -35,8 +35,11 @@ control's operating rhythm depended on a workstation cron bridge
    credentials, no tool enumerations.
 3. **Blueprints stay in kaizen-agentic; scheduling stays in
    activity-core; provider abstraction stays in llm-connect.** The
-   harness consumes all three and is the only credential holder and
-   policy enforcement point for agent sessions.
+   harness consumes all three. Per ADR-002 it is the
+   repository-transaction and rein-local tool-policy enforcement point
+   within a chained grant, not the only credential holder or the only
+   policy enforcement point in the estate. Tenant repos, blueprints, and
+   schedules still must not hold session credentials or tool wiring.
 4. The 2026-07-17 executor-worker prototype is adopted as the harness
    seed (`agent_harness/` package). binky-control is tenant #1.
 
@@ -55,3 +58,6 @@ Details: [docs/architecture.md](../architecture.md).
 - Repo-boundary discipline continues: any pressure to add scheduling,
   blueprint authoring, or tenant-specific logic here is a signal to
   extend the neighbor repo or the instance model instead.
+- ADR-002 (accepted 2026-08-29) amends the credential-holder and
+  policy-enforcement slogans in decision 3. The instance/runtime split
+  and the prohibition on tenant-held credentials are unchanged.

docs/adr/ADR-002-governed-execution-responsibility-chain.md

@@ -1,19 +1,28 @@
 ---
 id: ADR-002
 title: Governed execution is a responsibility chain, not a single enforcement point
-status: proposed
+status: accepted
 date: "2026-08-23"
-workplan_task: HARNESS-WP-0003-T01
+accepted: "2026-08-29"
+workplan_task: REINAH-WP-0003-T01
 ---
 
 # ADR-002 — Governed execution responsibility chain
 
 ## Status
 
-Proposed. Acceptance requires acknowledgement from the owners of Activity Core,
-Glas, sand-boxer, and llm-connect. Until then this document records the
-implementation target for `HARNESS-WP-0003` but does not amend `INTENT.md` or
-supersede accepted ADR-001.
+Accepted 2026-08-29 by operator Bernd Worsch. This is the implementation
+contract for `REINAH-WP-0003`. It amends the slogan wording in `INTENT.md` and
+ADR-001 on the same date; it does not replace ADR-001's instance/runtime split
+or the prohibition on tenant-held credentials and tenant-specific runtime
+wiring.
+
+The proposed text required sibling-owner acknowledgement before acceptance.
+Glas had already approved the boundary; Activity Core had deployed the queue
+and lease behavior it asked to see in writing. The operator accepted the
+substance without waiting for remaining exact-revision acknowledgements from
+Activity Core, sand-boxer, and llm-connect. Those recordings remain welcome;
+they are no longer a gate. Sibling objection still changes the matrix.
 
 ## Context
 
@@ -211,4 +220,8 @@ Reviews requiring follow-up:
   live spoof-refusal evidence, and no manufactured late-close run. Those facts
   are incorporated in this revision for final Activity Core acknowledgement.
 
-Pending: revised Activity Core acknowledgement, sand-boxer, and llm-connect.
+Pending as recording only, not a gate: revised Activity Core
+acknowledgement of this accepted text, sand-boxer, and llm-connect.
+
+Operator acceptance: Bernd Worsch, 2026-08-29, session decision to accept
+ADR-002 as written and proceed with T02 wiring.