Add a task close plan macro over existing lifecycle primitives #11

New issue

Open

opened 2026-07-29 01:47:32 +00:00 by perishadmin · 0 comments

perishadmin commented

2026-07-29 01:47:32 +00:00

Contributor

Context

A completed multi-repository task currently requires a correct sequence of audit, preflight, landed-member removal, exact retained-target removal, and finish calls. The protocol primitives are right; the repeated orchestration is mechanical.

Boundary

This must be a plan macro, not a new lifecycle primitive or hidden repair path.

Acceptance

Produce one deterministic close plan by composing existing primitives.
Default to a non-destructive plan when any removal is involved.
Require explicit execution and exact-target consent for retained memory or resources.
Stop on protocol disagreement or unlanded unique state.
Preserve the same checks and action evidence as invoking each primitive directly.
Support repo-less retained-memory tasks and multi-member tasks.

Context A completed multi-repository task currently requires a correct sequence of audit, preflight, landed-member removal, exact retained-target removal, and finish calls. The protocol primitives are right; the repeated orchestration is mechanical. Boundary This must be a plan macro, not a new lifecycle primitive or hidden repair path. Acceptance - Produce one deterministic close plan by composing existing primitives. - Default to a non-destructive plan when any removal is involved. - Require explicit execution and exact-target consent for retained memory or resources. - Stop on protocol disagreement or unlanded unique state. - Preserve the same checks and action evidence as invoking each primitive directly. - Support repo-less retained-memory tasks and multi-member tasks.