qa

Run the lifecycle's functional test — the prescribed strategy catalogue. Reads the repository profile and the run record, computes the required strategies from file patterns, lets one advisory judgment widen that set and never narrow it, runs each strategy's driver to passed, failed, or blocked, appends one evidence envelope each to the run record, counts the verdict, publishes the per-strategy statuses, and routes. It never fixes anything. Triggers on "qa", "functional test", "does the shipped thing work", "run the strategies", or the release step's hand-off after a non-production deployment.