Context
The workflow YAML must reflect exactly the contract’s canonical onboarding_basic states and transitions. Any mismatch breaks deterministic onboarding and tests.
Affected paths
- docs/ai/workflows/onboarding_basic.yaml
Steps
- Open side-by-side:
- docs/ai/api/CONTRACT_onboarding_action.md
- docs/ai/workflows/onboarding_basic.yaml
- Ensure the YAML contains exactly the canonical onboarding_basic states:
start, ask_name, ask_goal, summary, end
- Ensure transitions reflect the contract triggers:
start auto → ask_name
- user input routes correctly to next state
- Ensure
id: "onboarding_basic" matches filename and references in tests.
- Add minimal inline comments linking each YAML state to the contract’s state table section.
- Validate YAML syntax (no parse errors).
Definition of Done
- YAML states and transitions match contract’s canonical onboarding_basic definition
- YAML parses without errors
- Workflow id and filename are consistent
- Comments exist to trace each state back to the contract
Context
The workflow YAML must reflect exactly the contract’s canonical onboarding_basic states and transitions. Any mismatch breaks deterministic onboarding and tests.
Affected paths
Steps
start,ask_name,ask_goal,summary,endstartauto →ask_nameid: "onboarding_basic"matches filename and references in tests.Definition of Done