Skip to content

Normalize v1.1.0 release documentation#21

Merged
GsCommand merged 2 commits into
mainfrom
codex/normalize-documentation-for-v1.1.0-release
Mar 20, 2026
Merged

Normalize v1.1.0 release documentation#21
GsCommand merged 2 commits into
mainfrom
codex/normalize-documentation-for-v1.1.0-release

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • Normalize all release-facing documentation so v1.1.0 is clearly the current release and active schema line and v1.0.0 is historical/legacy only.
  • Remove or reframe language that implies signed or cryptographic provenance and replace it with accurate checksum- and manifest-based integrity descriptions.
  • Clarify that HTTPS hosting and IPFS pinning are separate distribution layers and that examples live in the repository (not necessarily in the npm package).

Description

  • Rewrote and harmonized release messaging across README.md, SPEC.md, SCHEMAS.md, SECURITY_PROVENANCE.md, COMPLIANCE.md, GOVERNANCE.md, RESOLUTION.md, ONBOARDING.md, and CHANGELOG.md so v1.1.0 is the current release and v1.0.0 is historical.
  • Replaced claims of “signed/cryptographic provenance” with precise language about checksums.txt, manifest.json, versioned schema paths, documented release metadata, and explicit statement that the repository does not currently publish signed release artifacts; updated receipt/provenance phrasing in schemas/docs to avoid overselling verification guarantees.
  • Updated package and metadata files (manifest.json, package.json) to align descriptions and active_release metadata with the documentation normalization and added explicit npm-package notes in README.md stating that examples are not included in the npm package and that TypeScript examples are illustrative only.
  • Cleaned .gitignore (removed stray NUL), converted RESOLUTION.md into a concise release log, and made other structural wording fixes to keep the tone precise and procedural while preserving all schema semantics, paths, and versions.

Testing

  • Ran npm run validate which compiled all schemas and validated all example fixtures successfully.
  • Ran npm run checksums:verify which verified file-level checksums in checksums.txt with all listed files reporting OK.
  • Ran npm run test:smoke:pack (pack preflight) which completed successfully and produced a package tarball (commandlayer-commons-1.1.0.tgz).

Codex Task

@GsCommand GsCommand merged commit b6637bd into main Mar 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant