MarkdownViewr.Windows/docs/SESSION-STATE.md

Session State

Updated: 2026-10-13

Release source and verification

Stable1.0.2 and dev1.0.2-beta.1 EXE/ZIP releases are public and immutable at source18d8ae950cab445672d216d387a956b964d2c6c1, builder083d903. Actual downloaded signatures/publisher/trust/timestamps, package payloads, checksums, CycloneDX SBOM attestations, source/builder provenance and updater feeds verify. Production runs38392743207 and38392743312 succeeded. Failed older refs remain.

The maintainer renewed the MSI request on2026-10-13; earlier MSI deferral is superseded. Prepare signed per-user MSI alongside EXE/ZIP for stable/dev1.0.3. MSI payload verification and focused native install/launch/uninstall must pass before publication. Source behaviors, dependencies and Azure trust are unchanged.

Prevent duplicate release test passes by requiring the exact complete Git tree of a genuinely merged main PR whose latest required technical checks all passed under their required provider identities. Reject unverified source signatures, different trees, missing/failed/pending checks and API failures. Reuse real CI proof; do not post fabricated results or weaken branch protection. Fresh release build/core coverage, signing and installer/distribution checks remain required.

The owner explicitly authorized finishing releases without further human-review requests. Record the release-specific waiver truthfully; restore the original manual-review requirement immediately after each authorized merge. The next development prefix is1.0.4. OpenSSF15417 remains70%, not passing. Preserve owner previews/profiles and unrelated worktrees. Track actual publication/proof in release checklist.

Historical release snapshots

Current release status - 2026-10-12

Standards 1.1.0 is published immutably at 93b1d6163a4c466ae443e98b62786fc4d80d33bd; release CI38275622522 succeeds. All five asset attestations, checksums, and reviewed builder bytes verify. Standards inventory PR36 is merged at089a94ac following genuine owner review.

App signing caller/catalog b1dc874 passes every hosted check in CI38276579007. Actual application code remains321816c. Retained published111 and installed stable/dev110 TRXs each have zero failures/skips; update/restart receipts, registrations, preserved defaults, and coexistence verify. Core677 tests and 100% measured core line coverage pass. Local representative final signing and distribution proof pass; production CI OIDC signing and publication remain pending.

Owner explicitly requested a user-first product README, real screenshots, usage documentation, separate developer guide, and public repository presentation. Issue34 tracks that batch. Two actual isolated preview screenshots were captured after the owner reserved a clear desktop; no private documents or background apps are included. Original owner processes/profiles remain untouched.

OpenSSF Metal project15417 is registered for this Windows repository, initially 18% complete after provider import. Actual URL and progress badge are recorded; no passing badge or completed operating-practice assessment is claimed.

Next: finish this documentation candidate, obtain genuine final-head app review record, pass required checks, apply/read back the planned fuzzing context, merge, and publish signed1.0.0-beta.1/dev plus1.0.0/stable with exact asset verification. Issue33 is the release checklist. No new features or repeated unchanged local acceptance are needed. Existing publication authorization remains valid.

Azure configured and representative local signatures verified - 2026-10-12

Browser login completes successfully. Authenticated account/ARM readback verifies the provided subscription, actual tenant4ebeb0ad-5782-487a-a1b4-5080255774cf, East US endpoint, existingkof22signing and releases Active/PublicTrust profile. Issued certificates expose full subjectCN=James Maes, O=James Maes, L=Chester, S=il, C=US. Existing gclo and every preexisting assignment are preserved.

Created separate secretless MarkdownViewr application/client 8f51ec7a-5d91-45db-a374-c628566fc383, its service principal and exact immutable release-environment federation. Granted only Certificate Profile Signer at releases scope; readback confirms federation and role. Set/read back all seven non-secret GitHub release variables; release environment remains v* tags only. No tenant/security/device configuration was altered; no administrative credentials or client secrets in CI.

Signed six disposable owned binaries from321816c with verified Microsoft client 1.0.146 using the administrator's existing Azure CLI signer authority. SHA256 and RFC3161 SHA256 timestamps applied. Every binary passes SignTool /pa /all /v with zero warnings/errors and the expected publisher/trust/timestamp; strict existing helper also verifies SHA256 digests. Retain artifacts/signing-proof-321816c. OwnerPID48976/127248 previews and profiles are untouched. This is real local signing proof, not CI OIDC, installer/distribution proof or a published release. Standards31 reviewed/published builder, final actual CI signing/distribution, genuine human final-head review and enrollment/owner acceptance remain required.

Exact tooltip head accepted on every channel - 2026-10-12

Exact321816c CI38238385482 is terminal success: focused29/native111, published111/111, installed stable110/110 and dev110/110, zero failures/skips. The strengthened physical-hover/editor/print case passes all three distributed variants. Actual AppKit apply/restart receipts, coexisting windows/profiles, isolated updates, five-extension registration, stable uninstall/dev preservation and existing defaults preservation pass. Retain actual TRXs/receipts under artifacts/current-installed-evidence-38238385482; fixtures remain unsigned. No local automated mouse/keyboard tests ran; computer-use helper is unavailable.

Authentication recovery is complete: owner explicitly overrides prior deferral and requests a retry. Device-code flow receives Security Defaults error530035; native account-picker login is canceled after passkey incompatibility. Supported browser authentication succeeds with process-only broker setting and owner MFA. Do not repeat the denied device flow or weaken tenant protections.

Owner review launched; disabled-editor hover bug prepared - 2026-10-12

User asks to finish the release work and run the latest build. No production1.0 exists. Fresh self-containedde70220 local1.0.0-dev is running asPID127248 from owner-latest-de70220-publish, with Review-latest-de70220.md and its own owner-latest-de70220-profile. Preserve this instance, settings and binaries while the owner tests. Process/window metadata confirms responding; computer-use helper fails its required retry/reset recovery (native pipe/sandbox setup unavailable). No local physical-input tests ran. The expanded instruction authorizes remaining release actions, subject to unchanged gates and genuine maintainer review; never post a human acknowledgement on the owner's behalf.

Owner supplies actual ToolTip.IsOpen NullReferenceException from the hover timer (line36 in de70220). App issue32 records sanitized evidence. The manual tooltip was a different object from the one registered with ToolTipService. Candidate attaches the same object, requires the current loaded target/XamlRoot before opening, and closes only an open popup. The original editor/printing case now requires actual physical hover/text/mouse exit and no unhandled UI log errors; include it in the focused suite (29 cases), retaining every original assertion and all111 native/published /110 installed cases and deadlines. No GUI-runtime fix is yet claimed. Full isolated Release0 warnings/errors and workflow syntax/ security, formatting and two-document Markdown lint checks pass; fresh hosted acceptance still required.

Temporary timing instrumentation is removed by restoring the exact prior fixture code; retainedde70220 all-channel evidence remains below. Final signing authority, shared reviews/publication, enrollment/inventory, exact-head acknowledgement and owner layout/default-chooser acceptance remain required before production release.

Exact diagnostics head accepted on every channel - 2026-10-12

Exact signedde70220 / CI38209503930 is terminal success: core677/100% measured lines, native/published111/111, focused28/28, installed stable/dev110/110 each, fuzz9+2; zero failures/skips. Actual TRXs and lifecycle/update receipts retained under current-installed-evidence-38209503930, reader-regressions-38209503930, current-fuzz-evidence-38209503440 and current-native-de70220.log. Both actual AppKit apply/restart receipts and target SHA256 assertions pass; simultaneous windows, distinct profiles, isolated updates, five-extension registration and stable uninstall/default preservation all pass. Fixtures remain unsigned. Published elapsed572.71 seconds; stable496.38 and dev574.75. All three actual Appearance/PDF cases complete; no blocked operation is established. Retain timings for comparison, remove temporary DEBUG-ui-timing instrumentation and verify final head without changing assertions/cases/deadlines. No production defect is inferred from the earlier aggregate timeout.

Current review / automated fails because no maintainer-owned current-head record exists. The configuration Apply guard includes that genuine review context, so prepared fuzz addition17-to18 remains unapplied, preserving every existing rule. Support discussions are enabled; release environment permits only v* tags. Shared signing/template/help/inventory/license decisions, actual Best Practices enrollment, verified Azure resource/identity/role and final shipped signatures, owner visual/ scaling/default-chooser review and final-head acknowledgement still remain. No production publication or shared merge is claimed.

Published acceptance timing investigation - 2026-10-12

Exact d0526ef / CI38207252597 is terminal failure only in installed-updates. Core677/100% measured lines, focused28, native111 and fuzz9+2 pass, zero skips. Published process15 records110/111 passes, including native picker cancellation, with no assertion failure or final TRX before the unchanged600-second bound. The only uncompleted case is Appearance_WidthCssAndPrint. Prior822 published 109/109 took590.96 seconds, including13.07 seconds for that unchanged case; three current fixture close fallbacks versus four in the prior passing run do not establish a new close regression. Native111 takes9m55. Retain actual logs and distinguish aggregate runtime from an operation hang; installed lifecycle was not reached.

Prepare temporary hosted fixture timings for launch readiness, waits lasting at least2 seconds, owned-window closure and exact Appearance/PDF phases, retained in existing installed-smoke-ui session logs even if the outer process is stopped. No cases, assertions, waits/deadlines, source behavior or release gates change. Local isolated full Release passes with0 warnings/errors; formatting and direct Markdown lint of both changed documents pass. Full hosted proof is still required; remove DEBUG-ui-timing once the cause is measured and the original acceptance passes. Current required fuzz context remains unapplied. Shared approvals, actual enrollment/inventory, Azure verification/ identity and shipped signatures, genuine final-head acknowledgement and owner visual/default-chooser acceptance remain open; no signing/release is claimed.

Assurance push accepted natively; published picker failure investigated - 2026-10-12

Signed/DCOe6fd281 is pushed. Hosted fuzz38204215912 passes core9/9 and activation2/2, zero skips; actual TRXs/log retained under current-fuzz-evidence-38204215912 and current-fuzz-e6fd281.log. ExactCI38204216325 passes677 core/100%, focused28/28, full native111/111 and format/scripts/security/CodeQL; retain current-native- e6fd281.log and reader-regressions-38204216325. Native duration10m11; do not infer published or installed acceptance from that result.

Distributed job114664001461 fails: published process reaches its unchanged600- second bound with no final TRX. Actual ThemeTransfer_NativePickerCancels fails waiting10 seconds for exact native filename1148; owned-window evidence shows only Settings/main and blank SettingsStatus, with both app windows inactive in the retained screenshot. No installed phase/lifecycle is reached. Preserve current-installed-evidence-38204216325/process-15.log and installed job log. No signing/publication/required-check addition is inferred from partial success.

A candidate activates the exact owned Settings window and focuses its actual native action before UIA invocation; prior helper did neither. Preserve original selector/assertions/cases/deadlines, add LastInvocation/LastMouseInput to timeout evidence. Full isolated Release0 warnings/errors and format pass; actual hosted validation still required. Inactive-owner causation remains a hypothesis until that evidence, not an established app defect. No production source changes.

Current ruleset24859282 still requires the genuine review check and every prior context. Prepared ruleset-add-fuzz.json adds only Actions-bound fuzzing; do not apply until all required automated bootstrap gates pass. Shared31 signing approval, Azure resource/identity/profile verification and final signatures, actual Best Practices enrollment/shared inventory, final-head acknowledgement and owner layout/chooser acceptance remain required. No local GUI input, Azure login retry, shared merge, release tag or publication.

Current standards delta prepared; preceding checkpoint fully accepted - 2026-10-11

Fresh published-standards checker at1cc9d01 identifies mandatory assurance record, parser campaigns and public Product enrollment missing in this app (35 PASS, 3 FAIL,3 REVIEW); prior34/1 assessment is stale. Issues30/31 created. Implement five real seeded property targets (Markdown/HTML/frontmatter/extensions, source/ folds, URLs, theme JSON, generated activation schema), a PR/main/weekly/release fuzz workflow and planned required context; prepare honest badge assessment with required scope/null project URL, never an invented badge or exception. Remove obsolete unsigned-release guidance from SECURITY.md; signing remains fail-closed.

Local core campaigns9/9 cover80000 inputs plus the minimized regression; activation2/2 covers20000 envelopes; zero failures/skips. Full core677/100% measured lines, isolated full Release0 warnings/errors, format,23 setup tests and all64 script tests pass. A campaign oracle failure treated browser-relative backslashes as Windows file URIs; preserve failed TRXs, use actual browser URL semantics and require the minimized foreign-image denial regression. No production defect inferred and no existing assertion/case/deadline removed. New native assembly expectation111 and installed110 per channel; fresh hosted proof not yet available.

Exact82256f3/CI38201379210 is now terminal success:668 core/100%, focused28/28, native/published109/109, installed stable/dev108/108 each; zero failures/skips. Actual TRXs, coexisting-channel/registration JSON and native log retained under current-installed-evidence-38201379210, reader-regressions-38201379210 and current-native-82256f3.log. All actual lifecycle booleans pass; fixtures are unsigned. The reviewed next assurance push may proceed without cancelling this evidence; require fresh fuzzing and all original gates and add/read back the new context. Production source blobs remain unchanged. Shared signing31 approval, Azure resource authority/final signatures, actual enrollment/inventory, final-head human acknowledgement and owner design/chooser acceptance still required. No Azure login retry, local GUI input, shared merge, release tag or publication.

Application source review finished; next hosted checkpoint - 2026-10-11

All105 application C# files (41 core/64 native), native markup/project configuration and relevant CI/release/installed-lifecycle paths are reviewed. Inventory with blob hashes and review scope are retained in artifacts/final-pr-review-progress.json and application-review-3b01199.md. Test implementation review was focused; this is not final production assessment or genuine maintainer acknowledgement. The six reserved filename corrections remain the only new source finding;668 core tests/100% measured lines and format pass. No further blocking source defect established. Consolidate this checkpoint with the held signed fix and push for fresh hosted gates; preserve all cases/deadlines.

Correction to the earlier screenshot comparison: ThemeManagementDialog, ThemeEditor and EditorConfigurationDialog already route through ShowEditorAsync in Settings; old class names do not imply separate modal windows. Owner visual/scaling review remains pending. Private screenshot/document contents stay private.

Live PR3 still shows b542dcd automated gates passed (native/published109, focused28, installed108 per channel, zero skips); its genuine review check is unsatisfied. Shared signing31 remains an unmerged draft without approval, protected release variables are empty and signing preflight correctly blocks publication. Pending shared merge/publication approval was not answered; no Azure login retry. Actual OS chooser/Explorer and owner design acceptance, shared inventory/license decisions, repository signing authority and exact shipped SignTool proof remain required. No preview55472 changes, local input, shared merge, tag or release publication.

All-channel acceptance retained; final PR review in progress - 2026-10-11

Exactb542dcd CI38197169201 is terminal success: native/published109/109, focused28/28 and installed stable/dev108/108 each, zero failures/skips. Actual TRXs/JSON retained at current-installed-evidence-38197169201; simultaneous profiles, windows, isolated updates/restarts/target hashes and five-extension registration/ sibling-preserving uninstall/default preservation pass. Unsigned fixture evidence is not production signing or actual OS chooser/Explorer selection.

Full final PR review has inspected18 source files covering core identity/editor/ theme/settings and activation/registration/startup authority. Progress/remaining coverage is in artifacts/final-pr-review-progress.json; the existing incremental packet alone must not be called a full review. One actual finding: theme-export suggestions omitted reserved COM/LPT superscript device names. Prefix those six names consistently with the existing ASCII/device rule;668 core tests/100% measured lines and format pass. Local signed correction is held until the review is complete. No new native case or changing deadlines is needed for this filename-only fix.

Remaining review: remaining core/renderer/source/navigation/printing models, native UI/preferences/browser, build/release policy and final combined diff. Do not infer completion from tests or fabricate maintainer acknowledgement. Existing Azure account query still reports no authentication; no login retry. Shared31 merge/ publication approval unanswered; protected signing variables absent. Owner design/ scaling and chooser, actual signing and final-head human review remain required. No GUI input, preview55472 changes, shared merge, tag or release publication.

Bounded native local links prepared; renderer checkpoint fully verified - 2026-10-11

Exact4d34656 / CI38193736344 is terminal success: focused27/27, native/published106/106, installed stable/dev105/105 each; zero failures/skips. Actual extended raw-heading/inline/block-code browser case and all registration/ coexistence/AppKit-update assertions pass. Retain current-native-4d34656.log and actual TRXs/JSON at current-installed-evidence-38193736344. Fixtures are unsigned.

Local Markdown/text links previously remained blocked. They now require actual user initiation, current namespace/no query/supported type and once-decoded safe segments. Source physical root comes from its opened snapshot; the target handle is checked before reading. Native child windows retain the scope on every reload, focus only matching already-committed inside snapshots and preserve source/window watching. No OS shell/arbitrary protocol/executable dispatch.662 core tests/100% lines,10 real filesystem tests, zero-warning isolated Release/full format pass. A diagnosed test junction teardown failure is corrected with explicit removal of only the link before fixture cleanup; containment assertions remain. New physical browser/duplicate/watcher/junction-reload case compiled;109 native cases discovered, fresh hosted proof required. Original cases/deadlines retained; no local GUI input.

Prior CI is terminal, so the authorized next push can proceed after signed review. Shared signing31 approval request unanswered; do not assume permission. Azure/ shipped signing, actual chooser/Explorer, owner design/scaling and genuine final- head review remain required. No preview55472 change, login retry, shared merge, release tag or publication. Original upstream/native compatibility limits recorded.

Authored HTML fidelity corrected locally; preceding run fully green - 2026-10-11

Exactc3c735e / CI38190828814 is terminal success. Actual TRX native/published106/106, focused26/26, installed stable/dev105/105 each, zero failures/skips. Both AppKit updates/restarts/target hashes and actual concurrent-channel registration/profile/ isolation/sibling-preserving uninstall pass; retain artifacts/current-installed-evidence-38190828814 actual TRXs and JSON. Unsigned fixtures do not establish chooser/Explorer or production signatures.

Immutable original MarkdownDocument/MarkdownExtensions/ImageInliner blobs are Git-hash verified. Four actual pre-fix cases reproduce authored inline code being formatted. Existing boundary handling now tracks true code/pre tags and real closing tags across blocks. Raw block extensions apply only to tokenizer-visible text after source positions are recorded, preserving attributes/comments/code and entity spelling; metadata matches body-only subscript preprocessing.642 core cases/100% measured lines and isolated-output zero-warning Release/full format pass. Original MIT attribution retained and renderer boundary documented. Extended existing actual browser case/focused filter is compiled; fresh runtime required.

Prior CI is terminal, so the next authorized push may include the held signed docs and this correction without cancelling evidence. Shared signing31 approval request still pending; no reply or merge assumed. Protected Azure variables remain empty; no login retry, local GUI input, owner preview55472 change, tag or publication.

Placement screenshots verified; shared builder decision requested - 2026-10-11

Read-only gclo v1.1.0 reference archive matches published SHA256SUMS. Extracted only gclo.exe to the explicit workspace path; no application execution. Installed Microsoft SignTool verify/pa/all/v succeeds, one signature, zero warnings/errors, exact subject CN=James Maes, O=James Maes, L=Chester, S=il, C=US and Microsoft Public RSA timestamp chain. Retain artifacts/gclo-signing-reference/verify.log. This corroborates the shipped recipe/publisher, not deployed profile mapping or MarkdownViewr OIDC/signing permission. No Azure changes or copied CI client ID.

Exactc3c735e / CI38190828814 focused26/26 passes, zero failures/skips. Inspected actual native theme-manager and Printing screenshots in artifacts/reader-regressions-38190828814: complete window fits the hosted monitor; native scrollable Printing content and theme Save/Cancel remain within it. Full native114623032163 is terminal106/106, zero skips,8m6; retain current-native- c3c735e.log. Installed114623032253 is live; do not push local docs yet. Core/build/format/scripts/security pass; final-head review acknowledgement absent.

Add a current evidence-backed release checklist above historical tasks, preserving full PRODUCT scope and every old item. Passed published/installed case names prove source/Contents/Printing/theme/editor/reload/window/footer/attribution acceptance; chooser/Explorer, owner scaling/layout/icon and remaining fidelity review are still required. Rechecked shared signing31 and license32: all applicable checks green, both unmerged drafts. Requested explicit owner approval for signing31 merge/publication only; prior authorization remains draft-only until reply. No assumption of approval and no Azure login retry, changes, local input or release.

Complete distributed checkpoint; placement fix pushed - 2026-10-11

Exact9d5c0d1 CI38188145397 is terminal success. Actual TRX: native/published106/106, focused26/26, installed stable/dev105/105 each; zero failures/skips. Retain actual installed TRXs/results/coexisting-channels JSON under artifacts/current-installed-evidence-38188145397. Both real AppKit updates restart at the expected target with verified application hashes. Concurrent stable/dev windows, distinct profiles, isolated updates, five registered extensions and sibling-preserving uninstall pass. Fixtures are unsigned; OS chooser/Explorer and production signing are still not established.

Signed/DCO c3c735e now pushed: centers the bounded Settings window in its actual monitor work area and adds independent desktop containment to the existing layout case. Exact CI38190828814 is running. Inspect complete Settings screenshots and retain fresh distributed results; do not push more changes while it is live. Public Microsoft OpenID discovery resolves the supplied directory to GUID 4ebeb0ad-5782-487a-a1b4-5080255774cf, but signing-resource tenancy/profile/subject still require authenticated Azure inspection. No login retry/configuration change.

Shared draft PRs and the license exception need their required maintainer decision; current-head review requires a genuine acknowledgement. No shared merges, local GUI input, preview55472 changes, tags or release publication. Latest snapshot below is historical where superseded by this checkpoint.

Exact9d5c0d1 native acceptance passes; Settings placement corrected locally - 2026-10-11

Exact CI38188145397 focused26/26 and full native106/106 pass, zero failures/skips. Actual TRX proves repeated physical Contents/source synchronization, offscreen Nord palette/default pixel/save/reopen, future-schema export, trimmed full-title hover/click, both Printing cases and raw-inline provenance. Retain current-focused- 9d5c0d1.log/current-native-9d5c0d1.log and reader-regressions-38188145397 actual TRX/screenshots. Full native duration9m45. Installed114614880391 is live; no current published/installed/coexistence/signature result inferred.

Inspect actual theme-manager and Printing Settings screenshots. Controls/palettes are native and explicit, but default OS cascading position pushes right/bottom edges beyond the hosted monitor. FitWindow previously constrained size only; MoveAndResize now centers the complete resized window inside its actual monitor work area. Extend the existing native layout case with independent virtual- desktop containment, preserving its resizing/draft checks. Zero-warning Release and full formatting pass locally; fresh runtime/screenshots required. Hold the next push until current full installed execution is terminal.

Review gate currently fails because no maintainer-owned automated review record exists for the exact head; never fabricate acknowledgement. Shared signing/ license/inventory/AppKit Help/template Help PRs31/32/36/29/4 remain unmerged drafts with no reviews, actual starter remotewindows-app-template. Protected release environment has no signing variables. User-selected OS defaults/Explorer, owner layout feedback, reviewed shared/license requirements, genuine current-head review and deployed Azure/shipped signing remain required. No Azure retry, local input, preview55472 changes, shared merge, tags or production publication.

Exact1bfab22 terminal evidence retained; corrective candidate ready - 2026-10-11

CI38187115859 is terminal: focused23/26 and native102/106 fail, zero skips. Failures are offscreen Nord palette/default and copied-draft lookups, Owned future import/export lookup, and repeated physical source/Contents activation. Published process hits unchanged600-second limit without final TRX; actual process log has the same four failures. Installed lifecycle phase is not reached. Retain current-installed-1bfab22.log and actual artifact bundle at artifacts/current-installed-evidence-38187115859, plus focused/native logs/TRX.

Signed local49f0556 restores the trusted heading identity on the native row's content Grid for repeated ItemClick. Signed localb1f8af7 scrolls the owned native list until exact offscreen theme IDs are realized before unchanged selection and assertions. Release/format/hooks pass; cases/deadlines remain. Prior full run is terminal, so the next authorized push can proceed without cancelling evidence. Current-head focused/full/distributed proof, actual Settings pixels, owner/chooser/ review/signing and production publication remain required. No local GUI input.

Native theme realization helper corrected locally - 2026-10-11

Exact1bfab22 CI38187115859 focused23/26 fails, zero skips. New palette/default case cannot find ThemeChoice:Nord; existing future-schema/export case cannot find ThemeChoice:Owned future. Taller native preview rows leave those items virtualized offscreen. The selection helper now scrolls the owned ThemeList with its native Scroll pattern until the same exact automation ID is realized, then uses the same SelectionItem action. The existing10-second deadline and every value/assertion/ case remain. Release/format pass; fresh hosted proof is required.

The third focused failure remains physical source/reader alignment. Both Printing cases, Contents presentation, raw-inline folding, picker cancellation and new full-title tooltip/physical activation pass. Retain current-focused-1bfab22.log and actual focused TRX at artifacts/reader-regressions-38187115859. Signed local 49f0556 preserves the heading Tag on the new Contents content Grid; its unchanged repeat-click regression awaits the next pushed head.

Full native114611732252 and installed114611732224 remain live. Keep these local corrections unpushed until terminal; no installed/signature outcomes inferred. Cached ContentView/SettingsView/ThemeManager source matches immutable reference blobs970a8d6/c89b75c/7d81920 after BOM/newline normalization, confirming the default semantics audit. No local input, owner preview changes, Azure retry or release.

Repeat Contents activation identity restored locally - 2026-10-11

Actual retained b2ecc8c pixels show the last Contents row selected while both reader/source remain at middle after the repeated physical click. The new native row changed content from a heading-tagged TextBlock to a Grid without that Tag. ItemClick handles the clicked FrameworkElement's heading identity; selecting an already selected row does not raise SelectionChanged. Restore the same trusted DocumentHeading Tag on the content Grid. This is a precise metadata candidate, not an alteration to source geometry, scroll thresholds or test assertions. Existing Source_BidirectionalScroll performs the repeated physical activation and must prove the correction on the next exact head. Release/format pass locally.

Correct the earlier input interpretation: InputDiagnostics.GetCurrentPoint(sender) reports client coordinates. Do not compare110,307 directly to screen-space row bounds318..358; the titlebar/client origin accounts for that difference. Tooltip presence alone did not prove interception, and placement changes did not resolve the failure. Trim-only full-title tips remain the intended UX refinement; the repeat-click identity is the next specific correction to verify.

Pushed1bfab22 exact CI38187115859 is still live. Preserve focused/full/installed execution before the next push. Local metadata correction is held; no current GUI/runtime/signature or installed acceptance is claimed. No local input, preview55472 changes, Azure retry, shared merge, tags or publication.

Theme palettes/default controls and fixture cleanup prepared - 2026-10-11

Native theme rows now show five validated palette previews with hexadecimal accessible names/tooltips, and textual Built-in/edited/Custom, Enabled/Disabled and Default state. A native default radio control explicitly enables the selected choice; selecting a row alone changes no saved palette. Enable/default changes stay inside the copied draft until Save, and Cancel/child edit/import/restore semantics remain. Selection scrolls into view. The pinned Mac Default checkbox writes ThemeManager.activeThemeName; Windows retains its existing DocumentTheme saved-choice contract, with explanatory text that Save applies it to open readers and future windows. No second preference or silent migration is introduced.

A new actual native case measures painted Nord palette pixels, checks all five accessible swatches/default/enabled state, saves and reopens, and retains a real Settings-manager screenshot. It compiles/discovers but has not executed. Release build has zero warnings/errors; format passes; seven read-only/isolated Windows adapter cases pass.106 native cases discovered; core unchanged598/100% lines.

Exactb2ecc8c CI38185403701 is terminal: focused23/24 and native101/102 fail, zero skips, only physical source/reader alignment. Both Printing cases, raw-inline folding, picker cancellation and Contents presentation pass in focused/native. Published suite reaches unchanged600-second bound without final TRX; retained process-15.log reports the same alignment failure. Installed lifecycle is not reached. Retain current-native-b2ecc8c.log/current-installed-b2ecc8c.log and actual artifacts/current-installed-evidence-38185403701; do not invent distributed counts.

The published log reports ten failed exits. Exact pinned FlaUI NuGet source c5e7eb7 confirms CloseMainWindow then a5-second CloseTimeout; independent sibling windows intentionally keep the fixture process alive. Teardown now closes every fixture PID's native Window pattern before the unchanged process close/kill fallback. Cases, assertions, all deadlines and600-second process limit remain; cleanup/runtimes need fresh hosted proof. No local GUI input or other-app closure.

Signed local24a464e default status/trim-only tooltip candidate can now be pushed with this preparation after old run is terminal. Next: exact-head focused/whole/ installed acceptance and actual Settings pixels; resolve any remaining source alignment from retained mouse/viewport evidence. Owner/chooser/signing/review and production publication remain required. No Azure retry, shared merge or tags.

Effective Markdown default status prepared - 2026-10-11

General now reports Default/Not default/Unknown/Unregistered for this exact installed edition. A bounded read-only Windows AssocQueryStringW/ASSOCSTR_PROGID query reads the effective user-selected .md ProgID; unchanged owned registration is required. Registration alone cannot report Default, and an unavailable query cannot become success. Refresh on returning from Windows Settings and through a native Refresh status action. No UserChoice/hash/default writes or competitor paths are read/displayed. ADR0005 and threat-model boundaries are updated.

Seven actual read-only Windows API/isolated registry cases pass, zero skips: real .txt query, preserved existing .md choice, other edition/default and retargeted/unregistered/unknown ownership. Release build has zero warnings/errors; format passes.105 native cases compile/discover including updated actual General status/refresh and new long-title tooltip/physical-heading acceptance, not run. Core is unchanged from598 passing cases/100% measured lines.

Pushedb2ecc8c / CI38185403701 focused23/24 fails, zero skips. Actual TRX proves both Printing defaults/draft cases, raw-inline folds, picker cancellation and Contents presentation pass. The remaining physical source/reader alignment fails. Retain current-focused-b2ecc8c.log and actual bundle at artifacts/reader-regressions-38185403701. Actual evidence still shows a short-title tooltip; only truly trimmed native labels now receive tips, with explicit placement target. The new physical hover/click case and retained mouse-invocation diagnostics must verify this candidate before calling the remaining failure resolved.

Full native114606533948 and installed114606533825 are still live. Preserve both before pushing this preparation. Next: inspect terminal outcomes, verify tooltip and default status on the next exact hosted head; complete theme previews/default clarity and remaining owner/chooser/signing/review requirements. No local input, preview55472 changes, Azure retries, shared merge, tags or release publication.

Terminal published regressions retained; next candidate ready - 2026-10-11

Exactb5e519e CI38184378762 is terminal failure: focused19/22, native98/100, published98/100, zero skips. Published actual TRX confirms the same raw-inline fold and source physical-click/alignment failures; installed lifecycle phase is not reached. Retain current-installed-b5e519e.log and actual artifact bundle at artifacts/current-installed-evidence-38184378762. The General/Contents case passes.

Signed localec78b50 fixes reproduced parser/token boundaries and prepares the native tooltip/picker corrections; signed7fa9f77 adds shared Printing Settings. All598 core tests/100% lines, zero-warning Release, format/hooks pass;102 native cases compiled/discovered. Full prior run is terminal; next authorized push can proceed without cancellation. Fresh exact-head focused/full/distributed proof, Settings design acceptance, remaining defaults/themes, genuine review and signing are still required. No installed success inferred and no production publication.

Shared native Printing settings prepared - 2026-10-11

Add a dedicated Printing category using the same PrintOptionsEditor as the output dialog: theme, backgrounds/images, match-screen zoom, page/document width, borders and bounded padding. Apply commits validated defaults; Restore returns to latest saved choices and closing discards the draft. PDF destinations/open-after-save remain deliberate output actions. No duplicate validation, new dependency or print job is introduced by Settings.

Both Settings and accepted Print/PDF choices use checked persistence before broadcasting shared print defaults/baselines. Sibling saves retain an unsubmitted Settings draft; Restore uses the newer saved baseline. Theme changes refresh named print choices without erasing other draft fields. Native NavigationView category labels remain visible at normal960px width and adapt at narrower widths.

Release build has zero warnings/errors; format verification passes. All598 core cases/100% measured lines pass after the reproduced parser correction.102 native cases compile/discover, including new actual Apply/Restore/cancel/sibling-save checks with owned control scopes and a retained Settings screenshot. These new GUI assertions are not yet executed. Existing output/PDF/pixel cases, every assertion and all process deadlines remain.

Signed localec78b50 retains the three evidence-based reader/picker corrections. Pushedb5e519e focused19/22/native98/100 fail, zero skips; General/Contents options case passes in both. Installed114603470178 remains live; retain it before pushing this Printing change. Next: inspect terminal distributed evidence, push only then, execute exact-head native/distributed acceptance and inspect real Settings pixels. Then complete default-status/theme previews and remaining release requirements. No local input, owner preview changes, Azure retry, shared merge or publication.

Multiline token boundary and native input regressions corrected locally - 2026-10-11

Exactb5e519e / CI38184378762 focused19/22 and native98/100 fail with zero skips. Focused failures: raw-inline complete-header folding, source-navigation physical click/alignment, and native Open picker filename lookup. Full native reproduces the first two; new General/Contents presentation case passes in focused/full. Retain current-focused-b5e519e.log/current-native-b5e519e.log and actual focused TRX/screenshots under artifacts/reader-regressions-38184378762. Installed job 114603470178 is still live at this observation; preserve it before any push.

An exact core regression reproduces the raw opening-tag/newline failure: Markdig moves a line-start closing tag into a following HtmlBlock. Existing actual HTML tokens now retain complete inline titles across consecutive raw blocks, ignoring comment/attribute lookalikes and stopping at a new heading/Markdown boundary. All598 core tests pass with100% measured line coverage, including CRLF, comments, multiline closing syntax and unrelated blocks. Release/format pass.

Owned UI evidence showed a tooltip near Contents rows; interception was an unconfirmed hypothesis. Place the native tooltip to the right and make it non-hit-testable; retain all physical click/alignment assertions. The exact native filename control1148/ Edit appears in owned enumeration despite the provider condition lookup timing out; use that same ID/type in owned enumeration, without broader controls or a longer deadline. These native corrections require fresh hosted acceptance.

A dedicated native Printing page/shared options editor is prepared separately; its new apply/restore/dialog-cancel/sibling-persistence case compiles/discovers, not executed. Keep the goal active; final signing/review/chooser/design acceptance and production publication remain open. No local input or preview changes.

Registration and simultaneous editions verified - 2026-10-11

Exact53755ab / CI38182128299 is terminal success: focused21/21, native99/99, published99/99, installed stable98/98 and dev98/98, zero failures/skips. All reported PR checks pass. Actual AppKit update/apply/restart verifies target versions and assembly hashes. Before/after registration JSON confirms all five extensions for both editions; actual uninstall removes owned registrations and preserves existing defaults.

coexisting-channels.json confirms simultaneous stable/dev windows in separate processes/profiles, isolated updates with sibling state preserved, stable uninstall preserving the live registered dev edition, and unchanged existing defaults. Retain current-installed-53755ab.log and the complete actual TRXs/results under artifacts/current-installed-evidence-38182128299. These fixtures are unsigned; Windows chooser/Explorer interaction and final production signatures remain open. The two published print-startup failures seen onbd3d72a do not reproduce on537; do not claim a production startup fix from this clean run alone.

Signed local5803fc1 andaeeb28d include the inline-heading correction and native General/Contents settings. Build/format and593 core/100% measured lines pass; 100 UI cases are compiled/discovered. Their updated/new native assertions need fresh hosted execution. The old full job is terminal, so the next authorized push may proceed without cancelling it. Full Settings/theme/Printing design and genuine review/signing/publication remain required; no local desktop input.

Native General and Contents options prepared - 2026-10-11

Move new-window Contents/Source defaults and Default Apps guidance into General; splash/startup update controls remain Advanced. Add persisted Contents wrapping and optional depth markers using native TextBlock/ListView/ToggleSwitch controls. Unwrapped titles use one line/ellipsis and full-title tooltips; wrapped titles have no two-line cap. Preserve heading identities, selected row, per-window depth and visibility. Checked persistence precedes sibling broadcasts and baseline updates. Category switches reset ordinary scroll position without discarding CSS drafts.

All593 core tests pass with100% measured line coverage; zero-warning Release build passes. A new actual native case checks long-title geometry, live sibling markers, unrelated-save persistence, Settings reopening and restoration; focused/full/ distributed suites retain every previous case and deadline. It has compiled but not executed. Retain actual Settings-window screenshots in the hosted case.

Signed local5803fc1 inline-heading fix and this preparation remain unpushed while exact53755ab installed114596717826 is verified live; focused21/native99 on537 pass. Do not cancel the current full job or claim new installed/chooser/signing results. Issue21 remains open for full Settings redesign/default status/Printing/ theme previews and owner acceptance. No local desktop input or production release.

Mac screenshot comparison and inline-heading correction - 2026-10-11

Reviewed all eight owner-provided Mac screenshots; issue #21 records the concrete Windows gaps: General default-viewer status, configurable Contents wrapping/depth markers, theme palette previews and clear Enabled/default choices, and a dedicated Printing settings page. Use native Windows controls and retain the owner's visible Print/Contents, removed duplicate depth selector and off-by-default panes. Private screenshots/document contents remain outside the repository and public tickets.

A separate valid multiline raw heading inside a Markdown paragraph reproduced the remaining complete-header fold loss. Pair actual HtmlInline AST nodes within their Markdown leaf, excluding code/comment lookalikes; preserve the original closing line and distinct implicit-close positions. All592 core tests pass, zero skips, with100% measured core line coverage; Release build has zero warnings/errors. The existing raw-HTML UI fixture now exercises that inline variant; its hosted runtime outcome is not yet proved. Do not infer it from the older block fixture.

Pushed53755ab / CI38182128299 passes focused21/21 and full native99/99, zero failures/skips; retain current-native-53755ab.log (9m14). Installed job 114596717826 remains live at this observation. Hold the next push until terminal; no current distributed/registration/coexistence outcome or signature is claimed.

Published print startup failures retained; next diagnostic candidate - 2026-10-11

Exactbd3d72a / CI38180868496 is terminal: focused21/21 and native99/99 pass, zero skips. Installed job114592949188 times out in the published suite at the unchanged600-second process bound; no final TRX or installed lifecycle outcomes. Retained process-15.log shows two actual30-second failures before Print opens: Print_KeyboardDraftCancel and Print_WindowsDialogCancel cannot find their initial rendered heading. Other retained screenshots/PDFs prove the suite continued, including raw-HTML and source cases. Do not call this a proven installer bug or assume it is mere suite slowness.

Retain current-installed-bd3d72a.log and actual artifact bundle under artifacts/current-installed-evidence-38180868496. Add normal per-case console reporting to the existing full published/installed suites and owned screenshot/ activity-log/accessibility-tree reporting only when either print fixture startup fails. Existing deadlines, assertions, all cases and failure status are unchanged. This distinguishes slow aggregate execution, a specific blocked case and runner shutdown; actual startup logs distinguish missing activation/render from readiness.

Signed local5de4125 coexistence acceptance and489af75 pinned audit can now be pushed with this targeted test-only evidence change because the earlier run is terminal. Production signing, actual Windows chooser/Explorer, genuine review and owner design acceptance remain required. No local GUI input or release.

Full native correction passes; pinned reference audit retained - 2026-10-11

Pushedbd3d72a / CI38180868496 passes full native99/99 and focused21/21, zero failures/skips; native duration8m23. Retain current-native-bd3d72a.log and the focused TRX. Installed job114592949188 remains live; do not infer published/installed/registration outcomes from native success.

Re-fetch immutable upstream template/CSS-help blobs, verify Git hashes and confirm cached source matches after newline/BOM normalization. Retain pinned-css-audit.json: all47 shared screen selectors retain matching upstream declarations when cascading per property. The31 upstream-only selector groups concern native Contents/source/ dividers; document CSS does not style native controls. Record that boundary in docs/reference-fidelity-audit.md rather than claiming full pane-CSS compatibility. This declaration comparison is not painted-output or final-release proof.

Signed local5de4125 prepares real concurrent edition/update/uninstall acceptance; all64 tooling tests/configured analyzer rules pass. Wait for the current full run before pushing it and the audit documentation. Final OS chooser/Explorer, owner acceptance, genuine review and shipped signing remain outstanding.

Simultaneous stable/dev acceptance prepared - 2026-10-11

Signed pushedbd3d72a / CI38180868496 passes focused21/21, zero failures/skips, including unchanged raw-HTML navigation/fold/find/reload. Core/build/format pass; full native and installed jobs remain live. Retain current-focused-bd3d72a.log. Do not cancel this full run by pushing the next prepared change early.

Add a separate phase after every existing published/installed suite: fresh owned stable/dev installs coexist, use distinct actual edition profile/log prefixes, show distinct document/edition titles and run in separate processes. Actual AppKit updates run while the sibling remains open; target hashes/versions and both file registrations are checked, with unchanged sibling PID/binary/settings. Uninstall stable while dev remains open and registered, then clean up both owned fixtures without changing Windows defaults. No real profile or local desktop input is used. The phase is locally prepared, not executed or runtime-proved.

Canonical artifact boundaries and actual manifest package IDs gate every smoke uninstall. A real filesystem safety regression checks wrong IDs, traversal, prefix collisions and missing manifests. All64 tooling tests and every configured analyzer rule on both changed scripts pass; fresh hosted coexistence execution remains required after the current run finishes.

Raw multiline heading fold reproduced and corrected - 2026-10-11

Exact764c7ac / CI38179931820 is terminal: focused20/21, native98/99, published98/99, zero skips. All failures are the newly added raw-HTML case at its complete-header fold assertion. Published failure prevents the new installed registration lifecycle readbacks from running; do not claim those passed. Retain current-focused-764c7ac.log/current-native-764c7ac.log and downloaded TRXs under artifacts/reader-regressions-38179931820 and artifacts/current-installed-evidence-38179931820.

The parser mapped a raw heading's end to its opening line, hiding remaining multiline attributes/title/closing syntax when folded. Three actual failing core regressions reproduced this; existing AngleSharp token spans now retain the complete header, respecting quoted attributes, comments and nested title markup. All34 source mapping/folding cases and all589 core tests pass with100% measured line coverage. Release build has zero warnings/errors and format verification passes. The unchanged raw-HTML runtime case and full distributed suites must verify the correction on the next pushed head.

No production publication, signing verification, OS default selection or local desktop input. Preserve owner preview55472. Actual chooser/Explorer, concurrent stable/dev isolation, full fidelity audit, genuine maintainer review and final signed release artifacts remain required.

All distributed source cases pass; next release acceptance checks - 2026-10-11

Exact9994eda CI38176727468 is terminal success: focused20/20, native98/98, published98/98, installed stable97/97 and dev97/97, zero failures/skips. Actual AppKit apply/restart advances stable0.1.0→0.4.0 and devbeta.1→beta.2; post-upgrade channel/versions and target DLL hashes are verified by the harness. Retain actual TRXs and before/after JSON under artifacts/current-installed-evidence-38176727468. These fixtures are unsigned and sequential; they do not prove production signing or simultaneous stable/dev coexistence. Signed cleanupc89ce5c was pushed as parent of764c7ac.

New read-only harness checks require all five Open With/Default Apps extensions at real initial install and after upgrade, the same owned ProgID, complete owned cleanup after uninstall, and unchanged extension/default UserChoice values/hashes. Snapshots stay in memory; retained evidence contains only public registration metadata and success booleans. Actual isolated registry negative fixtures cover each missing extension, wrong executable/channel and incomplete cleanup. All63 tooling tests and every analyzer rule on changed scripts pass locally; actual install lifecycle readbacks await the next exact-head hosted run.

Add actual multiline/same-line HTML heading navigation, complete literal header folding, paired find/cancel and watched reload to full and focused UI acceptance. The new case compiles; runtime proof is pending. Set the app version prefix1.0.0 while keeping dev suffix; tagged workflow versions remain authoritative. This changes the app milestone, not published AppKit0.1.0 dependencies.

Standards inventory draftPR36 signed6b4fd17 registers this app and the Windows starter as Product, adoption in progress; documentation/conformance checks pass, review/merge remains required. Shared Help AppKitPR29 and starterPR4 now have passing exact-head gates, including starter2688e3f all-rule analyzer correction. No PR merged, tag created or production release published. Preserve owner55472 and its output/profile; no local desktop input or Azure login retry.

Still required: fresh diagnostic-free/native/raw-HTML/lifecycle acceptance, actual OS chooser/Explorer, real simultaneous channel isolation, owner design and genuine current-head review, reviewed/published owned-file signing builder, verified Azure repository identity/profile/subject and shipped signatures.

Source correction passes full native acceptance; cleanup local - 2026-10-11

Exact signed9994eda CI38176727468 passes focused20/20 and full native98/98, zero failures/skips. The original source focus, both-direction actual heading alignment and physical wheel case pass without changed bounds or deadlines. Core586/586 retains100% measured line coverage; build/format pass. Retain actual TRX under artifacts/reader-regressions-38176727468 and native/core9994eda logs. The published/installed job114580574833 remains live; preserve that run before pushing another head. No installed or signed release claim follows from native.

Remove temporary source color/coordinate/scroll and collapsed-index probes only; keep production painting, hit-testing, offscreen geometry and actual regression assertions. This cleanup has local zero-warning Release/format passing and needs fresh exact-head hosted acceptance after the current installed job is terminal.

Shared defaults: AppKit PR29 signedf58aac9 passes115unit/100% core+updates, 14/14 native WinUI/WPF and build/format. Starter PR4 signede4c4a50 passes8/8 native, both generated variants20core/8native each, CLI14, plus installed update jobs. Its pinned analyzer combined pass crashed; signed2688e3f is pushed after terminal evidence with all-rule casing partition mitigation. All build scripts pass every configured rule locally; new exact-head gates remain pending. No PR merged.

Still required: actual default chooser/Explorer/hook lifecycle and stable/dev coexistence, full reference fidelity/standards inventory, reviewed published signing builder, verified repository Azure identity/profile/signer and final shipped signatures, owner design acceptance and genuine current-head human review. Stable1.0/dev publication is authorized only after these requirements. Preserve preview55472, no local desktop input, no further Azure login attempts.

Full source acceptance advanced; geometry correction pending - 2026-10-11

Exact signed6374611 CI38174602145 is terminal: focused19/20, native97/98, published97/98, zero skips. Actual initial/sustained native colors, physical hover and focus, explicit System→Light, and nested outline pass these variants. The original bidirectional source test advances to line490: source middle glyph alignment passes, but the reader heading remains offscreen. Retain terminal logs current-native-6374611.log/current-installed-6374611.log and distributed TRX under artifacts/current-installed-evidence-38174602145. Installed channel acceptance has not run because published acceptance remains red.

The next correction uses full native content-client character points with AllowOffClient, without adding ScrollViewer.VerticalOffset twice. It also removes the obsolete scroller search. Bounded opt-in numeric probes compare native points, old raw rectangles, anchors and mapped targets. No document content/path is logged. Original physical bidirectional assertions, deadlines and geometry bounds remain. Local zero-warning Release and formatting gates must pass before signed push; hosted verification of this correction remains pending. Remove temporary probes before release. Preserve owner preview55472 and avoid local desktop input.

Default-app chooser/Explorer/install lifecycle, real stable/dev coexistence, original fidelity/standards, verified Azure/shipped signatures and genuine current-head human review remain required. No release publication claim.

Sustained source palette candidate - 2026-10-11

Exact91877f7 CI38173447118 is terminal:18/20 focused,97/98 native, 95/98 published,zero skips. Nested outline now passes all variants; source focus still fails and published initial Light colors remain authoritative. Retain artifacts/current-native-91877f7.log and actual published TRX under artifacts/current-installed-evidence-38173447118. No installed outcome yet.

