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

CHANGELOG.md

@@ -1,45 +1,17 @@
 # Changelog
 
-This changelog records release-line differences that are visible in the checked-in schemas, cards, discovery artifacts, and validation flow.
-
 ## [1.1.0]
 
-### Summary
-
-`v1.1.0` is the current release-candidate Agent Cards line and the canonical repository line under review for tagging. It replaces the older `v1.0.0` working shape with a flatter current-line structure, direct schema bindings, and release validation centered on canonical root artifacts plus a reproducible derivative publish bundle.
-
-### Removed from the current line
-
-- Current-line reliance on `_shared` composition or inherited card structure.
-- Deprecated descriptive fields from the current `v1.1.0` card surface, including `slug`, `display_name`, `description`, `capabilities`, and `meta`.
-- Migration-era assumptions that treated older descriptor-led or packaging patterns as part of the active release path.
-- The stale assumption that every Agent Card entry is x402-routed.
-
-### Structural changes
-
-- `v1.1.0` cards are flat and live directly under `agents/v1.1.0/`.
-- Current cards bind directly to tagged Commons and Commercial schema URLs plus explicit `commandlayer.org` mirror URLs.
-- Commons cards now publish the canonical runtime execute entry, while commercial cards continue to publish semver-pinned x402 routes.
-- Root repository artifacts are the authority surface for the current line, while `dist-pin/agent-cards/v1.1.0/` is a committed derivative bundle that must remain reproducible from the root.
-- Validation for the current line includes schema/card integrity, manifest alignment, class-sensitive entry enforcement, canonical root checksum coverage, and derivative-bundle reproducibility.
-
-### Legacy status
-
-- `v1.0.0` remains in-tree only as an archival compatibility line.
-- Legacy `v1.0.0` materials may still include broader card fields, `_shared` schema structure, and older descriptor or publication assumptions that do not apply to the `v1.1.0` authority path.
-- Legacy artifacts are retained for migration review and compatibility, not as the preferred source for new integrations.
-- The repository now also normalizes archived commons card data to the runtime execute entry so the repo no longer carries mixed commons execution semantics.
-
-### Migration implications
+### Normalization changes
 
-- Treat `v1.1.0` as the authoritative repository line for current integrations and validation; publication claims still wait on release validation.
-- Update tooling that expected `v1.0.0` shared schema paths, broader descriptive card fields, or older descriptor-led publication layout.
-- Expect current cards to expose only the minimal binding fields required by the `v1.1.0` schema.
-- Enforce `entry` by class: commons use `https://runtime.commandlayer.org/execute`, commercial uses `x402://<agent>/<verb>/v1.1.0`.
-- Use the root package commands, especially `npm run validate` and `npm run validate:release`, when reviewing or publishing the current line.
+- Standardized all published schema bindings on `https://commandlayer.org/schemas/...`.
+- Removed the legacy duplicate schema field from cards, schemas, manifests, and validation.
+- Clarified that GitHub is a source repository only, not a published schema identifier surface.
+- Locked commons cards to `https://runtime.commandlayer.org/execute`.
+- Locked commercial cards to `x402://<agent>/<verb>/v1.1.0`.
+- Updated docs, examples, manifests, and validation logic to use the same canonical pattern.
 
 ## [1.0.0]
 
-- Legacy compatibility line retained in-tree for archival and migration purposes.
-- Looser schema and descriptor enforcement, including a permissive descriptor schema and a broader card field set.
-- Descriptor-based and IPFS-era schema references remain part of the legacy line.
+- Retained for archival compatibility.
+- Normalized archived cards to the same canonical `schemas` URL style used elsewhere in the repository.

ONBOARDING.md

@@ -2,57 +2,40 @@
 
 ## Start here
 
-Agent Cards v1.1.0 is the current release-candidate line. Root repository artifacts are authoritative within the repository, but the line should not be represented as fully published until `validate:release` and external bindings are confirmed.
+`v1.1.0` is the current line. The repository enforces one canonical publication model:
 
-- root `agents/v1.1.0/`, `meta/`, `.well-known/`, and `schemas/v1.1.0/` are canonical
-- `meta/manifest.json` is the registry index
-- `.well-known/` is discovery
-- `checksums.txt` is the canonical checksum record for the authoritative root artifacts; the committed derivative `dist-pin/` bundle is verified separately by reproducible rebuild, and publication claims still wait on `validate:release`
-- `agents/v1.0.0/` and `schemas/v1.0.0/` are archival legacy
-- `dist-pin/agent-cards/v1.1.0/` is a committed generated derivative current-line bundle reproducible from the repository root
+- schema bindings resolve through `https://commandlayer.org/schemas/...`
+- the legacy duplicate schema field is removed
+- commons cards use `https://runtime.commandlayer.org/execute`
+- commercial cards use `x402://<agent>/<verb>/v1.1.0`
 
-- `agents/v1.1.0/commons/*.json`
-- `agents/v1.1.0/commercial/*.json`
-- `schemas/v1.1.0/agent.card.schema.json`
-- `schemas/v1.1.0/agent.descriptor.schema.json`
-- `meta/manifest.json` as the canonical registry index
-- `.well-known/agent.json` only as the current discovery pointer
+Canonical current-line surfaces:
 
-Do not add new `_shared` helpers for v1.1.0.
-Do not add descriptive fields to current-line cards; if the detail is not a binding fact, keep it in external documentation or in the linked protocol schemas instead.
+- `agents/v1.1.0/`
+- `schemas/v1.1.0/`
+- `meta/manifest.json`
+- `.well-known/`
+- `checksums.txt`
 
-Remember the execution split when editing cards: commons cards are runtime-first and must use `https://runtime.commandlayer.org/execute`, while commercial cards remain x402-routed with semver-pinned `x402://<agent>/<verb>/...` entries.
+Archival-only surfaces:
 
-## Historical scripts
+- `agents/v1.0.0/`
+- `schemas/v1.0.0/`
+- `dist-pin/agent-cards/v1.0.0/`
 
-The `scripts/archive/` directory is retained for historical reference only. It is not part of the current `v1.1.0` workflow and should not be treated as an active or supported execution path.
+## Editing rules
 
-Use the supported root package scripts and current commands instead: `npm run validate`, `npm run validate:release`, `npm run generate:dist-pin`, `node scripts/generate-checksums.mjs`, and the current validators under `scripts/validate-cards.mjs` and `scripts/validate-release.mjs`.
+1. Keep `$schema`, `$id`, `version`, `schemas`, and `entry` aligned.
+2. Use only canonical hosted schema URLs under `commandlayer.org`.
+3. Never reintroduce the legacy duplicate schema field.
+4. Commons entries must stay on the runtime endpoint.
+5. Commercial entries must stay on the x402 route pattern.
 
-## Legacy / compatibility
+## Supported workflow
 
-- `v1.0.0` is superseded by `v1.1.0`.
-- Some legacy `v1.0.0` references may still use IPFS-era addressing; keep them for archival compatibility, not as the current authority path or a repo-only liveness guarantee.
-- Keep `v1.0.0` artifacts only for archival compatibility.
-- Do not use `v1.0.0` paths in new examples, new release work, or the main update flow.
+- `npm run generate:dist-pin`
+- `node scripts/generate-checksums.mjs`
+- `npm run validate`
+- `npm run validate:release`
 
-## Update flow for the current line
-
-1. edit the canonical root artifact under the correct `v1.1.0` path
-2. keep `$schema`, `$id`, `version`, class-specific `entry`, and schema URLs aligned
-3. update `meta/manifest.json` and related registry/discovery pointers if routing changes or the commons/commercial split changes
-4. rebuild the committed derivative publish bundle at `dist-pin/agent-cards/v1.1.0/` with `node scripts/build-dist-pin.mjs`
-5. regenerate `checksums.txt` with `node scripts/generate-checksums.mjs`
-6. update `RESOLUTION.md`
-7. run `npm run validate`
-8. run `npm run validate:release`
-9. `validate` checks local structure and canonical root checksum coverage; `validate:release` adds external URL resolution and derivative-bundle reproducibility before publication claims
-10. after review, have a maintainer create or move the release tag on the exact validated commit; the release snapshot is the tagged commit plus `checksums.txt`
-
-## Release procedure
-
-- Root artifacts are canonical for the `v1.1.0` line.
-- `dist-pin/agent-cards/v1.1.0/` is committed to git, reproducible from the repository root, always rebuilt from the canonical root artifacts, and never an independent authority surface.
-- `.well-known/` is discovery-only.
-- A maintainer must create or move any release tag after validation; this repo does not imply that an unreleased tag already exists.
-- The release snapshot is defined by the tagged commit together with `checksums.txt`.
+Historical scripts under `scripts/archive/` are preserved only for migration reference.

POLICY.md

@@ -1,26 +1,17 @@
 # Policy — Agent Cards
 
-## Release policy
+## Canonical normalization policy
 
-- `v1.1.0` is the current release-candidate Agent Cards line.
-- Root repository artifacts for `v1.1.0` are canonical.
-- `v1.0.0` is superseded and retained only as an archival compatibility line.
-- Current v1.1.0 work must stay flat and self-contained.
-- Current v1.1.0 work must not reintroduce `_shared`.
+- The repository publishes one schema identifier pattern: `https://commandlayer.org/schemas/...`
+- Raw GitHub schema URLs are not allowed in published repo artifacts.
+- the legacy duplicate schema field is removed and must not be reintroduced.
+- Commons cards must use `https://runtime.commandlayer.org/execute`.
+- Commercial cards must use `x402://<agent>/<verb>/v1.1.0`.
 
-## Surface policy
+## Authority policy
 
-- `meta/manifest.json` is the canonical registry index.
+- Root `v1.1.0` artifacts are canonical.
+- `meta/manifest.json` is the registry index.
 - `.well-known/` files are discovery pointers only.
-- `dist-pin/agent-cards/v1.1.0/` is a derivative current-line bundle for pinning/repinning and reproducible verification.
-- No surface other than the root `v1.1.0` artifacts may be treated as co-equal authority.
-
-## Binding policy
-
-- Commons cards bind directly to the intended Commons v1.1.0 URLs and commandlayer.org mirrors pending release validation.
-- Commercial cards bind directly to the intended Commercial v1.1.0 URLs and commandlayer.org mirrors pending release validation.
-- Stale path styles are non-compliant for the current line.
-
-## Release integrity
-
-Canonical cards, canonical schemas, manifest, discovery pointers, root checksum records, and the derivative dist-pin bundle verification target must move together.
+- `dist-pin/agent-cards/v1.1.0/` is derivative, reproducible, and non-authoritative.
+- `v1.0.0` remains archival-only.