fix(triage): exempt archived/dormant repos from context-quality flag (context 24→10)#37
Merged
Merged
Conversation
Context quality is a 'can someone resume this?' signal — meaningless for repos
that are intentionally not under active development. The context failure mode
fired purely on derived.context_quality with no lifecycle awareness, so every
archived GPT-built SaaS throwaway and parked tool nagged as context-weak.
Gate FailureMode.CONTEXT behind lifecycle_state not in {archived, dormant}.
Repos with no declared lifecycle still flag (enforce by default); active and
maintenance repos keep flagging. Triage drops 24 -> 10 flagged, leaving only
living repos (9 active + 1 maintenance) that genuinely need context work.
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.
Pile 1 of the context-quality triage cleanup (Arc A). The
contextfailure mode fired purely onderived.context_quality ∈ {none, boilerplate}with no lifecycle awareness — so every archived GPT-built SaaS throwaway and parked tool nagged as context-weak, even though resume-readiness is irrelevant for repos that aren't under active development. Same noise-class we just fixed for the catalog flag.Change
Gate
FailureMode.CONTEXTbehindlifecycle_state not in {archived, dormant}:Result
Triage drops 24 → 10 flagged. The 14 cleared are all archived (12) or dormant (2). The remaining 10 are the genuinely-living repos (9 active + LoreKeeper/maintenance) that actually need context work:
BattleGrid, GithubRepoAuditor, Grotto, LegalDocsReview, LoreKeeper, TabTriage, asc-radar, cost-tracker, portfolio-health, rag-knowledge-baseGate
test_portfolio_context_triage.pycovering archived/dormant suppression + active/maintenance/missing-lifecycle regression guardsruff check .clean; full suite 2200 passed, 2 skippedFollow-up (Pile 2): the 10 living repos lack the structured sections (current-state / how-to-run / known-risks / next-move). Open question whether to tune the analyzer's section detection or write the sections per-repo — tracked separately.