@gorban/dsh-job-stop

LIMITATIONS

Known limitations

- **Only `running` rows offer the stop affordance.** A `stopping` job is already ending; offering to stop it again would be a second request for the same outcome. - **The dialog restates what the registry published.** For `bash` that is the complete command (`args.command`, untruncated), which is why the dialog is worth opening. A producer that publishes a truncated label gives the dialog only that. - **A Session with no live Agent cannot have its jobs stopped** (`409`). The kill is fenced by that exact owner instance, and guessing one would be an authorization hole. - **Stopping a job does not remove its `run_in_background` card** from the transcript; the card was never live-updating, and the list is where the outcome is legible. - **The shadow depends on one cell id.** If upstream renames the `job-list` slot entry, this plugin's entry stops replacing it and both lists would render. The fix is a one-line id change here. - **The recorded kill reason is a fixed English string** (`stopped by the user from the background-job list`), kept stable so it greps in logs and in a job's terminal `detail`; it is not user-facing copy.