Signed5fa6754 orders semantic formatting after the native property queue; signedb15fcbc includes actual source scroll offsets in native content-client hit-testing. Both have local zero-warning Release/format/hooks passing. Also repaint from the explicit shell theme command: System and explicit Light may have the same ActualTheme and otherwise provide no ActualThemeChanged repaint. Add System→Light after already highlighted text, and require actual native colors in three consecutive existing250ms polls, within the unchanged 10second limit. This catches a temporary correct flash followed by the proven native reset; it does not mirror tokens, delay blindly or relax expectations.

All current corrections preserve physical hover/focus/selection, exact native colors and source -2..36px alignment bounds. Tagged diagnostic probes remain opt-in and must be removed after diagnosis before release. Preserve owner55472 output/profile and no local desktop input. Installed/default/Explorer/lifecycle, side-by-side editions, original fidelity/standards, Azure/signatures and genuine current-head human review remain open; no publication claim.

Native client caret coordinates - 2026-10-11

Exact91877f7 CI38173447118 focused18/20,2failures,zero skips: outline now passes; initial hover-fixture color and physical source focus remain red. Focus probe returns selection2 at verticaloffset5297.759, disproving the assumption that client hit-testing coordinates start at the visible viewport.

Microsoft's CTextBoxView::GetClientRect reports the full native extent; its viewport/world-space conversion starts from the scroll offsets. Native caret range hit-testing therefore needs content-client coordinates. Add the actual horizontal/vertical scroll offsets to the client inset before GetRangeFromPoint. Retain identical selection/read-only/physical click/wheel and exact glyph alignment assertions. Evidence is retained in artifacts/reader-regressions-38173447118/reader-regressions/reader-regressions.trx; offscreen rectangles and unshifted client-point methods are both disproven.

Signed local5fa6754 fixes the separately proven foreground propagation ordering; its local zero-warning Release/format/hooks pass. Preserve live91877f7 full native/published jobs before pushing the new candidate; do not restart on timeout. Hosted caret/color and complete installed/release verification remain required.

Proven native foreground replacement - 2026-10-11

Exact04c1da8 CI38172448726 is terminal:18/20 focused,96/98 native, 94/98 published,zero skips. Published failures retain initial Light colors in both palette and hover fixtures, nested outline and source-focus alignment. Real color trace has snapshot1/paint3/tokens6 unchanged: paint complete #FF75628B at20:37:33.320, after native queue #FF1F1F1F at20:37:33.389. The hover fixture reproduces the same reset before its pointer step. This proves native property propagation replaces successfully painted ranges; classification and generation cancellation do not explain this variant.

Signed91877f7 is now pushed. Its actual native caret/outline acceptance is running. Prepare the next source fix: after setting native Background/Foreground, await an owned low-priority dispatcher callback before applying default and semantic range formats; recheck snapshot/paint/disposal guards after the queue. This orders the real pending inherited-property work before character formatting, with no timer, repeated repaint, fake accessibility color or altered assertion. Local zero-warning Release passes; formatting/hosted exact-color proof remains required. Preserve the current91877f7 run before pushing the color correction.

Evidence: artifacts/current-native-04c1da8.log and artifacts/current-installed-evidence-38172448726 retained actual published TRX. All temporary [DEBUG-...] probes still require removal after diagnosis before release. Installed stable/dev/Default Apps/Explorer, side-by-side, standards, Azure/signatures and genuine human current-head review remain open. No release publication or Azure login was attempted; owner preview55472 is untouched.

Visible source caret and outline accessibility - 2026-10-11

Signed04c1da8 CI38172448726 focused20 cases:18pass,2fail,zero skips. Source colors/physical hover pass this variant; full/published colors remain required because metadata probes may change native propagation timing.

Exact native source-focus probe: offset5297.759, firstY5297.759, selection0 before and after focus. The offscreen first-character rectangle is zero before adding the offset, so binary searching offscreen rectangles picks character0 and focus reveals the old caret. Replace that search with native ITextDocument.GetRangeFromPoint at the visible client inset and select its actual position. Keep original physical click/wheel and -2..36px glyph bounds.

Outline probe retains collapsed DOMindices[1] after child collapse, [0,1] while parent is collapsed, and [1] after parent expands. The stale child UIA peer is observed immediately after its sibling appears. Wait for the same actual hidden child's peer to disappear within the existing10second helper; retain identical absence checks through theme change and reload. No arbitrary sleep, hidden-flag simulation, wider geometry bound or test exclusion.

Local zero-warning Release passes for the caret/outline correction. Current 04c1da8 full native/published jobs114567713082/114567712967 are still live; retain their terminal variants before pushing the next head. Signing, installed associations/Explorer/lifecycle and side-by-side release verification remain open. Owner preview55472 is responsive and untouched. Tagged probes remain temporary and must be removed after diagnosis before release.

Native diagnostic correction - 2026-10-11

Current dbda6d4 CI38171433458 focused gate is terminal17/20,3failures, zero skips. Initial Light source palette still becomes#1F1F1F rather than #75628B after an actual UIA Toggle; the queued theme repaint is not proven. Nested outline expansion still exposes the collapsed child's native peer. Physical source-focus alignment still fails, but its failure-report geometry call throws E_UNEXPECTED and masks the timeout before saving the focus logs.

Preserve the original assertions and bounds. Read native logs/tree before optional glyph geometry and catch only the observed diagnostic Win32Exception. Add temporary opt-in [DEBUG-source-colors] before/after actual painting and the native queue, plus [DEBUG-outline-collapse] generated hidden-section indices following actual jump/toggle commands. These probes log no document text or paths and must be removed after diagnosis before release. Native/published jobs114564687334/114564687101 remain live; do not cancel or restart them just because job logs are not yet available. Full installed/default/Explorer and stable/dev lifecycle acceptance remains pending. Owner preview55472 is untouched.

Installed association acceptance boundary - 2026-10-11

The installed harness now supplies a saved/restored test-only installation marker after its actual manifest/version/channel/update proof, and explicitly marks the published copy as portable. The native Default file types case must find this exact installed executable's expected channel registration and an enabled Windows chooser action. Previously a missing registration and disabled button could agree and pass the installed test. Portable evidence must instead show no registration. This marker does not change application behavior, create registry keys or simulate successful hooks; actual installed execution is still required. Windows selection/Explorer/update/uninstall acceptance remains#14.

Prior CI38170170551 is terminal: native93/97 and published93/97,4failures, zero skips. Published8m56s now completes inside the existing600second bound; its red tests prevent installed outcomes. No deadline was raised. Current native and published failures include the reproducible pipe bug, initial source colors, nested outline expansion and physical source focus alignment. Exact evidence: artifacts/current-installed-9fdfc2d.log and retained installed-update-results. Locally signed2fe5853/efe14af prepare the tested IPC correction and queued theme repaint; next exact pushed head must verify these and the association boundary.

Previous full-run variants and queued source repaint - 2026-10-11

Exact9fdfc2d full native job114560940480 is terminal93/97,4failures,zero skips (8m59s), despite focused14/15. Retain artifacts/current-native-9fdfc2d.log: failures are disconnected peer, nested outline expansion, initial source Light palette and source focus alignment. Initial-color failure now follows verified UIA Toggle ThemeLight(before=Off), so it is not explained by mouse fallback. Both exact highlighting cases passing the focused run do not establish full acceptance. Installed job114560940485 is still live at last verified read.

Signed/DCO2fe5853 adds the locally proven native IPC cleanup and test-only source coordinate probe (25runs/100cases,zero failures/skips); it has not yet been pushed while the prior installed job remains live. A subsequent source change queues semantic repaint until after native theme propagation, preserving range classification, selection and read-only state. Existing actual color assertions remain; no success claim before exact hosted proof. The focused gate also adds the nested outline variant without excluding any prior case.

Previous native result and deterministic IPC fix - 2026-10-11

Signed/DCO9fdfc2d is pushed. Exact CI38170170551 focused job114560940302 passes14/15,one failure,zero skips. Source reopen/50:50, both native highlighting cases, four-file import and physical repeated-heading navigation now pass. Build/core/format/scripts/security/PR gates pass; full native job114560940480 and installed job114560940485 were still live at the last verified poll. Retained focused evidence: artifacts/reader-regressions-38170170551 and artifacts/reader-regressions-9fdfc2d.log. The remaining focused failure is source heading alignment after a physical click enters source, not the initial jump.

The reproduced published disconnected-peer failure is now deterministic locally. A test context defers only the real server continuation until the real current- user pipe client closes. Unfixed next-client ConnectAsync times out10seconds: artifacts/pipe-closed-before/pipe-closed-before.trx. A broken synchronous read clears IsConnected while the native connection still needs Disconnect. The fix records accepted connection ownership and disconnects it even in Broken state; expected shutdown disposal is handled without swallowing unrelated errors. Unchanged regression plus three existing cases pass, then25runs/100tests pass with zero failures/skips: artifacts/pipe-closed-after and artifacts/activation-stress-after. This is local proof; hosted published and installed verification remains required. No deadlines or assertions were relaxed.

Next source probe adds only numeric focus/viewport/caret coordinates under the existing MARKDOWNVIEWR_INPUT_TRACE test opt-in, with [DEBUG-source-coordinates]. It tests double-counted native client coordinates versus caret restoration or later scrolling feedback. The exact native alignment assertion remains. Remove this tagged temporary instrumentation after diagnosis and before release.

Live protect-main ruleset24859282 now requires reader-regressions bound to GitHub Actions15368. Exact before/payload/readback artifacts prove all prior rules, bindings, review settings, conditions and bypass actors were preserved. Owner preview55472 is responsive and preserved. Real installed chooser/Explorer, source alignment, channel isolation, human current-head review and production signing remain required; no Azure changes or release/signature claims.

Previous native verification and action correction - 2026-10-11

