Repository navigation
Windows parity: Rename propagation needs complete live multi-view qualification #733
Description
Current reconciliation - 2026-11-09
The 2026-10-13 narrowed scope below supersedes the Edit Details requirement: that Windows-only sheet is not macOS parity. Required acceptance is repeated Rename from card/sidebar/overview, correct graph/sidebar/second-view/status propagation, stable identity, and unchanged Cancel.
Later #965 default integration retains a connected deterministic rename path, with existing button/command fallbacks; it is not every real-daemon multi-view Rename entrypoint or persistence proof. Still open / Partial: the complete repeated native propagation/cancel/identity matrix. Creation-only workspace normalization neither renames existing directories nor resolves this loop-title issue.
The original report, acceptance criteria and historical evidence below are preserved; the dated scope/progress above supersedes obsolete missing-feature claims.
Is your feature request related to a problem?
Parity row Node update/rename (Graph overview and project canvas) in investigation/ui-parity-matrix.md is Partial.
macOS: Dedicated rename prompt and safe typed updates.
Windows today: Rename prompt and Edit Details exist; beta25 D6 passed rename via native OK, cancel unchanged and reopen.
Gap: Live connected-daemon propagation is an intermittent gap; Edit Details has no live open/cancel/submit evidence.
Describe the solution you'd like
A Dev Box check opening Edit Details, cancelling and submitting typed changes, and verifying propagation to a second view and graphcode status, repeated to expose the intermittent gap.
Describe alternatives you've considered
N/A
Additional context
This is a testing gap: Windows implements it; only live/runtime evidence is missing. Convert to a bug if propagation fails reproducibly. Parity status and the beta25 Dev Box review are recorded in #719.
Activity
coneilen commentedon Oct 13, 2026
Still open: Partial. Run: GraphCode-DevBox-Return-testing-gaps (attempt 2, installed beta26, 100%, injected input).
Rename. 3 of 3 submits reached the persisted graph, the sidebar row, the canvas card and
graphcode statuswithin 0.19–0.20 s.Edit Details.
status, so propagation to all four surfaces couldn't be shown. The loop bar wasn't measured.The intermittent connected-propagation gap did not recur in these runs.
coneilen commentedon Oct 14, 2026
Narrowed to macOS scope (2026-10-13). macOS is the ground truth, so requirements macOS does not have are no longer parity requirements. This was checked against macOS source by the parity extras audit; citations are in the audit and the ledger.
Dropped: the Edit Details sheet (macOS has none).
Remaining requirement:
[-]Windows parity: Node update/rename needs live connected propagation and Edit Details evidence (testing gap)[/-][+]Windows parity: Rename propagation needs complete live multi-view qualification[/+]