The v0.3.36 tag validated the package content on most release smoke lanes but got stuck on one macOS/npm cold install before the publish job could start. Pre-publish verification should prove the tarball is structurally installable without making publication depend on the slowest npm/macOS dependency-resolution path.\n\nThis keeps npm tarball smoke on Ubuntu before publish and keeps macOS coverage in the Bun matrix plus the existing post-publish consumer jobs. The package version is bumped to v0.3.37 so the corrected release workflow is captured by the tag.\n\nConstraint: xpod releases are tag-driven; LinX must consume a registry-published package, not a local tarball.\nRejected: Manual npm publish from the workstation | bypasses the documented tag-driven release path.\nRejected: Waiting for the stuck macOS/npm job indefinitely | publication is blocked by dependency resolution time, not by the handler fix.\nConfidence: medium\nScope-risk: moderate\nDirective: Keep pre-publish release checks bounded; platform-specific slow consumer installs should not block npm publication when post-publish verification remains available.\nTested: bun run check:platform-package-version\nTested: bun run test:run tests/identity/ScopedPickWebIdHandler.test.ts tests/identity/PodLookupRepository.test.ts tests/api/handlers/PodManagementHandler.test.ts\nTested: bun run build:ts\nTested: local package-smoke-install + package-consumer-smoke for 0.3.36 tarball before workflow adjustment