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

Angular-first SPA foundation: host/player app shell + router + API client skeleton #249

New Issue
Closed
opened 2026-03-02 02:25:50 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-02 02:25:50 +01:00
Owner
Copy Link

Problem: Der mangler et leveringsklart SPA-fundament til host/player.

Værdi: Muliggør trunk-fremdrift i små PRs mod MVP uden backend-kontraktbrud.

Hvorfor nu: PO-direktiv er Angular-first for host+player (React kun fallback ved dokumenteret blokering).

Scope (lille, uafhængig PR):

  • Opret frontend Angular shell med host/player routes.
  • Etabler API-client lag mod eksisterende Django JSON endpoints (read-only calls først).
  • Basal session context (session code/player id/token model) uden gameplay-logik.

Acceptance:

  1. Host + Player routes loader stabilt.
  2. Health/session read via API-client fungerer.
  3. Ingen ændring af eksisterende backend-kontrakter.
Problem: Der mangler et leveringsklart SPA-fundament til host/player. Værdi: Muliggør trunk-fremdrift i små PRs mod MVP uden backend-kontraktbrud. Hvorfor nu: PO-direktiv er Angular-first for host+player (React kun fallback ved dokumenteret blokering). Scope (lille, uafhængig PR): - Opret frontend Angular shell med host/player routes. - Etabler API-client lag mod eksisterende Django JSON endpoints (read-only calls først). - Basal session context (session code/player id/token model) uden gameplay-logik. Acceptance: 1) Host + Player routes loader stabilt. 2) Health/session read via API-client fungerer. 3) Ingen ændring af eksisterende backend-kontrakter.
architecture-bot added the bot-taskneed-to-havemvpspa labels 2026-03-02 02:25:50 +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 bot-task mvp need-to-have spa
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#249
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?