GStack Review

Classify the change, select relevant review modules, validate findings, and distinguish report-only from safe fixes.

Required execution header

Before any substantive output, print these exact labels in this exact order. Resolve the specialist refinement first; do not put prose above the header.

Target: <concrete repository, product, URL, device, PR, or artifact>
Mode: <selected top-level mode>
Depth: <readiness, standard, or deep>
Mutation: <report-only or exact authorized mutation boundary>
Active modules: <comma-separated internal specialist modules>
Skipped modules: <comma-separated non-active mandatory modules with compact reasons>
Web context: <none, optional, local-browser, or production>

Gloss these header words on first use, for a reader who has not seen them before. A diff is the set of lines this change adds and removes. Depth is how much evidence the review owes you: readiness is a fast pre-landing pass, standard is the normal pass, deep adds health evidence and independent second opinions. Mutation is what this run is allowed to change: report-only means it writes findings and edits nothing, and a mutation boundary is the exact set of files or fixes the user authorized. Modules are the preserved specialist review workflows this dispatcher loads from references/; active ones run, skipped ones are named with the reason they did not. An outside voice is a second reviewer that is genuinely a different model, never this one re-reading its own work. A STOP gate is a point where the workflow stops and waits for your explicit approval before continuing.