procedure-cli 0.1.13 → 0.1.15

package/CODE-REVIEW.md

@@ -1,558 +0,0 @@
-# Code Review Log
-
-## Writing Standard
-- Language: English only.
-- Tone: Technical, concise, objective, and evidence-based.
-- Ordering: Findings listed by severity (`High`, `Medium`, `Low`).
-- Evidence: Every finding includes at least one concrete file reference (`path:line`).
-- Actionability: Every finding includes a clear recommendation.
-- Validation: Verification notes must be based on actual checks (inspection and/or command output).
-- Lifecycle: Each finding includes `Status`: `New`, `Still Open`, `Fixed`, `Regressed`, or `Not Reproducible`.
-
-### Entry ID Convention
-- Required field for every entry: `Entry ID`
-- Format: `CR-YYYYMMDD-###`
-- Example: `CR-20260221-001`
-
----
-
-## Entry 2026-02-21
-
-### Entry ID
-- `CR-20260221-001`
-
-### Scope
-- Full review of current `procedure` CLI codebase.
-- Focus areas: scaffolding safety, setup reliability, output integrity, and runtime checks.
-
-### Findings (ordered by severity)
-
-1. High - Powerline setup writes config to project-local path but references home-directory config (`Status: New`)
-- `src/lib/powerline.ts:29`
-- `src/lib/powerline.ts:41`
-- `settings.json` is configured with `--config=~/.claude/powerline-config.json`, but setup copies config to `<targetDir>/.claude/powerline-config.json`.
-- This creates a path mismatch: generated config may not be the file that the configured command reads.
-- Recommendation: align both paths. Either copy config to `~/.claude/powerline-config.json` or point the status-line command at `<targetDir>/.claude/powerline-config.json`.
-
-2. Medium - Git bootstrap can fail on machines without global git identity (`Status: New`)
-- `src/lib/git.ts:8`
-- `initGit()` runs `git commit` unconditionally; this fails when `user.name`/`user.email` are not configured.
-- Recommendation: pre-check git identity and show a guided fallback, or skip initial commit when identity is missing.
-
-3. Medium - `settings.json` parsing is not resilient to malformed existing config (`Status: New`)
-- `src/lib/powerline.ts:22`
-- `src/lib/powerline.ts:23`
-- Existing `.claude/settings.json` is parsed without `try/catch`; malformed JSON aborts setup.
-- Recommendation: wrap JSON parse in defensive handling (fallback to empty object + warning message).
-
-4. Medium - Generation flow can overwrite existing files without confirmation (`Status: New`)
-- `src/lib/template.ts:23`
-- `src/lib/template.ts:44`
-- `src/steps/generation.tsx:33`
-- Scaffolding writes directly into `process.cwd()` and unconditionally overwrites files such as `README.md`, `CLAUDE.md`, and docs.
-- Recommendation: add collision detection and explicit overwrite confirmation (or backup/skip mode).
-
-5. Low - "Skip generation" path still marks generation step as completed in timeline summary (`Status: New`)
-- `src/steps/generation.tsx:47`
-- `src/app.tsx:82`
-- `src/app.tsx:177`
-- Canceling generation advances the wizard, and summary still reports `"files generated"`, which can be inaccurate.
-- Recommendation: track generation result explicitly (`generated: true/false`) and render truthful summary text.
-
-6. Low - Generated `USER-STORIES.md` can be nearly empty in normal flow (`Status: New`)
-- `src/steps/product-context.tsx:80`
-- `templates/docs/USER-STORIES.md.hbs:3`
-- Wizard currently sets `userStories: []` with no later collection step, so output often contains only title/header.
-- Recommendation: either collect at least one story in wizard flow or generate a starter template section when `userStories` is empty.
-
-### Verification Notes
-- `npm run lint`: pass (`tsc --noEmit`).
-- `npm run build`: pass (`tsc`).
-- Runtime checks performed in temp directories with compiled modules:
-- `setupPowerline()` writes `.claude/powerline-config.json` but status command references `~/.claude/powerline-config.json`.
-- `setupPowerline()` throws on malformed `.claude/settings.json` (`SyntaxError`).
-- `initGit()` failed at `git commit` in environment without configured identity.
-- `scaffoldAll()` overwrote pre-existing `README.md` content.
-- `scaffoldAll()` with default wizard-shaped payload produced a mostly empty `docs/USER-STORIES.md` (`# demo — User Stories` only).
-
-### Residual Risks / Testing Gaps
-- No automated tests for overwrite-protection behavior in generation flow.
-- No automated tests for malformed `.claude/settings.json` handling.
-- No automated tests for `initGit()` behavior across machines with missing git identity.
-- No tests asserting generation summary truthfulness when user cancels.
-
----
-
-## Entry 2026-02-21
-
-### Entry ID
-- `CR-20260221-002`
-
-### Supersedes
-- `CR-20260221-001`
-
-### Scope
-- Validate `CR-20260221-001` findings against current code.
-- Perform a fresh review pass for post-fix regressions and remaining issues.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 1 | High | Fixed | `src/lib/powerline.ts:34`, `src/lib/powerline.ts:46` | Status-line command now points to project-local `.claude/powerline-config.json`, matching copied destination. |
-| 2 | Medium | Fixed | `src/lib/git.ts:13`, `src/lib/git.ts:19`, `src/lib/git.ts:27` | `initGit()` now checks identity and can return `{ committed: false, reason }` instead of failing immediately for missing identity. |
-| 3 | Medium | Fixed | `src/lib/powerline.ts:22`, `src/lib/powerline.ts:25` | Existing `settings.json` parse is wrapped in `try/catch`; malformed JSON no longer aborts setup. |
-| 4 | Medium | Fixed | `src/lib/template.ts:38`, `src/steps/generation.tsx:61`, `src/steps/generation.tsx:108` | Generation step now detects collisions and explicitly warns users before proceeding. |
-| 5 | Low | Fixed | `src/steps/generation.tsx:48`, `src/app.tsx:84` | Generation skip state is tracked and reflected in step summary (`"skipped"`). |
-| 6 | Low | Still Open | `src/steps/product-context.tsx:80`, `templates/docs/USER-STORIES.md.hbs:3` | `userStories` remains hardcoded to empty with no collection step. |
-
-### Findings (ordered by severity)
-1. Medium - Git init flow can hard-fail when Generation is skipped in an empty directory (`Finding #7`, `Status: New`)
-- `src/lib/git.ts:26`
-- `src/steps/powerline.tsx:47`
-- `initGit()` always attempts a commit. If no files exist (e.g., user skips generation in an empty folder), `git commit` fails and Powerline step enters unrecoverable error state.
-- Recommendation: allow empty initial commit (`--allow-empty`) or skip commit when index is empty while still completing setup.
-
-2. Low - Final completion message can be misleading when Generation was skipped (`Finding #8`, `Status: New`)
-- `src/app.tsx:134`
-- `src/app.tsx:137`
-- Completion text always says project "has been scaffolded" and prompts to check generated docs, even when step 6 was skipped.
-- Recommendation: gate final message content on `generationSkipped` and show a neutral completion message for skip flow.
-
-3. Low - Generated `USER-STORIES.md` can still be nearly empty (`Finding #6`, `Status: Still Open`)
-- `src/steps/product-context.tsx:80`
-- `templates/docs/USER-STORIES.md.hbs:3`
-- Wizard still outputs `userStories: []`, so file may contain only title/header.
-- Recommendation: collect user stories during wizard flow or render a starter section/template when array is empty.
-
-### Verification Notes
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Runtime probes:
-- `setupPowerline()` now writes a status command using `--config=.claude/powerline-config.json` and succeeds with malformed existing settings (parse fallback observed).
-- `initGit()` succeeds when files exist; still fails on empty repo commit path.
-
-### Residual Risks / Testing Gaps
-- No automated test for `initGit()` empty-index behavior.
-- No integration test for skip-generation + git-init flow.
-- No automated test asserting end-screen messaging for `generationSkipped`.
-
----
-
-## Entry 2026-02-21
-
-### Entry ID
-- `CR-20260221-003`
-
-### Supersedes
-- `CR-20260221-002`
-
-### Scope
-- Validate `CR-20260221-002` findings against current code.
-- Perform a new post-fix review pass for regressions and unresolved issues.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 7 | Medium | Fixed | `src/lib/git.ts:28`, `src/lib/git.ts:29` | Empty-index case is now handled; commit is skipped with a structured reason. |
-| 8 | Low | Fixed | `src/app.tsx:133`, `src/app.tsx:134`, `src/app.tsx:137` | Final completion messaging now reflects `generationSkipped`. |
-| 6 | Low | Still Open | `src/steps/product-context.tsx:80`, `templates/docs/USER-STORIES.md.hbs:3` | User stories are still not collected in wizard flow. |
-
-### Findings (ordered by severity)
-1. Low - Powerline step can claim git initialized even when commit was skipped (`Finding #9`, `Status: New`)
-- `src/steps/powerline.tsx:125`
-- `src/steps/powerline.tsx:127`
-- `src/steps/powerline.tsx:130`
-- `src/steps/powerline.tsx:132`
-- UI always shows "Git repository initialized." when user selected git setup (`wantGit === true`), even if `initGit()` returned `committed: false` (e.g., empty directory or missing identity). This creates mixed success/failure messaging.
-- Recommendation: track commit outcome separately (e.g., `gitCommitted`) and render success text only when true; otherwise show warning-only state.
-
-2. Low - Generated `USER-STORIES.md` can still be nearly empty (`Finding #6`, `Status: Still Open`)
-- `src/steps/product-context.tsx:80`
-- `templates/docs/USER-STORIES.md.hbs:3`
-- Wizard still outputs `userStories: []`, so generated file may contain only title/header.
-- Recommendation: collect at least one story in wizard flow or render a fallback starter template when empty.
-
-### Verification Notes
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Runtime probe:
-- `initGit()` in empty directory now returns `{ committed: false, reason: "Nothing to commit — directory is empty." }` instead of throwing.
-
-### Residual Risks / Testing Gaps
-- No UI test covering mixed-result messaging in Powerline step (`wantGit` true + `committed` false).
-- No automated test asserting non-empty/default content for generated `docs/USER-STORIES.md`.
-
----
-
-## Entry 2026-02-21
-
-### Entry ID
-- `CR-20260221-004`
-
-### Supersedes
-- `CR-20260221-003`
-
-### Scope
-- Correct review status drift by reconciling against latest `CODE-FIXED.md`.
-- Run a fresh current-state review after reconciliation.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 6 | Low | Fixed | `CODE-FIXED.md:54`, `templates/docs/USER-STORIES.md.hbs:3`, `templates/docs/USER-STORIES.md.hbs:23` | Previously mis-labeled as open in `CR-20260221-003`; fix existed in `CF-20260222-001` and template fallback is present. |
-| 9 | Low | Still Open | `src/steps/powerline.tsx:125`, `src/steps/powerline.tsx:130` | Success and warning can render together when commit is skipped. |
-
-### Findings (ordered by severity)
-1. Low - Powerline step can claim git initialized even when commit was skipped (`Finding #9`, `Status: Still Open`)
-- `src/steps/powerline.tsx:125`
-- `src/steps/powerline.tsx:127`
-- `src/steps/powerline.tsx:130`
-- `src/steps/powerline.tsx:132`
-- UI always shows "Git repository initialized." when `wantGit` is true, even when `initGit()` reports `{ committed: false, reason }`.
-- Recommendation: track commit outcome (e.g., `gitCommitted`) and render the success line only when a commit actually succeeded.
-
-### Verification Notes
-- Procedure compliance: read latest `CODE-REVIEW.md` and latest `CODE-FIXED.md` before this review.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Runtime probe: scaffolding with empty `userStories` now renders fallback user-story starter content (`fallback-ok`), confirming `Finding #6` is fixed.
-
-### Residual Risks / Testing Gaps
-- No UI test for Powerline mixed-result messaging (`wantGit` true + `committed` false).
-
----
-
-## Entry 2026-02-21
-
-### Entry ID
-- `CR-20260221-005`
-
-### Supersedes
-- `CR-20260221-004`
-
-### Scope
-- Fresh review cycle after `CF-20260222-003`.
-- Validate open findings against latest code and current build/typecheck status.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 9 | Low | Fixed | `CODE-FIXED.md:112`, `src/steps/powerline.tsx:22`, `src/steps/powerline.tsx:127`, `src/steps/powerline.tsx:132` | Powerline now separates success and warning states by commit outcome (`gitCommitted`). |
-| 6 | Low | Fixed | `CODE-FIXED.md:54`, `templates/docs/USER-STORIES.md.hbs:3`, `templates/docs/USER-STORIES.md.hbs:23` | USER-STORIES fallback remains in place for empty `userStories`. |
-
-### Findings (ordered by severity)
-- No new functional findings identified in this review cycle.
-
-### Verification Notes
-- Procedure compliance: read latest `CODE-REVIEW.md` and latest `CODE-FIXED.md` before review.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Code inspection confirms `CF-20260222-003` fix is present in current `src/steps/powerline.tsx`.
-
-### Residual Risks / Testing Gaps
-- No automated UI tests currently cover end-to-end Powerline branching (`gitCommitted` true/false).
-
----
-
-## Entry 2026-02-22
-
-### Entry ID
-- `CR-20260222-001`
-
-### Supersedes
-- `CR-20260221-006`
-
-### Scope
-- New review cycle on current `main` state.
-- Validate latest fixed findings against code and scan for regressions.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 9 | Low | Fixed | `CODE-FIXED.md:112`, `src/steps/powerline.tsx:22`, `src/steps/powerline.tsx:127`, `src/steps/powerline.tsx:132` | Setup UI still correctly separates successful git init from warning states. |
-| 6 | Low | Fixed | `CODE-FIXED.md:54`, `templates/docs/USER-STORIES.md.hbs:3`, `templates/docs/USER-STORIES.md.hbs:23` | USER-STORIES fallback remains intact for empty `userStories`. |
-
-### Findings (ordered by severity)
-- No new functional findings identified in this review cycle.
-
-### Verification Notes
-- Procedure compliance: reviewed latest `CODE-REVIEW.md` and `CODE-FIXED.md` before analysis.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Code inspection confirms latest fix-cycle behavior remains present in current source.
-
-### Residual Risks / Testing Gaps
-- No automated UI test coverage for generation + setup end-to-end branching scenarios.
-
----
-
-## Entry 2026-02-22
-
-### Entry ID
-- `CR-20260222-002`
-
-### Supersedes
-- `CR-20260222-001`
-
-### Scope
-- Review current local code state after latest UI/setup flow changes.
-- Validate previously fixed findings and check for new regressions.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 9 | Low | Fixed | `src/steps/powerline.tsx:127`, `src/steps/powerline.tsx:132` | Mixed success/warning messaging remains resolved. |
-| 6 | Low | Fixed | `templates/docs/USER-STORIES.md.hbs:3`, `templates/docs/USER-STORIES.md.hbs:23` | USER-STORIES fallback remains in place. |
-
-### Findings (ordered by severity)
-1. Low - Setup step summary always implies git initialization even when user declines git setup (`Finding #10`, `Status: New`)
-- `src/app.tsx:88`
-- `src/app.tsx:89`
-- Setup summary currently always includes `"Git init"` for step 7, regardless of user choice in `src/steps/powerline.tsx` (`onCancel` path for git).
-- Recommendation: track git setup choice/result in `WizardAnswers` (e.g., `setupGit: boolean`) and render summary based on actual user selection/outcome.
-
-### Verification Notes
-- Procedure compliance: reviewed latest `CODE-REVIEW.md` and `CODE-FIXED.md` before this cycle.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-
-### Residual Risks / Testing Gaps
-- No UI test coverage for setup summary correctness when user declines git initialization.
-
----
-
-## Entry 2026-02-21
-
-### Entry ID
-- `CR-20260221-006`
-
-### Supersedes
-- `CR-20260221-005`
-
-### Scope
-- New review cycle after latest documented fix entry (`CF-20260222-003`).
-- Validate current status of previously fixed findings and scan for regressions.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 9 | Low | Fixed | `CODE-FIXED.md:112`, `src/steps/powerline.tsx:22`, `src/steps/powerline.tsx:127`, `src/steps/powerline.tsx:132` | Commit outcome is now reflected in UI; mixed success/warning state is resolved. |
-| 6 | Low | Fixed | `CODE-FIXED.md:54`, `templates/docs/USER-STORIES.md.hbs:3`, `templates/docs/USER-STORIES.md.hbs:23` | USER-STORIES fallback remains present and active when story array is empty. |
-
-### Findings (ordered by severity)
-- No new functional findings identified in this review cycle.
-
-### Verification Notes
-- Procedure compliance: read latest `CODE-REVIEW.md` and latest `CODE-FIXED.md` before review.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Code inspection confirms `CF-20260222-003` changes remain present in `src/steps/powerline.tsx`.
-
-### Residual Risks / Testing Gaps
-- No automated UI tests currently cover end-to-end Powerline branching (`gitCommitted` true/false).
-
----
-
-## Entry 2026-02-22
-
-### Entry ID
-- `CR-20260222-003`
-
-### Supersedes
-- `CR-20260222-002`
-
-### Scope
-- Start a new review cycle on current local working tree.
-- Validate latest fix-log state and review recent UI/theme changes for regressions.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 10 | Low | Fixed | `CODE-FIXED.md:136`, `src/lib/types.ts:68`, `src/app.tsx:90`, `src/steps/powerline.tsx:49` | Setup summary now reflects actual git setup choice (`Git init: yes/no`). |
-
-### Findings (ordered by severity)
-1. Low - Theme rule is not fully applied; one `dimColor` usage remains (`Finding #11`, `Status: New`)
-- `src/steps/build-test.tsx:68`
-- Current procedure in `CLAUDE.md` requires using hex values from `src/theme.ts` and avoiding terminal color names/dim variants for consistency. `BuildTest` still renders `(<default>)` with `dimColor`.
-- Recommendation: replace `dimColor` with `color={C.overlay1}` and keep all color rendering sourced from `src/theme.ts`.
-
-### Verification Notes
-- Procedure compliance: read latest `CODE-REVIEW.md` and latest `CODE-FIXED.md` before this review.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Consistency scan: `rg "dimColor|color=\"(cyan|green|red|yellow|blue|magenta|white|black)\"" -n src` reports only `src/steps/build-test.tsx:68`.
-
-### Residual Risks / Testing Gaps
-- No snapshot/UI regression tests currently enforce theme consistency rules across wizard steps.
-
----
-
-## Entry 2026-02-22
-
-### Entry ID
-- `CR-20260222-004`
-
-### Supersedes
-- `CR-20260222-003`
-
-### Scope
-- New review cycle after recent CLI pre-flight and documentation updates.
-- Validate latest fixed findings and check for regressions in runtime behavior.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 11 | Low | Fixed | `CODE-FIXED.md:188`, `src/steps/build-test.tsx:68` | Theme consistency fix remains present (`color={C.overlay1}` in Build & Test default hint). |
-
-### Findings (ordered by severity)
-1. Medium - New empty-directory hard stop regresses overwrite-confirmation flow (`Finding #12`, `Status: New`)
-- `src/cli.tsx:7`
-- `src/cli.tsx:8`
-- `src/steps/generation.tsx:45`
-- `src/steps/generation.tsx:139`
-- `src/lib/template.ts:40`
-- CLI now exits before wizard render when cwd has any entries. This bypasses the existing generation-stage conflict detection and explicit overwrite confirmation (`checkConflicts` + "⚠ Will overwrite"), removing a previously supported safe path for regeneration in non-empty directories.
-- Recommendation: downgrade pre-flight to a warning (not hard exit), or gate strict-empty behavior behind an explicit flag while preserving Step 6 overwrite confirmation.
-
-2. Low - Empty-directory guidance command is inconsistent with repo package metadata (`Finding #13`, `Status: New`)
-- `src/cli.tsx:15`
-- `package.json:2`
-- Error guidance suggests `npx @b3awesome/procedure`, but repository package metadata is `procedure-cli` with bin `procedure`. This can mislead contributors running the package directly from this repo context.
-- Recommendation: derive suggested invocation from package metadata/config (single source of truth) or print both supported invocations explicitly.
-
-### Verification Notes
-- Procedure compliance: read latest `CODE-REVIEW.md` and `CODE-FIXED.md` before this review.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Reviewed local working-tree diffs in `README.md`, `docs/PRD.md`, `docs/USER-STORIES.md`, and `src/cli.tsx`.
-
-### Residual Risks / Testing Gaps
-- No integration test for behavior in non-empty directories vs regeneration flow (`checkConflicts` path).
-- No test that validates CLI guidance text stays aligned with actual package/bin invocation names.
-
----
-
-## Entry 2026-02-22
-
-### Entry ID
-- `CR-20260222-005`
-
-### Supersedes
-- `CR-20260222-004`
-
-### Scope
-- New review cycle after in-step navigation changes across wizard steps and docs updates.
-- Validate latest fixed findings and identify regressions in current unstaged workspace.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 12 | Medium | Fixed | `CODE-FIXED.md:210`, `src/cli.tsx:11`, `src/cli.tsx:13` | Non-empty directories now warn and continue; Generation overwrite flow remains reachable. |
-| 13 | Low | Fixed | `CODE-FIXED.md:214`, `src/cli.tsx:16` | CLI guidance now shows both invocation forms. |
-
-### Findings (ordered by severity)
-1. Low - Last-field navigation behavior is inconsistent with UI hints (`Finding #14`, `Status: New`)
-- `src/steps/build-test.tsx:47`
-- `src/steps/build-test.tsx:56`
-- `src/steps/build-test.tsx:109`
-- `src/steps/product-context.tsx:93`
-- `src/steps/product-context.tsx:103`
-- `src/steps/product-context.tsx:260`
-- On final text fields, the hint intentionally omits `↓ next` (showing only `enter confirm`), but pressing `↓` still completes the step via the shared down-arrow handler. This creates hidden behavior not reflected in the prompt and can trigger accidental completion.
-- Recommendation: gate `key.downArrow` completion behind `!isLast` (and keep `Enter` as the only completion key on last fields), or explicitly document/display `↓` as confirm on last fields.
-
-2. Low - PRD documentation reintroduces stale empty-directory behavior (`Finding #15`, `Status: New`)
-- `docs/PRD.md:29`
-- `src/cli.tsx:11`
-- PRD currently states the CLI "exits" when cwd contains files, but runtime behavior now warns and continues.
-- Recommendation: update PRD wording to match current behavior (warning + continue + Step 6 overwrite confirmation).
-
-### Verification Notes
-- Procedure compliance: read latest `CODE-REVIEW.md` and latest `CODE-FIXED.md` before this review.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Reviewed local diffs in `README.md`, `docs/PRD.md`, `docs/USER-STORIES.md`, `src/components/guttered-select.tsx`, `src/steps/build-test.tsx`, `src/steps/powerline.tsx`, `src/steps/product-context.tsx`, and `src/steps/project-info.tsx`.
-
-### Residual Risks / Testing Gaps
-- No interaction test currently asserts last-field key behavior (`↓` vs `Enter`) in Build & Test or Product Context.
-- No docs-consistency check to detect divergence between runtime guard behavior and PRD text.
-
----
-
-## Entry 2026-02-22
-
-### Entry ID
-- `CR-20260222-006`
-
-### Supersedes
-- `CR-20260222-005`
-
-### Scope
-- Continue review after Tab/Shift+Tab navigation refactor and accompanying docs updates.
-- Validate latest fix-cycle statuses and identify new regressions in current local changes.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 14 | Low | Fixed | `CODE-FIXED.md:128`, `src/steps/build-test.tsx:106`, `src/steps/product-context.tsx:253` | Last-field hint behavior is now consistent (`Tab / Enter confirm` shown where completion on Tab is supported). |
-| 15 | Low | Fixed | `CODE-FIXED.md:139`, `docs/PRD.md:29`, `src/cli.tsx:11` | PRD now reflects warn-and-continue behavior for non-empty directories. |
-
-### Findings (ordered by severity)
-1. Low - `Tab` navigation in Project Info select steps can surface incorrect required-field error and block expected flow (`Finding #16`, `Status: New`)
-- `src/steps/project-info.tsx:55`
-- `src/steps/project-info.tsx:57`
-- `src/steps/project-info.tsx:61`
-- `src/steps/project-info.tsx:153`
-- `src/steps/project-info.tsx:168`
-- Global `Tab` handler applies text-field validation logic to all steps, including `packageManager` and `license` select steps. If no value was already committed, pressing `Tab` can emit "Description is required" in select context and prevent progress, which conflicts with on-screen select hints.
-- Recommendation: scope `Tab` validation branch to text steps only, or provide select-specific `Tab` handling (derive value from active option or disable `Tab next` hints for select steps).
-
-2. Low - `Tab next` on Product Context multi-select phases can silently discard unsubmitted current selection state (`Finding #17`, `Status: New`)
-- `src/steps/product-context.tsx:90`
-- `src/steps/product-context.tsx:92`
-- `src/steps/product-context.tsx:217`
-- `src/steps/product-context.tsx:238`
-- `Tab` handler persists only `answers[currentPhase]`, but multi-select state lives inside `GutteredMultiSelect` until Enter submit. On `techStack`/`coreFeatures`, `Tab next` may advance with empty/stale data (including losing prefilled tech stack) despite hints implying "saves current value".
-- Recommendation: either remove `Tab next` for multi-select phases or plumb a controlled selection state upward so `Tab` can persist the current selection snapshot.
-
-### Verification Notes
-- Procedure compliance: reviewed latest `CODE-REVIEW.md` and latest `CODE-FIXED.md` before analysis.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Reviewed active diffs in `README.md`, `docs/PRD.md`, `docs/USER-STORIES.md`, `src/steps/build-test.tsx`, `src/steps/powerline.tsx`, `src/steps/product-context.tsx`, `src/steps/project-info.tsx`, and `AGENTS.md`.
-
-### Residual Risks / Testing Gaps
-- No interaction test currently verifies `Tab` behavior separately for text inputs versus select/multi-select phases.
-- No regression test covers preservation of prefilled tech-stack values when navigating Product Context with `Tab`.
-
----
-
-## Entry 2026-02-22
-
-### Entry ID
-- `CR-20260222-007`
-
-### Supersedes
-- `CR-20260222-006`
-
-### Scope
-- New review cycle after `CF-20260222-008` (Tab/Shift+Tab navigation fixes).
-- Re-validate open findings and scan current workspace changes for regressions.
-
-### Validation Matrix
-| Finding # | Previous Severity | Current Status | Evidence | Notes |
-|-----------|-------------------|----------------|----------|-------|
-| 16 | Low | Fixed | `CODE-FIXED.md:236`, `src/steps/project-info.tsx:51`, `src/steps/project-info.tsx:57`, `src/steps/project-info.tsx:156` | Project Info `Tab` handler now excludes select steps, and select hints no longer promise `Tab next`. |
-| 17 | Low | Fixed | `CODE-FIXED.md:241`, `src/steps/product-context.tsx:86`, `src/steps/product-context.tsx:92`, `src/steps/product-context.tsx:224`, `src/steps/product-context.tsx:241` | Product Context `Tab` handler now excludes multi-select phases, and multi-select hints no longer advertise `Tab next`. |
-
-### Findings (ordered by severity)
-- No new functional findings identified in this review cycle.
-
-### Verification Notes
-- Procedure compliance: read latest `CODE-REVIEW.md` and latest `CODE-FIXED.md` before this review.
-- `npm run typecheck`: pass.
-- `npm run build`: pass.
-- Reviewed active diffs in `AGENTS.md`, `README.md`, `docs/PRD.md`, `docs/USER-STORIES.md`, `src/steps/build-test.tsx`, `src/steps/powerline.tsx`, `src/steps/product-context.tsx`, and `src/steps/project-info.tsx`.
-
-### Residual Risks / Testing Gaps
-- No automated interaction tests currently verify keyboard navigation behavior (`Tab`/`Shift+Tab`/`Enter`) across text, select, and multi-select step variants.

