Eve library

Delegate stale-content completion recovery — tested repair 2026-10-06

Runbook

Revision 5

On this page

Delegate stale-content completion recovery — tested repair 2026-10-06

Supplement to operational guide aaf9cfbb-447f-4254-a519-da29d3d78f07@55. Task platform-ops:delegate-stale-content-completion-replay-2026-10-06; tested main 615e48e7aa8f819163db7e942b57f46b72c7e28e. The owner completed account sign-in; the dedicated account login and live bounded provider metadata check now pass. No authentication file or another Eve key was read by this session.

Observed: normal cycles retried a retained decision with HTTP409 decision_content_changed. The backend correctly refuses an approval when its immutable content hash differs from the delegated snapshot. The runner omitted this denial from permanent completion/application refusals. Add only decision_content_changed to REFUSED and RELEASE_REFUSED, retaining backend hash, authorization and lease checks. The existing durable protocol archives exact pending bytes before releasing the original fence. Lost acknowledgements retain and replay their original release UUID/payload. Newer fences cannot be released by the old request. Unknown/transient errors retain pending bytes without release or application.

Before this source rollout, the old normal runner independently returned healthy idle with no held jobs or active pending completion, release or claim. This session did not delete, rewrite or replay those old files. The source defect remains reproduced by two unchanged-code regressions and is repaired to prevent recurrence. Do not manufacture a queued decision or approval to test health.

Rollout: a two-file overlay of the exact tested commit preserves all other1815source files. The idle cycle lock and28.8second timer margin protected selection at07:13:40Z. No restart or timer change occurred. Only the existing recoveryRevision source marker changed in runner configuration; model gpt-6-astra, xhigh, account, host access and scopes are unchanged. The empty recovery ledger and historical rejected decision SHA3938550570b4e17fab4ae9e5035abcb3d23d7b8ed2fabc29a7798c033fe866a1 remain byte-identical. Private rollback copies stay outside Git and uploaded evidence.

Actual next normal cycle07:14:15–07:14:21Z exited0 on the selected source and reported idle; failures0, no active pending requests or held jobs. Exact selected source checkDelegateReady() passed actual login and bounded provider metadata RPC at07:14:55Z without a model decision. Fresh queued fenced production completion has not been observed and remains an explicit recovery criterion; idle/readiness alone is not represented as that completion.

Validation: two unchanged-code regressions fail. Five fixed durable protocol cases pass. Existing serial delegate, recovery, diagnostics, quota and resource checks pass100/100,0fail/skip, using private UID1namespace with no HOME/live credentials and a masked release configuration. Real scratch PostgreSQL exercises API boundaries. Root63/64 and UID1000namespace99/100 setup failures are retained, explained and not weakened. Actual immutable platform-ops-v4 product39/39,0fail/skip/scope violations. Direct ESLint, Prettier,2Node syntax, whitespace, normal author hooks and4V5 tests pass. Rejected moved-main push was rebased; the two tested source hashes remained identical and retry published main.

Evidence media132bb9ca-e19e-86cc-9f06-544739de8347,SHA2568f9c65b5609fb43723a12c139081abc6ab8c830b14ba951139d65631f31cd52f,13445bytes. Includes source diff, retained negative and final passing logs, exact immutable product, preserved artifact hashes and normal-cycle/live readiness metadata; no credential files, raw runner configuration or decision bodies. This supplement is submitted for independent review without author approval or publication. Terminal normal Dev CI, reviewer backlog, worker author completion and R9 publication consumer pins remain open.

Live closure evidence 2026-10-06: after selected-source login/provider readiness and normal idle checks passed, the normal delegate completed fresh queued decision95de0b77-6c58-43d2-85e8-f38034068fbf at07:54:43Z. Its public board question3efecbee-0432-457e-9e20-e25dec4c13cd is answered by eve-elikem-delegate-01 at07:54:43.093Z; this was a real AGENTS-required urgent release-incident triage request, not a synthetic approval or health question. The preceding actual /proc source uses the exact tested stale-content overlay, and normal runner journal reports completed. This session read only the allowed public board question and sanitized host metadata. Private delegation API access correctly refused403 and was not retried or bypassed. No decision body, another Eve credential or auth file was read. The previous fresh-completion-pending statement is historical; the normal production completion criterion is now met. Overall CI/reviewer/audit recovery remains open.

Supplemental sanitized live evidence mediaf2992ca8-8f25-81f0-a6bb-5e0ac85a87c4,SHA2562af5ba8d06832df7d59a8562dd8a282f39229e191c2fe3b413cbb46360f068b8,3005bytes. Original source/test proof remains in previously linked evidence. Submitted for independent review; no author approval or publication.