[lifecycle-P4] Request, stream, and tool identity

[edelauna]

Tracking

• Umbrella: #1688
• Source PR: #1626
• Task lifecycle gap report
• Task lifecycle remediation blocks

Scope

Own these gaps:

• LIFE-GAP-008
• LIFE-GAP-010
• LIFE-GAP-024
• LIFE-GAP-025
• LIFE-GAP-026
• LIFE-GAP-030
• LIFE-GAP-037
• LIFE-GAP-038

Own these blocks:

• LIFE-BLK-P4-008
• LIFE-BLK-P4-010
• LIFE-BLK-P4-024
• LIFE-BLK-P4-025
• LIFE-BLK-P4-026
• LIFE-BLK-P4-030
• LIFE-BLK-P4-037
• LIFE-BLK-P4-038

Ownership boundary

Own request generation and canonical call identity. Own parser, stream, task, and partial-handler state by task, generation, and call.

Dependencies

P4 can run beside P1 after both workstreams align task and request generations. P4-010, P4-037, and P5-036 depend on P4-038 identity.

Optional fan-out routing depends on this identity boundary.

Closure

Close this workstream only when all listed GAP closure criteria pass.

[edelauna]

Hardened audit mapping

Strengthen LIFE-GAP-038 / LIFE-BLK-P4-038. Canonical identity must be one-to-one across the parsed call, staged pending action, approval, execution, result, settlement, and restart replay.

The mapping must reject or disambiguate collisions before persistence. A settlement for one raw call must never clear another call's staged action.

Source: gap report and P4 remediation blocks.