3 Commits (feat/md-sourcemaps)

Author	SHA1	Message	Date
Divyansh Singh	5f8677e53f	fix(markdown): give stitched lines no position instead of a wrong one ... An output line assembled from more than one source (page text on the same line as an include directive) matches no single physical line, so any position on it names the wrong place. Rebasing trusted such lines' file attribution and rewrote the page's own relative links against the included file's directory when a mid-line include came first; columns on splice tail lines were measured against the expanded text. Links and attributes on spliced lines now carry no location at all, and the tail line after a mid-line include is marked spliced too. Also from the adversarial review: omit the column when the inline text appears more than once in its raw line (repeated table cells) instead of guessing the first occurrence; give a fully-elided source an identity line map instead of letting resolve() throw; store segment files posix-style so Windows builds compare and report one separator; offset alert paragraph_open attrs past the removed marker like their inline content; keep the page's line map and dev attrs out of excerpt renders; name the including page in dead-link reports for included files (deadLinks[].via); and harden the dev click handler (relative-base endpoint, fetch failure). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	ecd5a49a2a	fix(markdown): keep positions exact in github alert bodies ... The vp_github_alerts rule strips the alert marker from the first inline token's content before inline parsing, shifting every position in the body up by the marker line and breaking column re-alignment. The rule now records how many lines it removed (token.meta.vpLineOffset) and the source positions plugin adds them back. Also re-emit the source-location attribute from the remaining hand-built renderers that dropped it (::: v-pre and ::: raw wrappers, math blocks), and pop it off fence tokens in preWrapper so a custom highlight falling back to markdown-it's default fence renderer cannot emit it twice. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	6886a95953	feat: jump from rendered markdown to its source in dev ... Page renders in dev stamp block elements with data-v-inspector attributes carrying the cwd-relative source file, line and column — include-aware through the line map, so content pulled in via `<!-- @include -->` points at the included file. The attribute is the one vite-plugin-vue-inspector's overlay reads off arbitrary elements, so the Vue DevTools component inspector jumps to the markdown source out of the box; a ~50-line dev-only client handler additionally makes alt+click open the editor through Vite's built-in /__open-in-editor endpoint with no plugins installed (#4293). Fence wrappers, code groups and GitHub alerts re-emit the attribute from their hand-built markup; builds, the local search index and content loader output are env-gated and stay byte-identical. Opt out with `markdown.sourceAttrs: false`. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago