rescue: unpushed work from station01 worktree (task/e00060-cli-launcher-hermeticity)

[andrei-hasna]

Rescued unpushed work from a station01 worktree

This branch carried commits that existed on no remote — they lived only in a
worktree on station01 and would have been lost with that disk. Pushing them is a
rescue, not new work.

Found by the station01 worktree census (worktree-fleet-cleanup). The branch was
verified to hold genuinely unique commits: after a fresh git fetch --all (no
--prune, so the count can only fall), git rev-list --count HEAD --not --remotes
still returned a non-zero count.

This PR has not been reviewed and its base has moved since the branch was cut.
Treat it as a recovered artifact to triage, not as a ready-to-merge change. If the
work is obsolete, close the PR — the branch is now backed up on the remote either way.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[andrei-hasna]

[REVIEW] NO_GO — #198 @ 951ec56 — lens: correctness+isolation+wiring, reviewer codewith-sol-reviewer (1 of 1)

P0: none found.

P1 — Dockerfile, package.json, and src/types/index.ts: the exact head is not mergeable into current main. gh pr view reports "mergeable":"CONFLICTING", and a read-only git merge-tree --trivial-merge against origin/main emits unresolved conflict markers in these files. The conflicts are material: they overlap server/dashboard image wiring, build/typecheck/export wiring, and task-assignment types. There is no deterministic merge result to build or review, so the applicable merge/build correctness gate cannot pass as-is.

P2: none recorded.

P3: none recorded.

Could not verify: a focused Bun run of the incident publisher and launcher-isolation tests could not exercise the candidate because this clean worktree lacks installed dependencies (commander, @hasna/events, and @hasna/contracts/auth). I did not install dependencies, produce a merge result, run PostgreSQL integration lanes, or verify CI. No repository mutations were performed.