chore: public-repo readiness (group artifacts, scrub internal detail)#4
Merged
Conversation
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.
Tidies the public repo ahead of broader external visibility.
Group spec artifacts under
spec/openapi.json,openapi.yaml,provenance.jsonmove from the root intospec/.publish.ts,lint:spec, and the docs are updated to match.Consumer impact: none. GitHub Release asset basenames stay
openapi.json/openapi.yaml, so the docs sync (release-asset URL) and the producer (passes an input temp path) are unaffected. Only the raw-HEAD URL changes, and that's updated in the README.Scrub internal implementation detail from public docs/comments
The public repo should not expose our infra/auth topology. Removed from
README.md,AGENTS.md(CLAUDE.md symlinks to it), andpublish.tscomments: the GitHub App id, the 1Password reference, GitLab specifics, the bot user-id, the SSH host alias, and the detailed token-mint/CI mechanics. Kept consumer-facing content (what it is, file layout, versioning/tag scheme, how to pull/pin) and neutral maintainer guidance. The cross-org auth detail lives in the producer's own (private) AGENTS.md, which is its correct home.Verification
npm run typecheck,npm test,npm run lint:specall pass (no crash).publish:specon the unchanged path correctly reads the newspec/paths and no-ops.mainis already linear/conventional, so no history rewrite.