forked from bchanot/claude
feat(seo/geo): projected code-only score + 17/20 trajectory, wired into client-handover
- Analyzers (seo/geo): every finding tagged fixable:code|user; mandatory projected axis+global scores (bundle fully applied), honest code ceiling, TRAJECTORY TO 17/20 block (ranked code fixes or ceiling + unlocking user actions) - /seo: §1 carries actual+projected columns + merged trajectory; console shows projected scores + trajectory one-liner - /geo: audit-end deliverables (HUMAN-ACTIONS.md, trajectory in report + console) even in conservative mode — parity with /seo - client-handover: fix loop breaks at code ceiling (score ≥ projected−0.2) instead of burning iterations on user-bound points; STEP 8 gate gains the code-ceiling pass (gap items land verbatim in client doc §5 with expected gains, explicit status in score table); §4 NAP table consumes NAP-KIT.md first; §5 consumes HUMAN-ACTIONS.md first; HANDOVER-ROADMAP splits CODE-BLOQUÉ vs CLIENT-BLOQUÉ
This commit is contained in:
@@ -96,6 +96,20 @@ term). NEVER apply a GATED item before explicit approval.
|
||||
2. Record each applied change in the report change-log section.
|
||||
3. USER ACTIONS from the bundle → report §11 (each with automation-catalog ref).
|
||||
|
||||
### Audit-end deliverables + trajectory (ALWAYS — both modes)
|
||||
|
||||
Same contract as /seo:
|
||||
- The report carries the analyzer's actual AND projected code-only scores
|
||||
plus its `TRAJECTORY TO 17/20` block (ranked code fixes to 17, or the
|
||||
honest code ceiling + the user actions that unlock the rest) — the
|
||||
geo-analyzer spec (STEP 10) makes these mandatory in the envelope.
|
||||
- Regenerate `.claude/audits/HUMAN-ACTIONS.md` from the user actions
|
||||
(checkbox format, one `- [ ]` per action with automation ref + effort)
|
||||
right after the report is written, EVEN in conservative mode — an
|
||||
audit-only run must leave the user immediately actionable.
|
||||
- Console summary includes: actual + projected scores, the trajectory
|
||||
one-liner, and the HUMAN-ACTIONS.md path.
|
||||
|
||||
## Note on integration
|
||||
|
||||
If `.claude/audits/SEO.md` already exists, geo-analyzer merges its findings
|
||||
|
||||
Reference in New Issue
Block a user