Skip to content

Stop only registered development targets, including failed pre-activation candidates #202

Description

@adrianwebb

Objective

Fix development session cleanup visiting every manifest target instead of the registered selection. Reproduced with a session selecting api.service but not api.operations-runner: stop sends the latter to Deployment and correctly receives Development container is outside the registered session.

Contract

Read authoritative session target selection; stop only owned registered targets. Preserve other sessions, active work, overlays and unrelated selected CLI. Failed generation-zero candidates with no runtime must remain safely stoppable. No Docker permission bypass.

Acceptance

Regression tests for subset API selection, failed Agent candidate build, owned active target drain, unregistered target exclusion and independent CLI selection preservation. Issue -> PR -> Actions -> staging release.

Evidence / recovery

Platform #501 review acceptance found this in dev-4414ae1d-129. Candidate Docker build failed before any activation; generation0/no candidate evidence verified, then protected manager local.dev.session.stop retired registration successfully. Released Agent and other sessions preserved. No source or runtime data deleted.

Rollback

Retain existing ownership checks and manager stop semantics; do not loosen supervisor authorization. Actions evidence pending implementation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions