feat: Main-managed durable worker profiles and tasks #226
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/worker-board-model-tool"
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?
Usable slice
Main can create profiles, submit authorized work and inspect durable results through plugin_worker_tasks. Uses existing board and dispatcher; no scheduler/backend added. Explicit /worker-tasks stays available for operator inspection.
Model submissions inherit the current parent mandate through Dispatcher.submit; only explicit operator commands create their own mandate. Nested-worker and host-result guards preserved; nonempty explicit tool selections include the new tool.
Evidence
Independent substantive review: PASS, no P0/P1. Exact patch SHA256 1a9c152fbee35385ffaaaa2b172a405323173848d391a04dd42188191c489cda. 24 focused tests and typecheck pass; build passes. Real model E2E: natural-language instruction -> Main tool profile+submit -> actual worker read tool -> persisted result -> Main tool status -> visible final result. Isolated process restart retains identical execution UUID/result and exactly one execution. Evidence /home/node/runtime-support/internal-worker-tasks-delivery/model-tool-e2e/. No production activation claimed yet.
Optional P2 direct regression expansion for result-guard/tool-selection wiring. Unrelated review cache preserved, not claimed as coverage.