+1 (binding) I checked: - Signature and SHA-512 checksum are valid; the signing key CCF8C3FDF7351B68084BFA1D975D5AA38DC0BCFA is in KEYS - Tag v0.2.2-incubating-rc2 points to eeeae5128cdc7e498e2c8cae0881f138df3d8301, and the source tarball is byte-identical to git archive of that commit (only export-ignore omissions versus the raw tree) - Staged under dist/dev/incubator with "incubating" in the artifact names; DISCLAIMER-WIP, LICENSE and NOTICE are present and look correct - No compiled binaries or unexpected generated files in the source tarball; the project's license header check passes - npm ci, build, typecheck, lint, format check, notice checks and check:asf-source (97 tests) pass on Linux x86_64 with Node 22
Non-blocking notes: - DISCLAIMER-WIP says the authorization basis for the retained initial code still needs to be recorded. Please get that recorded before the next release. - One CLI remote TUI/MCP owner-association test still times out in an isolated rerun. The other local test failures were traced to host limits (missing Electron system libraries, bubblewrap, inotify) or host-specific config. - The full npm audit reports 7 high (including Electron 43.5.0), 1 moderate and 2 low findings. The production and shipped-dependency audits are clean at moderate and above. Xuanwo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
