Installed VB5 CCE: native file-open qualification boundary

Evidence: scratch/runs/20261117-vb5-installed-original-ide-sample/result.json.

No installed application or installer was invoked in this task. The preceding installer's final OK remains permanently UNKNOWN; its endpoint was never queried, rebound or replayed. Installation complete, its actual native wait 0, 258 persisted overlay records and 836 registry entries remain distinct facts.

The authentic recovery audit verifies the original manifest against its retained artifact hash, all 86 file blobs against both that manifest and the original artifact hashes, and exact index correspondence (86 files, 17 directories, 155 whiteouts). The seven bundled sample projects and installed IDE bytes match. The registry JSON's original recorded hash also matches. The original launch has no registry import; its native log records genuine setup-child state merge to 836 entries and the parent's 836-entry export on native exit. This is the actual persisted registry, including normal runtime defaults, rather than invented IDE settings or registration. Nothing was changed or reconstructed. The run-local recovery recipe preserves the original index, metadata, whiteouts, blob bytes and registry JSON for a future task-local hydration.

Before spending the single installed invocation, an authored ordinary x86 PE creates a main window, runs GetMessage/TranslateMessage/DispatchMessage, and opens GetOpenFileNameA from its WNDPROC on O. The real reviewed controller captures the main, binds once and sends one finite keyboard intent. DOWN is consumed and independent physical UP completes; the native common dialog opens. The next native-reviewed capture refuses with focus.modalTopLevel and control.unsupportedClass. The public native scene has main 0x10001, common dialog 0x10002 (class 12, owned by main), and focus still on main. Its listbox, filter combo and hidden combo popup also lack the currently qualified control state contract. A window-title whitelist or merely allowing class numbers would not establish their current selections, item lists and lifetime identity.

The same PE executes in an actual CPU Worker. Its actual native message queue, GetMessage, DispatchMessage and x86 WNDPROC produce the class-12 owned common dialog while the native focus remains on main. This is a main/Worker native qualification boundary, not evidence that the installed VB5 IDE has failed. Worker setup and exported observation calls are limited to authored fixtures.

The diagnostic asserts this refusal and safeForInstalledOriginal:false. UNKNOWN then forbids all further HTTP, including a later capture; the request ledger remains unchanged. No binding retry, keyboard batch, guest shortcut, file-open automation or second invocation follows. The immutable 500/1750/3000 ms controller limits and native-reviewed-context-v1 checks are unchanged. The prior normal-exit proof is reused only where exact source and module hashes match; native exit 7 or a signal with OS wait 0 still cannot become native exit 0 plus actual normal wait 0.

The first concrete boundary therefore precedes any installed invocation. Next work is generic native common-dialog focus and complete public listbox / combo / common-dialog identity qualification with faithful main and CPU Worker fixtures, before an installed IDE/sample attempt. No semantic runtime repair or successful IDE/sample/native Quit is claimed by this diagnostic change. Native teardown here is signal cancellation, with its actual OS wait recorded; it is not native Quit. Native control-session pipes, controller pipes and independent watchdog pipes have separate actual joins and EOF observations. No box was created; ID and expiry are null, state NOT_CREATED, stop inapplicable.