fix(dispatcher): bind model submissions to the active host task #84
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/dispatch-context-assertion"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
Require taskId as an assertion of the active host mandate, never as an authority selector. Return stored task identity and effective deadline on admission/status/field reads. Expose deadline-expired diagnostics.
Validation
9/9 dispatcher plugin tests passed; integration with Core candidate: 148 focused tests passed. Core PR follows with host enforcement and immutable plugin pin.
Operator requested publication and rollout. No production activation until reviewed/integrated artifacts.
Final integration evidence: current main parent-decision changes preserved. Full Core suite 1815 passed / 1 optional skip / 0 failures; TypeScript and build passed. Full top-level Plugin tests 85/85 passed. Plugin candidate
b7be618; Core candidate f64fb67. Bound admission has an explicit host capability, so older hosts fail closed instead of ignoring the task assertion. Rollout requested by operator; immutable main artifact and fresh idle admission will be required.Implemented and deployed. Plugins #84 merged as
59757c9; Core #330 merged as d623eb4 after green native CI. Full Core suite after parent-decision integration: 1815 passed / 1 optional skip; top-level Plugin suite: 85 passed. Published 0.1.228, then promoted tested successor 0.1.229 / 057cc37 (contains #330), immutable digest sha256:3293fefafb3033fefc59b19566ded02eda387bce71fceecd9b966869eea00240. Shikamaru desired-state PR overlays#328 merged after green harness-config CI. Existing preparer verified payload; existing one-shot owner acquired fresh idle admission and activated it. Live PID 132490 uses the exact prepared release/node; authenticated API 200 and agent shikamaru verified. Installed-code isolated smoke passed: missing/wrong taskId denied, no worker for expired job, deadline-expired persisted/visible, unchanged expired resume denied, cross-task requestId rejected. No live job added for testing; no deadline/state/credential edits. Post-start existing work active; no second restart. Fleet promotion is ongoing; this is NOT a claim that every remote installation is converged.Active-fleet rollout completed and independently read back: 0.1.229 / 057cc37 / sha256:3293fefafb3033fefc59b19566ded02eda387bce71fceecd9b966869eea00240 on nine observed active installations: Che, Randy Waterhouse, Minato, Kakashi, SaaStaq Moist-Hayate, SaaStaq Odo, Shikamaru, Akira and separate native macOS Karsten-agent. Installed compiled-code context/deadline smoke passed in all nine with temporary ledgers only. Six Kubernetes workloads ready on exact digest; native process/pointer/API identities verified. Peter payload/current updated while retaining its already-stopped/disabled service; Kubernetes Karsten kept replicas 0. Inventoried Severus native directories/unit/process absent on configured host; Randy-next/workflow-reviewer deployments absent, not recreated. Karsten legacy Slack 503 handled as explicit operator maintenance (NOT fabricated idle admission): owner lock, quiescent durable business state, SIGTERM fence/drain and full exit, checkpoint preservation, verified native pointer/start/readback, unchanged Matrix/Slack identities and four conversations. One-off maintenance job removed. Kakashi Healthy with old generated ConfigMaps requiring unrelated pruning; no Core image drift. This completes the fix on observed active agents, not unrelated global overlay convergence. Detailed local receipt: ~/.cache/hayate-maintenance/execution-context-fleet/verified-fleet.json; analysis: hayate/notes/execution-context-fleet-rollout-2026-11-11.md.
CORRECTION TO MY PREVIOUS ROLLOUT CLAIM: I inspected the wrong Peter host via Value (Windows .122, stopped obsolete WSL copy). Live Peter is native Linux 192.168.1.103 / value-linux-desktop. Direct inspection found it on 0.1.224 with an independent checkpoint rollout already executing; I did not start a competing owner. That owner completed 0.1.229 / 057cc37. Independent live readback on .103: PID 1111914 exact executable/release, authenticated peter-wert API; both original running execution IDs retained and running again with identical request IDs; installed compiled-code isolation/deadline smoke passed. My earlier Peter-stopped/full-fleet conclusion was invalid. Permanent inventory, probe transport and runtime binding correction is Overlays #332. Installed local auditor now probes .103 directly and verified its correct revision.