chore: three code comments still cite GSD-era planning paths
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
- Domain
- backend, documentation, frontend
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
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:145and:519cite.planning/STATE.md.internal/gitmeta/fixtures_test.go:70calls.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.gocomment names the layout without the GSD pointer. - The two
GraphCanvas.sveltecomments say what they mean without.planning/STATE.md, or citeplanning-archive-v0.15.0:.planning/STATE.md, in a PR that rebuildsweb/build. - Outside
openspec/andweb/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
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 107
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from seanb4t/codegraph-go
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
seanb4t/codegraph-go#380 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#379 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
seanb4t/codegraph-go#362 ·
Maintainers usually reply within 1 day
-
area:query bug priority:low spec-needed
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
seanb4t/codegraph-go#355 ·
Maintainers usually reply within 1 day
All issues in seanb4t/codegraph-go
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day