Repository navigation
Merged
Conversation
… task 1.1) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jason Cruz Falzon <jason@cognitivedelivery.co.uk>
…selves (DR-185, task 1.2) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jason Cruz Falzon <jason@cognitivedelivery.co.uk>
…sm (DR-185, task 2.1) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jason Cruz Falzon <jason@cognitivedelivery.co.uk>
…ion; CHANGELOG (DR-185, task 2.2) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jason Cruz Falzon <jason@cognitivedelivery.co.uk>
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
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.
A documentation site on the existing GitHub Pages deployment, generated on every deploy from the files
npm testchecks. The schema bytes at every$idand under each/<version>/are laid out by the workflow exactly as before and never touched by the generator.What. Four signed commits, one per spec task:
tooling/build-site.mjsandtooling/site.css;marked18.1.0 pinned exactly as a devDependency (zero transitive dependencies, not in the tarball); the front page, the SPEC, README, GOVERNANCE, CONTRIBUTING, SECURITY and CHANGELOG as pages, the guides, the conformance and proposals indexes, the versions page and the frozen-copy index pages, a 404 page. GitHub's heading-slug algorithm; relative links rewritten to site paths with an unknown path aborting the build. One docs fix the build found: an unescaped pipe inside a table code span indocs/upgrading-1.0-to-1.2.md.tooling/site-reference.mjs, the schema reference: one page per schema walked from the schema files with every property's path, type, required (including conditional), description, constraints and stability;$refrows link to definitions; the three inlined copies walked in place and labelled.conformance/site-check.mjsinnpm test: links and anchors, every schema and docs file paged, the1.x/bytes compared toschemas/, no script or external resource, two builds compared; NOT CHECKED from the installed package, which has notooling/.pages.ymlbuilds the pages after its unchanged schema layout; README "The site"; CHANGELOG.Checks.
npm test:Site: 32 pages, 591 links, 0 failure(s).,Conformant.; the workflow's build step simulated locally with1.x/and the six frozen directories (38 pages); the installed-package run printsSite: NOT CHECKEDandConformant.; three mutation proofs (an unknown link, a planted script tag, one changed schema byte) each failednpm testnaming the page and reason. The tarball gains one file,conformance/site-check.mjs, becauserun.mjsimports it.No page carries a script or reaches another host. No schema, fixture, lock, guard or SPEC text changes; no release needed. Governed as harness spec
build-documentation-site-governance-contract(DR-185); Linear COGDEV-278.🤖 Generated with Claude Code