feat(graphify): threshold signal from 200 tracked code files, the banner informs and the user decides

lib/graphify-gate.sh counts tracked code files (graphify's AST extension set, vendored trees excluded) and, from 200 with no graphify-out/graph.json, prints one banner-sized line; session-start shows it with the /graphify hint. Nothing is built, installed or updated: the rule is the user's (BDR-097), grounded in the LRN-162 measurements (AST build 2.3 s, 0 tokens, a query 2 to 3k tokens). Doctrine section and plugin-advisor thresholds follow the same rule; graphify claude install stays rejected. Test: 11 checks. GRAPHIFY_MIN_CODE_FILES overrides the threshold.
This commit is contained in:
bastien
2026-09-24 12:12:16 +02:00
parent 76ad5bb8d5
commit c81b1731af
6 changed files with 127 additions and 4 deletions
+2 -2
View File
@@ -79,9 +79,9 @@ Factors (weighted):
**Score thresholds:**
- **0-30% (simple)**: superpowers only. No gstack, no gsd, no ctx7, no graphify.
_Examples: site vitrine, landing page, script CLI, simple CRUD._
- **30-60% (moderate)**: + context7 if fast-libs, + graphify after implementation.
- **30-60% (moderate)**: + context7 if fast-libs. graphify only once the codebase passes 200 tracked code files (session-start banner informs, the user decides — BDR-097), never at scaffold.
_Examples: blog with auth, dashboard with charts, API with validation._
- **60-85% (complex)**: + gstack if browser-QA, + gsd if multi-session, + graphify both passes.
- **60-85% (complex)**: + gstack if browser-QA, + gsd if multi-session. graphify: same 200-file rule, likely reached — say so, do not pre-enable.
_Examples: SaaS with billing, game with social features, e-commerce._
- **85-100% (enterprise)**: all tools justified.
_Examples: multi-service platform, real-time collab app, marketplace._