fix(import): preserve missing fragment diagnostics - #25
Open
0dust wants to merge 3 commits into
Open
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.
Summary
Missing Obsidian heading and block warnings now survive conversion into portable Markdown.
okfy validate, Inspector, and MCP therefore report the samemissing_wikilink_fragmentwarnings as the original import instead of silently losing them.Generated bundles persist only the warning provenance that Markdown cannot reconstruct. Each warning is bound to the exact emitted Markdown link and its import-time multiplicity, so an unrelated link cannot keep a removed conversion warning alive. Validation conservatively suppresses stale or ambiguous provenance and still clears warnings after real target repairs.
Plain and JSON CLI presentation now encode C0, DEL, and C1 terminal controls without changing the underlying diagnostic values. This blocks ANSI, OSC, BEL, and C1 injection from untrusted provenance while preserving valid writer-produced paths and JSON round trips.
Malformed or unsafe metadata remains non-fatal and produces one actionable validation warning.
Validation
pnpm test— 255 tests passed from a clean detached checkoutpnpm typecheckpnpm lintpnpm buildnpm pack --ignore-scripts --dry-run --jsonRelated