Skip to content

chore: record rail gestures and refresh diagnostics (refs #3093) - #3103

Merged
mblua merged 4 commits into
mainfrom
chore/3093-rail-click-observation
Oct 18, 2026
Merged

mblua merged 4 commits into
mainfrom
chore/3093-rail-click-observation

Conversation

@mblua

@mblua mblua commented Oct 18, 2026

Copy link
Copy Markdown
Owner

The intermittent first rail click currently lacks enough evidence to distinguish a missing click from node replacement or reverted selection. This adds scoped Debug/Trace records for gestures, real node lifecycle, focus/selection and relevant refreshes, sending each record immediately through the backend logger added in PR #3094.

Records use opaque identities and a closed, bounded payload. Info sends none; existing selection, focus, DOM identity, capture/reordering and product scheduling are preserved. The shared capture module retains its browser listeners and can also load in the original Node suites. This instruments future reproductions; the original cause remains undetermined. No final packaged build, installation, release or version bump was requested.

Validation at head 58e9dda23057267005f44a901606bc5627735424:

  • 377 focused tests across 12 files, plus 18 unchanged Node archive tests across 2 files.
  • Typecheck, frontend dependency gate, Rust arcs/cycles and complete phase diff check pass.
  • Real gate/FakeTransport controls cover interrupted gestures without click, node/config identity, two rails, selection reversal, immediate pending/rejected IPC, privacy, cleanup and bounded refresh pairs.
  • Both independent Grinches pass code and positive-proof review. The F1 regression covers pointer, mouse and compatibility-mouse presses outside the rail.
  • Full Rust PRE/POST graph/SCC sets/1,211 arc pairs match; three guards pass all 9 tests at 57a8e654c46f9727166922a755346bb51244a23d. Review confirms applicability to this head: the correction changes only two TSX files and leaves every Rust/build input unchanged. Those checks were retained, not rerun.

Main 970c907972be62dd642c0d3d8219a70b206da4ff is integrated without conflicts. Its menu JSON change is preserved; the PR owns only the ten planned frontend paths. V4 phase SHA256: 787AAD2AAD97444D23FE3A7CC4476FAC09042A7702E6A736431E00E8CD4DF618. Shared evidence: .ac/plans/3083-rail-click-diagnostics/P02-code-review-receipt.json and room25 room-shared/3093-P02/.

Closes #3093
Refs #3083

@sonarqubecloud

Copy link
Copy Markdown

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.

P02: Observe rail clicks and refreshes with immediate diagnostic delivery

1 participant