feat(aidd-telemetry): record orchestration pauses and resumptions #970

Objective / Problem

An interactive SDLC run can wait for a person's decision on its contract, plan or final outcome. Telemetry currently records no explicit pause or resumption, so its journal cannot distinguish that wait from continued orchestration.

This requirement was deferred from #910 when #967 shipped.

Proposed Solution

Record orchestration pauses and resumptions, linked to the same session, orchestration and decision gate. Distinguish a human decision wait from an ordinary end of turn.

The orchestrator owns when it pauses and resumes; telemetry owns recording the observations. Measurement remains opt-in and never controls whether the workflow continues.

Context / Technical Constraints

• Reuse the existing append-only journal and attribution contracts.
• Record timestamps and gate identity without copying the user's response or artifact contents.
• A rejection followed by revision and another pause remains attributable to the same orchestration.
• Preserve existing journal readers and cost attribution.
• Report redesign and changes to the SDLC's approval gates are outside this issue.

QA

• An interactive run records each actual pause and resumption at the contract, plan and outcome gates.
• Rejection, revision and another pause remain distinguishable without duplicate observations.
• An autonomous run does not emit human approval waits.
• Disabling telemetry leaves the orchestration unchanged and writes no observations.
• Existing journal records still parse and existing cost attribution tests remain green.
• Verify the behavior in Claude Code and Codex; document any host limitation.

References

• feat(aidd-orchestrator): add an interactive SDLC mode #910: interactive SDLC product decision.
• feat(aidd-orchestrator): add an interactive SDLC mode #967: delivered the gates and explicitly deferred pause/resumption telemetry.
• Observation ownership.