Surfaced while fixing #12366, whose scope was held to the 5 sites under content/. These are the objectstack-ai/spec spellings that survive outside that scope. Filed unassigned; not touched by that PR.
The one with latent functional impact
.changeset/config.json:6
"changelog": [
"@changesets/cli/changelog",
{ "repo": "objectstack-ai/spec" }
]The option is real config, not prose — but the generator it is handed to is @changesets/cli/changelog, the default generator, which emits plain release lines and never reads repo. Only @changesets/changelog-github consumes it.
So it is inert today, and inert for a reason nobody can see from the file: the value is correctly shaped, correctly placed, and silently unread. The moment anyone swaps in @changesets/changelog-github — the ordinary reason to touch this block — every generated CHANGELOG entry starts emitting links built from the wrong repository name, with nothing in the diff that would look wrong at review time.
This is the same hazard #12366 was filed for ("inert config carrying a wrong value is what someone wires up later, having reasonably assumed it was maintained"), one directory over, and it was not in that card's census.
Census — every other spec spelling outside content/
Measured on origin/main at 262145bef4:
| file | hits | character |
|---|
.changeset/config.json | 1 | config, latent (above) |
packages/spec/README.md:3 | 1 | published README — the StackBlitz "Try Online" badge target |
packages/plugins/plugin-auth/ARCHITECTURE.md:179 | 1 | prose link to PR #580 |
CONTRIBUTING.md | 3 | git remote add upstream, Discussions, Issues |
CHANGELOG.md | 21 | link-reference block, historical version compares |
packages/plugins/plugin-auth/CHANGELOG.md | 2 | link-reference block |
docs/notes/airtable-dashboard-analysis.mdx | 16 | numbered /spec/issues/712-714 links |
#12366 already declared CONTRIBUTING.md, CHANGELOG.md and docs/notes/** a maintainer call. Two rows here were in neither that card nor its out-of-scope list: .changeset/config.json and packages/spec/README.md.
packages/spec/README.md is worth separating from the rest — it is published to npm, so its badge is served to readers who never see this repo, and unlike a CHANGELOG entry it makes no historical claim.
⛔ docs/notes/airtable-dashboard-analysis.mdx carries a recorded decision not to rewrite it — docs/audits/2026-06-handwritten-docs-accuracy-followups.md:40, on the grounds that those links carry issue numbers whose identity could differ between the two names. That reasoning is specific to numbered links and should not be overturned without addressing it. It does not reach the rows above, none of which names an issue number.
Why it matters
All three repository names resolve to the same repository today, so every one of these costs a 301 rather than a 404. The reason to fix them is that a rename redirect is kept only while the old name stays unclaimed.
Generated by Claude Code
Surfaced while fixing #12366, whose scope was held to the 5 sites under
content/. These are theobjectstack-ai/specspellings that survive outside that scope. Filed unassigned; not touched by that PR.The one with latent functional impact
.changeset/config.json:6The option is real config, not prose — but the generator it is handed to is
@changesets/cli/changelog, the default generator, which emits plain release lines and never readsrepo. Only@changesets/changelog-githubconsumes it.So it is inert today, and inert for a reason nobody can see from the file: the value is correctly shaped, correctly placed, and silently unread. The moment anyone swaps in
@changesets/changelog-github— the ordinary reason to touch this block — every generated CHANGELOG entry starts emitting links built from the wrong repository name, with nothing in the diff that would look wrong at review time.This is the same hazard #12366 was filed for ("inert config carrying a wrong value is what someone wires up later, having reasonably assumed it was maintained"), one directory over, and it was not in that card's census.
Census — every other
specspelling outsidecontent/Measured on
origin/mainat262145bef4:.changeset/config.jsonpackages/spec/README.md:3packages/plugins/plugin-auth/ARCHITECTURE.md:179CONTRIBUTING.mdgit remote add upstream, Discussions, IssuesCHANGELOG.mdpackages/plugins/plugin-auth/CHANGELOG.mddocs/notes/airtable-dashboard-analysis.mdx/spec/issues/712-714links#12366 already declared
CONTRIBUTING.md,CHANGELOG.mdanddocs/notes/**a maintainer call. Two rows here were in neither that card nor its out-of-scope list:.changeset/config.jsonandpackages/spec/README.md.packages/spec/README.mdis worth separating from the rest — it is published to npm, so its badge is served to readers who never see this repo, and unlike a CHANGELOG entry it makes no historical claim.⛔
docs/notes/airtable-dashboard-analysis.mdxcarries a recorded decision not to rewrite it —docs/audits/2026-06-handwritten-docs-accuracy-followups.md:40, on the grounds that those links carry issue numbers whose identity could differ between the two names. That reasoning is specific to numbered links and should not be overturned without addressing it. It does not reach the rows above, none of which names an issue number.Why it matters
All three repository names resolve to the same repository today, so every one of these costs a 301 rather than a 404. The reason to fix them is that a rename redirect is kept only while the old name stays unclaimed.
Generated by Claude Code