Repository navigation
feat: verify native imports with durable migration records - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Real imports previously had no durable publication intent, and destination observation depended on title handling. Every real import/transfer now records intent before native installation, observes acknowledged publication and either completes its record or returns typed reconciliation evidence without retrying the importer. Convert, dry-run and informational proposals do not create a ledger.
Captured source bytes feed a strict native auditor and an independent expected projection for Claude, Codex and OpenCode v2. Parser fidelity remains separate from raw coverage; unknown observed fields cannot inherit a verified expectation. Namespace qualification requires issued loader/capture evidence. Source and target checkpoints remain independent, with unproven native turn boundaries and no in-place update capability.
The CLI/TUI preserve existing success JSON and expose uncertain outcomes with native_not_started, attempted_unknown or acknowledged state, reserved identity and evidence availability. Tests cover cancellation during intent fsync, changed content with restored filesystem metadata, namespace substitution, partial acknowledgement and zero native calls before durable intent. Release metadata is 0.12.0.dev6; optional dependencies remain unchanged.
Validation:
Independent review is recorded locally; CI must pass on this exact head before merge. Native session update, continuity assessment and the web dashboard remain subsequent milestones.