fix: migrate schema $id base to live github pages registry#14
Open
OgeonX-Ai wants to merge 1 commit into
Open
Conversation
Rewrite every JSON-Schema $id and $ref off the phantom domain schemas.coding-autopilot.dev to the live, org-controlled GitHub Pages registry base that actually resolves 200: https://coding-autopilot-system.github.io/cas-contracts/registry/ The version paths (v0.1/v1.0/v1.1 and the immutable releases/ tree) are unchanged; only the domain moves, so each $id now dereferences directly to the schema it identifies. Updates the scripts/lib.mjs $id base used by the example validator, the vendored example artifact uris, the contract test expectations, and docs/DISTRIBUTION.md (the canonical-namespace/custom-domain guidance is superseded now that $id == hosting URL). npm ci && npm test (35 pass), validate:registry (3 releases / 3 lines) and validate (7 examples) all green after regenerating the registry manifests with the new content hashes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
2 participants
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
Migrates every JSON-Schema
$id(and$ref) off the phantom domainschemas.coding-autopilot.devand onto the live, org-controlled GitHub Pages registry base that actually resolves:Verified live before migrating:
GET .../registry/index.json→ 200 andGET .../registry/v0.1/common.schema.json→ 200. The served path layout (registry/<line>/<name>.schema.json) matches the new$idbase exactly, so each$idnow dereferences directly to the schema it identifies.This is a rewrite-in-place: the
v0.1/v1.0/v1.1version lines and the immutablereleases/tree are unchanged — only the domain moves.Changes
schemas/**(v0.1, v1.0, v1.1) —$idand internal$refs.scripts/lib.mjs— the$idbase used byschemaIdForExamplefor the example validator.examples/v0.1|v1.0/artifact-manifest.json— the vendoredurifields that point at schema locations.tests/contracts.test.mjs,tests/goal-contract.test.mjs— contract-test$idexpectations.docs/DISTRIBUTION.md— the canonical-namespace / custom-domain guidance is superseded now that$id== hosting URL.The gitignored
registry/build artifacts were regenerated vianpm run build:registryto confirm manifests carry the new content hashes; they are rebuilt by the Pages workflow at publish time, not committed.Validation
npm ci && npm test— 35 passingnpm run validate:registry— 3 releases / 3 stable lines validatednpm run validate— 7 lifecycle examples validated🤖 Generated with Claude Code