T-5JMP-backupfilepreview-render-snapshot-notes-through-mdviewer
State: closed/done · Impact: medium · Complexity: small
BackupFilePreview.vue shows markdown and text as an escaped <pre>, so a note inside a snapshot
reads as raw markup. The retired dashboard rendered it, chipped wikilinks, and split frontmatter
into a properties panel. @sksizer/markdown-ui’s MdViewer restores that, as polish, fitness and
agent-chat already use it.
Proposed
Section titled “Proposed”experiences/backup depends on @sksizer/markdown-ui. Markdown files render through MdViewer,
with frontmatter shown as properties and wikilinks shown as labelled, non-navigating chips. Plain
text stays a <pre>. Images and the binary/oversize stub are unchanged.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: A markdown note at a snapshot renders headings, lists and links, not raw markup.
- AC-2: Its frontmatter appears as properties, not as a YAML block in the body.
- AC-3:
wikilinksrender as chips, and neither them nor ordinary Markdown links in a snapshot preview navigate the app. - AC-4: Focused automated coverage verifies rendered Markdown, preserved frontmatter, and inert snapshot-preview links. Storybook enrollment is out of scope until this experience has a Storybook host.
Out of scope
Section titled “Out of scope”- The desktop window backdrop B-425L also lists; the shell owns the window frame.
- Navigating wikilinks to other files in the same snapshot.
Dependencies
Section titled “Dependencies”- None.