Skip to content

Correct overclaimed Show in Graph parity evidence - #423

Merged
coneilen merged 1 commit into
mainfrom
ledger-show-in-graph-evidence
Sep 23, 2026
Merged

coneilen merged 1 commit into
mainfrom
ledger-show-in-graph-evidence

Conversation

@coneilen

Copy link
Copy Markdown
Collaborator

Summary

Parity ledger row 112 (Show in Graph) was marked Validated on evidence that does not exist. This corrects it to Partial and states precisely what the live gate does and does not prove.

What was wrong

The row claimed two things that are not supported by the gate:

  1. "the return-to-graph-card walkthrough now run against the real shell build and pass" -- there is no such walkthrough. Tools/windows/uia-live-gate.ps1 contains zero occurrences of graph-card. The only file on main referencing graph-card besides the ledger is Accessibility.zig, which is the Zig contract, not the tree the live gate traverses.
  2. "the workspace UIA tree exposes a stable invokable Show in Graph child" -- $workspaceShowGraph is discovered at uia-live-gate.ps1:1156 and checked for non-null at :1188 with the message workspace chrome omitted the Show in Graph child. It is never passed to GetCurrentPattern, never given an InvokePattern, and never invoked. Presence is the entire assertion.

The underlying feature is fine; the menu action and loop bar exist. Only the evidence claim was overstated, which is the more damaging failure mode: a Validated row is what a reader trusts when deciding a surface needs no further work.

What the row says now

Presence of a workspace-show-graph-* child named Show in Graph in the real shell build, with the exact file and line numbers backing it, plus an explicit statement that invocation and the resulting navigation still need live evidence. Status Partial.

Doc-only change. No behavior, no test, no gate modification.

RED: grep for the cited evidence -> git grep -c graph-card -- Tools/windows/uia-live-gate.ps1 returns no match on main, so the row's "return-to-graph-card walkthrough" citation names a walkthrough that is not present in the gate
GREEN: row restated to match the code -> row 112 now cites only uia-live-gate.ps1:1156 discovery and :1188 Require, both of which exist and assert exactly presence, and the status is Partial
REGRESSION: verify no other row depends on the removed claim -> audited all Validated rows for graph-card and workspace-show-graph references; row 112 was the only consumer, and the recount is 50 Validated / 42 Partial / 2 Blocked

Provenance

Found while verifying a sibling session's claim on #421 that graph-card was an aspirational Zig-only contract id safe to delete. That claim checked out, but it exposed that a Validated ledger row was citing the same id as passing live evidence. This is the second such row: #418 is separately rewriting row 53, which asserted Windows keeps Move as an Explorer /select handoff after #408 had already replaced that with a disabled unavailable item.

No conflict with in-flight work: #421 edits row 151, #418 edits rows 53/54/87.

Row 112 was marked Validated and cited a "return-to-graph-card
walkthrough" passing in the live gate. No such walkthrough exists:
uia-live-gate.ps1 contains no graph-card assertion at all, and the
workspace-show-graph element is only ever discovered and checked for
non-null presence (:1156 discovery, :1188 Require). It is never
retrieved via InvokePattern and never invoked, so the "stable
invokable" claim is also unproven.

Restate the row as Partial, describe exactly what the gate does prove
(presence in the real shell build), and name the missing evidence.

Signed-off-by: Colin Neilens <coneilen@microsoft.com>

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@coneilen
coneilen force-pushed the ledger-show-in-graph-evidence branch from c9126d6 to aeb89cc Compare September 23, 2026 01:50
@coneilen
coneilen merged commit 32bb104 into main Sep 23, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant