feat: publish a machine-readable JSON of each variant - #10
Merged
Conversation
json joins pdf and html as a first-class build format. The emitted file is the variant-filtered document — the same entries and bullets the matching PDF shows, x-tags/x-highlights stripped — so a machine consumer can never see content the published cut withholds. The build stamp lands in meta (version, lastModified), giving the file the same provenance the human formats print in the colophon. resume site publishes it for every publish=true variant and the landing page links it; the no-leak site tests now cover the JSON artifact too, and new build tests pin schema validity and variant conformity. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
json joins pdf and html as a first-class build format. The emitted file is the variant-filtered document — the same entries and bullets the matching PDF shows, x-tags/x-highlights stripped — so a machine consumer can never see content the published cut withholds. The build stamp lands in meta (version, lastModified), giving the file the same provenance the human formats print in the colophon.
resume site publishes it for every publish=true variant and the landing page links it; the no-leak site tests now cover the JSON artifact too, and new build tests pin schema validity and variant conformity.