diff --git a/.kaizen/agents/custodian-codex/supervision.json b/.kaizen/agents/custodian-codex/supervision.json index 63063f73..9f5317ba 100644 --- a/.kaizen/agents/custodian-codex/supervision.json +++ b/.kaizen/agents/custodian-codex/supervision.json @@ -1308,27 +1308,38 @@ "packet_sha256": "df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34", "outcome": "failed after verified coverage repair; old-policy rollback verified", "approval_ref": "User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02", - "outcome_ref": "docs/changes/2026-11-01-scanner-json-digest/native-r4/prior-execution-outcome.json" + "outcome_ref": "docs/changes/2026-11-01-scanner-json-digest/native-r4/prior-execution-outcome.json", + "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": true, + "outcome": "failed", + "verification_ref": "docs/changes/2026-11-01-scanner-json-digest/native-r4/prior-execution-outcome.json" + } } ], - "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", + "revision": 4, + "packet_sha256": "64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd", "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": true, - "outcome": "failed", - "verification_ref": "docs/changes/2026-11-01-scanner-json-digest/native-r4/prior-execution-outcome.json" + "approved_at": "2026-11-02T01:59:02.333371+00:00", + "approval_ref": "User: Approve exact revision4; request_user_input_async call_f68b7e7de81a4c089e8864b3d66773a9 item0,2026-11-02", + "executed": false }, - "score_note": "One stable trial across revisions. Exact explicit revision3 approval/execution supports its failed accepted-revised outcome; earlier revision2 remains unscored in attempts. No missing approval is backfilled into a success, and current revision4 is pending.", + "score_note": "Summary fields retain the latest completed revision3 failed outcome; current revision4 exact approval is separate pending execution. Original failed attempts stay preserved; no success or missing earlier approval backfilled.", "original_digest": "75bc6e4bf1a98444cd844306bf8f3f81aca1e31b1609081905fd42ed1b76ae42", "approved_digest": "df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34", - "executed_digest": "df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34" + "executed_digest": "df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34", + "current_approved_revision": 4, + "current_approved_digest_sha256": "64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd" } ], "trials": [ 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 8ae9415f..cdb34d07 100644 --- a/docs/changes/2026-11-01-scanner-json-digest/README.md +++ b/docs/changes/2026-11-01-scanner-json-digest/README.md @@ -33,3 +33,5 @@ Founder approval received for exact revision3 packet `df1cb48259ec5411a3f8cd24d4 The founder executed approved revision3: the missing-fragment repair and171-repository coverage verification succeeded; candidate receiver probes passed; hook migration failed before deployment patch. The old policy/template/probes and protected metadata were verified by rollback. The repair remains installed. Exact failed receipts are preserved in `native-r4/`. The pinned Forgejo userspace reproduces the unsupported `chmod --reference` defect; workstation tests had missed it. [Revision4](native-r4/PLAN.md), packet SHA256 `64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd`, corrects numeric mode handling and exact known group-write restoration, reuses the existing verified immutable ConfigMap, and has a fresh execution/source gate. Eight shell image cases, a four-case171-repository/1539-hook controller run, three controller checks and runtime self-test passed. Candidate scanner/profile and six owner source hashes are unchanged. Await exact revision4 review; no native revision4 action has run. The proposed founder launcher is `/tmp/forge-scanner-rollout-r4.sh`. + +Founder approval recorded for exact revision4 packet `64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd` via User: Approve exact revision4; request_user_input_async call_f68b7e7de81a4c089e8864b3d66773a9 item0,2026-11-02. Attended execution pending at `/tmp/forge-scanner-rollout-r4.sh`; approval receipt `docs/changes/2026-11-01-scanner-json-digest/native-r4-approval.json`. Earlier failures and exact approvals remain preserved; no execution success is inferred from approval. diff --git a/docs/changes/2026-11-01-scanner-json-digest/native-r4-approval.json b/docs/changes/2026-11-01-scanner-json-digest/native-r4-approval.json new file mode 100644 index 00000000..f7373276 --- /dev/null +++ b/docs/changes/2026-11-01-scanner-json-digest/native-r4-approval.json @@ -0,0 +1,10 @@ +{ + "proposal_id": "SYNC-SCANNER-JSON-DIGEST-20261101", + "revision": 4, + "packet_sha256": "64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd", + "approved_by": "Bernd Worsch", + "approved_at": "2026-11-02T01:59:02.333371+00:00", + "approval_ref": "User: Approve exact revision4; request_user_input_async call_f68b7e7de81a4c089e8864b3d66773a9 item0,2026-11-02", + "status": "approved; native execution pending", + "prior_failures_preserved": true +} diff --git a/docs/repository-sync-2026-11-01.md b/docs/repository-sync-2026-11-01.md index 5d12dead..f888326b 100644 --- a/docs/repository-sync-2026-11-01.md +++ b/docs/repository-sync-2026-11-01.md @@ -103,3 +103,5 @@ Founder execution of exact approved revision3 fixed the one missing old-policy f A reproduced userspace defect explains a migration failure: Forgejo11.0.3-rootless pinned image691657c7 lacks `chmod --reference`; workstation tests used different tools. Revision4 replaces it with numeric modes, restores only known group-write additions to unchanged/owned hook inodes, reuses the existing immutableCM after exact data/UID checks, and uses fresh native/source receipt gates. Eight shell cases in the pinned image, four actual controller cases across171 repositories/1539 hooks (including19 mode restorations and rollback), three controller checks and runtime self-test passed. Same candidate binary/profile, deployment-field patch and six source postimages. Proposed exact revision4 packet SHA256 `64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd`; no native revision4 execution. Existing decision5410707c-ce73-4f80-9c03-805102c31c58 is reopened for this revised action, while exact revision3 approval/outcome stays preserved. The new launcher is `/tmp/forge-scanner-rollout-r4.sh`. Prior failed revisions are one trial, not new successes; exact reviewed revision3's failed outcome is scored as accepted-revised, never unchanged success. Current revision4 remains pending. + +Founder approval recorded for exact revision4 packet `64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd` via User: Approve exact revision4; request_user_input_async call_f68b7e7de81a4c089e8864b3d66773a9 item0,2026-11-02. Attended execution pending at `/tmp/forge-scanner-rollout-r4.sh`; approval receipt `docs/changes/2026-11-01-scanner-json-digest/native-r4-approval.json`. Earlier failures and exact approvals remain preserved; no execution success is inferred from approval. 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 70f3c48d..4d933f97 100644 --- a/workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md +++ b/workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md @@ -59,13 +59,13 @@ status: progress decision_id: "5410707c-ce73-4f80-9c03-805102c31c58" priority: high needs_human: true -intervention_note: "Review exact revision4 packet 64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd for portable hook migration, verified ConfigMap reuse and exact baseline mode restoration. Revision3 coverage repair/rollback verified; JSON activation failed on unsupported chmod --reference. Founder launcher after approval: bash /tmp/forge-scanner-rollout-r4.sh." +intervention_note: "Founder approved exact revision4 packet 64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd. Run bash /tmp/forge-scanner-rollout-r4.sh in the founder terminal and return its sanitized output/receipt. Approved scope includes portable migration, exact mode restoration, reused ConfigMap and same six source changes." state_hub_task_id: "589e1a54-9a4e-5f90-bd29-5c61a6cf8081" ``` Human-lane checkpoint, current 2026-11-02: approved revision3 repaired the missing markitect-main fragment and verified171 active old-policy scanner fragments plus unchanged protected metadata. Its native JSON candidate probe passed. Hook migration then failed before deployment patch; rollback verified the old template/policy, all171 fragments and old-policy probes. The repair and original failed receipts remain intact. Same-image reproduction identified an unsupported `chmod --reference` command that workstation tests missed. -Revision4 is prepared at `docs/changes/2026-11-01-scanner-json-digest/native-r4/PLAN.md`, packet SHA256 `64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd`. It uses portable numeric mode copying, restores only known group-write additions to unchanged/owned hook inodes after pod recreation, verifies/reuses the already-created immutable ConfigMap, and uses a fresh native/source receipt gate. Same scanner/profile, two deployment fields and six source candidates; prior packets/receipts are unchanged. Eight pinned-image shell cases, four full-controller cases across171 repositories/1539 hooks, three controller checks and the runtime self-test passed. The six owner-source preimages remain unchanged. Native revision4 is pending exact founder review; no inferred retry, source activation or authority grant. The verified failed revision3 is recorded as failed, with the earlier unscored revision2 preserved in the same trial. +Revision4 is prepared at `docs/changes/2026-11-01-scanner-json-digest/native-r4/PLAN.md`, packet SHA256 `64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd`. It uses portable numeric mode copying, restores only known group-write additions to unchanged/owned hook inodes after pod recreation, verifies/reuses the already-created immutable ConfigMap, and uses a fresh native/source receipt gate. Same scanner/profile, two deployment fields and six source candidates; prior packets/receipts are unchanged. Eight pinned-image shell cases, four full-controller cases across171 repositories/1539 hooks, three controller checks and the runtime self-test passed. The six owner-source preimages remain unchanged. The founder explicitly approved exact revision4 via User: Approve exact revision4; request_user_input_async call_f68b7e7de81a4c089e8864b3d66773a9 item0,2026-11-02. Attended native execution is pending at `bash /tmp/forge-scanner-rollout-r4.sh`; no additional approval is requested within that scope. Source activation awaits verified native outcome. The verified failed revision3 is recorded as failed, with the earlier unscored revision2 preserved in the same trial. Installing the repaired fragment does not retroactively admit existing history or establish why adoption missed this repository. Preserve historical/lifecycle coverage limits and source-owner class-level followup in T03 and the final audit.