Normalize commons cards to runtime execute and enforce class-specific entry semantics

[GsCommand]

Motivation

• Remove the stale universal-x402 assumption and make the runtime vs x402 split explicit so commons cards are runtime-first and commercial cards remain x402-routed.
• Ensure docs, schema, validators, examples, manifests and derived artifacts are fully consistent with the intended invocation model.

Description

• Enforce class-specific entry semantics in schema and validation: commons cards must have entry = https://runtime.commandlayer.org/execute and commercial cards must match x402://<ens>/<verb>/v1.1.0 (schema allOf rules added and validator logic updated).
• Normalize every commons card (both v1.1.0 and archived v1.0.0) to use the runtime execute URL and update their updated_at timestamps, and update manifest/dist-pin metadata to reflect commons runtime entries while preserving commercial x402 entries.
• Update repository documentation and guidance (README, SPEC, ONBOARDING, CHANGELOG, RESOLUTION) to describe the split and the class-sensitive semantics of entry, and adjusted source URL formatting for clarity.
• Regenerated derived artifacts and integrity files to match the canonical root changes (rebuild dist-pin, regenerated checksums.txt) and updated validator expectations (scripts/validate-cards.mjs).
• Files changed include (high-level): schemas/v1.1.0/agent.card.schema.json, schemas/v1.0.0/_shared/agent.card.base.schema.json, scripts/validate-cards.mjs, agents/v1.1.0/commons/*.json, agents/v1.0.0/commons/*.json, meta/manifest.json, meta/commons-agent.json, meta/commercial-agent.json, dist-pin/agent-cards/v1.1.0/**, README.md, SPEC.md, ONBOARDING.md, CHANGELOG.md, RESOLUTION.md, and checksums.txt.

Testing

• Ran npm run generate:dist-pin and the derivative bundle was rebuilt successfully. (passed)
• Regenerated checksums.txt with node scripts/generate-checksums.mjs and checksum verification passed. (passed)
• Ran local validation npm run validate (current-line + checksum checks) and npm run validate:legacy (v1.0.0 legacy checks), both completed successfully and confirmed manifest/cards/schema alignment with class-sensitive entry rules. (passed)
• Ran npm run validate:release (release-grade validation) which performed local checks and attempted external schema resolution; local checks passed but external network resolution of upstream raw.githubusercontent.com schema URLs failed (network/external availability), so the release-grade external fetch gate remains blocked until upstream sources/mirrors are reachable. (partial — local pass, external fetch failures)

---

Codex Task