Normalize agent card schema bindings to commandlayer.org and remove schemas_mirror

[GsCommand]

Motivation

• Enforce one canonical agent-card schema pattern across the repo so all cards, docs, manifests, examples and validators reference hosted commandlayer.org schema URLs rather than raw GitHub or mixed mirror fields.
• Make the commons vs commercial execution split explicit and enforced: commons use the runtime execute endpoint and commercial retain semver-pinned x402 routes.
• Remove the legacy duplicate schema field (schemas_mirror) and clean up legacy IPFS/GitHub path variants so validation and publication are unambiguous.

Description

• Canonical schema URLs: all schemas.request / schemas.receipt were normalized to https://commandlayer.org/schemas/<version>/(commons|commercial)/<verb>/<verb>.(request|receipt).schema.json across agents/, meta/, dist-pin/, docs and examples.
• Removed legacy duplicate field: schemas_mirror was removed from current schemas and cards, and schema JSONs were updated so schemas is the single hosted request/receipt binding surface; related schema files no longer require or expose schemas_mirror.
• Entry semantics enforced: commons cards now use https://runtime.commandlayer.org/execute and commercial cards use x402://<agent>/<verb>/v<version>; validators and schema allOf logic updated to enforce this split.
• Manifest and registry descriptors: meta/manifest.json, meta/commons-agent.json, meta/commercial-agent.json, and the dist-pin copy were updated to advertise schema_root under https://commandlayer.org/schemas/... and to use normalized schema_request/schema_receipt values.
• Validators and scripts: scripts/validate-cards.mjs and scripts/validate-release.mjs were rewritten to validate against the canonical schema roots (including introducing SCHEMA_ROOTS), to stop expecting schemas_mirror, and to assert manifest <-> card alignment with the canonical URLs; archive helpers updated for historical migration clarity.
• Documentation and examples: README.md, SPEC.md, ONBOARDING.md, POLICY.md, CHANGELOG.md, RESOLUTION.md, and related docs were edited to state the single canonical pattern (commandlayer.org schemas, no raw GitHub surface, removed duplicate schema field, commons/runtime vs commercial/x402 split).
• Rebuilds and packaging: derivative bundle was rebuilt (dist-pin/agent-cards/v1.1.0/) and checksums.txt regenerated to reflect the normalized root artifacts.

Testing

• node scripts/build-dist-pin.mjs / npm run generate:dist-pin — succeeded and rebuilt the committed derivative bundle.
• node scripts/generate-checksums.mjs — ran and wrote updated checksums.txt; verification (--verify) passed after regeneration.
• npm run validate (current-line validation) — passed: descriptor validation, authoritative card set presence, per-card schema validation, manifest ↔ cards alignment, and checksum verification all succeeded.
• npm run validate:release — local checks (manifest bindings and bundle reproducibility) passed, but external resolution of https://commandlayer.org/schemas/... failed in this environment due to network reachability (ENETUNREACH), so full external-hosted-schema verification could not complete here (this is an environment/network limitation, not a repo-format issue).
• Repository scans and quick regex checks — zero remaining occurrences of raw GitHub schema URLs and zero occurrences of the legacy duplicate schema field in the normalized root artifacts and docs.

If you want, I can produce a short checklist of any remaining files to review manually (edge cases such as archived scripts or external docs) or re-run the release-grade external schema checks once network access to commandlayer.org is available.

---

Codex Task