…lyco#258) (#19) Add a smoke-test step that runs BEFORE the freshly-built binary replaces the brew Cellar binary. Catches the class of regression where the build succeeds at the bundler layer but the produced binary crashes at module-load / plugin-resolution / config-read — the surface that silently shipped a U.length crash 2026-05-27 (PR #14-17 era) and went undetected for ~1h because already-running tabs kept their mmap'd old binary. Two layers, both cheap (~0.7s total on a healthy binary): 1. `--version` — catches module-load + top-level import crashes 2. `debug info` — catches plugin-resolution + config-load regressions (exercises the same module graph the TUI mount path does) If either layer fails — non-zero exit, OR exit 0 with TypeError / ReferenceError / SyntaxError / fatal-error / U.length / 'Cannot read prop' on stderr — the install aborts and the working brew binary stays put. The build output is preserved at $SRC_BIN for inspection. `--skip-smoke` flag provided for emergency overrides (rebuild loops on a known-broken state where the new binary is wanted despite a smoke fail). `timeout` wrapper detection: macOS doesn't ship coreutils by default, so `timeout`/`gtimeout` are detected at runtime; absent both, the smoke runs unwrapped (the commands themselves exit fast, so the wrapper is belt-and-suspenders, not load-bearing). Verified locally with three integration cases against the in-script smoke block: - Healthy gruntcode binary → proceeds to install - Crashing fake-bin → refused + exit 1, install aborted - Stealth crash (exit 0 + TypeError on stderr) → refused + exit 1 - `--skip-smoke` → smoke skipped, install proceeds Help text + doc-comment header updated; new `Smoke-test (pre-install verification)` section explains what the smoke does + how to disable. Closes anomalyco#258.

[feat] support color output when invoke tools #258

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions