Align docs: declare v1.1.0 as active in‑repo (pre‑release) and scope v1.0.0 as last pinned canonical release

[GsCommand]

Motivation

• Make the repository documentation internally consistent about the status of v1.1.0 versus v1.0.0 for both schema semantics and provenance/pinning.
• Remove or re-scope legacy v1.0.0-only rules (notably x402/trace) so they are not presented as universally normative for v1.1.0.
• Preserve strong provenance and governance language while avoiding accidental claims that v1.1.0 is already fully pinned/canonical when its CID is still pending.

Description

• Document status policy: treat v1.1.0 as the active in-repo schema family but explicitly mark it as a pre‑release candidate for provenance until a v1.1.0 CID is published, and treat v1.0.0 as the last fully pinned canonical release. (updates across SECURITY_PROVENANCE.md, SPEC.md, SCHEMAS.md, COMPLIANCE.md, README.md).
• Scope legacy conventions: mark nested layout, _shared, x402, and trace as legacy/v1.0.0-only and add explicit guidance that those are not automatically normative for v1.1.0. (changes in SPEC.md, SCHEMAS.md, COMPLIANCE.md).
• Make compliance version-aware: require compliance claims to name the version and forbid claiming fully pinned canonical v1.1.0 compliance until CID publication and provenance are complete. (changes in COMPLIANCE.md).
• README polish: change schema badge/text to indicate v1.1.0 candidate status and update the integrity notice to reference v1.0.0 as the last pinned CID while pointing to TBD (pre-release) for v1.1.0. (changes in README.md).
• No schema files, examples, or example content were modified in this pass; only documentation files were edited.

Files modified: SECURITY_PROVENANCE.md, SPEC.md, SCHEMAS.md, COMPLIANCE.md, README.md.

Testing

• Ran repository validation with npm run validate which compiled all schemas and validated examples for both v1.0.0 and v1.1.0; result: success.
• Verified checksums with npm run checksums:verify; result: success for all listed schema files.
• Confirmed working-tree status and that only documentation files were changed and no schemas/examples were altered.

---

Codex Task