Skip to content

Automation: detached job TTL, ownership binding, and cancellation controls #34

@mark-e-deyoung

Description

@mark-e-deyoung

Summary

Add lifecycle controls for detached automation jobs (TTL, ownership/session binding, cancellation).

Problem

Detached jobs are bounded by process-store capacity, but they currently lack explicit TTL/cancel semantics and first-class status ownership controls.

Scope

  • Add optional TTL for detached jobs.
  • Bind jobs to active session/controller context.
  • Add cancel endpoint and terminal status reporting.
  • Expose detached job state in operations/status APIs.
  • Add policy checks to avoid cross-session orphan control.

Acceptance Criteria

  • Detached jobs can be enumerated and cancelled safely.
  • Expired jobs are terminated/reaped with clear status.
  • Session transitions cannot leave uncontrolled detached ownership.
  • Tests validate TTL expiry, cancel, and ownership enforcement.

Notes

Deferred from temporal-correctness Wave 1 implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions