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

Open
#130 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
go

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
Go
Stars
0
Forks
0
Avg merge
5h 16m
Merged PRs (30d)
107

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seanb4t/codegraph-go

All issues in seanb4t/codegraph-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.