Skip to content

Add worker run inspection and cooperative CLI controls - #143

Merged
highbyte merged 1 commit into
mainfrom
feature/worker-launch-control
Sep 16, 2026
Merged

highbyte merged 1 commit into
mainfrom
feature/worker-launch-control

Conversation

@highbyte

Copy link
Copy Markdown
Owner

Wrighty skills can now inspect and cooperatively stop an exact worker run through workers show, workers drain, and workers interrupt. CLI and web-hosted runs reuse the existing registry and worker-control protocol, including process-start identity verification and independent control of runs sharing a web-host PID. Stop responses distinguish an accepted request from completed shutdown.

Foreground workers emit structured startup and completion receipts with run identity, selection, limits, ownership, and status/log locations. Worker-spawned sessions carry a recursion marker that prevents launching another worker. The bundled skill and documentation explain pickup assessment, launch authorization, foreground/terminal lifetime, and ambiguous outcomes. This adds no service installation, detached worker manager, or automatic restart.

Validation:

  • 2,470 .NET tests, 96 JavaScript tests, eight packaging/smoke-script tests, and skill validation pass.
  • Executable smoke checks cover inspection, drain, interrupt, idle timeout, recursive-launch refusal, and targeted fake-agent process-tree interruption with item finalization; no paid vendor calls.
  • Local SonarAnalyzer rebuild has no findings on changed code. Hosted merge gates will validate the pushed commit.

@sonarqubecloud

Copy link
Copy Markdown

@highbyte
highbyte merged commit 996d355 into main Sep 16, 2026
6 checks passed
@highbyte
highbyte deleted the feature/worker-launch-control branch September 16, 2026 12:31
highbyte added a commit that referenced this pull request Sep 16, 2026
Use concrete `Dictionary<string, string>` properties in the two worker
test helpers that always store dictionaries. This resolves the two
informational CA1859 findings reported during PR #143 without changing
production behavior.

Only two property declarations differ from `main`. Validation: all 98
`LocalDispatchStateTests` pass; all hosted CI checks and the SonarCloud
quality gate pass, with zero open SonarCloud issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant