fix(cli): make `omo update` actually report its refusal honestly (Fixes #7172)

CO
3mo ago
+264-17

Supersedes #7180.
Fixes #7172.

fix(cli): make omo update actually report its refusal honestly (Fixes #7172)

QA-proven: RED->GREEN, package tests pass.

Landed by mass-ulw fix dag (dag_d890c4cc) on 2026-08-25.


Summary by cubic

Refuses self-update requests in the omo launcher with an honest message and non-zero exit. Previously omo update printed a success line and exited 0 without updating; now it prints a refusal with the correct update command and exits 1 to prevent automation from misreading success.

  • Changes in packages/omo-native/bin/lib/launcher.js: the self-update branch now prints "omo does not self-update (the senpi engine is version-pinned)." then "Run: " and sets process.exitCode = 1.
  • Tests in packages/omo-native/test/launcher.test.ts add regression coverage for all self-update spellings and install layouts; assert exit 1, exact stdout, and that no engine process spawns.
  • Migration: if any wrapper or CI step relied on omo update exiting 0, update it to treat exit 1 as "no update performed" and invoke the printed command.
  • Out of scope: local-install paths in packages/omo-senpi/src/install/local-launcher.ts and plugin/scripts/install.mjs still emit the old message and exit 0; follow-up will address them.