docs+tests(sort-order): update for code-binding order on stories/tasks

- Rewrite docs/patterns/sort-order.md: float-insertion PBI only; story/task
  sort_order = parseCodeNumber(code), never drag/membership mutated
- Update plan-to-pbi-flow.md: sort_order auto, sprint_id param, priority=label
- Update make-plan.md: priority=label, array order = execution order
- Update rest-contract.md: fix sprint-tasks ordering, remove reorder endpoint
- Add ADR-0011: code is bindende volgordesleutel voor stories/taken
- Regenerate docs/INDEX.md via npm run docs
- Remove reorderStoriesAction/reorderTasksAction mocks from backlog tests
- Remove dnd-kit mocks from task-panel test (panel no longer uses dnd)
- Extend materializeIdeaPlanAction test: assert sort_order=parseCodeNumber(code)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Scrum4Me Agent 2026-05-14 18:13:42 +02:00
parent 3a5aba2824
commit 3a7141114c
9 changed files with 150 additions and 76 deletions

View file

@ -102,7 +102,7 @@ stories:
2. Test toevoegen Y
3. Verifieer Z
# task.priority is optioneel en wordt door materialize GENEGEERD.
# Tasks erven story.priority; sort_order = positie in deze tasks-array.
# Tasks erven story.priority; sort_order wordt afgeleid van de auto-code.
verify_required: ALIGNED_OR_PARTIAL # ALIGNED | ALIGNED_OR_PARTIAL | ANY
verify_only: false # true voor pure verify-passes
- title: "Taak B"
@ -146,9 +146,9 @@ Beschrijf:
- `pbi.priority`, `story.priority`: integer 14, **verplicht**.
- `task.priority`: integer 14, **optioneel**. **Wordt door materialize genegeerd**
ten faveure van story-priority — alle tasks binnen een story erven dezelfde
priority. Reden: worker sorteert op `priority ASC, sort_order ASC`; gemixte
task-priorities zouden de YAML-volgorde verstoren. De YAML-volgorde *is* de
execution-volgorde — daar is `sort_order` (positie in de array) voor.
priority. `priority` is een **label** (urgentie), géén sorteerkriteria voor stories
of taken. De **YAML-array-volgorde** is de execution-volgorde: de server berekent
`sort_order = parseCodeNumber(auto-code)` op basis van aanroep-volgorde.
- Minimaal 1 story; per story minimaal 1 taak.
- `implementation_plan`: max 8000 chars.
- `verify_required`: enum exact `ALIGNED` | `ALIGNED_OR_PARTIAL` | `ANY`.