machine-bridge-mcp v1.0.1

Startup and release-gate reliability

• Fix two production CLI references that were used without imports: readdirSync in the default Worker deployment fingerprint path and inspectProcessInstance in secret rotation. The former made a freshly installed 1.0.0 package fail immediately on zero-argument startup even though syntax, package, and cross-platform CI checks were green.
• Fix the Windows Wrangler execution boundary uncovered by the new startup probe. Runtime code no longer passes wrangler.cmd to spawn(..., { shell: false }), which fails with EINVAL on Node 26; it invokes the dependency's declared JavaScript entrypoint through the current Node executable on every platform. A focused regression and the installed startup probe prevent a return to shell shims.
• Add an ESLint correctness gate over Node production code, tests, scripts, and the packaged browser extension. Undefined identifiers, redeclarations, duplicate keys, unreachable statements, and non-loop constant conditions now fail npm run check before packaging or publication. A configuration self-test injects synthetic undefined Node/browser bindings so retaining a no-op or mis-scoped lint script cannot satisfy the gate.
• Strengthen install:test to install the real npm pack tarball into an isolated global prefix and execute the installed CLI with zero arguments from a package-free workspace and isolated state root. A cross-platform fake Wrangler shim provides a controlled external boundary; the test requires state initialization, rejects ReferenceError/is not defined, and proves that default startup reaches Worker orchestration rather than only supporting --version.
• Make both static lint and the installed zero-argument startup probe mandatory parts of the complete local, prepublish, Linux, macOS, and Windows release gate. Architecture checks prevent either gate from being removed silently and now enforce the existing exact-semver dependency policy instead of leaving it as documentation only.