[Umbrella] Task lifecycle gap remediation — LIFE-GAP-001..038

[edelauna]

Purpose

Track baseline remediation for LIFE-GAP-001..038 from PR #1626.

Source documents:

• Task lifecycle gap report
• Task lifecycle remediation blocks

LIFE-GAP-* IDs own the burn-down. GitHub issue numbers are tracking links only.

Delivery order

The critical path is P1 -> P7 -> P2 -> P5 -> P6.

P3, P4, and P8 can run in parallel when their dependencies allow.

Concurrent fan-out is outside baseline closure. Track it as a separate optional program.

Child issues

• #1689 — P1: Persisted ownership and generation
• #1690 — P2: Durable operation and crash recovery
• #1691 — P3: Schema, path, and vocabulary
• #1692 — P4: Request, stream, and tool identity
• #1693 — P5: Tool-owned task state and queueing
• #1694 — P6: Event and ingress contracts
• #1695 — P7: Serial scheduler baseline
• #1696 — P8: Verification and traceability platform
• #1697 — Optional concurrent fan-out program

Closure

Close this umbrella when all LIFE-GAP-001..038 closure criteria pass. Fan-out does not block baseline closure.

[edelauna]

Hardened lifecycle audit update

The covered baseline range is now LIFE-GAP-001..041.

Inventory completeness does not imply composed protocol verification. The inventory maps each boundary to local evidence. Only joint checking or trace validation can support an end-to-end protocol claim.

#1714 is concrete evidence of this distinction. The involved symbols had inventory coverage, but the composed restart and replay loop remained possible.

New GAP ownership:

• LIFE-GAP-039 / LIFE-BLK-P2-039 → #1690: make rejected-action settlement crash-safe and bound persisted replay.
• LIFE-GAP-040 / LIFE-BLK-P2-040 → #1690: define pending-action rules for startup repair and reconciliation.
• LIFE-GAP-041 / LIFE-BLK-P3-041 → #1691: make cascade deletion traversal cycle-safe and duplicate-safe.

The audit also strengthens existing obligations:

• 006: cover completion messages, both pair files, child pending-action state, and replay in one failure-phase table.
• 012: include staged replay attempts, bounded retry identity, stale settlement, and valid later generations.
• 020: define pending-action behavior during convergence and after rejected-action settlement.
• 031: define restart composition between queue loss and pending-action replay.
• 036: correlate staged actions with task, action, and call identity. Give denial, cancellation, and error durable settlement rules.
• 038: prove one-to-one identity through staged action, approval, execution, result, settlement, and restart replay.

Source of truth: gap report and remediation blocks.