chore: three code comments still cite GSD-era planning paths

Aperta
#130 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
58/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

Start with the comment at internal/gitmeta/fixtures_test.go:70 and reword it to describe the .claude/worktrees/<name>/ layout without the GSD pointer. The two comments in web/src/lib/components/graph/GraphCanvas.svelte (lines 145 and 519) can only change in a PR that also rebuilds web/build, since task web:drift fails otherwise, so pick that part up only when a rebuild is already planned. Done means no .planning/ reference remains outside openspec/ and web/build/ except archive-tag references like planning-archive-v0.15.0:.planning/STATE.md.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:ui chore priority:low
What's wrong

Three code comments point at the GSD planning record. #126 deleted that record, and the tag planning-archive-v0.15.0 archives it.

  • web/src/lib/components/graph/GraphCanvas.svelte:145 and :519 cite .planning/STATE.md.
  • internal/gitmeta/fixtures_test.go:70 calls .claude/worktrees/<name>/ "the motivating GSD layout (see CONTEXT.md § Specific Ideas)". Claude Code puts its own worktrees there, so the fixture still has a reason. Only the pointer is stale.
Constraint

Any edit under web/src/, a comment included, fails the SPA build drift guard (task web:drift) in the required test job, unless the same PR rebuilds and commits web/build. Fix the two GraphCanvas.svelte comments in the next PR that rebuilds the SPA for another reason.

Acceptance criteria
  • The fixtures_test.go comment names the layout without the GSD pointer.
  • The two GraphCanvas.svelte comments say what they mean without .planning/STATE.md, or cite planning-archive-v0.15.0:.planning/STATE.md, in a PR that rebuilds web/build.
  • Outside openspec/ and web/build/, every .planning/ reference in the repository is an archive-tag reference.

Split from #122. docs/RELEASE-PROCEDURES.md §3 is covered by #107.


🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Lingua principale
Go
Stelle
0
Fork
0
Merge medio
7h 42m
PR unite (30g)
111

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di seanb4t/codegraph-go

Tutte le issue di seanb4t/codegraph-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.