Skip to content

chore(release): v0.11.1#426

Merged
jithinraj merged 2 commits intomainfrom
chore/release-v0111
Feb 23, 2026
Merged

chore(release): v0.11.1#426
jithinraj merged 2 commits intomainfrom
chore/release-v0111

Conversation

@jithinraj
Copy link
Member

@jithinraj jithinraj commented Feb 23, 2026

Summary

  • MCP carrier e2e smoke test (release gate): full round-trip from receipt issuance through _meta carrier attachment, extraction, and offline verification
  • Version bump to 0.11.1 across all 65 workspace packages
  • CHANGELOG entry for Evidence Carrier Contract, A2A mapping, MCP/ACP/UCP/x402 carrier adoption
  • Normative specs: EVIDENCE-CARRIER-CONTRACT.md, A2A-RECEIPT-PROFILE.md, MCP-EVIDENCE-PROFILE.md
  • AGENTS.md: updated MCP section to v0.11.1 carrier format, added A2A metadata carrier example
  • Registry updates: a2a, ucp, stripe entries (removed duplicate UCP)

Two commits (surgically revertable):

  1. test(smoke): MCP carrier e2e round-trip - 5 tests covering full flow, tampered receipt_ref (DD-129), legacy format, field preservation
  2. chore(release): v0.11.1 - version bump + CHANGELOG + specs + AGENTS.md + all alignment fixes

Spec alignment fixes (squashed into release commit):

  • Removed non-canonical header casing literal (guard failure fix)
  • HTTP transport is embed-only in v0.11.1; reference mode deferred
  • MCP legacy wording covers both _meta["org.peacprotocol/receipt"] and top-level peac_receipt
  • RFC 9711 (EAT) analogy softened (PEAC receipt_ref is not derived from EAT nonce)
  • DD-129 enforcement scope: producer computes correctly before sync attach, consumer verifies via async extractAsync
  • Node >= 20 runtime capability vs >= 22 dev baseline clarified
  • Fixture valid-http-reference.json description clarifies schema-validity vs transport-attachability
  • Removed duplicate UCP entry in registries.json

Gate results: 185 test files, 4456 tests passing. Build (78 targets), lint, typecheck, 26/26 guards, planning leak check, format check, fixture validation, version sync, publish list all green.

Test plan

  • pnpm build && pnpm lint && pnpm typecheck:core && pnpm test
  • ./scripts/guard.sh && ./scripts/check-planning-leak.sh
  • node scripts/check-version-sync.mjs
  • node scripts/validate-fixtures.mjs
  • pnpm format:check
  • bash scripts/check-publish-list.sh
  • CI passes (Build, Lint, Test)
  • After merge: git tag v0.11.1 + push (triggers publish workflow)

Full flow: issue -> computeReceiptRef -> attachReceiptToMeta ->
extractReceiptFromMetaAsync -> verifyLocal. No network calls, no clock
dependencies; uses deterministic key material for reproducible failures.

Tests:
- Full round-trip with offline verification
- Tampered receipt_ref detection (DD-129)
- Legacy org.peacprotocol/receipt extraction with receipt_ref computation
- Round-trip carrier field preservation
- Null return for missing _meta

Also re-enables tests/smoke in vitest config and adds @peac/mappings-mcp
alias for root-level test resolution.
Evidence Carrier Contract + A2A Mapping release.

- Bump all 65 workspace packages to 0.11.1
- CHANGELOG entry for Evidence Carrier Contract, A2A mapping,
  MCP _meta carrier, ACP/UCP/x402 carrier adoption, discovery profile
- AGENTS.md: v0.11.1 carrier format, A2A metadata example
- Normative specs: EVIDENCE-CARRIER-CONTRACT.md, A2A-RECEIPT-PROFILE.md,
  MCP-EVIDENCE-PROFILE.md
- Registry: a2a, ucp, stripe entries (version 0.10.0)
- Spec fixes: embed-only HTTP in v0.11.1, MCP dual-legacy wording,
  softened RFC 9711 analogy, DD-129 producer/consumer split,
  Node >= 20 runtime vs >= 22 dev baseline, fixture description clarity,
  removed duplicate UCP registry entry

PRs: #414-#421 (8 merged)
Design decisions: DD-124 through DD-131
@jithinraj jithinraj merged commit a0f98b9 into main Feb 23, 2026
9 checks passed
@jithinraj jithinraj deleted the chore/release-v0111 branch February 24, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant