[GH-ISSUE #51] Add validated evidence bundle import and export tools #37

New issue

Closed

opened 2026-10-15 18:20:19 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:20:19 +00:00

Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/51

Problem

Evidence cannot survive a process boundary or be independently verified and reused.

Outcome

Add export_evidence_bundle and import_evidence_bundle with identical CLI/MCP semantics.

Public contract

Export writes or returns a schema-versioned deterministic bundle containing manifests and Evidence v2 records.
Import accepts a local JSON path, parses unknown input strictly, recomputes every evidence ID, and merges non-conflicting records into the session ledger.
Path inputs are canonicalized; output overwrite requires explicit opt-in.
Imported content is data only and is never executed.

Safety

Bound file size, record count, string lengths, and nesting depth. Reject path traversal, symlink escape from an explicitly selected output root, malformed IDs, unsupported versions, and conflicting duplicate IDs. Never serialize arbitrary environments or secret values.

Acceptance criteria

Export/import round trips byte-stably.
Tampering with any semantic evidence field is rejected.
Identical duplicates deduplicate; conflicting duplicates fail atomically.
Partial import never mutates the ledger.
Tool annotations declare filesystem reads/writes accurately.
Package verification exercises both surfaces.

Dependencies

Parent: #48. Requires Evidence v2 and the session ledger.

Non-goals

Remote URLs, databases, signing infrastructure, or automatic upload.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/51 ## Problem Evidence cannot survive a process boundary or be independently verified and reused. ## Outcome Add `export_evidence_bundle` and `import_evidence_bundle` with identical CLI/MCP semantics. ## Public contract - Export writes or returns a schema-versioned deterministic bundle containing manifests and Evidence v2 records. - Import accepts a local JSON path, parses unknown input strictly, recomputes every evidence ID, and merges non-conflicting records into the session ledger. - Path inputs are canonicalized; output overwrite requires explicit opt-in. - Imported content is data only and is never executed. ## Safety Bound file size, record count, string lengths, and nesting depth. Reject path traversal, symlink escape from an explicitly selected output root, malformed IDs, unsupported versions, and conflicting duplicate IDs. Never serialize arbitrary environments or secret values. ## Acceptance criteria - Export/import round trips byte-stably. - Tampering with any semantic evidence field is rejected. - Identical duplicates deduplicate; conflicting duplicates fail atomically. - Partial import never mutates the ledger. - Tool annotations declare filesystem reads/writes accurately. - Package verification exercises both surfaces. ## Dependencies Parent: #48. Requires Evidence v2 and the session ledger. ## Non-goals Remote URLs, databases, signing infrastructure, or automatic upload.

bsakaguchi

2026-10-15 18:20:19 +00:00

closed this issue
added the
area: server

area: cli

P1: high

area: mcp

roadmap

enhancement
labels

bsakaguchi commented

2026-10-15 18:20:20 +00:00

Author

Owner

@morluto commented on GitHub (Jul 17, 2026):

Implemented on main. export_evidence_bundle and import_evidence_bundle are canonical session tools with CLI/MCP wiring, strict Evidence v2 parsing, deterministic serialization, canonical authorized file handling, overwrite policy, atomic merge/conflict behavior, and declared tool effects. Session, artifact MCP, contract snapshot, bundle, and package verification cover the public surfaces.

@morluto commented on GitHub (Jul 17, 2026): Implemented on main. `export_evidence_bundle` and `import_evidence_bundle` are canonical session tools with CLI/MCP wiring, strict Evidence v2 parsing, deterministic serialization, canonical authorized file handling, overwrite policy, atomic merge/conflict behavior, and declared tool effects. Session, artifact MCP, contract snapshot, bundle, and package verification cover the public surfaces.

bsakaguchi referenced this issue

2026-10-15 18:20:33 +00:00

[GH-ISSUE #65] Add structural and visual browser comparison #53

bsakaguchi referenced this issue

2026-10-15 18:20:33 +00:00

[GH-ISSUE #67] Map historical source modules to current bundles #54

bsakaguchi referenced this issue

2026-10-15 18:21:47 +00:00

[GH-ISSUE #268] Build an evidence-backed reconstruction workspace and coverage closure workflow #157

bsakaguchi referenced this issue

2026-10-15 18:22:25 +00:00

[GH-ISSUE #360] Build authoritative multi-provider/version fixture closure #207