# Owned update cancellation and restart

The native update dialog stays present while an operation is running. Escape,
Ctrl+C and outside clicks do not dismiss it. Its top-right Cancel control sends
an explicit request; it shows cancellation pending until the owned work settles.
An error remains in the same dialog with a Close action. Ordinary menu dismissal
and native frame animation remain unchanged for other dialogs.

The initiating client creates a private cancellation capability. Durable update
state contains only its hash. Cancellation requests carry the exact operation
identity and require the capability; clients adopting an existing shared update
receive progress without cancellation authority. The worker observes a private,
operation-specific request file, aborts its own installer process group, waits for
process close, and attempts recovery of a daemon it quiesced. Status remains
`running` during `cancelling` and `recovering`, then becomes `cancelled`. No UI
client signals an arbitrary recorded PID. Interrupted package changes are
retained; cancellation never claims package rollback. A recovery failure remains
explicit in the terminal receipt.

Quick Update waits for durable terminal settlement rather than treating a polling
timeout as proof of termination. A cancelled transaction does not restart the
client. Safe task admission, checkpointing, failure resume and the acknowledged
verified launcher handoff stay in the shared restart flow. The replacement keeps
the current configuration, environment, arguments, working directory and session
identity; native interface and transcript persistence are separate checkpoints.

`/update full` is now an alias for the coordinated package, daemon and indicator
transaction. It no longer automatically updates Ollama, Python, Cloudflared or
subordinate packages, or deletes global package directories and daemon artifacts.
Explicit `/update deps`, `/update rebuild`, `/update python`, individual dependency
menu actions and `/update ollama` remain available. Owned npm/pip maintenance
commands use the same process-group cancellation mechanism. Interactive privilege
and system-runtime setup prompts temporarily borrow the terminal through the
existing explicit handoff; these prompts keep their own terminal controls.

Verification uses scratch state directories, injected installers/service receipts,
actual native renderer input and harmless Node process groups. It does not install
an Omnius release, change services, load models or exercise CUDA. POSIX process
group escalation is tested locally; Windows uses its owned PID's task tree via
`taskkill`, with a direct-child fallback if that command is unavailable.
