WebCodex v0.3.6
WebCodex 0.3.6 adds bounded semantic code inspection and structured Go test evidence, expands the native release matrix to Windows ARM64, and rolls up the reliability and release-pipeline work completed since 0.3.5.
Highlights
- Bounded semantic code inspection. Adds typed call hierarchy /
code_impacton the existing multi-language LSP bridge, with project-relative output, external/private location filtering, explicit capability negotiation, bounded depth/fanout/call-site/result budgets, and one shared operation deadline. - Structured Go validation evidence. Go test recipes use
go test -json ./...and derive bounded pass/fail/skip counts plus failed-test identities from machine-readable output. - Native Windows ARM64 distribution. The main npm package now selects a native
win32-arm64artifact directly; x64 emulation is no longer the release path for ARM64 hosts. - Five-target native release builds. Published artifacts cover Linux x64/ARM64, macOS ARM64, and Windows x64/ARM64. Both Linux artifacts are built in manylinux2014 userspace and enforce the glibc 2.17 / dynamic-dependency gates.
- CLI HTTP proxy controls. Adds an explicit credential-free HTTP proxy override and
--no-system-proxywhile preserving Runner proxy semantics. - Runtime reliability. Fixes UTF-8 output-tail truncation panics, hardens persistent-shell/LSP/process lifecycle concurrency, and bounds queued Job start inputs.
Compatibility
There is no intentional breaking protocol change. New semantic-navigation and validation capabilities are negotiated explicitly and fail closed on older Runners.
Published native platforms:
linux-x64linux-arm64darwin-arm64win32-x64win32-arm64
Known distribution limits: macOS x64 is not a published native artifact, and the npm installer wrapper requires Node.js 18 or newer.
Upgrade
Install or upgrade the main package normally:
npm install -g @yyjeqhc/webcodex@0.3.6Upgrade Server/CLI/Runner together when possible so capability negotiation and runtime metadata stay aligned.
Release validation
The immutable v0.3.6 tag was built by the reviewed five-target release workflow from one source commit and one shared build timestamp. Native architecture/provenance checks, Windows npm-install smokes, Linux glibc/dynamic-dependency gates, release metadata validation, npm package tests, and an exact-binary npm install smoke all passed before publication.