docs: CLAUDE.md drift — internal/ui status, lipgloss in go.mod, phase table points at closed #17/#18 #106

What

CLAUDE.md drifted again after the recent fix-wave merges (same class of problem as #54, new instances):

1. Architecture section — internal/ui/ is described as "(planned, not yet implemented)". The scaffold (Writer + theme + mode) merged in e37b326; version.go and root.go already use it. Should read "partial — scaffold merged, rollout tracked by feat(ui): complete internal/ui rollout — spinners, huh prompts, migrate remaining call sites (#74 phases 2–4) #105".
2. Dependencies section — says huh, bubbletea, lipgloss are "planned but not yet in go.mod". lipgloss v1.1.0 is in go.mod now; only huh and bubbletea remain planned.
3. Phase table — Phase 7 and Phase 8 both say "tracked by chore(release): finalize GoReleaser config and npm wrapper #17 / chore(release): prepare v1.0.0 release #18", but both issues are CLOSED. The live remaining item is Release prep: publish nodeup-npm to npm registry on v1.0.0 cut #35 (manual npm publish of nodeup-cli on the v1.0.0 cut). The rows should point at Release prep: publish nodeup-npm to npm registry on v1.0.0 cut #35 (and feat(ui): complete internal/ui rollout — spinners, huh prompts, migrate remaining call sites (#74 phases 2–4) #105 if UI is considered a v1.0.0 blocker).

Also worth a pass in the same PR

SPEC.md §T is behind the merged work — e.g. T3 (wire AcquireLock) is still marked todo though it landed via PR #79, and T18 (internal/ui) is partially done. Update statuses via the spec workflow rather than leaving §T stale.

One docs PR covers all of this.