fix: align child tool exposure with parent-owned continuation #253

Merged
akira merged 1 commit from akira/hayate-agent-core:fix/worker-continuation-contract into main 2026-11-04 15:55:12 +00:00
Collaborator

Worker/subagent-specific outcome contract replaces parent continuation instructions; shared denied-tool list drives PI excludeTools, capabilities and guards. Parent toolset unchanged. 5/5 real PI-adapter/Harness integration tests pass, typecheck pass. Independent functional+changeset review37bfb noP0/P1; resume/subagent-specific tests optional followups. Live fleet activation still required; this does not claim all worker stalls fixed. Existing release CI gates preserved.

Worker/subagent-specific outcome contract replaces parent continuation instructions; shared denied-tool list drives PI excludeTools, capabilities and guards. Parent toolset unchanged. 5/5 real PI-adapter/Harness integration tests pass, typecheck pass. Independent functional+changeset review37bfb noP0/P1; resume/subagent-specific tests optional followups. Live fleet activation still required; this does not claim all worker stalls fixed. Existing release CI gates preserved.
Workers and subagents were advertised plugin_task_continuation (and, for
dispatcher workers, delegation/loop tools) plus continuation instructions,
while the host guard denied every call with worker_orchestration_denied.
Live evidence: 13 such denials in recent child sessions (10x
plugin_task_continuation, 3x plugin_dispatch).

One list now drives both enforcement and exposure: the PI session excludes
denied tools for child sessions (default and explicit tool selections,
across reload), capability facts report them unexposed, and child turns get
a worker outcome contract instead of continuation allowance/scope. The guard
still denies manual calls. Parent continuation, validation, budgets and
delegation restrictions are unchanged.
akira merged commit 0815b55bac into main 2026-11-04 15:55:12 +00:00
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!253
No description provided.