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

[READY][i18n][P18] Angular host+player i18n binding med simpel telefon-UX og nul client-audio #206

New Issue
Closed
opened 2026-03-01 19:32:28 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-01 19:32:28 +01:00
Owner
Copy Link

Problem:
Frontend-flowet mangler konkret i18n-binding efter fælles kontrakt samt PO-krav om enkel telefonklient uden lokal lydafspilning.

Værdi:
Sikrer korrekt da/en visning i MVP-flow og reducerer klientkompleksitet på telefon.

Hvorfor nu:
SPA-sporet er Angular-first; dette er næste konkrete bid der kan merges uafhængigt af cutover-hardening.

Acceptance:

  • Angular host+player bruger shared i18n keys (ingen nye hardcoded danske tekster i MVP-flow).
  • Mobile/client views holder simpel UX (få felter/tydelige handlinger/lav visuel kompleksitet).
  • Telefon/client afspiller ikke lyd (client_has_no_audio_output=true verificerbar).
  • Primær enhed/host følger locale-valg for eventuelle lyd-referencer.

Afgrænsning:

  • Ingen redesign af gameplay-regler.
  • Ingen React-implementering medmindre dokumenteret Angular-blokering opstår.
Problem: Frontend-flowet mangler konkret i18n-binding efter fælles kontrakt samt PO-krav om enkel telefonklient uden lokal lydafspilning. Værdi: Sikrer korrekt da/en visning i MVP-flow og reducerer klientkompleksitet på telefon. Hvorfor nu: SPA-sporet er Angular-first; dette er næste konkrete bid der kan merges uafhængigt af cutover-hardening. Acceptance: - Angular host+player bruger shared i18n keys (ingen nye hardcoded danske tekster i MVP-flow). - Mobile/client views holder simpel UX (få felter/tydelige handlinger/lav visuel kompleksitet). - Telefon/client afspiller ikke lyd (`client_has_no_audio_output=true` verificerbar). - Primær enhed/host følger locale-valg for eventuelle lyd-referencer. Afgrænsning: - Ingen redesign af gameplay-regler. - Ingen React-implementering medmindre dokumenteret Angular-blokering opstår.
architecture-bot added the bot-taskneed-to-havearchitectuii18nfrontend labels 2026-03-01 19:32:28 +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 architect bot-task frontend i18n 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#206
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?