3.4 KiB
3.4 KiB
| id | slug | title | status | kind | priority | labels | created_at | updated_at | assignee | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 20260531-054728-remove-insomnia-pod-binary | remove-insomnia-pod-binary | CLI: remove insomnia-pod installed/runtime alias | closed | task | P2 |
|
2026-05-31T05:47:28Z | 2026-05-31T06:10:39Z | null |
Background
Parent/umbrella ticket: single-binary-insomnia-cli.
Previous phases have already:
- added
insomnia pod ...as the Pod runtime entrypoint; - moved internal spawn/restore defaults to typed
current_exe() + ["pod"]command resolution; - left
insomnia-podas a temporary old binary/package output.
The user decision is that insomnia-pod does not need to remain as a compatibility alias. It was never designed as a human-facing command. The next phase is to remove/demote it so the installed package exposes one primary runtime executable: insomnia.
Requirements
- Remove the long-term
insomnia-podinstalled/runtime alias. - Prefer removing the
insomnia-podbinary target from thepodcrate if no active tests/build paths require it.- The
podcrate should remain as a library crate providing the Pod runtime entrypoint used byinsomnia pod .... - If a temporary binary target must remain for a narrow reason, document exactly why and do not install/expose it.
- The
- Update Nix packaging:
- build/install only the user-facing
insomniabinary as the package command; - remove
apps.insomnia-podfromflake.nix; - update install checks to use
insomnia pod --helpinstead ofinsomnia-pod --help.
- build/install only the user-facing
- Update devshell behavior:
- remove the
insomnia-podwrapper if internal callers no longer need it; - preserve the “do not pollute
INSOMNIA-READYstderr handshake with cargo output” property for dev workflows if a wrapper remains necessary; - document any remaining dev override path (
INSOMNIA_POD_COMMAND) if still relevant.
- remove the
- Update docs that describe installed commands / Nix usage / profile manifest CLI examples:
- replace user-facing
insomnia-pod ...examples withinsomnia pod ...where current behavior is intended; - avoid rewriting historical work-item artifacts;
- leave clearly historical docs alone unless they are current user docs.
- replace user-facing
- Preserve runtime behavior:
insomnia pod --helpworks;- Pod spawning/restoration still uses
insomnia pod ...by default; INSOMNIA_POD_COMMANDoverride behavior remains executable-only if still supported, or is intentionally removed with tests/docs updated.
- Do not rename the
tuipackage/crate in this ticket. - Do not merge Pod controller into the TUI process.
Non-goals
- Crate/package rename from
tuitoinsomnia. - Removing the
podlibrary crate. - Changing Pod runtime flags/profile/manifest semantics.
- Changing Pod protocol.
- Large CLI UX redesign.
Acceptance criteria
- Installed/Nix package exposes
bin/insomniaas the primary command and no longer exposesbin/insomnia-pod. nix build .#insomniaand install checks pass usinginsomnia pod --help.flake.nixno longer advertisesapps.insomnia-pod.insomnia pod --helpand relevant Pod runtime parser tests pass.- Internal spawn/restore tests still pass after removing the old binary output.
- Current docs no longer instruct users to run
insomnia-podas the normal runtime command; useinsomnia podinstead. cargo fmt --check, focused pod/tui/client/nix tests or checks,cargo check -p tui -p pod -p client,./tickets.sh doctor, andgit diff --checkpass.