Skip to content

Instantly share code, notes, and snippets.

@3esmit

3esmit/logos-inspector-f252-issue-evidence.md

Created July 22, 2026 19:46
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save 3esmit/b3bcc137ed6b07268396bb3b229314d3 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save 3esmit/b3bcc137ed6b07268396bb3b229314d3 to your computer and use it in GitHub Desktop.
Download ZIP
Standalone close regression evidence
Raw
logos-inspector-f252-issue-evidence.md

Standalone close regression evidence

Before the fix

The compiled standalone application completed its primary route census. After a normal window-manager WM_DELETE_WINDOW request, every visible window was gone but the process stayed alive. The harness reported GUI did not exit after WM_DELETE_WINDOW.

The process was blocked waiting for active bridge work while a LogosCore CLI-backed report was still in flight.

After the fix

Release package commit e5d5335 passed:

  • a direct normal-close replay;
  • a 16-route, 17-interaction primary-screen census; and
  • the same 16-route census seeded from a real Inspector Testnet configuration.

Each replay exited after normal WM_DELETE_WINDOW, had no fatal QML diagnostics, preserved protected source state, and ran from a clean tracked worktree. During the live-seeded census, a LogosCore CLI module-discovery process was observed and no temporary CLI process remained after close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment