Add EPI Recorder: TRACE Level 0 record-producer + WCM attestation-source - #148
Add EPI Recorder: TRACE Level 0 record-producer + WCM attestation-source#148mohdibrahimaiml wants to merge 2 commits into
Conversation
…testation-source. Request Verified tier. Reproduction is pip install epi-recorder==4.4.1 and trace-tests verify --level 0.
|
🔴 Contributor Check: HIGH
Automated check by AgenTrust Contributor Check. |
|
@imran-siddique — EPI Recorder 4.4.1 is tagged and on GitHub Releases. This PR is the TRACE Level 0 + WCM |
b58edca to
f839295
Compare
|
Updating this listing from 4.4.1 to 4.4.3. While auditing seal completeness we found that sealed step content was truncated at 2000 characters through 4.4.1 — artifacts sealed on those versions are not full transcripts. 4.4.3 seals full payloads, truncates only in the viewer, and records |
|
4.4.3 is now on PyPI; CI is green. |
Reproduction, digest, KNOWN_LIMITATIONS, and CI pin move off 4.4.1. origin.producer is epi-recorder/4.4.3.
1fe8a93 to
5c4af35
Compare
Summary
Adds
integrations/epilabs-epi-recorder/for epi-recorder 4.4.3.record-producer,trace_conformance_level: 0(software-only log-import). L1/L2 are not claimed (TR-RTE-001,TR-RTE-004).attestation-source(no WCM conformance level; we do not verify a custody manifest).iter_errors=0,origin.producer=epi-recorder/4.4.3):sha256:d17f305b7f3e9950614df5ae6810b86b111c6a9aa23c37c71cac5dd503da591f.Verified tier requested
Please evaluate for Verified. Reproduction (released packages only):
Also:
tool_transcript.hash == sha256(.epi); tamper ->InvalidSignature.Release artifacts: https://github.com/mohdibrahimaiml/epi-recorder/releases/tag/v4.4.3
Seal completeness (truncation through 4.4.1): https://github.com/mohdibrahimaiml/epi-recorder/blob/v4.4.3/docs/KNOWN_LIMITATIONS.md#historical-step-content-truncation-through-441
Marketplace catalog regenerated via
python scripts/generate_marketplace_catalog.pyon the original listing; this commit updates yaml/README/CI pin only.Links checked