feat(workflow): config-driven status labels with query response support

[jpicklyk]

Summary

• Add StatusLabelService for config-driven trigger-to-label auto-mapping on role transitions (start→"in-progress", complete→"done", block→"blocked", cancel→"cancelled", cascade→"done")
• Labels configurable via .taskorchestrator/config.yaml status_labels section with hardcoded defaults as fallback
• Wire label resolution into AdvanceItemTool and CompleteTreeTool, including cascade events
• Surface statusLabel in all QueryItemsTool response formats (get, search, overview) via toMinimalJson and toFullJson serializers
• Label precedence: hardcoded resolution (cancel/reopen) > config-driven > null

New Files

File	Purpose
StatusLabelService.kt	Interface + NoOpStatusLabelService with hardcoded defaults
YamlStatusLabelService.kt	YAML-backed implementation reading from config with AGENT_CONFIG_DIR support
TestStatusLabelService.kt	Test double with configurable label map
YamlStatusLabelServiceTest.kt	11 unit tests covering config parsing, defaults, edge cases

Modified Files

File	Change
ToolExecutionContext.kt	Add statusLabelService parameter with default
CurrentMcpServer.kt	Construct and wire YamlStatusLabelService
AdvanceItemTool.kt	Resolve config label, compute effectiveLabel, apply to transitions + cascades
CompleteTreeTool.kt	Same effectiveLabel pattern for batch completion
QueryItemsTool.kt	Add statusLabel to global overview root items and children
EntityJsonSerializers.kt	Add statusLabel to toMinimalJson() and toFullJson()
workflow-guide.md	New "Status Labels" documentation section
api-reference.md	Document statusLabel in response schemas
workflow-orchestrator.md	Enforce explicit model parameter in delegation table
implement/SKILL.md	Add model selection table for agent dispatches

Test Results

23 new tests added across 4 files, all passing:

Test File	New Tests	Coverage
YamlStatusLabelServiceTest	11	Config parsing, defaults, partial overrides, coexistence, edge cases
AdvanceItemToolTest	6	Config-driven labels, cascade statusLabel, cascade custom label, cancel precedence, reopen config, block/resume
CompleteTreeToolTest	2	Config-driven labels, cancel precedence
QueryItemsToolTest	4	get non-null/null, includeAncestors behavior, minimal JSON key-absence

Full test suite: BUILD SUCCESSFUL (all existing tests unaffected)

Config Example

# .taskorchestrator/config.yaml
status_labels:
  start: "in-progress"
  complete: "done"
  block: "blocked"
  cancel: "cancelled"
  cascade: "done"
  # resume: null  (inherits pre-block label)
  # reopen: null  (clears label)

MCP Items

• ddbe1829 — Custom status labels feature (parent)
• 85321ddd — Status Labels test coverage gaps
• 4c85f0dc — Model enforcement improvement proposal

🤖 Generated with Claude Code