Define session continuation and workflow variants

[dapi]

Parent: #104 — Add durable orchestration and Task Capsule model for Memory Bank

Goal

Make continuation between short model sessions explicit and ensure different task types use the smallest applicable workflow.

Scope

• Define the continuation contract based on Task Capsule, canonical owners, priming inputs, checks, and next action.
• Specify what a new session must read before acting.
• Map minimal paths for Small Change, Bug Fix, Research, Feature, Epic, and Refactoring.
• Define rerouting conditions when scope, risk, or contract changes.
• Add examples for pause, resume, failed handoff, and human stop conditions.

Out of scope

• Runtime scheduling.
• Temporal integration.
• Full implementation of every workflow variant.

Acceptance criteria

• A new session can resume from persisted state without the full transcript.
• Each supported task type has a documented minimal route.
• Rerouting and stop conditions are explicit.
• Continuation does not bypass governance or validation gates.
• Examples are linked from the relevant process documentation.

Dependencies

• Depends on Task Capsule contract.
• Uses role/handoff protocol and validator contracts when available.

References

• Article
• Task Routing
• Session Handoff template
• Lifecycle Protocol template