Skip to content

feat(import): conversation-export importers — reconstruct proposals from prior agent history #431

Description

@plind-junior

vouch has register_source / register_source_from_path for citing a source, an Obsidian vault sync for editing approved pages, and a proposed bulk-markdown importer (#321). what it lacks is a path for someone arriving with existing agent history — chat exports, prior-tool memory dumps — to seed a kb from it. today that user starts empty and re-teaches everything by hand, which is the biggest friction on adoption.

this proposes format-specific importers that parse an export dump and emit proposals (claims/pages) into the review queue — same gate, nothing auto-approved.

proposed surface

vouch import <format> <path> [--dry-run] [--max-proposals N]
# formats: chat-json | markdown-vault | memory-export

review gate & scope

every imported item is a proposal — the importer has no path to approve. a human drains the queue exactly as for any other write; the gate is untouched. --max-proposals and dedup keep an unattended import from overwhelming the reviewer. local-first: reads a local file, writes only pending proposals into .vouch/, no network, no hosted component.

acceptance criteria

related: #321 (bulk markdown import — this generalizes it to export formats), #147 (dup warnings), #319 / #320 (other propose-only ingest paths).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions