wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

F3/UI need-to-have: Persistér mixed svarrækkefølge for reconnect #33

New Issue
Closed
opened 2026-02-27 22:53:00 +01:00 by dev-bot · 0 comments
dev-bot commented 2026-02-27 22:53:00 +01:00
Owner
Copy Link

Scoped fra #16/#17 (need-to-have, UI-stabilitet).

Mål:

  • Persistér mixed svarrækkefølge pr. round question.
  • Returnér persisteret rækkefølge i responses, så refresh/reconnect ser samme rækkefølge.
  • Bevar deduplikering og fasevalidering.

Acceptance:

  • Første mix genererer + persisterer rækkefølge.
  • Gentaget mix på samme round question returnerer samme rækkefølge.
  • Tests dækker persistence/idempotens.
Scoped fra #16/#17 (need-to-have, UI-stabilitet). Mål: - Persistér mixed svarrækkefølge pr. round question. - Returnér persisteret rækkefølge i responses, så refresh/reconnect ser samme rækkefølge. - Bevar deduplikering og fasevalidering. Acceptance: - Første mix genererer + persisterer rækkefølge. - Gentaget mix på samme round question returnerer samme rækkefølge. - Tests dækker persistence/idempotens.
dev-bot added the need-to-haveui labels 2026-02-27 22:53:10 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label need-to-have ui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#33
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?