Description
SKT-0011 scenario H2 reproduced the missing-token and unsafe-exposure remedies, but the remaining documented symptoms could not be exercised end to end from the clean environment. New users have prose remedies without a maintained way to prove each symptom and recovery path.
Acceptance Criteria
- #1 Every troubleshooting symptom has a reproducible precondition, action, expected diagnostic, remedy, and post-remedy assertion
- #2 The matrix distinguishes local startup success from live delivery recovery
- #3 A maintained check exercises all non-destructive remedies from a clean environment
- #4 Symptoms requiring unavailable external products are explicitly marked with their prerequisite rather than silently skipped
Definition of Done
- #1 just check </dev/null (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen </dev/null (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump </dev/null — inventory diffed against signals/
Implementation Plan
Lane E converts every troubleshooting symptom to a five-part executable row and validates all non-destructive remedies.
Implementation Notes
2026-08-30 closeout: troubleshooting-check executed all ten local symptom rows successfully and emitted explicit BLOCKED_EXTERNAL dispositions for all eight product-dependent lanes; final just check exited 0.
Final Summary
Troubleshooting is now a maintained executable matrix with local-versus-live proof boundaries and explicit external prerequisites.