Implement bidirectional sync v2 for SchLib, PcbLib, SchDoc, and PcbDoc - #10
Draft
akiselev wants to merge 7 commits into
Draft
Implement bidirectional sync v2 for SchLib, PcbLib, SchDoc, and PcbDoc#10akiselev wants to merge 7 commits into
akiselev wants to merge 7 commits into
Conversation
akiselev
force-pushed
the
agent/bidirectional-sync-v2
branch
from
August 16, 2026 04:34
d08faec to
d47cb90
Compare
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.
Summary
altium-spec-langsource/intent boundary with lossless source retention, source IDs, generic top-level resource discovery, and explicitinherit / set / clear / resetsemanticsaltium-syncas a three-way synchronization engine with durable bindings, versioned external baselines, conservative conflict classification, persisted self-contained plans, semantic ECO rendering, and transactional apply helpersaltium-format-opspackageCLI
Plan drift now exits with status 2; errors remain status 1.
Safety properties
applynever re-plansaltium-format, semantically verified, journaled, then committedValidation
cargo fmt --all -- --checkcargo test -p altium-spec-lang -p altium-sync -p altium-clidata/BlankSchlibComponent.SchLibwere skippedaltium-spec-langandaltium-sync; normal no-deps Clippy for CLI integration (the CLI has pre-existing lint debt outside this change)Scope / follow-ups
altium-format-specsemantic materializer behind the new planner boundary; apply correctness is independent of it because document plans carry the exact materialized CFB bytes