Kit review backlog

Open findings from kit-value-and-model-agnostic-review.md (refreshed 2026-09-01). Track work here; mark items done with a PR reference.

P0: honesty / prove-what-you-claim

No open P0 items. R1 (rename) and R2 (host writers, not Cursor-only copy) are in Done below. Remaining skill-trigger work is asserting required_patterns (product, not copy).

P1: eval / CI proof

IDFindingProposed actionStatus
R3Merge gate is scripted-only; nightly live skips without wk _EVAL_API_KEYKeep scripted as default; document required secrets for live; fail a scheduled job loudly when CURSOR_API_KEY is missing; workflow_dispatch may skip with allow_unkeyed_skipDone (PR #107)
R4Live client is OpenAI-compatible only; ANTHROPIC_API_KEY as bearer is easy to misconfigureDocument gateways honestly; consider native Anthropic/Gemini adapters only if demand appearsOpen

P2: maintainability / adoption

IDFindingProposed actionStatus
R6Several lang-* / framework-* skills are short checklists (~38–48 lines)Cut unused profiles or deepen with evals + concrete anti-patterns (see lang-typescript direction)Open

Done since Aug 30 draft (do not reopen without new evidence)

IDFindingResolution
D1Architecture stack felt non-optional / blocks adoptionApplicability & opt-out + seed ADRs (#36)
D2EDD closed-loop entirely aspirationalSuites/depth (#23), shadow/OTel path (#28–#30), skill coverage (#31), nightly live workflow
R1“Live trigger” language for a non-model skill-registration checkRenamed CLI help + harness banner to skill-trigger / prompt hygiene. Harness still ignores required_patterns.
R2Multi-IDE peer-depth oversoldMCP/model/rules writers for Cursor, Claude, Copilot, Antigravity; Windsurf is rules-only forever (docs/hosts.md).
R5Role skills over ~150-line kit-review budgetVerify gate remains. agent-copy / agent-debug / agent-prune / agent-orchestrator thinned via SOPs + references/ (2026-09-06). Allowlist empty.
R7Full lifecycle ceremony is heavy for day-to-day codingMinimal path on start, jobs, wk help, and kit commands: debug + light XFN vs feature lifecycle.

How to use

  • Prefer small PRs that close one ID.
  • Link the ID in the PR body (Closes review backlog R1).
  • When closing an item, set Status to Done (PR #N) and leave one line of evidence.

Markdown source