[v1 readiness][legolas] FIT tracker and v1 scope reconciliation

[JeremyDev87]

[v1 readiness][legolas] FIT tracker and v1 scope reconciliation

Goal

Reconcile stale local FIT tracker references with live GitHub state and define what is truly blocking v1.0.0.

Source of Truth

• Parent epic: [v1 readiness] Legolas release gate epic (no version bump) #109
• Repo: JeremyDev87/legolas
• Parent implementation plan artifact: /Users/pjw/.hermes/thread-workcells/discord/282499436049858561/1508085811139051580/TASKS/v1-ddplan-issues/IMPLEMENTATION_PLAN.md
• Version bump, tag, publish, CI dispatch, branch, commit, and PR creation are out of scope for this issue.

Wiki Context Manifest

• Queries attempted: frontend evidence gates release evidence contract, code is not cheap AI maintenance cost ratio, alex core invariants SSoT No Silent Fallback idempotency, 12-factor agents runtime contract event log release workflow, overeager coding agents task scope destructive action, prompt assets skill issue planning evidence
• Wiki sources read: [wiki: frontend/evidence-gates.md], [wiki: principles/code-is-not-cheap.md], [wiki: principles/alex-core-invariants.md], [wiki: harness-engineering/12-factor-agents-runtime-contract.md], [wiki: harness-engineering/overeager-coding-agents-scope-contract.md], [wiki: harness-engineering/prompt-assets.md], [wiki: raw/2026-05-24-ai-maintenance-cost-ratio-source-map.md]
• Relevant wiki facts: v1 readiness requires artifact/runtime/evidence bundles, not only test-green; release and wrapper flows must preserve SSoT, atomicity, idempotency, and No Silent Fallback; destructive or fix-like commands need task-scope/evidence gates; AI-generated velocity must lower future maintenance cost rather than add broad v1 scope.
• remember-wiki applicability / skip reason: skipped; target repos are JeremyDev87/* personal CLI repos, not Remember/dramancompany repos.
• Non-wiki inference: repo-specific split below is based on live local repo docs/config/workflows and npm registry checks performed before issue creation.

Quality Lens Router Output

• Applicable gate families:
  • evidence-contract: v1 readiness, package install, CLI output, release/publish, and fallback claims need concrete proof.
  • simplicity-deletability: v1 work must prefer contract/evidence gaps over broad new features or nonessential abstractions.
  • tdd-systematic-debugging: false-positive, fallback, exit-code, and packaging regressions should be fixture/test-backed.
• Skipped gates:
  • frontend-design: not-applicable; CLI/runtime/docs work only.
  • vercel-agent-skills: not-applicable; no React/Next/Vercel/mobile surface.
  • deploy-token-safety: limited; no token/deploy mutation in this issue, only release credential evidence requirements.

Evidence Contract

• Required evidence:
  • Candidate SHA/version alignment evidence when a candidate is selected.
  • Repo test evidence plus source CLI smoke.
  • npm pack / packed-install evidence for the user-consumed artifact.
  • Release workflow/check/dist-tag/GitHub Release evidence where release automation is touched.
  • Explicit fallback/unsupported-platform evidence where wrapper/native-runtime selection is touched.
• Evidence not applicable:
  • Browser screenshot/DOM: not-applicable, CLI repos.
  • Production URL: not-applicable, npm/GitHub release surface only.
• Blocking evidence gaps:
  • Final v1 version bump/tag is intentionally out of scope for this issue set.

Owned files / likely touched areas

• TODO.md
• docs/plan/FIT-INDEX.md
• docs/plan/FIT-ISSUE-EXECUTION.md
• docs/plan/**

Inspect-only files

• README*.md
• CONTRIBUTING.md
• .github/workflows/**
• package.json

Must not touch

• close historical issues without separate live evidence
• version bump/tag/publish

Implementation steps

1. Compare TODO/FIT docs against live issue/PR state.
2. Mark each referenced FIT slice as done/deferred/v1 blocker/unknown.
3. Create or update tracked docs so future work does not rely on stale issue numbers.
4. Record v1 non-goals explicitly.

Parallelization note

Not parallel with other docs-plan edits; unblocks L2-L5 scope clarity.

Dependencies / blocked by

Parent only; should happen first.

Validation / evidence required

• git diff --check
• npm run test:release-contract if docs reference release wiring
• manual live issue/PR evidence list in PR body

Completion criteria

• Required validation evidence is pasted into the PR body or final issue comment.
• No v1 version bump/tag/publish is performed.
• If any required evidence is unavailable, the issue remains open with the gap classified as Medium/High rather than being marked complete.

[JeremyDev87]

구현 계획 (ddalggak plan)

라이브 증거를 먼저 확인했습니다.

• [v1 readiness][legolas] FIT tracker and v1 scope reconciliation #110: OPEN, label chore, assignee JeremyDev87, 댓글 없음.
• [v1 readiness] Legolas release gate epic (no version bump) #109 parent epic: OPEN, L1~L5 matrix에서 #110이 선행 scope reconciliation으로 지정됨.
• open PR: 없음 (gh pr list --state open = []).
• 과거 FIT 이슈 PR-FIT-013B: workspace summaries를 scan/budget/ci output에 반영 #44~FIT Phase 10 machine output and fix guidance tracker #53: 현재 모두 CLOSED이며, 대응 PR PR-FIT-013B: workspace summaries를 scan/budget/ci output에 반영 #54~PR-FIT-014B: SARIF 리포터 추가 #62 및 PR-FIT-FINAL: product-fit verification gate 실행 #51 final gate가 merge/close된 상태로 확인됨.
• 현재 로컬 문서: TODO.md, docs/plan/FIT-INDEX.md, docs/plan/FIT-ISSUE-EXECUTION.md가 아직 2026-04-24 시점의 열린 FIT lane/frontier를 active처럼 참조함.

작업 범위

1. TODO.md를 GitHub + v1 readiness docs로 재지정하고, PR-FIT-013B: workspace summaries를 scan/budget/ci output에 반영 #44~#53은 historical FIT archive로 내려 active tracker에서 제거합니다.
2. docs/plan/FIT-INDEX.md를 current frontier가 아니라 completed FIT archive + v1 readiness handoff 문서로 갱신합니다.
3. docs/plan/FIT-ISSUE-EXECUTION.md에 live reconciliation snapshot과 [v1 readiness][legolas] FIT tracker and v1 scope reconciliation #110~[v1 readiness][legolas] Release workflow evidence and docs parity #114 v1 child issue matrix를 추가/정리합니다.
4. 필요 시 docs/plan/ 아래에 v1 scope reconciliation artifact를 추가해, v1 blocker/deferred/non-goal을 이후 issue들이 재사용하게 합니다.

제외

• historical issue close/reopen 없음
• version bump/tag/publish 없음
• README/CONTRIBUTING/workflow/package.json은 inspect-only 유지

검증

• git diff --check
• release wiring을 문서에서 참조하므로 npm run test:release-contract도 실행합니다.