feat(rendering): add configurable Markdown extensions and fidelity acceptance #15

Open
opened 2026-10-11 10:32:47 +00:00 by KofTwentyTwo · 3 comments
KofTwentyTwo commented 2026-10-11 10:32:47 +00:00 (Migrated from github.com)

Implement reference-configurable highlight/superscript/subscript/underline with published AppKit0.1.0. Refs #1, #4 and draft PR #3. No new dependency.

Independent local worktree now includes immutable rendering options, four enabled-by-default native View toggles, separate persisted fields and sibling-safe merges. Existing Markdig parses the syntax without changing the literal source; AST guards retain protected code/newline and reference caret/tilde whitespace boundaries. Sanitizer permits passive mark/ins while stripping active attributes; selected theme palette styles highlights/underlines.

Validation:408 core tests/100% measured lines,32 focused cases, zero-warning full build and format pass. All16 preference combinations, code/escapes, nested formatting/hostile attributes, frontmatter/source provenance, old JSON and sibling preferences are covered. Evidence:artifacts/markdown-extensions-core-final. One hosted UI case compiles and requires actual glyphs, highlight paint, toggle persistence, source integrity and watched reload; not executed yet. Existing four window corrections remain separately staged. Neither local correction nor extension milestone is committed/pushed: 1Password signing authentication remains pending after two signer failures. No unsigned commit or new hosted result.

  • Configurable native syntax and backward-compatible preferences, local headless verification.
  • Actual native/published58 and installed stable/dev57 with zero failures/skips once both milestones are signed/pushed.
  • Confirm final browser highlighting/underline typography, source/find/print integration and retained screenshots.
  • Audit raw authored-HTML extension edge cases against the pinned reference and address differences.
  • Complete remaining local link/image/render fidelity.

Substantial AI assistance: Codex (GPT-6). No local GUI input, Azure sign-in, merge/tag/release or fabricated review.

Implement reference-configurable highlight/superscript/subscript/underline with published AppKit0.1.0. Refs #1, #4 and draft PR #3. No new dependency. Independent local worktree now includes immutable rendering options, four enabled-by-default native View toggles, separate persisted fields and sibling-safe merges. Existing Markdig parses the syntax without changing the literal source; AST guards retain protected code/newline and reference caret/tilde whitespace boundaries. Sanitizer permits passive mark/ins while stripping active attributes; selected theme palette styles highlights/underlines. Validation:408 core tests/100% measured lines,32 focused cases, zero-warning full build and format pass. All16 preference combinations, code/escapes, nested formatting/hostile attributes, frontmatter/source provenance, old JSON and sibling preferences are covered. Evidence:artifacts/markdown-extensions-core-final. One hosted UI case compiles and requires actual glyphs, highlight paint, toggle persistence, source integrity and watched reload; not executed yet. Existing four window corrections remain separately staged. Neither local correction nor extension milestone is committed/pushed: 1Password signing authentication remains pending after two signer failures. No unsigned commit or new hosted result. - [x] Configurable native syntax and backward-compatible preferences, local headless verification. - [ ] Actual native/published58 and installed stable/dev57 with zero failures/skips once both milestones are signed/pushed. - [ ] Confirm final browser highlighting/underline typography, source/find/print integration and retained screenshots. - [ ] Audit raw authored-HTML extension edge cases against the pinned reference and address differences. - [ ] Complete remaining local link/image/render fidelity. Substantial AI assistance: Codex (GPT-6). No local GUI input, Azure sign-in, merge/tag/release or fabricated review.
KofTwentyTwo commented 2026-10-12 01:56:15 +00:00 (Migrated from github.com)

Pushed signed/DCO 4d34656 to complete a concrete authored-HTML fidelity gap found while checking the pinned Mac source.

  • Four pre-fix core cases reproduced active extension formatting inside authored inline code. Actual code/pre boundaries now preserve literal text and release protection after real closing tags, including across HTML blocks.
  • Enabled extensions now format visible raw HTML block text after source identities/ranges are captured. Tokenizer ranges preserve attributes, comments, code and entity spelling. Metadata retains the original body-only subscript preprocessing boundary. Windows protects all four syntax families in authored code.
  • All642 core tests pass with100% measured line coverage. Complete isolated-output Release build has zero warnings/errors; full formatting and applicable signed/DCO/security/workflow hooks pass. Original MIT attribution retained.
  • Extended the existing real browser preference case with distinct inline/block code peers and raw-heading labels. It is also included in the focused gate; new hosted runtime is pending, with all prior cases/assertions/deadlines retained.

The preceding CI38190828814 is terminal success: native/published106/106, focused26/26, installed stable/dev105/105 each, zero failures/skips. Actual full Settings screenshots and registration/coexistence/update TRXs/JSON are retained. Those results predate this new renderer correction.

Shared signing31 merge/publication approval remains pending; no response assumed. Actual Azure resource/profile/identity and shipped MarkdownViewr signatures, Windows chooser/Explorer, owner design feedback and genuine final-head review remain required. No release, shared merge, Azure login retry or local GUI input. Substantial AI assistance: Codex.

