Skip to content

integration: ten UX fixes + Gnirehtet lifecycle/privacy (hardware QA) - #67

Draft
man612 wants to merge 63 commits into
mainfrom
integration/ux-lifecycle-hardware-20261029
Draft

man612 wants to merge 63 commits into
mainfrom
integration/ux-lifecycle-hardware-20261029

Conversation

@man612

@man612 man612 commented Oct 29, 2026

Copy link
Copy Markdown
Owner

Purpose

Combine the ten real UI/UX fixes from Draft PR #50 with the native Gnirehtet lifecycle and serial-log privacy fixes from Draft PR #63, without changing dependency versions, source version, or the regular installed Wirebound app. Both parents are preserved by merge commit 29230c5773d53b55ac16b75b77d696e9140f06e9 (PR #63 head 383f806 and PR #50 head 69473c2).

Merge audit

Actual Git merge on isolated F:\Wirebound-Lab\qa-ux-lifecycle-integration-20261029 had exactly one text conflict: AGENTS.md. Resolved it by keeping both branch documentation sections. All UX renderer files, IPC/preload API, Gnirehtet engine source and privacy helper merged without text conflicts, but behavioral integration and package testing remain mandatory.

Evidence tiers

Previous PR #50 synthetic renderer UX tests and previous PR #63 two real Motorola HTTPS/VPN cycles belong to separate builds. They are not evidence that this combined build passes. Hosted Windows CI and temporary two-day qa-ux-lifecycle-win-unpacked artifact will test this exact integrated head; after successful CI, unpack into F: QA with F:-isolated userData, validate ten UX items and (if USB authorized) retest one Moto g45 5G Android 15 via app IPC and real HTTPS/TUN. Maintain privacy and process ownership checks.

Boundaries

DRAFT, NO MERGE/RELEASE/INSTALLATION YET. Preserve current main, ordinary installed Wirebound profile, unrelated default ADB clients and VPNs. Do not upgrade dependencies or accidentally merge startup investigation PR #51. Electron startup issue #44 remains separately open. Historical UX issue #48 and Gnirehtet issues #53/#58 stay open until completed QA and maintainer-approved integration delivery.

man612 and others added 30 commits October 20, 2026 21:01

man612 commented Oct 29, 2026

Copy link
Copy Markdown
Owner Author

2026-10-29 continuation: integrated UI QA completed for available no-device scenarios; guarded shutdown PASS

New dated evidence is committed in docs/qa/PR67_COMBINED_UX_LIFECYCLE_QA_2026-10-29.md, commit 5c2444c. This is documentation-only; no application source or dependencies changed.

Exact hosted unpacked package hash reverified. Guarded relaunch from F: produced v1.2.0, isolated QA profile, autoStart:false, engine=disconnected, 0 authorized devices and no Gnirehtet port 31416 listener.

Actual bundled Electron renderer GUI results: onboarding Dark -> Light -> Dark preview PASS with persisted setting untouched until completion and QA-only onboarding state restored; manual diagnostics collapse/open PASS; rerun expands, completes and auto-collapses PASS for normal scan; Copy Report clicked -> Copied PASS for UI feedback (clipboard bytes not separately compared); CLEAR disabled with empty log PASS; Settings Dark -> Light -> Dark PASS; real update-check completed successfully and recorded/persisted lastAttempt=lastSuccess=1793264645078 across Dashboard -> Settings navigation; no document overflow at 1000px. No engine Start was intentionally invoked, and status stayed disconnected with port 31416 closed. The transient first post-reload DevTools inspection error was a QA timing error; a readiness-waiting repeat passed.

QA cleanup: full ownership guard found exactly 5 Wirebound processes from F: QA package, 1 ADB process from F: QA userData, no external Wirebound/ADB processes, no listening/connected relay, 0 authorized Android devices and no established ADB clients. Targeted shutdown exited 0; final QA Wirebound=0, QA ADB=0, 31416 not listening. Ordinary installed Wirebound/profile untouched.

