fix: external retained-task judgments must not withhold launcher startup readiness #435

Merged
karsten merged 1 commit from fix/startup-assessment-readiness into main 2026-11-13 23:13:39 +00:00
Owner

Narrow residual found during actual installed-task verification after433. The per-task release fix allowed real existing Akira Matrix work to resume/complete (same ID, depth40->48, changed actual worker result). However CLI still awaited the ENTIRE external recovery-assessment scan before sending hayate-runtime-ready/Started-and-ready. A backlog of30–120s external judgments can park launcher readiness for many minutes despite valid structurally recovered state/channels/dispatcher. This is not persisted task loss and must not be conflated with separate TypeSafe HTTP504.

Move ONLY the semantic retained-task assessment scan after native readiness acknowledgment. All structural restoration, parent revocation/reset/cancel reconciliation, subagent/Dispatcher recovery, authenticated channels, durable inbox replay counters and persist remain BEFORE ready. Existing same-task per-admission persist/eligibility/stop/expiry/approval/unknown-effect fences remain unchanged; no completion inference, reset, manual unpause, fallback or replacement business execution. Unexpected scan infrastructure failures invoke existing graceful shutdown; normal missing judgments remain independently held/read-only retries.

Actual process regression for BOTH dist/cli.js and dist/launcher.js with durable original task and intentionally pending non-model reviewer: baseline025276a fails BOTH within15s (assessment entered but readiness withheld); fixed BOTH pass (2–3.6s) while assessment remains open. Authenticated capabilities respond and graceful SIGTERM cancels the assessor without productive work. Full2402pass/1existingSkip; typecheck/build/diff-check green. Prior433 installed/proven on all13 agents with8behavioral checks each. No production ledger/config changes. Protected exact-head CI and normal managed publisher only.

Narrow residual found during actual installed-task verification after433. The per-task release fix allowed real existing Akira Matrix work to resume/complete (same ID, depth40->48, changed actual worker result). However CLI still awaited the ENTIRE external recovery-assessment scan before sending hayate-runtime-ready/Started-and-ready. A backlog of30–120s external judgments can park launcher readiness for many minutes despite valid structurally recovered state/channels/dispatcher. This is not persisted task loss and must not be conflated with separate TypeSafe HTTP504. Move ONLY the semantic retained-task assessment scan after native readiness acknowledgment. All structural restoration, parent revocation/reset/cancel reconciliation, subagent/Dispatcher recovery, authenticated channels, durable inbox replay counters and persist remain BEFORE ready. Existing same-task per-admission persist/eligibility/stop/expiry/approval/unknown-effect fences remain unchanged; no completion inference, reset, manual unpause, fallback or replacement business execution. Unexpected scan infrastructure failures invoke existing graceful shutdown; normal missing judgments remain independently held/read-only retries. Actual process regression for BOTH dist/cli.js and dist/launcher.js with durable original task and intentionally pending non-model reviewer: baseline025276a fails BOTH within15s (assessment entered but readiness withheld); fixed BOTH pass (2–3.6s) while assessment remains open. Authenticated capabilities respond and graceful SIGTERM cancels the assessor without productive work. Full2402pass/1existingSkip; typecheck/build/diff-check green. Prior433 installed/proven on all13 agents with8behavioral checks each. No production ledger/config changes. Protected exact-head CI and normal managed publisher only.
fix: separate structural startup readiness from external task judgments
All checks were successful
decision-interface-ci / full-validation (pull_request) Successful in 2m55s
cb3124d5e9
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/core!435
No description provided.