phase-5-validator

The phase-5-validator is a critical automation utility designed to serve as the final quality gate before a software development workflow concludes. Targeted at lead developers, devops engineers, and automated agents, it ensures that all project artifacts meet established organizational standards. By executing a series of programmatic checks, the tool prevents incomplete documentation, uncommitted code, or unaddressed technical debt from entering the production handoff stage. It functions as a blocking authority, meaning that any violation of its mandatory checklists will prevent the workflow from being marked as complete.

• Performs a mandatory Single Source of Truth validation to ensure no bash, procedural, or automation duplication across skills and documents.

• Enforces strict file size constraints on lessons learned documentation to maintain repository health and prevent technical debt accumulation.

• Validates version control integrity, checking for uncommitted git changes, commit message standards, branch synchronization, and the absence of merge conflicts.

• Audits documentation completeness, ensuring the file registry is updated, PROGRESS.md is current, feature documentation is exhaustive, and CLAUDE.md is maintained.

• Verifies deployment readiness by checking for passing test suites, the absence of blocking issues, and the presence of deployment notes.

• Automates repository cleanup by identifying temporary files, session work directories, and orphaned project assets.

• Exit Code 0 indicates a successful finalization, while Exit Code 1 signals blocking violations or quality gate failure.

• Mandatory for all feature development cycles to ensure vertical slice architecture compliance and documentation parity.

• When a validation fails, the agent must inspect the logs, resolve the specific blocking violation (e.g., file size, uncommitted changes), and re-run the validator.

• Integrates directly with the WitchCityRope agent ecosystem to provide consistent, repeatable outcomes across all development phases.

• Requires developers to maintain a file registry, update deployment notes, and adhere to standard commit formatting for automated validation success.