This repository was archived by the owner on May 24, 2026. It is now read-only.
docs: surface README TOC, clarify receipt agent optionality, add v1.0.0 changelog, split CONTRIBUTING, remove redundant ajv entrypoint#13
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
agentas optional so docs match the schema contract.v1.0.0entry toCHANGELOG.md.Description
Table of Contentsimmediately after the title/purpose block and adjusted surrounding README navigation and validation guidance to recommendnpm run validateas the canonical command.agentis mandatory and updated the receipt examples to showagentas optional while calling outresult_hash/result_cidas optional evidence fields.## 1.0.0initial release entry toCHANGELOG.mddescribing the original release and its relationship to the currentv1.1.0line.CONTRIBUTING.mdwith a strict PR spine, commit conventions, required checks, schema-change requirements, and versioning expectations, and updatedONBOARDING.mdto be focused on orientation and working norms.validate:schemapackage script and deletedscripts/ajv-run.mjs, leavingvalidate,validate:schemas, andvalidate:examplesas the clear validation entrypoints and updatedpackage.jsonand README to match.Testing
npm run validatewhich executesnpm run validate:schemasandnpm run validate:examples, and observed success with✅ All 45 schemas compiled successfully.and✅ All example validations completed..npm run validate:schemasandnpm run validate:exampleswere exercised as part of thevalidaterun and completed successfully.Codex Task