Clarify v1.1.0 HTTPS hosting status and separate IPFS CID pinning state

[GsCommand]

Motivation

• Make repository metadata and prose truthful about the current live state: v1.1.0 schema $id URLs under https://commandlayer.org/schemas/v1.1.0/ are live, while IPFS / CID publication remains unrecorded in the repo.
• Remove stale “publication not yet guaranteed / working line” wording that incorrectly conflated HTTPS hosting with IPFS pinning.
• Preserve provenance integrity by not inventing or adding any CID or signature artifacts that do not exist in the repo.

Description

• Updated metadata to represent HTTPS hosting and IPFS pinning as distinct: manifest.json description and status fields were changed and active_release.pin_status was set to https-published-ipfs-pending while keeping schemas_cid: "PENDING".
• Tightened spec/provenance wording so HTTPS $id resolution is described as live for v1.1.0 while IPFS CID publication is still explicitly pending; changes applied to SPEC.md, README.md, SECURITY_PROVENANCE.md, SCHEMAS.md, COMPLIANCE.md, GOVERNANCE.md, and RESOLUTION.md (notable token replacements: current-working-line → current-canonical-https-hosted and similar phrasing to reference HTTPS-hosted vs IPFS pinning).
• Small package metadata update in package.json to reflect the HTTPS-hosted line wording; no schema files, schema semantics, or version numbers were modified.
• Files changed: manifest.json, SPEC.md, README.md, SECURITY_PROVENANCE.md, COMPLIANCE.md, RESOLUTION.md, SCHEMAS.md, GOVERNANCE.md, and package.json.
• Intentionally NOT changed: no v1.1.0 CID was added or fabricated, no schema content or $id values were altered, and historical v1.0.0 pinned-release metadata (including its CID) was preserved exactly.

Testing

• Ran npm run validate:schemas and npm run validate:examples via npm run validate, and the schema compilation succeeded (All 45 schemas compiled successfully).
• Example validation completed successfully (All example validations completed) and the repository validation pipeline reported no failures from the edits.
• Verified locally via npm run validate that documentation/manifest edits did not break schema or example validation.

---

Codex Task