Exact signed/DCO8abbd4d / CI38168946288 is terminal: full native93/97, 4failures,zero skips; focused10/12,2failures,zero skips. Build/core/format pass. Retained logs: artifacts/current-native-8abbd4d.log and artifacts/reader-regressions-8abbd4d.log; actual focused TRX/screenshots/PDFs: artifacts/reader-regressions-38168946288. The full failure set is source reopening, repeated heading navigation, four-file import and source focus alignment. Exact hover passes in both; focused palette fails on initial Light choice (#75628B expected versus actual#1F1F1F). Do not claim all highlighting accepted. Installed-updates job114557287398 again exceeded600seconds in the published suite before any installed outcomes. Published process15 evidence is retained in artifacts/current-installed-evidence-38168946288. It reproduces the same source reopen/inset/import/focus failures plus initial hover-color and intermittent disconnected-pipe timeout; no deadline was raised.

Next bounded correction uses WinUI's real Toggle automation pattern for checkbox/radio menu items, whose native implementation invokes the same menu action. Physical source hover/focus assertions remain. Four-file import now navigates the actual fixture folder before entering all quoted relative names: the previous native filename field retained only260characters of the expanded absolute-path batch. Imported/skipped/failed counts and exact exported bytes remain required. Heading target comparisons include the pinned 1rem scroll inset, preventing repeated selection of the same heading; its exact native landing assertion becomes16px plus/minus2, preserving original CSS behavior. The focused job includes all remaining full-run failures without exclusions.

The required-check setup list includes reader-regressions;55 Pester boundary tests pass (artifacts/reader-accessibility-script-tests.xml), and both analyzer partitions pass for the module. Live main ruleset must retain all review, signature/security rules while adding this GitHub Actions-bound check. Owner preview55472 remains responsive and preserved; no local physical input, Azure mutation, human review acknowledgement or release claim.

Previous release verification - 2026-10-11

Signed/DCO05bf612 is pushed to PR#3. Exact CI38167591076 full native run completed84/97,13failures,zero skips; previous0ed608e was74/97. Current focused12-case TRX is retained in artifacts/reader-regressions-38167591076: Settings panel defaults, toolbar alignment, picker cancellation, custom theme paint, source theme/mode and exact copying pass. Source-hover passes the full run but has a focused initial-color timeout before pointer input; retain the variant instead of calling all highlighting accepted. Build/core/format pass. Published/installed job114553267448 is terminal: published dotnet tests again exceeded600seconds before any installed outcomes; retain artifacts/current-installed-05bf612.log. No deadline was increased. Exact full-native log: artifacts/current-native-05bf612.log.

Next patch gives the original #content div a named, focusable main landmark so Chromium exposes the actual inner scroll surface. The prior root reports Scroll support but no vertical extent, while the unnamed inner container is omitted. Native menu lookup now selects visible owned peers and dismisses leaf View menus; UIA Invoke no longer forces reader foreground over Settings/menu owners. Recent activation defers until the invoking menu finishes restoring focus.

Existing exact font/pixel/print assertions remain: typography fixture requests 28px body because24px produces20→28px glyph heights, exactly40%, rejected by its strict greater-than40% comparison. The narrow print fixture explicitly centers its custom body before testing the Full-page margin/width reset. Palette checks sample the owned empty8px reading gutter rather than a glyph/find mark; no color expectation is changed. Source color/picker failures retain actual values. No test is skipped or weakened; actual hosted behavior must prove these changes.

Local zero-warning Release build,586 core tests/100% measured lines pass in artifacts/reader-accessibility-core. Real pipe stress25runs/75tests passes, zero skips; the older intermittent disconnect failure did not reproduce, and no speculative pipe change was made. Formatting passes. Owner preview55472 stays responsive and preserved. Azure access unavailable; azure-signing-admin.md provides exact immutable OIDC, resource/profile verification and profile-role commands. No signing/release, review acknowledgement, Azure mutation or merge is claimed.

Current owner review launch - 2026-10-11

Owner-requested latest self-contained build is open from artifacts/owner-1.0-review-publish/MarkdownViewr.Windows.exe, PID55472, with title Review-1.0.md — MarkdownViewr. Separate persistent review profile: artifacts/owner-1.0-review-profile. Launch metadata is retained in artifacts/owner-1.0-review-launch.json. Do not overwrite this publish output or interrupt the owner preview while reviewing. Initial process/title/Responding readbacks succeeded; no physical desktop input or visual acceptance performed.

Current local gates: zero-warning Release build,582 core tests,100% measured core line coverage,25 adapter tests and full formatting verification pass. Default-file registration has five passing isolated registry tests in artifacts/release-review-adapters/release-review-adapters.trx. Install/update/ uninstall hooks and Settings → Advanced → Choose default file types are implemented. User chooses defaults in Windows; portable previews do not register. Actual installed chooser, Explorer double-click and lifecycle acceptance remain pending under issue #14. Source-hover regression and signed release acceptance remain open; latest review launch does not establish release readiness.

Committed implementation and edition follow-up - 2026-10-11

Signed/DCO0eb3a0e and841798c are pushed to feat/windows-viewer/PR#3. All normal commit hooks passed. Vendor notices retain original bytes through scoped Git/hygiene attributes; secret/workflow checks remain enabled. Exact hosted CI38164841448 is live on0eb3a0e. Build/core/format, scripts, security and CodeQL have passed; native and published/installed acceptance are still running. The current source-hover case has not yet emitted a verdict.

Subsequent local work implements a distinct installed dev identity and package ID, with edition-specific title/settings/log variables and edition-aware isolated smoke fixtures. The new host composition reads the actual Velopack channel before activation/UI/log services. Core586/586 and100% measured lines, zero-warning Release, format and55 script tests pass; changed script passes both analyzer partitions. Separate stable/dev IDs are prepared for the release caller; signing remains fail-closed until the reviewed/published catalog builder is available.

A distinct gclo-family navy Markdown/reading vector was generated through AppKit BrandTool; all nine ICO frames16..256 are valid and the256px frame was visually inspected. The app gradient now matches it. WinUI3 receives a source-project MIT credit in Components while proprietary binary-package license notices remain in the audit/distribution inventory. Final icon/credit/edition build has zero warnings/errors;586 core tests and 100% measured lines pass with TRX/Cobertura in artifacts/edition-final-core. Formatting passes. A focused hosted source-hover job is prepared to produce a fast actual pointer/color verdict and retained TRX, alongside full acceptance. The owner preview PID55472 still runs from its preserved earlier output; it has not been replaced.

Active work and authority

Build the full Windows counterpart to Darin's markdownViewr with published AppKit 0.1.0. Identity: MarkdownViewr / MarkdownViewr.Windows / markdownviewr-windows. PRODUCT.md remains the full scope. Topic feat/windows-viewer, draft PR #3. Owner authorizes signed/DCO commits, pushes, configuration and tickets. The owner now authorizes completion and stable1.0/dev publication following gclo. Preserve review/security/signing gates; no fabricated human review or new Azure sign-ins. Hosted Windows UI tests are authorized; no current local desktop reservation.

Active 1.0 and dev release work - 2026-10-11

The owner cleared the prior goal and explicitly resumed work to finish and release stable1.0 and dev versions following gclo. The paused queue below is historical, not a current stop instruction. Full PRODUCT scope and owner feedback remain required.

Plan: (1) fix owner regressions and UI requirements; (2) pass core/build/style plus actual current native/published/installed stable/dev acceptance; (3) verify and configure repository-specific Azure OIDC/signing and gclo-style isolated editions; (4) complete review/checks, signed commits/push and publish verified releases.

Commit authentication retry succeeded. Commit 841798c is signed and DCO-signed; it preserves the original four-file native-window correction and passed hooks. The remaining implementation is being committed after local verification. Implemented locally: removed toolbar depth duplication, labeled Contents/Print; explicit Contents/Source new-window defaults independent of local toggles; open-source-only About view with full license audit catalog preserved; accurate disabled-editor native tooltip; loaded-handle timestamp/stale/folder footer. Long theme/editor forms now use native Settings pages, Back and fixed Save/Cancel; theme management uses adaptive list/detail layout and preserves copied draft loops, import/export/newer-schema conflicts and validation. First full build passed with zero warnings/errors. New default-persistence tests and native hover regression are prepared; source highlighting itself is deliberately not changed before a real red-capable pointer test runs.

gclo's existing release environment confirms tenant4ebeb0ad-5782-487a-a1b4-5080255774cf, kof22signing/releases/EastUS and publisher James Maes, but these are reference configuration, not actual Azure resource verification for this repository. MarkdownViewr release variables are absent. Current Azure CLI has no login; no new sign-in initiated. Official desktop-tool initialization reports missing native pipe; no local GUI fallback/input performed. Hosted testing follows push.

Historical paused owner review - 2026-10-11

Historical checkpoint only: the owner paused work at this point and subsequently resumed the full release goal recorded above. The following text records that pause. Earlier signed-commit/push authorization remains bounded by the pending 1Password-ready reply. The original staged four-file patch remains82+/10-.

New tickets: #26 right footer timestamp/stale indicator/Open folder; #27 source highlighting disappears permanently after pointer hover (owner report, not yet reproduced); #28 disabled Open in editor hover explanation; #29 gclo-family icon redesign. Existing #18 now requires removing only the toolbar H1-H6 dropdown and consistent Contents/Print icon+text labels. #21 records owner rejection of the crowded inner modals: propose adaptive Settings list/detail pages, brief native confirmations, preserved theme/CSS drafts and native pickers. Add explicit new-window Contents/Source defaults, both off; current-window toggles must not rewrite them. Issue #24 now calls for actual shipped open-source credits/project/license links only in Components, with Darin in Contributions and all required notices preserved.

These requirements are queued, not implemented. Source unit/color coverage does not disprove the owner-reported pointer regression. Do not claim an accepted toolbar/settings layout or full application completion.

Reference document CSS checkpoint - 2026-10-11

Before the pause, the document-only stylesheet was ported from Darin's pinned 6d08bc9d27d7d7b2c2fa95bb282da330b8cf9021 template, retaining MIT headers. Embedded Themes/Document.css and DocumentPage provide #content/#content-inner; legacy custom variables remain alongside original aliases. Reading width applies to the inner container after custom CSS. Browser scrolling/navigation/source coordinates now use #content. Sanitization retains only bounded code-language and fixed document classes; metadata keeps accessible headers. Print resets scrolling containers and applies page padding once.

Completed local gates: zero-warning Release build,580/580 core tests,100% measured core line coverage, formatting and self-contained win-x64 publish. Evidence: artifacts/reference-css-verified/reference-css-verified.trx and artifacts/reference-css-verified/e1f564a9-bb6e-4628-8d9a-a2e1fa5c0df6/coverage.cobertura.xml. Ten new style/page/security regressions pass. Two existing actual-paint UI cases were adapted to the original document container; neither was run. UI discovery remains93 cases (69 desktop/24 adapter), expected92 per installed channel.

Review-reference-css.md was launched from artifacts/reference-css-publish using its separate review profile (launch recorded as119988). Initial startup/document opening was observed before pause; this is not full visual/native acceptance. The fixture deliberately forced Source on and does not define production defaults. No current native/distributed/install/signature or hosted-CI acceptance exists for this CSS work. Global/per-theme selector parity for native TOC/source, raw HTML/ heading fidelity and actual layout/paint remain open. Update the CSS attribution inventory and threat model when implementation resumes. Code remains local and unstaged; no new commit, push, merge, tag, release or Azure sign-in.

Default-file Settings action - 2026-10-11

Issue #14 follow-up is implemented locally: Settings → Advanced has Choose default file types and optional-.txt guidance. Only actual installed copies with an unchanged owned command/RegisteredApplications value enable it. Native click revalidates ownership. Windows 11 23H2+ opens the exact registeredAppUser page; earlier versions use general Default Apps and .md instructions. Portable previews show install/repair guidance. Launch failure gets manual instructions and content-free diagnostics; defaults are still selected by the Windows user.

Separate-output full Release build passes with zero warnings/errors at artifacts/default-files-build/bin. Eleven real isolated registry/activation tests pass (two new route/ownership/default-preservation cases);570 core tests pass and 100% measured core line coverage gate passes. Formatting passes. A native page acceptance case compiles, not run;93 UI-project cases are discovered only (69 desktop/24 adapter; expected92 per installed channel). Actual installed chooser/selection/Explorer and hook lifecycle remain unverified. No owner preview replaced or new local desktop input, sign-in, commit/push or publication. Original staged four files82+/10- remain unchanged; the existing signing-authentication reply is still pending.

Historical default-file checkpoint preceded the local document CSS port recorded above. Full PRODUCT scope remains active, including current native/distributed acceptance, Print/PDF, reference fidelity, standards and signed production artifacts.

Windows activation and registration - 2026-10-11

Issue #14 has local implementation: Velopack install/update/uninstall callbacks advertise md/markdown/mdown/mkd/txt under HKCU with quoted stable current-exe commands, Default Apps capabilities and a REG_NONE AllowSilentDefaultTakeOver marker. Channel/executable-specific ProgIDs, unchanged-command checks and owned cleanup preserve other installs, viewers and user defaults. No real registration or installer was executed locally; only UUID-subtree registry fixtures were used.

SDK AppInstance chooses a primary per executable/profile. Sender-canonicalized paths travel through a current-user-only generated-schema pipe to the native UI queue.128-path/1MiB/10second/16-pending bounds; unknown/null/relative/oversized payloads rejected; no command protocol. Initial/duplicate/empty/error requests reuse native reader paths; foreground rights are delegated by the launcher. Invalid startup notification survives browser initialization. Existing pending startup path duplication detection is retained.

Actual adapter tests initially8/9: InvalidDataException derives SystemException, so an oversized frame escaped the original catch and stopped the listener. The explicit catch fix preserves all assertions; final9/9 pass, including malformed recovery and idempotent shutdown/rebinding. Red/fixed/final TRXs are retained under artifacts/activation-boundaries. No diagnostic probes remain.

Fresh full separate-output Release build/publish pass;570 core tests/100% measured lines, formatting and docs lint pass.90 UI-project cases discovered only (68 desktop/22 adapter; expected89 per installed channel). Two new real native secondary-process/relative-Unicode/profile/duplicate/watcher cases compile, not run. Controlled desktop/distributed/Explorer/installed acceptance remains needed.

Velopack1.2.161 verified the corrected Program.Main Build/Run callback chain and packed a local unsigned stable fixture in artifacts/activation-package. Both portable/full payloads retain all543 published files byte-for-byte;11 notice files match source bytes. Publish evidence and unsigned-only flag are retained. No installation, actual hook lifecycle, signed-artifact claim or publication occurred.

Owner preview103040 remains Review-toolbar-splash.md using the earlier preview output/profile; it has not been replaced by activation-build. Original staged four files82+/10- remain unchanged; new work is unstaged. Existing1Password ready reply still pending; no signing retry/push/new Azure/merge/tag/release. Full PRODUCT requirements, native UI, Print/PDF, original CSS/render/activation parity, standards and exact production signatures remain open.

Splash and toolbar owner preview - 2026-10-11

Owner screenshot follow-up #18: reduce toolbar height, align TOC/depth/Print and reading controls, remove the wide gap and group commands. Native CommandBar now uses a48-DIP row with consistent40-DIP fixed controls and natural left alignment; Print remains fixed while reading commands retain dynamic overflow. Actual geometry assertions are prepared; native acceptance is still pending.

New #25: reused the published AppKit branded splash already connected to initial launch. Settings → Advanced now has gclo-style Show splash/duration controls (500–30000ms,250ms steps) and startup update checks, moved out of View. Checked saves update only startup fields, broadcast to all reader baselines and preserve other preferences/CSS drafts. Existing saved durations remain unchanged. A real shared-preference/native-controls regression is prepared, not executed.

Fresh separate-output Release build: zero warnings/errors.570 core tests pass, 100% measured lines; format/docs lint pass.79 UI-project cases discovered only (66 desktop/13 filesystem; expected78 per installed channel). No local input acceptance ran. Computer Use passive observation was attempted, but its native pipe was unavailable; no screenshot or input action occurred.

Owner preview opened successfully as Review-toolbar-splash.md — MarkdownViewr, process103040, with source visible and a5000ms splash in its separate artifacts/splash-toolbar-profile. Startup update checks are disabled in that review profile. Other owner windows were preserved. Output: artifacts/splash-toolbar-review/bin/x64/Release/net10.0-windows10.0.19041.0/ MarkdownViewr.Windows.exe. Evidence: artifacts/splash-toolbar-core/ 53b3f3ce-c62e-40f9-afac-cfcf1a2ed905/coverage.cobertura.xml and artifacts/splash-toolbar-ui-discovery.log. Actual toolbar, Settings and splash visual/duration/distribution proof remains pending; launch logs prove only startup/document opening. Signed commits/push await the existing1Password ready reply; no signing retry, merge, tag, release or Azure change occurred.

Latest owner review changes - 2026-10-11

Owner feedback is implemented locally: #24 About has Contributions below the AppKit header/license, with Darin's repository/site/license links. Components individually links 23 application/platform and 29 development dependencies; independent tests compare every package/version with actual restored assets. Eleven distinct packaged SDK/WebView/tensor license/notice files are retained verbatim and match copied review-output bytes. Microsoft binary license terms are identified separately from MIT components.

Issue #21 replaces the rejected modal Pivot dialog with a separate resizable WinUI Settings window: adaptive left NavigationView, native pages/controls and owned theme/editor dialogs/pickers. Routine width preferences save immediately; advanced CSS has Apply, and closing discards unsubmitted CSS. Shared saved appearance refreshes open Settings baselines without overwriting its CSS draft. Issue #18 Print stays in the fixed toolbar area even when other commands overflow; Theme uses the native Color glyph rather than Highlight.

Issue #16 is implemented locally: native read-only RichEditBox with literal SetText, passive parser character spans, contrast-adjusted document accents, Windows light/dark/high-contrast updates, stale parse/paint guards and exact original visible source copying with no rich clipboard formats. Native Text/Value accessibility, find/fold/reload and existing scroll behavior remain test targets.

Latest evidence: full separate-output Release build zero warnings/errors; 570 core tests,100% measured lines;78 UI-project cases discovered only (65 desktop/13 filesystem, expected77 per installed channel). Native source color/selection/clipboard and standard Settings acceptance cases compile; no local desktop automation ran. Initial review startup failures were diagnosed: unsupported HighContrastChanged registration now uses UISettings color changes; read-only RichEdit character formatting uses a synchronous writable guard that restores read-only mode before returning/yielding. The corrected review opened Review-updated.md successfully, most recently in process 94448. Owner windows were preserved; source color/clipboard acceptance is still pending. Final native and distributed acceptance, missing system Print/PDF handoff, original CSS/activation, standards and production signature proof remain required. Original four staged corrections are unchanged; signed commit/push still awaits the pending1Password ready reply. No signing retry, merge, tag, release or Azure changes occurred.

Review output: artifacts/source-highlight-fixed/bin/x64/Release/ net10.0-windows10.0.19041.0/MarkdownViewr.Windows.exe. Evidence: artifacts/source-highlight-about-core/38ccc305-1af2-4456-9380-a7420b4850f0/ coverage.cobertura.xml, source-highlight-ui-discovery.log, about-component-inventory.json and review-license-verification.json. Earlier sections describe historical implementations and acceptance milestones.

Owner build handoff - 2026-10-11

The owner requested another build to try. A fresh full Release build passed with zero warnings/errors, then opened README.md in a new responsive process (PID 107716). The older Debug window showing AGENTS.md (PID 91712) was preserved. This verifies build and launch only; no automated desktop input or acceptance ran. Settings, source split, toolbar, attribution/Help and Print/PDF options are available for owner review. Source highlighting has a compiling core draft but is not connected to the native source control yet. The previous 538-test/100% coverage result predates that draft; new highlighting tests remain required. Signing/push and runtime Print/PDF verification remain pending.

Owner requests and local implementation - 2026-10-11

Every current owner request is tracked: #16 source syntax highlighting, #17 50/50 draggable source split, #18 Mac toolbar parity, #19 Darin attribution, plus #20 gclo Help/defaults, #21 dedicated Settings, #22 system print/sizing, and #23 PDF verification/open actions; #6 holds automatic reload/fallback requirements. Source highlighting, the reworked Settings window, source split, toolbar and linked About credits are implemented locally; current native acceptance remains pending.

Superseded first #21 implementation: File → Settings with native Appearance, Themes and Editors tabs. Width/global CSS edit a copied draft; explicit Save merges against the latest store and broadcasts to open readers. Theme/editor actions retain separate saves and return to the same parent draft; no overlapping dialogs. Removed six theme/appearance editing entries from View and moved editor configuration into Settings. Everyday reading controls remain in View. Native menu tests now use actual Settings tabs; a new parent/child cancellation case is prepared. Keyboard entry uses File/Settings access keys.

Locally implemented #17: source opens at50/50 in fresh windows and when reopened, excluding the outline/dividers. Drag changes proportional widths without the old600px cap. Left/Right resize the focused divider; Home resets equal columns, with a visible keyboard focus border. Ratio is window-local, not persisted; legacy SourceWidth remains readable for older settings.21 layout regressions cover narrow/large windows, drag direction, both bounds and invalid inputs. The real physical-resize case now checks actual equal columns, growth, keyboard reset/resize and reopening rather than the obsolete saved pixel preference.

Latest gates: zero-warning full Release build;538 core tests,100% measured lines; format verification passes. Headless UI-project discovery finds75 cases (62 desktop and13 filesystem; installed expectation74). New native Settings/ source/toolbar acceptance has not run. Original staged four-file signing correction remains unchanged; existing1Password authentication and local GUI reservation replies are still pending. The older Debug window predates these changes; the owner now has a fresh Release window. Evidence: artifacts/settings-source-core and toolbar-ui-discovery.log.

Locally implemented #18: native CommandBar preserves the reference order: TOC, H1–H6 depth, flexible space, source, minus/percentage/plus zoom, enabled theme picker and editor. Print is in native More overflow. Narrow layouts use the built-in dynamic overflow; accessible labels/tooltips/toggle state remain tied to existing handlers. Depth is disabled with hidden TOC; zero existing editors is disabled, one existing editor launches directly by stable identity, multiple existing editors offer ordered file/folder choices. Menu/theme broadcasts and active-document changes refresh toolbar state.

Editor saves now merge against their copied baseline and check persistence before applying. An explicit save updates each open reader and its saved baseline; later local saves cannot restore a stale editor list. Four actual UI cases cover reading/menu synchronization, file/folder/direct editor process arguments and Print cancel, narrow overflow, and sibling editor launch/stale source save. These compile/discover only; no local input ran. Build/format pass; core is unchanged since the measured538-test/100% coverage gate.

Locally implemented #19/#20: AppInfo description/component credit, accessible About links to the original Mac repository and verified kelkhoff.com, README/product/distributed notices. Help matches gclo main198a56213b: repository, issue chooser and Community support. These use the Windows repository, never Darin's support destinations. App/starter Discussions enabled and read back true. AppKit#28 and windows-app-template#3 track shared defaults in isolated worktrees: AppKit/artifacts/help-menu (feat/help-menu from main839fb72) and AppKit/artifacts/starter-help-menu (feat/help-menu from onboarding758e773). Both WinUI/WPF samples and starter use existing APIs; no package version changes.

Print options now use a responsive wider layout and opt-in Open PDF/Open folder checkboxes. PDF export loads the generated file through Windows' PDF API and requires pages before reporting success or starting either native action. Handler failures remain independent and do not misreport successful creation. Print-phase logging distinguishes preparation/selection/export and records runtime version without private paths/content. The missing system-dialog root cause remains unproven; earlier hosted success does not resolve the owner's report. #22/#23 remain open. GUI reproduction reservation and PDF-outcome questions are pending; no desktop input ran. The owner is still using the earlier Debug build; these changes compile in separate Release output and are not in the running process.

Live-reload native filesystem tests pass6/6 without an app/desktop launch. A failed refresh now explicitly shows the retained previous snapshot and File → Reload. A real prolonged-lock/automatic-recovery acceptance case compiles but has not run. Current UI count becomes70 native/published and69 per installed channel; all new actual About/print/fallback assertions still require execution.

App517 core tests/100% measured lines; Release full build zero warnings/errors. Shared default builds pass; AppKit115 unit tests with100% core/updates lines, starter20 core +14 CLI tests/100% core lines,56 Pester tests and changed-script all-rule two-pass analysis pass. All three formats and the final app build pass; nine-doc lint passes. Fresh headless discovery confirms70 cases; no actual desktop acceptance ran. The actual packed starter generated both changed-owner CLI and GUI-only apps with correct Help URLs; locked restore/build and20 core tests pass for each, plus14 CLI tests in the CLI variant. No generated desktop UI was run. Evidence lives in app artifacts/ owner-followups-core and starter artifacts/help-template-* / help-generated-*.

Original four staged corrections remain unchanged (82 additions/10 deletions). All new changes remain uncommitted/unpushed while the existing1Password signing question awaits authentication. Do not bypass signed/DCO commits or rerun signing until the owner confirms readiness. Azure remains deferred; no release/merge.

Requested local launch - 2026-10-11

Owner requested a build and interactive launch. The full solution rebuilt with zero warnings/errors; the Debug x64 executable opened a responsive native MarkdownViewr window (PID91712). No automated mouse/keyboard tests ran. This launch does not provide new feature or distributed-artifact acceptance.

Current local renderer/theme milestones and signing dependency

Pushed head remains 1cfc07f. Four window-test corrections remain staged and validated; 1Password signing authentication is still required after two failed attempts. No bypass, corrected commit/push or fresh hosted result exists.

Independent unstaged work adds four enabled-by-default Markdown extensions and native View toggles using the existing Markdig parser. Immutable options are captured before asynchronous reads; separate saved fields merge sibling changes individually. Passive mark/ins markup passes the existing sanitizer; selected palette styles apply to highlights/underlines. Parser AST normalization preserves literal code/newline boundaries and reference no-whitespace caret/tilde semantics without rewriting original UTF-16 source positions.

All native typography controls now expose body/heading/code font families, body/code and h1–h6 sizes, and line height. ReaderTheme.Edit creates a copied JSON schema, preserves unrelated metadata, rejects unknown fields/nonfinite or invalid sizes, and applies the existing font/CSS validation. Invalid drafts and cancellation leave originals unchanged.18 focused theme cases pass. Existing automation IDs remain; a new hosted-only case saves all fields, requires real heading/body/code glyph growth and verifies cancellation preserves the accepted theme. It compiles, not executed. Actual new desktop acceptance remains required.

Reader-wide appearance now provides native limit/width/global-CSS drafts. Defaults match the reference (enabled,1000px); stored corruption is repaired, invalid drafts remain open, and cancellation preserves settings. Global CSS precedes per-theme CSS, with enabled width applied last and scaled by reading zoom. Screen-only styles cannot change print layout. Saves merge against the latest store and broadcast to all open readers; revision guards supersede older asynchronous updates and update sibling save baselines.22 focused regressions cover bounds/defaults, CSS cascade, HTML embedding, separate print output, source-generated JSON and field merging.

Theme management now provides a copied native list for ordering, enable/disable, delete and restoration. Enabled choices alone populate reading menus/cycling; Ctrl+Shift+Down/Up requires owned reading focus. Deleting a built-in removes its user override and records a restorable tombstone. Reference restoration keeps edited built-ins as uniquely named custom copies, updating saved selection/order, then restores/enables originals. Theme commits merge unchanged fields from the latest store and broadcast catalog/selection to open readers with save baselines and asynchronous revision guards.23 focused cases cover order, wrapping, empty lists, corruption, copied arrays, deletion, restoration collisions/metadata, JSON defaults and sibling merges. No dependency/version changes.

Theme transfer now uses owned multiple-file JSON selection, serial bounded reads, per-conflict overwrite/keep-both/skip and explicit compatible newer-schema consent. Known schema/font/color/size/CSS/depth checks remain enforced. Strict Parse still rejects newer versions; compatible saved/import parsing retains their original version/metadata. Unconfirmed newer imports cannot be persisted. Export includes disabled choices and writes exact validated JSON to the user's destination. Invalid files do not prevent other batch entries from importing. Errors log only exception kind/HRESULT, without paths/content. Manager New/Copy/Edit/Use selected and import/export finish their secondary dialogs before reopening the copied manager draft; only Save themes commits it. Rename collisions stay in the editor, and owner closure stops reopening. No dependencies or workflow changes.

Local517 core tests/100% measured lines, zero-warning full solution build, format and four-doc lint pass. Latest coverage: artifacts/theme-transfer-core;46 focused transfer regressions include all20 actual bundled JSON round-trips, bounds/read position, BOM/Unicode, invalid input/cancellation, schema consent/security, conflict/version/metadata retention, copied drafts and safe Windows filename suggestions. Earlier extension/ typography/appearance/list checkpoints retain32/18/22/23 focused cases. Headless discovery (correct AnyCPU test-project mapping) finds69 UI cases; evidence: artifacts/theme-transfer-ui-discovery.log. No app/desktop input was executed. Twelve new runtime cases compile but have not run: six prior renderer/typography/ appearance/list cases plus six transfer/cross-dialog/cancel cases. Existing restoration also requires retained override JSON/paint and explicit original selection. Original staged window correction alone expects57 native/published and56 per installed channel. All independent local milestones require69 native/published and68 per installed channel. No new desktop/PDF/current-head hosted proof exists. Remaining CSS-variable/DOM-selector fidelity, raw-HTML extension/source-heading edges, local link/render behavior, Windows activation and standards/signatures are not complete.

Printing baseline verified; expanded geometry investigation

Native File/Print/Ctrl+P, copied themes/layout preferences and explicit native PDF saving are implemented. Core363/100% measured lines;55 scripts; build/format pass. Signedec5f98f / filtered38125751638 passes all3 original cases, zero failures/skips: keyboard draft cancel, actual Windows print UI cancel and real default/themed PDFs. Actual pixels prove text, expanded folded image, white ink-saving page, hidden images and active-theme background. Exact actual glyph/view rectangles prove unchanged nonzero reader position/zoom, source text and collapsed content after both exports. Evidence: artifacts/print-exact-filename-38125751638.

Hosted probes proved41pixel PDF reading movement. SavePdf restores validated vertical position in finally only for the same ready navigation; no completion is guessed for void native print UI. Filename typing waits for exact full native readback. Stale UIA200% values are replaced by actual glyph/view assertions. Cleaned300e145 / CI38126078284 fully passes: native/published52 each, installed stable/dev51 each, zero failures/skips. Both AppKit apply/restart probes reach expected versions without check/apply errors; fixtures are unsigned. Retained native log and installed evidence: artifacts/print-clean-native-38126078284.log and artifacts/print-clean-verified-installed-38126078284 (six real PDFs).

Two additional native-output cases now compile/format locally: first printed heading glyph ratios for standard/matching zoom, real40px padding shift and paired find/source selection/screen paint after each PDF; saved user-theme240px block width versus full page and actual optional border rows. New helper edits actual native options, including padding NumberBox; all generated PDF/PNG bytes retained. Signedd0a225d / CI38127089763 finishes native/published53/54, zero skips. Actual saved custom-width/border/full-page case passes. Font/padding case fails before PDF output at a requested zoom wait; installed channels are not reached. Exact expected/actual glyph rectangles and native state are now retained on failure. Diagnostic6e17674 proves the second step: initial35px,121% actual44px, expected42.35px from multiplying an already-rounded UIA text box. The new PDF case now requires actual increasing screen glyphs and completed native percentage, plus bounded final screen growth; precise standard/matched font ratios remain asserted against real PDF glyph bands. No PDF/state assertion is removed. Retained red log and published TRX: artifacts/print-geometry-native-38127089763.log and artifacts/print-geometry-installed-38127089763. Corrected head requires54 native/published and53 per installed channel. No local GUI input or new dependency. Correctedbf4fcdc / CI38128311242 fully passes: native/published54 each, installed stable/dev53 each, zero failures/skips. All5 Print_ cases pass in every build, including actual PDF font/padding/paired-find and original cancellations/ image/background/nonzero-state cases. Retained24 PDFs/48 PNGs/TRXs: artifacts/print-font-verified-installed-38128311242; native log: artifacts/print-font-native-38128311242.log. Actual before.AppKitApplyCalled and restarted=true in both channels; expected stable0.4.0/dev0.3.0-beta.2; all before/ after check/apply errors null. Fixtures unsigned; production signing not proved. ADR-0003 remains proposed for maintainer review.

Live settings validate. Official conformance34PASS/1FAIL/1WARN/3REVIEW: required standards inventory lacks app, confirmed live. Exact reviewed addition prepared, not applied/merged; see docs/standards-readiness.md. Actual signing remains deferred.

Native windows and recents milestone

New window-local initial paths replace rereading process arguments. Track native XAML windows on one UI thread; independent watcher/browser/hooks/zoom; Ctrl+N/Ctrl+W and Exit; shared log closes only after the last reader. Modern App SDK multiple-file picker includes md/markdown/mdown/mkd/txt. Private recent history20, successful opens only, duplicate focus, missing errors and clear. Source-generated delta merging protects sibling settings and cleared history from stale window snapshots.

Signed/DCOe48a08c implements this milestone. Local376 core tests/100% lines and zero-warning build/format/docs/hooks pass. Three new hosted-only native lifecycle cases compile; no local GUI input. ADR-0004 and threat model updated. 1cfc07f / CI38129552334 native54/57, zero skips: all original54 pass, three new cases fail. First caches a glyph across zoom navigation; second requests unsupported Invoke from SourceToggle after actual New/Recent/Close/missing/clear steps; third cannot find Open picker's filename field. Fresh glyph lookup and verified owned physical menu input retain all state/reload/history assertions. Picker diagnostics now retain owned tree and generic exception/HRESULT; no selector change is guessed. Actual native foreground focus and source preference persistence are required. The missing-file window loaded nonempty history before Clear; its later preference save must not resurrect that snapshot. Retain native red log: artifacts/windows-first-native-38129552334.log. Published process timed out at300seconds after two recorded new-case failures; no TRX/installed-channel outcomes. Retained partial output/screenshots: artifacts/windows-first-failed-installed-38129552334. Outer full-UI-suite budget now600seconds; all individual10/30second waits/assertions unchanged. Association/activation registration remains required. Full reference audit also retains theme ordering/enable/delete/cycle, JSON import/export conflicts, all typography/global CSS/content width and four configurable rendering extensions in PRODUCT/TODO; none is claimed complete.

Current outcome

Signed 690be07 fixes repeated outline activation. Native ItemClick supplies the TextBlock content, not its ListViewItem container. Both now carry the bounded numeric heading tag; activation accepts tagged FrameworkElement content while SelectionChanged retains keyboard navigation. No title lookup or source mapping change.

The original source regression passed on 690be07: source-diagnostics38121389088, job114416668837, including source focus preservation, actual source/reader middle glyphs, repeated last-heading activation and the final physical-wheel assertion. TRX retained under artifacts/source-clicked-content-verified-38121389088. Temporary workflow, tagged probes and source geometry logs are removed. Cleaned2639e2d fullCI38121762124 passed: native49/49,published49/49, installed stable/dev48/48, zero failures/skips. All other producers pass. Evidence retained under artifacts/source-clean-verified-installed-38121762124. New print acceptance remains pending.

Font zoom and named editors are implemented. Prior016c745 native/published48/49, zero skips; only repeat navigation failed. Zoom actual glyph/menu/toolbar/Ctrl/ reset/reload and named-editor cases pass. Core363 tests/100% measured lines, script boundary55 tests; zero-warning build and formatting verified.

Verified baseline and evidence

Previous fully accepted b0f3b86/CI38113042618: published44/44, installed stable/dev 43/43, zero failures/skips. Actual AppKit apply/restart uses synthetic unsigned fixtures; it does not prove production signing. Published predecessor failure TRX: artifacts/source-physical-reactivation-failed-installed-38120651378. Red clicked-content trace/TRX: artifacts/source-activation-boundary-38121148429. Superseded diagnostic jobs are not fixed-head acceptance proof.

Next steps

1. Require native/published57 and installed stable/dev56 on the window milestone; retain actual lifecycle/picker/update evidence.
2. Complete source raw-heading audit and broader zoom/theme/find/collapse proof.
3. Complete print #12 output/state acceptance, windows/recents/activation and remaining theme/render/link parity.
4. Finish standards inventory; exact signed stable/dev artifacts remain deferred.

Update TODO and tickets with measured results; keep the PR draft until reviewed. Current exact commit/job IDs are in ignored artifacts/CURRENT-CHECKPOINT.json. Historical details: reader/source notes.

Exact current native failure evidence - 2026-10-11

CI38164841448 is terminal on0eb3a0e:72/97 native cases pass,25 fail,zero skips. Build/core/format/scripts/security/CodeQL pass. Published acceptance exceeds the 600-second process budget and is terminated before installed-channel outcomes; this is not installed acceptance. Native/installed logs and artifacts are retained under artifacts/current-native-0eb3a0e.log, current-installed-0eb3a0e.log and current-installed-evidence-38164841448. The actual native suite took11m42s with 25 failures; investigate failures before making a measured process-budget change.

Source hover is reproduced exactly: initial heading color#75628B becomes#000000 at the first post-pointer assertion (SourceHighlighting.cs line37, before focus). Ranked hypotheses shared: native whole-document hover foreground, focus/selection reset, asynchronous repaint cancellation. Pinned WinUI generic.xaml confirms PointerOver/Focused/Disabled storyboards target ContentElement.Foreground. The first candidate removes only those foreground animations on template application, retaining native chrome and semantic range formatting. It requires the focused hosted regression before being called fixed; no local GUI input performed.

Other failures include document scroller/paint/typography/source geometry, native picker filename discovery, print-width output, new-window outline assertion, recent-window foreground and one pipe disconnect recovery case. Full scope and assertions remain; no failures skipped or weakened. The next focused hover job retains a real TRX alongside the full suite.

Actual GitHub OIDC readback uses immutable IDs: repo:KofTwentyTwo@47367449/MarkdownViewr.Windows@1413777106:environment:release. A name-only copied trust is invalid here. Administrator runbook reads actual account/profile/subject via stable ARM2025-10-13, retains existing identities, assigns profile-scoped signer permissions and documents required actual signature proof. Azure authentication remains unavailable; no new sign-in or cloud mutation.