diff --git a/.kaizen/agents/custodian-codex/supervision.json b/.kaizen/agents/custodian-codex/supervision.json index ee33b4cc..6fcea977 100644 --- a/.kaizen/agents/custodian-codex/supervision.json +++ b/.kaizen/agents/custodian-codex/supervision.json @@ -1264,8 +1264,8 @@ "risk_estimate_eur": null, "risk_estimate": "Old-policy atomic fragment install then expected1-3 minute JSON-phase Recreate interruption. Retain repaired protection during old-policy rollback. Illustrative recovery EUR100; full security loss and founder time unpriced, supervised judgement required.", "supervisor": "Bernd Worsch", - "approved_revision": null, - "approved_digest_sha256": null, + "approved_revision": 3, + "approved_digest_sha256": "df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34", "executed_revision": 2, "executed_digest_sha256": "d22b1f555af96c203b7d68efd25e80815ce18ca4e3bf0dd3ab96b6f699d50237", "refinement_or_rescue": true, @@ -1299,7 +1299,19 @@ "outcome": "failed; before native mutation" } ], - "current_revision_status": "pending_founder_review" + "current_revision_status": "approved_waiting_founder_execution", + "approved_at": "2026-11-02T01:13:07.073986+00:00", + "approval_ref": "User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02", + "current_revision_approval": { + "revision": 3, + "packet_sha256": "df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34", + "supervisor": "Bernd Worsch", + "disposition": "accepted_revised", + "approval_ref": "User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02", + "approved_at": "2026-11-02T01:13:07.073986+00:00", + "executed": false + }, + "score_note": "Prior revision2 failure remains unscored/failed and preserved; exact revision3 approval is recorded separately pending execution. No missing approval for revision2 is backfilled." } ], "trials": [ diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md index b3f6660f..fbb62d51 100644 --- a/WORK-RECORDS.md +++ b/WORK-RECORDS.md @@ -83,7 +83,7 @@ | workplan | CUST-WP-0080 | finished | — | workplans/CUST-WP-0080-netkingdom-security-blueprint-and-gap-closure.md | | workplan | CUST-WP-0081 | finished | — | workplans/CUST-WP-0081-netkingdom-architecture-review-and-reuse.md | | workplan | CUST-WP-0082 | backlog | — | workplans/CUST-WP-0082-netkingdom-security-hardening.md | -| workplan | CUST-WP-0083 | blocked | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | +| workplan | CUST-WP-0083 | active | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | | workplan | THE-WP-0001 | finished | — | workplans/THE-WP-0001-federation-interface.md | | task | CUST-WP-ADHOC-2026-05-02-T01 | done | — | workplans/ADHOC-2026-05-02.md | | task | CUST-WP-ADHOC-2026-07-02-T01 | done | — | workplans/ADHOC-2026-07-02.md | @@ -583,7 +583,7 @@ | task | CUST-WP-0083-T01 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | | task | CUST-WP-0083-T02 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | | task | CUST-WP-0083-T03 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | -| task | CUST-WP-0083-T04 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | +| task | CUST-WP-0083-T04 | progress | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | | task | CUST-WP-0083-T05 | wait | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | | task | CUST-WP-0083-T06 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | | task | CUST-WP-0083-T07 | done | — | workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md | diff --git a/docs/changes/2026-11-01-scanner-json-digest/README.md b/docs/changes/2026-11-01-scanner-json-digest/README.md index 8be7f1dc..aebc71f3 100644 --- a/docs/changes/2026-11-01-scanner-json-digest/README.md +++ b/docs/changes/2026-11-01-scanner-json-digest/README.md @@ -25,3 +25,5 @@ The first diagnostic was returned: node/deployment/pod identity, readiness, old ## Current proposed recovery, revision3 The founder's condition report found exactly one missing scanner fragment among171 repositories, at `coulomb/markitect-main.git`. This explains the safe revision2 refusal. [Revision3](native-r3/PLAN.md), packet SHA256 `df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34`, restores only that old-policy fragment, verifies its dispatcher and all171 active hook sets, preserves the failed receipt, then reuses the sealed unchanged JSON rollout and six source changes. Seven controller and six real filesystem cases passed; the original scanner accepts this preparation and all source preimages remain unchanged. Await exact founder review/execution via `/tmp/forge-scanner-recover-and-rollout.sh`. This new repair is not covered by an inferred retry permission; it is concretely included in the reviewed revision3 action. Repair protection remains installed on later JSON rollback. Existing-history admission and the cause of missing adoption are not established by this repair. + +Founder approval received for exact revision3 packet `df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34` (User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02). Attended execution is pending via `bash /tmp/forge-scanner-recover-and-rollout.sh`; the approval receipt is `native-r3-approval.json`. No new review is requested within this approved scope. diff --git a/docs/changes/2026-11-01-scanner-json-digest/native-r3-approval.json b/docs/changes/2026-11-01-scanner-json-digest/native-r3-approval.json new file mode 100644 index 00000000..e7852217 --- /dev/null +++ b/docs/changes/2026-11-01-scanner-json-digest/native-r3-approval.json @@ -0,0 +1,10 @@ +{ + "proposal_id": "SYNC-SCANNER-JSON-DIGEST-20261101", + "revision": 3, + "packet_sha256": "df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34", + "approved_by": "Bernd Worsch", + "approved_at": "2026-11-02T01:13:07.073986+00:00", + "approval_ref": "User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02", + "status": "approved; native execution pending", + "original_failed_revision2_preserved": true +} diff --git a/docs/repository-sync-2026-11-01.md b/docs/repository-sync-2026-11-01.md index f25f3f3a..855b91c2 100644 --- a/docs/repository-sync-2026-11-01.md +++ b/docs/repository-sync-2026-11-01.md @@ -93,3 +93,5 @@ The read-only condition report examined171 repositories and found only `scanner- Prepared revision3 of the same stable proposal, packet SHA256 `df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34`. It restores the existing-policy hook only at the exact missing path using atomic no-replace creation; verifies the actual dispatcher in a disposable receive fixture and all171 active hook hashes/metadata; preserves the original failed receipt; then continues the sealed unchanged JSON activation and six owner-source changes. The repair remains installed during any later JSON rollback. Seven controller and six real filesystem cases passed, including a171-repository full inventory/install/verification round trip. The original local policy accepts all new packet files and all six source preimages still match. No revision3 native action has run. Exact founder review is pending because this adds a native repair to revision2. Decision5410707c-ce73-4f80-9c03-805102c31c58 and T04 point to the revised plan/launcher. Original revisions, failed execution and diagnostics remain intact; no authority or success is invented. Missing-fragment installation does not prove historical admission, lifecycle coverage, or why adoption missed this repository; carry those limits into the source-owner class-level followup. + +The founder explicitly approved exact revision3 packet `df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34` via User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02. Recorded approval separately from the original failed revision2; T04 is in progress and the workplan active. Attended native execution is pending; no verified mutation/success or prior missing approval is invented. The approved scope includes the exact hook repair, sealed JSON continuation and same six source changes. diff --git a/workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md b/workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md index fc0549c3..b68c7981 100644 --- a/workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md +++ b/workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md @@ -4,7 +4,7 @@ type: workplan title: "Publish local repository changes and resolve scanner publication failures" domain: infotech repo: the-custodian -status: blocked +status: active owner: codex created: "2026-11-01" updated: "2026-11-02" @@ -55,17 +55,17 @@ Generated-only gates, local/remote scanner deadlines and false positives are ind ```task id: CUST-WP-0083-T04 -status: wait +status: progress decision_id: "5410707c-ce73-4f80-9c03-805102c31c58" priority: high needs_human: true -intervention_note: "Review exact SYNC-SCANNER-JSON-DIGEST-20261101 revision3, packet SHA256 df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34. It restores the one missing old-policy markitect-main hook, verifies171 repositories, then continues sealed JSON rollout and same six source changes. Founder launcher: bash /tmp/forge-scanner-recover-and-rollout.sh." +intervention_note: "Founder approved exact revision3 packet df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34. Run bash /tmp/forge-scanner-recover-and-rollout.sh in the founder terminal and return its sanitized result/receipt. No further approval requested; native execution has not yet been verified." state_hub_task_id: "589e1a54-9a4e-5f90-bd29-5c61a6cf8081" ``` Human-lane checkpoint, current 2026-11-02: the founder's diagnostics identified exactly one missing scanner fragment among171 repositories, at `/data/git/gitea-repositories/coulomb/markitect-main.git/hooks/pre-receive.d/10-custodian-secret-scan`. Identity/readiness/template/artifact guards passed. Revision2 failed safely during inventory before mutation; its original packet and failure receipt remain preserved. -Revision3 is prepared at `docs/changes/2026-11-01-scanner-json-digest/native-r3/PLAN.md`, packet SHA256 `df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34`. It installs only that missing old-policy fragment with atomic no-replace creation; verifies the actual dispatcher with an isolated receive probe; snapshots/verifies all171 active hook sets; preserves the failed receipt; then reuses unchanged sealed revision2 for guarded JSON activation and the same six owner-source changes. Seven controller and six actual filesystem tests passed, including171-repository install/verification and retention of coverage repair on JSON failure. The current scanner accepts the preparation; the six source preimages remain unchanged. Live revision3 execution is pending exact founder review, required because this adds a native repair. No admin borrowing, mutation retry, source activation, new authority or scored success is inferred. +Revision3 is prepared at `docs/changes/2026-11-01-scanner-json-digest/native-r3/PLAN.md`, packet SHA256 `df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34`. It installs only that missing old-policy fragment with atomic no-replace creation; verifies the actual dispatcher with an isolated receive probe; snapshots/verifies all171 active hook sets; preserves the failed receipt; then reuses unchanged sealed revision2 for guarded JSON activation and the same six owner-source changes. Seven controller and six actual filesystem tests passed, including171-repository install/verification and retention of coverage repair on JSON failure. The current scanner accepts the preparation; the six source preimages remain unchanged. The founder explicitly approved exact revision3 via User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02. Attended native execution is now pending via `bash /tmp/forge-scanner-recover-and-rollout.sh`; no further approval is requested. No admin borrowing, mutation retry, source activation, new authority or scored success is inferred. Installing the fragment does not retroactively admit existing history or establish why adoption missed this repository. Preserve that limitation and source-owner lifecycle/coverage followup in T03 and the final audit. Existing failure/refinement evidence and all original revisions remain intact.