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

[READY][SPA][P13] Foundation: Angular API-kontrakt smoke for host/player endpoints #199

New Issue
Closed
opened 2026-03-01 18:02:21 +01:00 by architecture-bot · 1 comment
architecture-bot commented 2026-03-01 18:02:21 +01:00
Owner
Copy Link

Problem:
Nu mangler vi en lille, dedikeret SPA-foundation-opgave der beviser at Angular API-client fortsat matcher eksisterende Django-kontrakter før flere gameplay-PRs lander.

Værdi:
Reducerer regressionsrisiko i SPA-sporet og gør review hurtigere, fordi kontraktbrud fanges tidligt.

Hvorfor nu:
PO-direktiv låser retning til Angular-first; vi har aktive gameplay-PRs, så kontrakt-sikkerhed skal på plads før yderligere flow-udvidelse.

Acceptance:

  • Der findes en dokumenteret smoke-check (script/test) for Angular API-client mod mindst: session read, join, start-round.
  • Check kan køres i CI/local uden at ændre backend-kontrakter.
  • PR beskriver tydeligt hvilke endpoints/responsefelter der er dækket.

Afgrænsning:

  • Ingen nye backend-endpoints.
  • Ingen UI-polish.
  • Fokus kun på kontrakt-verifikation i SPA foundation-laget.
Problem: Nu mangler vi en lille, dedikeret SPA-foundation-opgave der beviser at Angular API-client fortsat matcher eksisterende Django-kontrakter før flere gameplay-PRs lander. Værdi: Reducerer regressionsrisiko i SPA-sporet og gør review hurtigere, fordi kontraktbrud fanges tidligt. Hvorfor nu: PO-direktiv låser retning til Angular-first; vi har aktive gameplay-PRs, så kontrakt-sikkerhed skal på plads før yderligere flow-udvidelse. Acceptance: - Der findes en dokumenteret smoke-check (script/test) for Angular API-client mod mindst: session read, join, start-round. - Check kan køres i CI/local uden at ændre backend-kontrakter. - PR beskriver tydeligt hvilke endpoints/responsefelter der er dækket. Afgrænsning: - Ingen nye backend-endpoints. - Ingen UI-polish. - Fokus kun på kontrakt-verifikation i SPA foundation-laget.
architecture-bot added the bot-taskneed-to-havearchitectfrontend labels 2026-03-01 18:02:21 +01:00
dev-bot commented 2026-03-01 19:06:17 +01:00
Owner
Copy Link

Scheduler assignment (dev-lane-2) — 2026-03-01T18:06:16Z

PR-first queue check: Ingen åbne PRs (merge/review-kø tom), derfor ny udvikling tilladt.
Throughput-mode: READY-kø >= 5 og review/integrator backlog lav => 3 parallelle dev-lanes aktiveret.

Krav til execution:

  • Scope: #199 (Angular API-kontrakt smoke for host/player endpoints)
  • Opret/brug feature-branch + PR til main
  • Acceptance: implementér issue acceptance-kriterier fuldt; dokumentér test/check-resultater i PR-beskrivelse
  • Artifact-gate (obligatorisk): rapportér commit SHA + PR head SHA i afslutningskommentar
  • Ved blocker: skriv konkret blocker + næste handling i issue/PR
Scheduler assignment (dev-lane-2) — 2026-03-01T18:06:16Z PR-first queue check: Ingen åbne PRs (merge/review-kø tom), derfor ny udvikling tilladt. Throughput-mode: READY-kø >= 5 og review/integrator backlog lav => 3 parallelle dev-lanes aktiveret. Krav til execution: - Scope: #199 (Angular API-kontrakt smoke for host/player endpoints) - Opret/brug feature-branch + PR til main - Acceptance: implementér issue acceptance-kriterier fuldt; dokumentér test/check-resultater i PR-beskrivelse - Artifact-gate (obligatorisk): rapportér commit SHA + PR head SHA i afslutningskommentar - Ved blocker: skriv konkret blocker + næste handling i issue/PR
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 need-to-have
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#199
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?