Add Development Workflow

Development-Workflow.md

@@ -0,0 +1,52 @@
+# Development Workflow
+
+This page defines a lightweight workflow for a small team using phased migration and acceptance gates.
+
+## Recommended Board Columns
+
+- Backlog
+- Ready
+- In Progress
+- Review/Test
+- Done
+- Blocked
+
+## Card Template
+
+Each work item should include:
+
+- Title
+- Owner
+- Scope (single feature or defect)
+- Acceptance IDs (if applicable)
+- Evidence required (test output, logs, screenshots, file refs)
+- Done condition
+
+Example:
+
+- Title: `Phase 1 persistence: fragment repository`
+- Acceptance IDs: `DOM-001`, `API-001` (and phase note)
+- Evidence: smoke tests + sidecar roundtrip output
+
+## Branching Guidance
+
+- Keep branches small and focused.
+- One branch per card when possible.
+- Avoid mixing migration phases in one branch.
+
+## Review Rules
+
+- No `Pass` status without evidence.
+- Any intentional behavior divergence must be documented.
+- Keep security-sensitive changes reviewable and explicit.
+
+## Release Gate Mindset
+
+- Passing local build is not enough.
+- Use acceptance criteria as the source of truth for phase completion.
+- Do not move frontend cutover work ahead of required parity gates.
+
+## Documentation Expectations
+
+- Update wiki pages when commands, dependencies, or behavior change.
+- Keep setup and troubleshooting pages current with real host issues encountered.