orchestration-qa

Workspace orchestration validation checks agent routing and skill references across .github directories. It enforces governance rules, verifies metadata consistency, and detects structural breakage to prevent silent misconfigurations in your control-plane.

Orchestration QA validates workspace control-plane configurations across agents, skills, MCP, hooks, instructions, and context artifacts. It detects structural breakage, stale paths, and doctrine drift while generating a structured QA report with severity scoring to guide remediation.

To detect stale paths and doctrine drift in orchestration hooks, validate the .github/hooks and .github/context directories. The QA process identifies script and artifact mismatches, ensuring your orchestration layer maintains end-to-end consistency and correct agent routing.

Yes, you can use orchestration validation to enforce model naming and canonical path consistency. It checks configurations across .github/bin, .github/context, and related artifacts, verifying that all references align with documented governance rules and metadata standards.

Run workspace orchestration validation checks after making changes to any orchestration-related files, including agents, skills, MCP, hooks, or instructions. This verifies end-to-end consistency and catches structural breakage or legacy trace cleanup issues before they cause silent failures.

The best way to clean up legacy traces in a GitHub agents registry is to run a comprehensive orchestration QA validation. It identifies stale paths, detects doctrine drift, and generates a severity-scored report to guide your remediation of the AGENTS registry and related artifacts.