**0.1.3 is live** — https://pypi.org/project/nemostation/. Your local is already on it.

The build wait now shows a step counter + a running clock instead of a static spinner:
```
⠹ building the local engine (one time) — [3/4] compiling the Metal kernel (slowest) · 2m18s
```
The `[k/N]` tells you which of the 4 phases you're in (clone → venv → compile → download; it drops to fewer on re-runs), and the clock keeps ticking so it never looks frozen. I deliberately didn't fake a %-bar — the two slow phases report no real progress, so a bar would just sit pinned at ~100% during the long download, which is worse than honest.

To actually *see* it you need a real build (it only renders while building — a re-run with the engine already present just says "✓ engine ready"). So next fresh start:
```bash
marlin stop && rm -rf ~/.marlin
uv tool install --refresh nemostation     # --refresh dodges the index lag → 0.1.3
marlin                                     # hero → detect → [k/4] build with the clock
```

Agents get the same info as clean `[k/4]` stderr lines (stdout stays JSON).