Still blocking merge/release: physical combined PR #67 Moto connection/VPN/HTTPS 200/TUN RX+TX/Stop/Retry; UX-05 device details, UX-06 responsive real device card and counters, UX-08 ready banner and UX-10 log-scrolling on live connect; negative scenarios for diagnostics/copy/update; source/timing of earlier unexpected Start. The Moto was not enumerated (authorized=0) on this pass. Keep this integration Draft and do not treat PR #63's separate hardware pass as equivalent. Issue #44 startup investigation remains separate.

man612 commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

2026-10-30 — combined PR #67 real Motorola API + GUI Start/Disconnect/Retry/Stop + HTTPS/TUN PASS

Canonical new checkpoint: docs/qa/PR67_MOTOROLA_GUI_END_TO_END_2026-10-30.md. Documentation commit f7e9c74; agent handoff e7b5927.

  • Exact prebuilt integrated Electron app, isolated F: QA profile, one authorized Moto g45 5G / Android 15, no preexisting Gnirehtet client, reverse, VPN, or relay. autoStart:false. Standard ADB 5037, no global ADB kill.
  • App API cycle PASS: Start → relay 31416 → Android VPN + reverse → HTTPS 200 → actual kernel TUN RX and TX increased → Stop → app disconnected, Android client/VPN/reverse absent, relay closed.
  • Actual GUI buttons PASS independently: Start Connection → connected; device-card Disconnect → VPN/reverse removed while relay stayed up; device-card Retry → connected again, a second HTTPS 200 and RX/TX increase; GUI Stop Connection → clean final state.
  • Real-device UI: live card displays battery/RX/TX/actions; widths 1000/800/600/480 CSS px keep both buttons on-screen without document overflow. Ready-banner Dismiss worked. Diagnostic Android version/API populated; no corrupted text. Raw Android serial absent from diagnostic UI when compared correctly to the true snapshot ID. Initial QA probe's apparent serial match was against an already-masked ID (false positive).
  • Live GUI Start showed 35 terminal entries without scrolling the dashboard away from top in that observation. Manual scrolled-up terminal preservation still requires dedicated acceptance.
  • Independent Windows final verification: Wirebound 0, ADB 0, Gnirehtet 0, no listening ports 5037/15379/31416/19667. QA-only cleanup script had an exception in final report generation after the targeted processes were stopped; independent check passed and null-path reporter was corrected. Normal install/user profile and main untouched.
  • Code checked against CI artifact commit: only documentation/agent files changed afterward. No app code or dependency upgrade.

Do not merge/release yet: maintainer explicitly plans to provide a separate personal hands-on UI/UX audit now. Keep PR #67 Draft, preserve source PR history. Existing unresolved scopes: manual terminal scroll/negative UI cases, Wi-Fi/cellular-off and USB unplug/replug, older unexplained QA Start origin, startup issue #44/PR #51. One physical phone only; two-phone hardware test waived.

man612 commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

2026-10-30 — maintainer's 7-point UI/UX audit: implemented and directly launched on Windows

Current PR head: e5dd04e (follow-up React lint correction), based on actual initial implementation e7cd787. The existing Draft PR #67 was updated in place, without creating an additional competing PR. Documentation: owner UI audit QA.

Implemented changes: purposeful hover/press/page/diagnostic motion with Windows reduced-motion support; compact multi-device-oriented Android rows with per-device actions, real ADB/tunnel/RX/TX counters and real Android battery level/charging status/optional codename/version; compact masked diagnostic device lines; terminal log toolbar (All/Errors, pause/resume auto-follow, unread, jump latest, copy/export and feedback, masked known device identifiers); grouped 8-entry navigation: Dashboard, Devices, Diagnostics, Activity Logs, Speed Test, Updates, Settings, About. Activity Logs is functional; other new destinations intentionally say “not enabled yet” as explicitly authorized by the maintainer.

Validation: Windows local main+renderer TypeScript passed; original 13 files / 77/77 Vitest passed after feature implementation, and the additional React effect-state lint issue was subsequently corrected. Targeted ESLint showed 0 errors (remaining Prettier warnings, many from pre-existing source; full initial lint had the one newly fixed error). Actual Electron Vite production main/preload/renderer build passed again after the fix. No dependency upgrades.

Real Windows executable: original hardware-tested PR #67 unpacked Electron QA runtime was copied into F:\Wirebound-Lab\qa-packages\ux-audit-20261030\wirebound.exe, and the QA-only ASAR was replaced with the newly compiled code (SHA256 021800c9f8999cc2f49bfbb9a2b7714154bbcbb5f0c88ed83bd5a69bc0787a90). The currently running QA app was relaunched under an entirely separate F: profile, with autoStart:false, telemetry disabled, CDP loopback 19669; no normal-user installation or profile touched. Read-only final renderer: v1.2.0, 1 authorized Moto, real Android version/codename/charging metadata, eight sidebar entries, masked ID, dark mode, engine disconnected, no document overflow at 1000px. First interactive package passed responsive checks at CSS 1000/800/600/480px and nav/logs/Settings behavior; the final refreshed build's follow-up viewport script was interrupted during active page navigation so repeated multi-width acceptance on that final binary is not claimed. Owner can inspect QA app immediately on their PC.

Still not release/merge-ready: owner plans more UI/UX revisions; the new rebuilt package has not re-run physical HTTPS/TUN Start/Stop/Retry (previous unchanged connection lifecycle passed on original PR #67 runtime); native 125% Windows scaling, low-battery scenarios and real scrolling/copy/export edge cases remain. Preserve Draft status, main, original installation, prior QA evidence, and the one-phone hardware limitation. Do not run npm ci or recursively delete the isolated worktree's node_modules junction.

man612 commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

30 October 2026 — owner UI/UX audit round 2 implemented and tested in an isolated Windows QA build

Source commit: c323fdc. Detailed QA checkpoint: PR67_OWNER_UI_AUDIT_ROUND2_2026-10-30.md. All changes were pushed to this existing Draft PR, without creating another PR or touching main.

Implemented all 14 requested review topics at a first shippable QA iteration: delayed tooltips for sidebar/icons (keyboard-focus accessible); fixed ADB $Ready → ADB Ready; stable-width crossfading Copy/Export labels and notifications; motion for diagnostics, page navigation, popups and notices with reduced-motion support; native TXT/LOG/MD/JSON/CSV export filters and actual corresponding file data; real six-check IPC diagnostics progress reaching 100% only on completion; animated diagnostic expansion, transient “Checks complete”, collapsed dashboard on return; per-device Connect in place of Retry and stopping idle relay when the last VPN disconnects, preserving another active VPN; Gauge speed-test icon/tooltip; empty-terminal controls disabled, scroll-follow indication, differentiated export/jump icons, animated Clear-confirmation dialog; enabled Android speed test without Wirebound tunnel with a mobile-data warning modal.

Verification: TypeScript node + web PASS, 83/83 Vitest PASS, targeted changed-code ESLint 0 errors, main/preload/renderer Electron Vite production build PASS. Actual newly packaged Windows QA ran with one authorized Moto, engine disconnected, autoStart:false, eight nav entries, ADB Ready with no dollar, device Connect, no overflow at 1000px. Keyboard focus showed tooltip “Connected Android devices”; actual GUI diagnostic rerun emitted stages 2/6 → 3/6 → 4/6 → 5/6 → 6/6, bar reached 100, panel auto-collapsed afterward. The authorized/disconnected phone's Speed Test button was enabled, and its actual warning modal was shown and safely canceled (no test traffic generated).

QA executable now launched on YASMAN: F:\Wirebound-Lab\qa-packages\ux-audit-round2-20261030\wirebound.exe, isolated profile F:\Wirebound-Lab\qa-profiles\ux-audit-round2-20261030, QA ASAR SHA256 7733b68a3aff96d8850b049a351a9990eba05877a0b256c6e58c9ed6e7965f39. Earlier active QA session was not overwritten; once ADB/VPN/reverse and process ownership were independently verified safe, only old QA processes were stopped. Ordinary installed Wirebound and its user data remain untouched.

Keep Draft / do not release yet. Remaining hands-on gates: physical USB HTTPS/TUN Start/Stop/Retry with modified lifecycle, native Save dialog manual format selection, long incoming-log pause/unread and Clear interactions, 125% Windows scaling/reduced-motion and owner's visual evaluation. Dependency upgrades deferred.

man612 commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

2026-10-30 — owner UI/UX audit round 3, screenshot-driven fixes

Commit d021ced, pushed to existing Draft #67. QA handoff: docs/qa/PR67_OWNER_UI_AUDIT_ROUND3_2026-10-30.md.

10 maintainer concerns addressed: eliminate hidden diagnostic feedback space; fix dismissed ready banner flex-gap and real grid collapse; treat stopped Gnirehtet check as informational (5/5 passed + 1 info), and refresh actual diagnostics when engine state changes (real connected → 6/6 passed verified on running QA); sidebar tooltip hover delay 1300ms, no tooltip on mouse click or focus restoration after modal; terminal auto-follow reacts only to deliberate upward scroll, not programmatic scroll events, with visible amber paused state in toolbar and a distinct ListEnd jump icon; explain desktop speed and global Start/Stop with tooltips; remove phantom horizontal scrollbar beneath sidebar via nav overflow-x hidden and no translated full-width hover rows.

Actual Chrome/Electron DOM measurements before the final structural fix: collapsed diagnostic details 0px, feedback 0px, but hidden progress 16px from direct child margin; dismissed notice 18px from direct child padding/borders, even though CSS set grid track 0fr. Both have now been nested inside clipping wrappers with zero-size direct children. Sidebar nav scrollWidth=clientWidth=199px, confirming scrollbar fix.

Tests: 84/84 PASS across 14 files, TypeScript main + renderer PASS, Electron Vite main/preload/renderer production build PASS, targeted runtime ESLint 0 errors. The completed compact QA-only Windows ASAR SHA256 f0dfec9b907c8a59de537a53ced2c43e34a1af7f0df534fd9e3cc6330dbdc164 is staged at F:\Wirebound-Lab\qa-packages\ux-audit-round3b-20261030\wirebound.exe.

CRITICAL: this final round3b package was NOT launched yet. Actual preflight of existing round3 QA later found status=connected, authorized Moto VPN active, native Gnirehtet reverse mapping active. It would be unsafe to stop/restart its Windows processes while the owner is testing internet. The previous round3 QA remained running untouched. Await a clean authorized disconnect before switching. Thus final round3b DOM height verification and full stream-log interaction QA are still pending. No normal installed Wirebound or main changed, no dependencies upgraded; keep PR Draft.

man612 commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

Final round-3 UX verification — zero-height compact panels confirmed on a running Windows build

Updates earlier round-3 checkpoint. QA evidence has been appended to the round-3 document, committed as 9d697eb. The application change remains d021ced; the new commit is documentation-only.

The user disconnected Gnirehtet, and an independent preflight verified disconnected, autoStart:false, exactly one authorized phone, Gnirehtet VPN inactive and its reverse mapping absent. We safely stopped only old F: QA-owned processes and launched the new, isolated F:\Wirebound-Lab\qa-packages\ux-audit-round3b-20261030\wirebound.exe (main process PID 2388 at launch) with new separate profile F:\Wirebound-Lab\qa-profiles\ux-audit-round3b-20261030 and CDP loopback 19676. No regular installation/profile, main, or other process was changed.

Live Electron DOM measurements, now PASS:

State Previous package New compact build
Hidden diagnostic details 0px 0px
Hidden diagnostic feedback 0px 0px
Hidden diagnostic progress 16px 0px
Dismissed ready notice 18px 0px
Collapsed diagnostics total height 71.5px 55.5px
Sidebar scrollWidth/clientWidth 199/199px 199/199px

The actual prior running round-3 code was also independently observed connected with 6/6 diagnostic checks passed, addressing the formerly stale blue “Gnirehtet client” status. In the stopped state, that check remains informational, correctly summarized as 5/5 passed · 1 info, never a fake green PASS.

Test/build gates: 84/84 Vitest passed, TypeScript main/renderer passed, Electron Vite production build passed, changed-runtime ESLint 0 errors. New round3b app.asar SHA256 f0dfec9b907c8a59de537a53ced2c43e34a1af7f0df534fd9e3cc6330dbdc164.

While automated tooltip timing testing was being prepared, the owner started another actual tethering session; the automation aborted before any pointer events to avoid interrupting their interaction. Delayed tooltip, modal-return behavior, long-log follow/pause and new round3b physical HTTPS/TUN still need owner review/appropriate QA. Keep PR #67 Draft.

man612 commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

30 October 2026 — maintainer UI/UX audit round 4 completed, code and Windows QA ready

Commit: cb3cb58. Detailed QA report. Updated the existing Draft PR #67, no extra PR, merge or release, no dependency upgrade.

Corrections implemented:

  • Scrolling up no longer toggles Follow to Pause. Explicit Pause/Resume is independent from temporary reader detachment, so incoming logs cannot steal the reader's position. Pause/Resume keeps one fixed button width and crossfades labels. The oversized bright permanent yellow badge is gone; a small transient 1.5-second message lives inside the terminal. Unread count only shows when needed. Jump-to-latest uses guarded smooth scroll.
  • All readiness states, including “Relay and Android VPN are active”, have a dismiss X, without leaving layout space.
  • Diagnostics displays 0% first, then serializes actual emitted IPC milestones monotonically to 100%, no jumping/reversing.
  • ADB-authorized per-device Connect is enabled when the engine is disconnected, without clicking global Start. It launches native gnirehtet relay -p PORT plus targeted gnirehtet start SERIAL -d DNS -p PORT. Global Start still uses all-devices autorun. Corrected CLI flags using upstream documentation; added concurrency/Stop cancellation tests. Global Stop now remains available while the relay is connecting, rather than locking the user out.
  • Maintainer item Auto start on login #2 was only “gaada wkwkkw”, with no technical change described.

Validation: 87/87 Vitest PASS, web+node TypeScript PASS, Electron Vite production main/preload/renderer build PASS, changed-code targeted ESLint zero errors. Actual new F:-isolated Windows QA package was launched:
F:\Wirebound-Lab\qa-packages\ux-audit-round4-20261030\wirebound.exe with userData under F:\Wirebound-Lab\qa-profiles\ux-audit-round4-20261030, no autoStart. ASAR SHA256 aca4aef611f1a3f22d853b24ab0ed72b9baf38c156671e1043484121d8fd94e7. Existing regular install and main untouched.

Live renderer checks: Disconnected state displayed enabled Motorola Connect, enabled phone speed-test, dismiss notice, eight navigation entries, and Start Connection. Clicking Run Again showed bar at 0% at 0/80/180 ms, then 33→50→67→100%, while native milestones actually arrived as 2/6→3/6→4/6→5/6→6/6. This was measured directly from the running packaged renderer.

Outstanding physical acceptance: A scripted per-device Connect+Stop functional test did not execute because its safety preflight observed the owner had already reconnected the Android VPN. It aborted before clicking anything and did not stop the owner's tethering. Manual Connect-path VPN/HTTPS/TUN, incoming-log smooth-scroll interaction, and active-banner dismissal are pending hands-on validation. Keep Draft.

man612 commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

QA checkpoint — 2026-11-10 (Windows YASMAN, non-destructive)

Verified actual latest PR #67 HEAD cb3cb58e18ef21713eac44dd2fa43d248d8aa96b using existing isolated F:\Wirebound-Lab\ux-audit-20261030 checkout; git status had only pre-existing untracked qa-profile/ (left untouched). No change to regular installed app/profile, global ADB, VPN or main.

  • npm run typecheck: PASS (node + web).
  • npm test -- --testTimeout=15000: 87/87 PASS, 14/14 files, Vitest 5.0.1.
  • npm run build: PASS (main, preload, renderer; process exit 0).
  • Original npm test on this run had 86/87 PASS, one formatUiTimestamp test hit its 5000ms wall-time timeout while machine was busy. Rerun with 15s timeout passed in 36ms for the formatters file. No application assertion failure was observed; do not claim flaky test conclusively solved.
  • GitHub PR integration: ten UX fixes + Gnirehtet lifecycle/privacy (hardware QA) #67 exact HEAD CI run 41036509079 concluded success.
  • Read-only Get-PnpDevice -PresentOnly query found no present devices named Motorola, Android or ADB. Therefore physical targeted per-device Connect/Stop, VPN, HTTPS/TUN, active-banner dismiss and log animations in live Android session remain unverified on this new QA visit. Previous round-4 notes aborted direct-connect before clicking, due to active owner VPN.

Disposition: Keep PR #67 Draft; do not merge, release or close its parent PRs/issues solely on synthetic QA. Once authorized Motorola is present and disconnected without affecting an owner session, run isolated packaged PR #67 physical QA (targeted Connect -> HTTPS/TUN RX/TX -> per-device Disconnect -> reconnect -> explicit Quit; observe notice X / terminal interactions). If passed, evaluate PR #67 for merge, then retire superseded PRs #50/#63/#55/#59 and close completed issues with a precise rationale. Startup #44 / PR #51 and release readiness #38 remain independent.

man612 commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

Repository hygiene sync checkpoint — 2026-11-10:

  • PR chore(repo): remove unused assets and stale operational clutter #68 was independently tested (48/48 local tests, TypeScript/build/lint 0 errors, GitHub Windows CI + package smoke green) and squash-merged to main at 847183c0be800bc8b8a3dd8d860f1de36a2d53f5.
  • Merged that main into this PR's integration branch in a separate clean F: checkout, producing 6f6977b31556036ba2e6f55405ab415ffb282fa7. Exactly one content conflict, AGENTS.md, was resolved manually. Replaced 97 dated/contradictory handoff lines with the cleaned, stable guidance plus concise references to integration: ten UX fixes + Gnirehtet lifecycle/privacy (hardware QA) #67's actual QA records.
  • Cleanup carried here: unused duplicate TerminalLog removed, Windows-unused macOS packaging assets and duplicate icon PNGs removed, stale docs/README repaired, QA profile paths ignored. No live Gnirehtet, ADB, renderer functional source, runtime/dependencies, normal user profile or installed application was changed in this sync.
  • Branch is again mergeable with main. GitHub Actions for the new exact head are running; do not claim the previous CI run validates the new SHA until this one finishes.
  • Keep this PR Draft. Real per-device targeted Connect and remaining user-interaction QA from round 4 stay independent of repository hygiene and must not be inferred from this merge.

man612 commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

Repository hygiene sync CI update (2026-11-10): the exact new integration HEAD 6f6977b31556036ba2e6f55405ab415ffb282fa7 passed Windows CI run 42749654175, including lint, typecheck, automated tests, main/preload/renderer build, packaging smoke, locale audit, and temporary QA artifact upload. The branch is mergeable and remains Draft. This validates source/build integration of PR #68, not the still-pending latest real-device Connect/Disconnect and manual UI behavior tests.

man612 commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

2026-11-10 — exact-head packaged Motorola QA (partial, owner-session guard)

Source/build identity: Draft PR #67 HEAD 6f6977b31556036ba2e6f55405ab415ffb282fa7, Windows CI run 42749654175 (all steps green). Downloaded that run's qa-ux-lifecycle-win-unpacked artifact into isolated F:\Wirebound-Lab\qa-packages\pr67-current-head-20261110. Packaged resources/app.asar SHA-256: c63a15f39ce6f68c193ed5eed81f020e699ce03e58cc735b4993fc03accbf4. Did not touch the installed app or normal profile.

Preflight: one Windows PnP moto g45 5G and ADB Interface; exactly one ADB-authorized Android device; Gnirehtet Android process absent, Gnirehtet reverse mapping absent, VPN transport absent. No Wirebound or Gnirehtet Windows process and port 31416 free. Existing shared ADB on 5037 remained untouched.

QA launch: created fresh F:\Wirebound-Lab\qa-profiles\pr67-exact-20261110 with redirected APPDATA/LOCALAPPDATA/TEMP and Chromium user-data directory, autoStart:false, telemetryEnabled:false, onboardingCompleted:true; launched only the unpacked QA exe. Renderer debugger bound to loopback only.

Important race/owner-safety observation: Before the test driver performed ANY direct Connect click, its precondition recheck found an already active Gnirehtet Android client, reverse mapping and VPN. Driver aborted at EXISTING_RELAY_OR_VPN_ABORT, without clicking, disconnecting, killing processes or cleaning ADB. A separate host process inspection found a relay -p 31416 native Gnirehtet child belonging to this QA executable, spawned ~28s after app launch. This is the manual/per-device relay mode, not global autorun. Source of the action initiating it (external owner UI action versus some other trigger) was not observed, so do not label it an accidental autorun defect or a controlled-button PASS.

Read-only live app evidence: window.api.getSettings().autoStart === false, telemetry false, engine connected, exactly one authorized and connected device; device card's Putuskan enabled, active banner has a dismiss X, terminal exists, no horizontal document overflow, measured RX/TX available.

Independent read-only Android HTTPS test during the active session: one Gnirehtet reverse mapping, Android VPN transport active, /system/bin/curl https://example.com returned HTTP 200 and both tun* RX and TX counters increased. This is real hardware network evidence on the exact-head package, NOT an isolated Wi-Fi/cellular-off internet test and NOT a verified origin of the initial Connect action.

Still pending: controlled human/UI-initiated disconnected per-device Connect → per-device Disconnect → reconnect → global Stop on this latest package; terminal follow/scroll animation and active-banner X interactions under live logs; unplug/replug and tray Quit gates. Leave the currently active session alone until the owner decides to stop it; do not run global cleanup or adb kill-server. Keep PR Draft. Startup issue #44 remains separate.

man612 commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

2026-11-10 final integration sync checkpoint: main now contains narrowly scoped Windows ASAR build/release integrity gate from merged PR #69 at 5081398afed282b5ceb8c3aeaaae70d0d0281c3e. Merged current main into Draft PR #67 at exact head 844403bb446919cf82eb29366c0b5a2c26dd2421, with zero textual conflicts. Verified compare against previously physically inspected 6f6977b: only .github/workflows/ci.yml, electron-builder.yml, package.json and two ASAR verifier scripts changed; no renderer/ADB/Gnirehtet runtime source changed. New exact-head Windows CI run 42752639800 SUCCESS, including Vitest, typecheck, build, deliberate ASAR corruption test, packaged ASAR content verification and temporary QA-artifact upload. PR remains mergeable and Draft. The separately packaged 6f6977b Motorola session provided actual HTTPS 200 and rising TUN RX/TX; it was deliberately not interrupted, and controlled per-device UI click→Stop→retry tests on this latest head remain unverified.

man612 commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

2026-11-10 — UX feedback implementation and QA for four new observations

Commit 3f354871e70cfa69b89d6db216e5f17e7d77b180 is now on Draft PR #67.

Implemented:

  1. Terminal's "Jump to latest" is disabled (existing muted style) while auto-follow is active and the log viewport is already at the bottom (or there are no logs). Physical scroll-up detaches the viewport and enables it; smooth jump returns to bottom and re-disables it. When auto-follow is intentionally paused, Jump stays available.
  2. Removed both unintended auto-diagnostic triggers: connection status changes in App.tsx and dashboard mount/remount. One startup diagnostic now runs from App per renderer launch after settings load for returning users (onboarding preflight still runs when its own step requests it). Dashboard details default collapsed on every navigation, including initial app startup; manual Run Again reveals live progress and can auto-collapse afterward.
  3. Compact diagnostics cards and device-detail paddings, tighter header action widths, icon-only disclosure with accessible aria-label/tooltip to eliminate the long Indonesian label overflow.
  4. Closing a green/yellow/red status notice now marks the whole notice as dismissed for the current App process session, not just its last status tone. Navigation and status changes do not revive it. Added a persisted showStatusNotices boolean with default true, normalization for old profiles and bilingual toggle in Settings; false suppresses the entire banner until re-enabled in Settings.

Local source verification (isolated checkout, no production profile changes): npm ci PASS; TypeScript PASS; 91/91 Vitest PASS across 15 files (four newly added checks); npm run build PASS; lint exit 0 / 0 errors (572 primarily inherited Prettier warnings on integration, not mass-formatted). git diff --check PASS.

Browser interaction QA used generated production renderer served only on loopback, a separate headless Chrome profile, and an injected synthetic Electron API (no real device actions):

  • PASS startup: 1 scan, diagnostic disclosure collapsed.
  • PASS Settings → Logs → Dashboard: no rescan, still collapsed.
  • PASS dismiss X + status tone change + menu navigation: banner stays hidden, scan count unchanged.
  • PASS persistent Settings toggle: saved showStatusNotices=false, banner hidden.
  • PASS latest-log jump initially disabled, enables on manual scroll-up, returns to disabled after smooth jump; while following paused, remains enabled.
  • PASS manual Run Again: second scan, six checks shown in compact panel, header fits 800px viewport; panel auto-collapses, no third automatic scan and no horizontal document overflow.
  • Browser harness result: BROWSER_UI_ACCEPTANCE=PASS. Synthetic data do not prove live Motorola button behavior.

Hosted CI for this exact commit: Windows run 42756187055 SUCCESS on all steps, including tests, packaging smoke and integrity checks.

Scope/safety: existing live QA Motorola VPN and normal installed Wirebound were not stopped/replaced. Keep #67 Draft pending exact updated packaged-app owner acceptance and the separate physical Disconnect/Retry/tray release gates. This is not a claim that the installed executable already includes the changes.

man612 commented Nov 10, 2026

Copy link
Copy Markdown
Owner Author

2026-11-10 — real packaged Windows QA for four follow-up UX fixes (commit 3f354871e70cfa69b89d6db216e5f17e7d77b180)

Exact artifact: downloaded qa-ux-lifecycle-win-unpacked from successful Windows CI run 42756187055 to F:\Wirebound-Lab\qa-packages\pr67-feedback-exact-3f35487-20261110. Packaged resources/app.asar SHA-256 83A090D759420CA10B8245D2F833E7DC70BDD44B390822A3E11616B50A302B08. Independent checksum-aware ASAR scan: 3,959 entries verified, 0 skipped, 0 failed. Verified application was actually running from that path, not the installed app.

Safe session transition: previous QA-only build 6f6977b still ran its relay in connecting state; read-only Android probe found no VPN and no Gnirehtet reverse mapping. Invoked its public stopGnirehtet() API; returned success and engine disconnected, with no Android VPN/reverse on recheck. Released only that old QA executable's 5 processes, after verifying relay process/port absent. Shared ADB server remained running and untouched; normal installed app/profile untouched. New exact-head build launched through a guarded standalone launcher in isolated F:\Wirebound-Lab\qa-profiles\pr67-feedback-3f35487-20261110, autoStart:false, telemetry off, notice preference on.

Live packaged renderer evidence (real Windows Electron process, not mock, viewport 1000×648):

  • Dashboard diagnostic disclosure initially collapsed with compact icon-only expand action; no horizontal overflow. Status notice can be closed and remains hidden while switching pages. A local private screenshot was captured for inspection but intentionally not uploaded (live relay terminal contains IP addresses).
  • Actual in-app Settings toggle for status notices saved false to the Electron settings service; returning to Dashboard kept banner hidden. Re-enabled true and verified the earlier X dismissal remained effective through Settings → Dashboard → Logs → Dashboard. Preferences restored after test.
  • Terminal Jump to latest initially disabled when attached to bottom; a physical DOM scroll-up enabled it, pressing Jump returned to the bottom with smooth scroll and re-disabled it (tested in the real packaged renderer).
  • App connection state and actual displayed traffic changed during owner session; did not programmatically click Connect/Disconnect. Do not attribute the connection transition to any specific action or mark targeted Connect/Stop acceptance as done.
  • Manual Run Again on actual app while engine disconnected: before report timestamp 10 Nov 2026 11:46:34; after 11:56:13. Immediately after click, disclosure expanded and progress was 0%; after real ADB checks, progress 100%, details auto-collapsed, with no horizontal overflow. Engine remained disconnected. LIVE_MANUAL_DIAGNOSTIC_RERUN=PASS.
  • Pre-existing synthetic browser interaction suite also passed; local TypeScript/build, 91/91 tests, and exact-head Windows CI + packaging all green.

Acceptance: all four requested UI changes now pass both synthetic browser and key live packaged Windows interactions. Preserve Draft PR #67 pending the distinct physical scripted per-device Connect → Disconnect → Retry, unplug/replug, tray explicit Quit, and release readiness gates. No new installer/release published and no installed application overwritten.

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