Summary
.claude/hooks/validate-orchestrator-output.ps1 delegates its routing-contract
validation to a Python module that does not exist in this repository. The hook's
default invoker runs:
python -m scripts.dev_tools.validate_orchestration_artifacts \
<ArtifactType> <CheckpointPath> --require-complete --require-model-routing
There is no scripts/dev_tools/ directory in TaskMaster. scripts/ contains only
dev-tools/, vscode/, and temp-extract-coverage.ps1. A repository-wide search for
validate_orchestrator_state* returns no results.
Environment
(not provided in potential file)
Steps to Reproduce
(not provided in potential file)
Expected Behavior
One of:
- The Python validator modules are vendored into TaskMaster so the hook's default
invoker resolves; or
- The hook's default invoker is repointed at the MCP-backed validator that this
repository actually ships; or
- The hook fails open with a clear diagnostic when the validator is unavailable,
rather than reporting a routing-contract failure it did not evaluate.
In every case the rule files should cite the enforcement mechanism that exists in this
repository rather than paths inherited from the reference repository.
Actual Behavior
(not provided in potential file)
Logs / Screenshots
(not provided in potential file)
Impact / Severity
(not provided in potential file)
Source
From: docs/features/potential/2026-08-14-orchestrator-hooks-reference-absent-python-validators.md
Summary
.claude/hooks/validate-orchestrator-output.ps1delegates its routing-contractvalidation to a Python module that does not exist in this repository. The hook's
default invoker runs:
There is no
scripts/dev_tools/directory in TaskMaster.scripts/contains onlydev-tools/,vscode/, andtemp-extract-coverage.ps1. A repository-wide search forvalidate_orchestrator_state*returns no results.Environment
(not provided in potential file)
Steps to Reproduce
(not provided in potential file)
Expected Behavior
One of:
invoker resolves; or
repository actually ships; or
rather than reporting a routing-contract failure it did not evaluate.
In every case the rule files should cite the enforcement mechanism that exists in this
repository rather than paths inherited from the reference repository.
Actual Behavior
(not provided in potential file)
Logs / Screenshots
(not provided in potential file)
Impact / Severity
(not provided in potential file)
Source
From: docs/features/potential/2026-08-14-orchestrator-hooks-reference-absent-python-validators.md