Shared Claude Code / Codex hook wire protocol: matcher engine, stdin/exit-code/stdout codec, multi-hook merge, and hook/* session events

Run binaries from node, with easy stdout/stderr manipulation + signal passthrough + exit code propagation.

`process.exitCode` behavior back-ported from io.js and Node.js 0.12+

Execute a callback when the process exits, passing the exit code (ESM/CJS)

Cross-platform CLI wrapper that runs any command and exits with zero

Node.js program finisher - run your last callback with `exit code` and `signal name` as arguments

Shared Claude Code / Codex hook wire protocol: matcher engine, stdin/exit-code/stdout codec, multi-hook merge, and hook/* session events

Shared Claude Code / Codex hook wire protocol: matcher engine, stdin/exit-code/stdout codec, multi-hook merge, and hook/* session events

The adoption doctor — declared ≠ loaded, enabled ≠ exercised, a baseline that grew, a runner whose exit code is the only verdict.

Whole-graph architecture scans a per-file linter cannot do — unique module names, route collisions, tier direction, dead files — as configurable packs behind one exit code.

Duplexes stdout and stderr to a file, like tee, but also forwards the exit code of the original process

Shared Claude Code / Codex hook wire protocol: matcher engine, stdin/exit-code/stdout codec, multi-hook merge, and hook/* session events

Terminate Node-RED by setting exit code.

The `agentchat` command-line interface: the command framework, output modes, and exit-code contract.

Shared Claude Code / Codex hook wire protocol: matcher engine, stdin/exit-code/stdout codec, multi-hook merge, and hook/* session events

Run a command and get a tri-state answer: did it RUN, did it FAIL, and was the failure the RIGHT one. An exit code cannot tell you the first.

CLI for illari job monitoring: wrap a command and report its start, exit code, duration, and output tail.

Grader provider scoring an attempt by the exit code of a pinned command in the frozen workspace

Sets the exit code appropriately, given some tap output.

The customer walk as a gate: eight computed-DOM probes over a list of URLs, one JSON report, and an exit code that tells a could-not-run from a clean page.