fix(cli): assign-schedule-type dispatch at top level #8
Reference in New Issue
Block a user
Delete Branch "fix/assign-schedule-type-dispatch"
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?
Summary
hf assign-schedule-typefailing withunknown assign-schedule-type subcommand: <agent-id>.assign-schedule-typeis registered as a Group in CommandSurface(), so the default branch of main()'s switch routes it through handleGroup, which treatsargs[0](the agent-id) as a subcommand. Since this group has no subcommands, findSubCommand returns ok=false and the run aborts.Test plan
hf assign-schedule-type analyst1 standard→ "unknown assign-schedule-type subcommand: analyst1"hf assign-schedule-type analyst1 standardreturns "Assigned schedule type 'standard' to agent 'analyst1'"Surfaced during recruitment workflow Step 5 on prod-t2 (sherlock/agent-resource-director).
`assign-schedule-type` is registered in CommandSurface() as a Group, so the default branch of main()'s switch picks it up via findGroup() and hands it to handleGroup. handleGroup then treats args[0] (the agent-id) as a subcommand name, fails findSubCommand, and errors: unknown assign-schedule-type subcommand: <agent-id> The group has no subcommands — it's a leaf — so the call never reaches handleAssignScheduleType. Add an explicit top-level case before the default branch so the leaf bypasses the group dispatcher. Pre-fix repro: $ AGENT_ID=ard hf assign-schedule-type analyst1 standard unknown assign-schedule-type subcommand: analyst1 Post-fix: $ AGENT_ID=ard CLAW_IDENTIFIER=server-t2 hf assign-schedule-type analyst1 standard Assigned schedule type 'standard' to agent 'analyst1' Surfaced during recruitment workflow Step 5 on prod (sherlock/agent-resource-director).