Scrum4Me/lib/schemas
Madhura68 0a040b721f fix(ideas): respecteer YAML-volgorde bij plan-materialize
Tasks erven nu story-priority i.p.v. eigen task.priority bij
materializeIdeaPlanAction. Worker sorteert op `priority ASC, sort_order ASC`;
gemixte task-priorities binnen één story zouden anders de YAML-volgorde
verstoren (e.g. tasks met priority 1/1/1/2/1/2 → worker-volgorde 1,2,3,5,4,6
i.p.v. 1,2,3,4,5,6).

- actions/ideas.ts: priority = s.priority bij task-create
- lib/schemas/idea.ts: task.priority optional (geaccepteerd, genegeerd)
- lib/idea-prompts/make-plan.md: documenteer dat task.priority genegeerd wordt
- __tests__/lib/idea-schemas.test.ts: test dat omitted task.priority slaagt

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-14 01:57:48 +02:00
..
idea.ts fix(ideas): respecteer YAML-volgorde bij plan-materialize 2026-05-14 01:57:48 +02:00
pbi.ts feat(codes): generateNextTaskCode + CODE_REGEX export + Zod regex op alle 3 schemas 2026-05-04 08:36:28 +02:00
product.ts feat(product-dialog): conform aan dialog-pattern + entity-profile 2026-05-04 07:18:39 +02:00
question-answer.ts feat(answer-modal): conform aan dialog-pattern + entity-profile 2026-05-04 07:34:56 +02:00
sprint.ts feat: sprint-switcher overal + PBI auto-toevoeging + cleanups (#163) 2026-05-08 02:32:50 +02:00
story.ts feat(codes): generateNextTaskCode + CODE_REGEX export + Zod regex op alle 3 schemas 2026-05-04 08:36:28 +02:00
task.ts feat(codes): generateNextTaskCode + CODE_REGEX export + Zod regex op alle 3 schemas 2026-05-04 08:36:28 +02:00
user.ts feat(ST-qfpqpxzy): DB schema + settings-UI voor min_quota_pct worker-drempel (#118) 2026-05-06 03:45:59 +02:00