discover: add Repairability verdict + blockers/gaps split; repair refuses not-repairable#19
Merged
Conversation
…uses not-repairable DISCOVERY.md previously had no way to say 'this can't be repaired because it was never built' — only blocker severity. Now: - discover emits a top-of-file Repairability verdict (repairable | partially-runnable | not-repairable) and splits fixable blockers from never-built gaps; gaps never become DoD checkboxes - repair gains a second refusal: it stops on not-repairable, keeps gaps out of scope on partially-runnable, and treats a missing verdict field (pre-existing DISCOVERY.md files) as repairable - README + OVERVIEW updated to match Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CognitiveCodeAI
added a commit
that referenced
this pull request
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Closes the structural hole found in the 2026-06-07 review (and listed as "designed but not built" in the v0.4.0 release notes):
discoverhad no way to express outcome #3 — "not repairable, because it was never built." It could only rank blockers by severity, so a half-finished app produced a plan that quietly turned repair into feature development.Changes
discover(SKILL.md):DISCOVERY.mdnow opens with a## Repairability verdict:repairable | partially-runnable | not-repairable, with a one-sentence evidence-cited justification and confidence tag.## Blockers preventing local startupis restricted to fixable defects; a new## Gaps (never built)section holds referenced-but-unimplemented functionality (stub bodies, imports of nonexistent modules, README features with no code).partially-runnable/not-repairable, not a reason to add "implement X" to the plan.repairableto be agreeable).repair(SKILL.md):not-repairable, stop and present the real options (re-scope discovery to what exists, or commission the missing pieces as deliberate feature work).partially-runnable: proceed, but the Gaps list stays out of scope — never quietly build a gap.DISCOVERY.mdwith no verdict field (predates this change) is treated asrepairable, noted inVERIFICATION_REPORT.md.Docs: one-line updates to the README command table and
docs/OVERVIEW.mdworkflow descriptions.Not in scope
Routing discover's gaps onward (a future router, or
auditingesting them) stays a separate, deliberately-unbuilt problem perdocs/PROPOSAL_audit-repair.md— this PR only makes the gap visible and load-bearing inside the discover → repair line.Verification
claude plugin validate ./plugins/lazaruspasses (only the expected no-version warning)🤖 Generated with Claude Code