docs: refresh post-merge status in GOAL.md and NEEDS.md

[slittycode]

Summary

A doc-vs-code audit found that the recommendation-proof campaign was authored on the worktree-goal-doc branch and landed via PR #114 (commit 348498d), but the status sections in GOAL.md and apps/backend/NEEDS.md still described the pre-merge state — most visibly claiming the work was not on main and that a branch convergence was still owed.

What changed

• GOAL.md "Implementation status" — rewritten from "built on worktree-goal-doc, not on main" to reflect that the scorer, fixtures, deterministic-source bridge, UI verification badge, and verdict write-up all landed on main in PR feat: land the recommendation-proof campaign (GOAL.md + scorer + corpus + UI badge) #114. The remaining open work (renders, real-corpus verdict, badge bands) is now framed as owner-gated, not branch-merge-gated.
• apps/backend/NEEDS.md "RETROACTIVE Fix backend naming mismatch in return values #5" — dropped; the branch convergence item it described is done.
• apps/backend/NEEDS.md "Branch convergence needed for 3.2" — reframed as "Phase 2 audit context for 3.2" since the audit branch (chore/phase2-surface-audit-and-claude-md) and Tier-1/2 prompt fixes (5610ca5, ade2ae5) are on main and the campaign sits on top of them.
• apps/backend/NEEDS.md provisional finding — replaced the "coordinate with branch convergence below" caveat with a pointer to the existing NEEDS-WIRING dead-code finding, which is the real remaining caveat.

What was audited and left alone

The rest of the doc surface (root CLAUDE.md, README.md, PURPOSE.md, BACKLOG.md, CHANGELOG.md, docs/ARCHITECTURE_STRATEGY.md, docs/SETUP.md, docs/SAMPLE_GENERATION.md, docs/PUBLIC_HOSTING_FOUNDATION.md, per-app README.md/AGENTS.md/CHANGELOG.md, backend ARCHITECTURE.md/JSON_SCHEMA.md/RECOMMENDATION_VERDICT.md) was cross-checked against the actual code layout, route list, env vars, scripts, and fixture directories. The file/module inventory matches, env vars match .env.example, and the route list matches server*.py. No other concrete drift required updating; the historical paper trail in docs/history/ is intentionally past-tense and was left untouched.

Test plan

• git diff — only GOAL.md and apps/backend/NEEDS.md touched (2 files, +29/-32)
• No code paths affected — pure markdown
• Grep confirms no remaining worktree-goal-doc, not on \main`, or Branch convergence` references in the repo

https://claude.ai/code/session_01Kh5q91wQoF8EF2BD41RMWN

---

Generated by Claude Code

[slittycode]

Verdict: APPROVE

Summary

Docs-only PR: updates the "Implementation status" section in GOAL.md and matching items in apps/backend/NEEDS.md to reflect that the recommendation-proof campaign (scorer, fixtures, UI badge, verdict write-up) landed on main in PR #114 rather than remaining on a worktree branch. No code paths touched. Audited all cross-references, commit hashes, and file paths against the live tree — all correct.

Findings

None.

Test results

N/A — docs only, no code changed.

Phase boundary check

Clean.

Cross-reference audit

• All four commit hashes cited in NEEDS.md (bd975ab, dc8daa0, 5610ca5, ade2ae5) exist in the branch history. ✓
• NEEDS-WIRING cross-reference in the modified provisional-finding line resolves to ## NEEDS-WIRING — mostly closed at line 147 of NEEDS.md. ✓
• All six file paths cited in the updated GOAL.md exist in the tree (recommendation_evaluation.py, evaluate_recommendations.py, emit_deterministic_recs.ts, AnalysisResults.tsx, RECOMMENDATION_VERDICT.md, tests/fixtures/recommendation_tracks/README.md). ✓

---

Generated by Claude Code

[slittycode]

Verdict: APPROVE

Summary

Pure markdown cleanup reflecting that the recommendation-proof campaign landed on main in PR #114. The before/after are factually consistent with the stated commit hashes and file locations. No code touched.

Findings

None.

Test results

CI green (Frontend / Backend / Loudness WASM). No test surface for docs-only changes.

Phase boundary check

N/A — no code changed.

---

Generated by Claude Code