jochen 52e275ad2f Bring node-tools' lock back in step with package.json, and fail the check when it falls behind (hq issue 624) ...

The lab installs node-tools with npm ci, which refuses a lock that no longer
describes package.json; the SDK's range and the toolchain's development
dependencies had moved in package.json alone, so every lab run stopped at
setup. The image's build runs npm install and never read the lock, so nothing
noticed.

2026-10-13 15:12:10 +02:00

..

alive

Say the node tools are there, every minute (hq to-be 45 Phase 1, S11)

2026-10-06 10:06:29 +02:00

announce

Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554)

2026-10-12 13:56:50 +02:00

bus

Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554)

2026-10-12 13:56:50 +02:00

console

Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554)

2026-10-12 13:56:50 +02:00

launch

Wait for a stopped bundle's exit instead of sleeping after it

2026-10-12 10:43:22 +02:00

meshtest

Serve a key's kept values so the issue tracker can carry them into its log (ADR 0307, issue 502)

2026-10-12 10:18:34 +02:00

npmlock

Bring node-tools' lock back in step with package.json, and fail the check when it falls behind (hq issue 624)

2026-10-13 15:12:10 +02:00

runtime

Wait for a stopped bundle's exit instead of sleeping after it

2026-10-12 10:43:22 +02:00

wire

node-tools in Go: the node's runtime, launch-only, wire-compatible with the TypeScript (hq ADR 0193)

2026-10-03 21:21:52 +02:00