fix: durable priorities and non-starving post-restart task coordination #372

Merged
karsten merged 2 commits from fix/automatic-post-restart-continuation into main 2026-11-12 18:14:48 +00:00
Owner

Akira selected #368 but its due activation verification was starved by another continuing Main task. Persist explicit operator priorities across Main → Dispatcher → Worker recovery; retain last-committed priority during pending/failed saves; validate natural-language changes independently from authenticated operator text only. Fair bounded priority scheduling and independent task coordination; no capacity increase, preemption, effect replay, hold/budget reset or DAG claims. Startup-only timerless-wait reassessment, including deferral behind restored turns. Integrates latest main #369–371 rather than duplicating their retry/diagnostics fixes.

Validation: npm run build; complete suite 2036 passed / 1 skipped / 0 failed. New integrated regression proves two retained Main tasks delegate workers that overlap at capacity2, without post-restart user input. Explicit stop/block/expiry/legacy holds preserved. PR workflow now triggers for Harness/assessment/priority source paths; no target-host suite gate.

Evidence: development-evidence/post-restart-priority-coordination-2026-11-12.md. Independent supplied-diff review required before merge; native activation/live proof follow CI.

Akira selected #368 but its due activation verification was starved by another continuing Main task. Persist explicit operator priorities across Main → Dispatcher → Worker recovery; retain last-committed priority during pending/failed saves; validate natural-language changes independently from authenticated operator text only. Fair bounded priority scheduling and independent task coordination; no capacity increase, preemption, effect replay, hold/budget reset or DAG claims. Startup-only timerless-wait reassessment, including deferral behind restored turns. Integrates latest main #369–371 rather than duplicating their retry/diagnostics fixes. Validation: npm run build; complete suite **2036 passed / 1 skipped / 0 failed**. New integrated regression proves two retained Main tasks delegate workers that overlap at capacity2, without post-restart user input. Explicit stop/block/expiry/legacy holds preserved. PR workflow now triggers for Harness/assessment/priority source paths; no target-host suite gate. Evidence: development-evidence/post-restart-priority-coordination-2026-11-12.md. Independent supplied-diff review required before merge; native activation/live proof follow CI.
Merge remote-tracking branch 'origin/main' into fix/automatic-post-restart-continuation
All checks were successful
decision-interface-ci / full-validation (pull_request) Successful in 2m12s
57dfacaedb
# Conflicts:
#	src/harness.ts
Author
Owner

Post-merge activation verified: Akira and Shikamaru both report active Core f21b2ff20d through authenticated capabilities, not merely an available release. Native agent tool install completed and owner selected replacement after old runtime exit. Akira existing Matrix task $3OvXYPALbaXRwIfLt2Qvw7nbPhMLAzzvCbQpb5eFGYU resumed from retained depth5 to6 and produced a new actual revision/state verification reply; another previously waiting task resumed as well. Read-only monitoring observed no new Matrix task IDs over this interval and no productive request was injected after restart. Persistent proof: post-restart-pr372-live-proof.json, akira-pr372-live-observations.jsonl. Independent integrated diff review APPROVE; remote full-validation success in2m12s.

Parallelism is proven by the integrated restore/delegate regression with two simultaneously pending worker promises; this is distinguished from live native parallelism. An additional isolated, read-only native two-worker timing probe is in progress and is not yet claimed successful.

Post-merge activation verified: Akira and Shikamaru both report active Core f21b2ff20de72cb059734e032d8a8fb865c72498 through authenticated capabilities, not merely an available release. Native agent tool install completed and owner selected replacement after old runtime exit. Akira existing Matrix task $3OvXYPALbaXRwIfLt2Qvw7nbPhMLAzzvCbQpb5eFGYU resumed from retained depth5 to6 and produced a new actual revision/state verification reply; another previously waiting task resumed as well. Read-only monitoring observed no new Matrix task IDs over this interval and no productive request was injected after restart. Persistent proof: post-restart-pr372-live-proof.json, akira-pr372-live-observations.jsonl. Independent integrated diff review APPROVE; remote full-validation success in2m12s. Parallelism is proven by the integrated restore/delegate regression with two simultaneously pending worker promises; this is distinguished from live native parallelism. An additional isolated, read-only native two-worker timing probe is in progress and is not yet claimed successful.
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!372
No description provided.