Windows port implementation tracking #89

Current reconciliation - 2026-11-09

Native Windows delivery is incremental; whole macOS parity is NOT complete. This reconciliation reviewed 64 relevant issues (53 open, 11 closed), including the parity-label inventory and directly related onboarding, navigation, lifecycle, tooling and rendering issues. It preserves existing discussions, attribution, historical failures and acceptance checklists; it does not infer missing features from stale ledger rows or close broad visual trackers from unit/CI results.

Verified delivery and release boundaries

Live main was 2073e81af4f89f6eb11f27366f732b391808b3a8. GitHub compare reports zero commits behind main for each of these merges:

Windows beta31 is published from fd8d, BEFORE #965. It includes Wire/restored-input and preceding card/terminal work, not #965's new workspace form or #966's subsequently merged creation-only naming work. Its ZIP build/Verify and manifest hashes are release evidence, not an installer or in-app beta30-to-beta31 walkthrough.

Live exact-head PR check inventories were nonempty and complete: #962 head 1a5514a has 23 SUCCESS / 5 SKIPPED, #963 head 04cc0e7c has 23 SUCCESS / 5 SKIPPED, and #965 head 6afc111 has 22 SUCCESS / 5 SKIPPED. These are PR-head checks, not executions on the merge SHA. Linux/macOS path-gated skips are NOT executions. The #965 E1 local checkpoint records 684 unique units / 2,238 direct executions plus one separately derived proof / 66 shell sections; older 2,231-direct/65-section reports remain historical and correct for their own inputs. Source-bound native receipts are not relabeled as merged-head runs.

Creation-only workspace naming is now in main: PR #966 merged on 2026-11-09 at f0e8ac1e11a29d25f6282142a5be6339ae4c23ea (tree 78174bcac01e5a3ddcd6b0e955c8c5e69896c6d7). All 26 checks on PR head c30b789c2cb70a970960550b6b9e01b5f4f1af7e completed: 21 SUCCESS / 5 SKIPPED, including legitimate Linux/macOS skips, not executions. Local naming/full/shard/default-integration acceptance retains its original source bindings, NOT newly executed merge-head runtime evidence; original wrapper policy-stop and earlier integration failures remain preserved. Existing directory identities and legacy rename are unchanged. This bounded creation-only change does not establish all-Unicode or paired visual/device parity. Windows beta32 was published as a public prerelease on 2026-11-09 at 17:48:21Z from exact f0e8ac1e11a29d25f6282142a5be6339ae4c23ea / tree 78174bcac01e5a3ddcd6b0e955c8c5e69896c6d7, including #965 and #966. Hosted release run 42665844030 completed successfully on attempt 1 at that source. GitHub lists exactly the 49,982,485-byte ZIP (SHA-256 010807612977ffba628f0cb0a8c77e0fd09767aba93d7eae7b60b5c1d7430402) and 96-byte checksum sidecar; release evidence records fresh build/Verify and 50/50 manifest hashes. This unsigned invitation-only preview is not an installed beta31-to-beta32 upgrade, installer walkthrough, all-Unicode or whole-parity qualification; publication does not relabel old native receipts as new executions. Beta31 remains fd8d-based and excludes both #965 and #966. Local 040ba native acceptance records nine facts/two Create & Open cases/three preserved legacy identities; unfiltered 684 units with 2,238 direct executions plus one derived proof, the 66-section three-shard union and canonical default integration were separately accepted with all-six cleanup evidence. This does not resolve loop/node collisions in #94.

Issue summaries actually updated

Dated current scope/progress was added to 31 issue bodies, with 13 stale titles corrected. Original bodies remain intact below the dated update and no whole visual checklist was ticked.

Reviewed without manufacturing new evidence

These open issues retain unresolved scoped criteria; no current evidence justifies closure: #721, #722, #727, #728, #735, #739, #740, #748, #749, #750, #753, #765, #770, #773, #777, #799, #801, #857, #858, plus the separate layout-sharing product bug #712. Current App.jumpToNode still selects the project canvas (#799); the native provider still restricts SelectionItem to dynamic row keys (#801). Those are not presumed fixed by newer unrelated PRs.

#94 has no scoped issue body: loop/node collisions must not be equated to creation-only workspace slug normalization. Deliberate Windows extras in #770/#778 still require their own product decision; this metadata reconciliation does not authorize removal or a native-host rewrite.

These 11 existing closures are preserved, not reopened merely because a broader visual row is Partial: #725, #731, #737, #738, #741, #766, #776, #808, #812, #818, #915. Functional/tooling scope, extras-outside-parity decisions and their original evidence remain distinct from whole-port visual acceptance.

No new issue was created or closed. The finite M0-M4 functional cycle is delivered; whole Windows parity, paired visuals, higher-DPI/mixed-monitor/devices, complete glyph/clipboard/selection, onboarding/project/ingress/remote obligations remain incremental. No source/runtime changes, builds, tests, installs, desktop sessions, new images/privacy verdicts or CI dispatch/retry were performed by this headless issue reconciliation. Original failed/UNKNOWN/missing-cleanup/foreground attempts remain original failures or uncertainty; later passes do not rewrite them.

The original contributor task registry and dated baseline history below are preserved. Broad multi-surface task boxes are not blanket-checked from this finite functional cycle.

Goal

Deliver a native Windows x64 port of GraphCode while preserving the shared Swift
orchestration model, persistent terminal sessions, POSIX remote-host support, and the
application's terminal-first visual identity.

Provider streams

• Winghostty host extraction: https://github.com/coneilen/winghostty
• zmx Windows backend: https://github.com/coneilen/zmx

Execution rules

• Red/green/refactor TDD for every feature and bug fix.
• Dedicated worktree per task.
• Green, DCO-signed commits cherry-picked individually into the Windows integration branch.
• Provider commits pinned before GraphCode consumes them.
• Existing macOS behavior remains green throughout.

Durable task registry

• win-bootstrap — validation matrix, forks, tracking, worktree conventions
• win-tdd-harness — RED/GREEN/REGRESSION evidence and deterministic fixtures
• win-contracts — platform/protocol/provider/remote contracts
• win-swift-platform — shared Swift package, paths, process, shell
• win-protocol-dualstack — v1 compatibility and v2 correlation/subscriptions
• win-daemon-pipe — Windows daemon and CLI
• win-wing-baseline / win-wing-host-api / win-wing-* — terminal host extraction
• win-zmx-rebase / win-zmx-platform / win-zmx-* — real zmx Windows backend
• win-remote-spike / win-remote-bridge / win-remote-e2e — POSIX remote parity
• win-terminal-gate — two complete persistent terminal surfaces
• win-shell-scaffold — native Zig/Win32 GraphCode shell
• win-sidebar / win-canvas / win-workspace / win-forms / win-attention-worktree
• win-ui-integrate — visual, keyboard, DPI, IME, and accessibility integration
• win-packaging / win-hardening / win-final-pr

Each task update should record repository, branch/worktree, base SHA, owner, RED command
and failure, GREEN command and result, regression command, provider pin, PR, integration
commit, blockers, and next dependency.