This repository was archived by the owner on May 24, 2026. It is now read-only.
Prepare Protocol-Commercial v1.1.0 release — flat v1.1.0 schemas, examples, docs, and CI#3
Merged
GsCommand merged 1 commit intoMar 19, 2026
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
v1.1.0current line that aligns with Commons/Agent-Cards v1.1.0 and treats x402 as first-class for payment/settlement semantics._sharedfragments and is easy for Agent Cards and mirrors to bind.Description
1.1.0and updatedpackage.jsonmain/exports,manifest.json(now pointing atschemas/v1.1.0and markingv1.0.0as legacy), and addedschemas/v1.1.0/index.json.schemas/v1.1.0/commercial/{authorize,checkout,purchase,ship,verify}with deterministic$idvalues underhttps://commandlayer.org/schemas/v1.1.0/....examples/v1.1.0/commercial/<verb>/{valid,invalid}(valid and invalid request + receipt fixtures for all five verbs).README.md,SPEC.md,ONBOARDING.md,POLICY.md,GOVERNANCE.md,RESOLUTION.md,SECURITY.md,SECURITY_PROVENANCE.md,COMPLIANCE.md) to reflect v1.1.0, flat schemas, x402-first posture, and release rules.scripts/validate-all.mjs,scripts/validate-examples.mjs, andscripts/generate-checksums.mjsand adjusting.github/workflows/validate.ymlto run the new checks; CI now validates the v1.1.0 tree, examples, and regenerates checksums.checksums.txtto cover the v1.1.0 index, schemas, examples, and manifest so the integrity surface represents the current release candidate.Testing
npm run validate(which runsvalidate:schemasandvalidate:examples) and it completed successfully with strict Ajv compilation of the v1.1.0 schema set. (Result: succeeded.)npm run generate:checksumsand the script wrote the newchecksums.txtfor the release artifact set (Result: succeeded; 32 release checksums written).sha256sum -c checksums.txtand the listed examples, schemas, and manifest all passed (Result: all OK).npm install --package-lock-onlyto ensure lockfile coherence (Result: succeeded).Codex Task