docs: align v1.1.0 release posture messaging

[GsCommand]

Motivation

• Remove stale "candidate" / "pre-release" framing so the repository consistently presents v1.1.0 as the current canonical in-repo line while preserving factual provenance status.
• Keep v1.0.0 clearly marked as the historical pinned release and avoid inventing any new provenance claims.
• Make minimal, restrained wording edits across governance/provenance docs and package metadata without changing schemas, examples, checksums, or version numbers.

Description

• Replaced candidate/pre-release language with restrained, factual wording that documents schemas/v1.1.0/commons as the current canonical in-repo line and retains CID publication as pending in repository metadata.
• Updated the README badge and integrity notice to remove "candidate" wording and to present CID status as PENDING/publication metadata.
• Aligned governance and provenance documents and manifest metadata by removing phrases such as "Active In-Repo Pre-Release Candidate" and similar framing, replacing them with "current canonical in-repo line" or equivalent where appropriate.
• Files modified: README.md, GOVERNANCE.md, COMPLIANCE.md, ONBOARDING.md, SPEC.md, SCHEMAS.md, SECURITY.md, SECURITY_PROVENANCE.md, RESOLUTION.md, and manifest.json (no schema/example files were edited).

Testing

• Ran npm install and the command completed successfully with dependencies installed.
• Ran npm run validate (which executes validate:schemas and validate:examples) and all schema compilation and example validations completed successfully.
• Ran npm run validate:schemas and npm run validate:examples individually and both succeeded without errors.
• Ran npm run checksums:verify and all listed schema checksums verified as OK.
• Performed a case-insensitive grep for stale terms and verified that remaining matches are either unrelated schema text or intentional factual provenance wording (no stale candidate/pre-release framing for v1.1.0 remains).

---

Codex Task