ENGRAM 0.6.0 — Evidence reports

ENGRAM 0.6.0 — Evidence reports

Export the findings you are reviewing as a Markdown report or CSV table, directly from the Trace desk or CLI.

• Choose the complete filtered queue, bookmarked findings or the entire open case. An empty scope cannot silently export everything.
• Keep reports minimal by default; full recorded paths, evidence details and analyst notes are three separate opt-ins.
• Save through the native destination picker and keep a receipt with the finding count, byte count and SHA-256 checksum.
• Export the current review while preserving Unsaved review. Use Save case to retain a restorable observation.
• Use engram export for saved cases, with explicit finding IDs, bookmarked selection and optional JSON receipts.

engram export ./sample.engram.json --out ./findings.report.md
engram export ./sample.engram.json --bookmarked --format csv --out ./bookmarks.report.csv

Reports are bounded to 10,000 known findings and 16 MiB. Markdown escapes imported markup. CSV uses a UTF-8 BOM, quoted fields, CRLF records and formula protection; identifiers that cannot be preserved safely in CSV require Markdown. Field selection is not universal anonymization: reports remain sensitive local artifacts.

Verification records cross-platform Rust/backend checks and frontend validation. Native Linux evidence includes six startup views and a separate real-picker Markdown/CSV exercise. Platform package build provides fresh Windows x64, macOS Apple Silicon and Linux x64 archives. Exact source identities, checksum verification and evidence scope are recorded in BUILD-INFO.txt.

Windows requires WebView2; Linux requires GTK 3 and WebKitGTK 4.1. These packages are unsigned; the macOS app is not notarized. Extract the archive before opening the app.

Case schema remains 1 and existing saved cases open without conversion. Reports are separate output artifacts. Reader coverage and recovery capabilities are unchanged.