package/config/defaults.json

@@ -1,8 +0,0 @@
-{
-  "packageManager": "npm",
-  "license": "ISC",
-  "buildCommand": "npm run build",
-  "testCommand": "npm run test",
-  "typecheckCommand": "tsc --noEmit",
-  "lintCommand": "npm run lint"
-}

package/config/powerline-config.json

@@ -1,52 +0,0 @@
-{
-  "theme": "tokyo-night",
-  "display": {
-    "style": "powerline",
-    "colorCompatibility": "auto",
-    "lines": [
-      {
-        "segments": {
-          "directory": { "enabled": true, "showBasename": true },
-          "model": { "enabled": true },
-          "git": {
-            "enabled": true,
-            "showSha": false,
-            "showWorkingTree": false,
-            "showOperation": false,
-            "showTag": true,
-            "showTimeSinceCommit": false,
-            "showStashCount": false,
-            "showUpstream": false,
-            "showRepoName": false
-          },
-          "context": { "enabled": true, "showPercentageOnly": true }
-        }
-      },
-      {
-        "segments": {
-          "block": {
-            "enabled": true,
-            "type": "time",
-            "burnType": "both"
-          },
-          "session": {
-            "enabled": true,
-            "type": "both",
-            "costSource": "calculated"
-          },
-          "today": { "enabled": true, "type": "both" },
-          "version": { "enabled": false },
-          "metrics": {
-            "enabled": false,
-            "showResponseTime": true,
-            "showLastResponseTime": true,
-            "showDuration": true,
-            "showMessageCount": true,
-            "showLinesAdded": true,
-            "showLinesRemoved": true
-          }
-        }
-      }
-    ]
-  }
-}

package/config/stacks/typescript-node.json

@@ -1,15 +0,0 @@
-{
-  "codeStyle": [
-    "TypeScript strict mode, ESM imports",
-    "camelCase for variables, PascalCase for types",
-    "stdlib -> external -> internal import ordering",
-    "Return errors, don't throw"
-  ],
-  "buildCommand": "npm run build",
-  "testCommand": "npm run test",
-  "typecheckCommand": "npm run typecheck",
-  "lintCommand": "npm run lint",
-  "architectureNotes": "",
-  "framework": "Node.js",
-  "language": "TypeScript"
-}