chore(deps): update agentrust-trace requirement from >=0.3.0 to >=0.4.0

[dependabot]

Updates the requirements on agentrust-trace to permit the latest version.

Release notes

Sourced from agentrust-trace's releases.

TRACE v0.4.0

Add azure-cvm-sev-snp platform (vTPM-rooted SEV-SNP for Azure confidential VMs).

Changelog

Sourced from agentrust-trace's changelog.

[0.4.0]

Added

• azure-cvm-sev-snp platform — Azure confidential VMs run AMD SEV-SNP behind a Hyper-V paravisor: the SNP report is read from the vTPM (the guest does not control REPORT_DATA), so the runtime binding rides a vTPM AK-signed quote rather than the SNP report_data. Given its own runtime.platform value (distinct from amd-sev-snp) so a consumer keying on runtime.platform knows the root of trust is vTPM-rooted, not direct-silicon. Added to the RuntimeInfo model and the JSON schema enum. Hardware-validated on a live Azure SEV-SNP VM via cMCP.

• delegation (optional object): the A2A profile delegation-link block, carrying parent_record_hash (digest of the parent hop's Trust Record) and credential_id (the delegation credential this hop acted under). A chain of records linked this way forms an offline-verifiable delegation DAG. Backward-compatible: existing records without delegation remain valid. This is a MINOR (additive) change and the foundation of the forthcoming A2A profile; A2A is now stable at v1.x, clearing the prior blocker.

---

[0.3.0] — 2026-06-30

Security

• verify_record now requires an explicit trusted key. Self-verification from the embedded cnf.jwk is no longer the default; use allow_embedded_key=True to opt in.
• Verification enforces freshness (iat / max_age_seconds, default 24h) and an optional expected_nonce. JWK kty / crv are validated.

Breaking

• BREAKING: Canonicalization is now RFC 8785 (JCS). Trust records are NOT cross-verifiable with 0.2.0 (the prior json.dumps canonicalization was non-conformant).

---

[0.1.0] — 2026-06-23

Initial public draft. Announced at Confidential Computing Summit, San Francisco.

Specification

• Trust Record logical schema (§3.1): subject, model, runtime, policy, data_class, tool_transcript, build_provenance, appraisal, transparency, cnf
• Wire format (§3.2): EAT/JWT and CBOR-COSE envelopes; profile URI tag:agentrust.io,2026:trace-v0.1
• Signing and key management (§3.2.1): ES256/ES384/EdDSA; four-layer key hierarchy; hash agility; revocation
• Verification protocol (§3.3): five-step offline verification, no issuer callback
• Standards composition (§4): RATS/EAT, SLSA, SPIFFE, SCITT, EAR, MCP, A2A, AIBOM, C2PA
• Hardware roots (§4.2): NVIDIA H100/Blackwell, Intel TDX, AMD SEV-SNP, Azure MAA, GCP Confidential Space, AWS Nitro
• Reference implementation (§5): cMCP Phase 1–3 roadmap

Schema

• schema/trace-claim.json: JSON Schema (draft/2020-12) for Trust Record validation

Examples

• examples/amd-sev-snp.json: AMD SEV-SNP Trust Record
• examples/intel-tdx.json: Intel TDX Trust Record
• examples/nvidia-h100.json: NVIDIA H100 Confidential Computing Trust Record

Open questions

Seven open questions requiring community input before v0.2 are documented in §7 of the spec.

... (truncated)

Commits

• 1dd52be feat: add azure-cvm-sev-snp platform (v0.4.0) (#105)
• 6c1cb93 test: add action receipt conformance fixtures (#101)
• 1dd2086 docs: add PRIVACY.md (no data collected; local processing) (#100)
• c0a20ad chore(deps): update mkdocstrings requirement from >=1.0.4 to >=1.0.6 (#99)
• 5ab3781 chore(deps): update mkdocs-material requirement from >=9.5 to >=9.7.6 (#88)
• e8c2d7b chore(deps): update mkdocstrings requirement from >=0.25 to >=1.0.4 (#87)
• 2dcdfd2 chore(deps): bump actions/checkout from 4 to 7 (#82)
• d8b5c87 chore(deps): bump actions/github-script from 7.0.1 to 9.0.0 (#83)
• 37b38c8 chore(deps): bump actions/download-artifact from 4 to 8 (#84)
• b6067c0 chore(deps): bump actions/upload-artifact from 4 to 7 (#85)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)