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.