[Bug] False-positive startup warning "Windows bundled runtime missing providers: glm" on node-bundle distribution (Windows, 3.11.2)

Pre-submission checklist · 提交前确认

• I searched existing issues and discussions; this is not a duplicate.
• I read CONTRIBUTING.md.

Category: Other
Agent framework: ZCode Agent (in-house)
Severity: Minor
Reproducibility: Always

Description

ZCode 3.11.2, Windows, node-bundle distribution. On every startup the app logs:

[startup] Windows bundled runtime missing providers: glm

but the agent runs fine: it is launched via resources\glm\zcode.cjs and missingBinaryMessage is never triggered (that message does not appear in any log).

Steps to reproduce

1. Install ZCode 3.11.2 desktop on Windows (node-bundle layout: resources\glm\ contains zcode.cjs and .node-bundle-meta.json with {"runtime":"electron-node","entry":"zcode.cjs"}; there is no zcode-agent.exe, which is expected in this layout).
2. Start the desktop app.
3. Check the startup logs.

Expected behavior

No warning, or the integrity check resolves the node-bundle entry file (zcode.cjs) when the declared runtime is electron-node.

Actual behavior

Every startup logs [startup] Windows bundled runtime missing providers: glm even though nothing is missing. Reproduces on every startup since ~Aug 26.

Probable cause (from code inspection): logWindowsBundledRuntimeIntegrityDiagnostic performs the integrity check via resolveBundledGlmBinaryPath, which builds candidate paths from resolveEntrySegments (native-binary layout: zcode-agent.exe) instead of resolveNodeBundleSegments (zcode.cjs) on node-bundle installs.

Version: 3.11.2

Environment: Windows 11 x64 (build 10.0.26200), desktop app

Logs / evidence

[startup] Windows bundled runtime missing providers: glm
[zcode-agent] ZCode agent process started    ← agent actually starts, via resources\glm\zcode.cjs

The real failure message (missingBinaryMessage: "glm binary 未找到") never appears in any log.

Start with logWindowsBundledRuntimeIntegrityDiagnostic and trace its call to resolveBundledGlmBinaryPath, then compare the candidate paths from resolveEntrySegments with resolveNodeBundleSegments. Reproduce the Windows node-bundle startup and verify that resources\glm\zcode.cjs is recognized without the false warning while the agent still starts.