Complete PUB-3 hygiene: .vercel ignore and agents.json exception - #16
Merged
Merged
Conversation
- Add .vercel to .gitignore, the one baseline pattern from Repo Standards that was missing. - Record a served-only agents.json exception in INTENT.md. Repo Standards place agents.json at the repository root, but here it is build output fetched over HTTP by server.json, llms.txt and the README, and the committed docs/ copy already travels with a clone; a root copy would only add drift risk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Finishes PUB-3 from the 2026-09-14 cross-repo assessment. The release-prose part merged in #15; this commit reached that branch after the merge, so it comes here instead.
.gitignore. Adds.vercel, the one pattern from the Repo Standards baseline that was missing. Every other baseline pattern was already present.agents.jsonplacement. Repo Standards listagents.jsonas travels-with-code at the repository root. PubLedge's copy is build output ofscripts/build-extras.js. It is fetched over HTTP byserver.json,llms.txtand the README, and it is committed underdocs/, so a clone already carries it. A root duplicate would add drift risk without serving any consumer the committed copy doesn't. Instead of adding the file, this records the deviation inINTENT.mdunder a new "Exceptions to Repo Standards" section, with a decision-history entry.docs/INTENT.mdis regenerated and matches.If you'd rather follow the standard literally, the alternative is to have
build-extras.jsalso write a rootagents.json, plus an eval that enforces byte parity withdocs/agents.json.Test plan
OBLIGATION_FIRST_DIR=../obligation-first npm run verify:cipasses on top of mainf6d96ed7./scripts/validate-hashes.shpassesINTENT.mdanddocs/INTENT.mdare byte-identical after build🤖 Generated with Claude Code