Pushed signed/DCO `4d34656` to complete a concrete authored-HTML fidelity gap found while checking the pinned Mac source. - Four pre-fix core cases reproduced active extension formatting inside authored inline code. Actual code/pre boundaries now preserve literal text and release protection after real closing tags, including across HTML blocks. - Enabled extensions now format visible raw HTML block text after source identities/ranges are captured. Tokenizer ranges preserve attributes, comments, code and entity spelling. Metadata retains the original body-only subscript preprocessing boundary. Windows protects all four syntax families in authored code. - All642 core tests pass with100% measured line coverage. Complete isolated-output Release build has zero warnings/errors; full formatting and applicable signed/DCO/security/workflow hooks pass. Original MIT attribution retained. - Extended the existing real browser preference case with distinct inline/block code peers and raw-heading labels. It is also included in the focused gate; new hosted runtime is pending, with all prior cases/assertions/deadlines retained. The preceding [CI38190828814](https://github.com/KofTwentyTwo/MarkdownViewr.Windows/actions/runs/38190828814) is terminal success: native/published106/106, focused26/26, installed stable/dev105/105 each, zero failures/skips. Actual full Settings screenshots and registration/coexistence/update TRXs/JSON are retained. Those results predate this new renderer correction. Shared signing31 merge/publication approval remains pending; no response assumed. Actual Azure resource/profile/identity and shipped MarkdownViewr signatures, Windows chooser/Explorer, owner design feedback and genuine final-head review remain required. No release, shared merge, Azure login retry or local GUI input. Substantial AI assistance: Codex.
KofTwentyTwo commented 2026-10-12 02:05:14 +00:00 (Migrated from github.com)

Fresh exact 4d34656 CI38193736344 focused acceptance passes27/27, zero failures/skips. Actual retained TRX confirms the extended Extensions_NativePreferences browser case: distinct authored inline/block code stays literal, raw-heading formatting responds to independent preferences, and existing actual paint/source/reload assertions pass. Core/build/format/scripts/security pass. Full native and published/installed acceptance remain live; no production signing or release claim.

Fresh exact `4d34656` [CI38193736344](https://github.com/KofTwentyTwo/MarkdownViewr.Windows/actions/runs/38193736344) focused acceptance passes27/27, zero failures/skips. Actual retained TRX confirms the extended `Extensions_NativePreferences` browser case: distinct authored inline/block code stays literal, raw-heading formatting responds to independent preferences, and existing actual paint/source/reload assertions pass. Core/build/format/scripts/security pass. Full native and published/installed acceptance remain live; no production signing or release claim.
KofTwentyTwo commented 2026-10-12 02:48:22 +00:00 (Migrated from github.com)

Pushed signed/DCO b542dcd to complete the remaining local-document link behavior. Actual user-initiated Markdown/text links in the current namespace open native reader windows, preserve the source reader and focus a matching already-loaded reader. Once-decoded type/path checks and the opened target handle enforce the source physical folder. The new reader retains that root for every manual/watcher/frontmatter/extension reload, preventing a later junction from reading outside content. No linked target is dispatched through an arbitrary OS shell/protocol.

Validation: all662 core tests pass with100% measured line coverage; all10 actual document/image filesystem cases pass, including linked outside-root/junction denial; full isolated Release has zero warnings/errors; format and signed/DCO/security/workflow hooks pass. A fixture disposal failure was corrected by removing its owned junction explicitly before teardown.109 UI cases are discovered. The new physical-link/duplicate/watcher/junction-reload regression is included in focused CI; fresh runtime remains required, with every previous case/assertion/deadline retained.

Preceding CI38193736344 is terminal success: focused27/27, native/published106/106, installed stable/dev105/105 each, zero failures/skips. Actual renderer/code/source and simultaneous channel lifecycle TRXs/JSON retained. These unsigned fixtures do not establish production signing or actual Windows chooser/Explorer selection.

Shared signing31 approval is unanswered; actual Azure resource/profile/identity, final shipped signatures, owner design/scaling and genuine final-head review still gate release. No shared merge, Azure login retry, local GUI input, owner preview change, release tag or publication. Substantial AI assistance: Codex.

Pushed signed/DCO `b542dcd` to complete the remaining local-document link behavior. Actual user-initiated Markdown/text links in the current namespace open native reader windows, preserve the source reader and focus a matching already-loaded reader. Once-decoded type/path checks and the opened target handle enforce the source physical folder. The new reader retains that root for every manual/watcher/frontmatter/extension reload, preventing a later junction from reading outside content. No linked target is dispatched through an arbitrary OS shell/protocol. Validation: all662 core tests pass with100% measured line coverage; all10 actual document/image filesystem cases pass, including linked outside-root/junction denial; full isolated Release has zero warnings/errors; format and signed/DCO/security/workflow hooks pass. A fixture disposal failure was corrected by removing its owned junction explicitly before teardown.109 UI cases are discovered. The new physical-link/duplicate/watcher/junction-reload regression is included in focused CI; fresh runtime remains required, with every previous case/assertion/deadline retained. Preceding [CI38193736344](https://github.com/KofTwentyTwo/MarkdownViewr.Windows/actions/runs/38193736344) is terminal success: focused27/27, native/published106/106, installed stable/dev105/105 each, zero failures/skips. Actual renderer/code/source and simultaneous channel lifecycle TRXs/JSON retained. These unsigned fixtures do not establish production signing or actual Windows chooser/Explorer selection. Shared signing31 approval is unanswered; actual Azure resource/profile/identity, final shipped signatures, owner design/scaling and genuine final-head review still gate release. No shared merge, Azure login retry, local GUI input, owner preview change, release tag or publication. Substantial AI assistance: Codex.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/MarkdownViewr.Windows#15