domain-skills: Best Coast Pairings (bestcoastpairings.com)

[chocobo1900-pixel]

Adds a domain skill for Best Coast Pairings, the tournament pairings platform for tabletop wargames.

Covers the logged-out REST API (newprod-api.bestcoastpairings.com with the client-id: web-app header): event search, rosters/placings, team events, per-round pairings, and army lists (the one auth-gated read).

Field-tested traps documented:

• Player lists come back under active/dropped, not data
• For upcoming events, placings=true returns an empty roster — drop the param, and note deleted mirrors active exactly
• Team-event roster rows: team is club affiliation, the event team is teamPlayerId

🤖 Generated with Claude Code

---

Summary by cubic

Adds a new domain skill for Best Coast Pairings, detailing how to read their REST API logged out with the client-id: web-app header. Enables fetching events, rosters, team data, and pairings without driving the UI.

• New Features
  • API base and required header documented
  • Event search with pagination and location JSON param
  • Rosters/placings shape under active/dropped, plus upcoming-event placings trap
  • Team events via /teamplayers and teamPlayerId vs club team
  • Per-round pairings endpoint; list under active, with player/game fields
  • Army lists endpoint noted as auth-required

^{Written for commit a975838. Summary will update on new commits.}

[browser-harness-review]

✅ Skill review passed

Reviewed 1 file(s) — no findings.

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="domain-skills/bestcoastpairings/scraping.md">

<violation number="1" location="domain-skills/bestcoastpairings/scraping.md:88">
P3: The Pairings API endpoint is documented under the `## UI notes` heading, but it's a logged-out REST API call — no browser needed. The UI notes section should cover only browser/interaction concerns (React, cookie consent, location autocomplete). Consider promoting this to a `## Pairings` subsection under `## Private API` (or a sibling section alongside it) so readers looking for REST endpoints don't miss it.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P3: The Pairings API endpoint is documented under the ## UI notes heading, but it's a logged-out REST API call — no browser needed. The UI notes section should cover only browser/interaction concerns (React, cookie consent, location autocomplete). Consider promoting this to a ## Pairings subsection under ## Private API (or a sibling section alongside it) so readers looking for REST endpoints don't miss it.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At domain-skills/bestcoastpairings/scraping.md, line 88:

<comment>The Pairings API endpoint is documented under the `## UI notes` heading, but it's a logged-out REST API call — no browser needed. The UI notes section should cover only browser/interaction concerns (React, cookie consent, location autocomplete). Consider promoting this to a `## Pairings` subsection under `## Private API` (or a sibling section alongside it) so readers looking for REST endpoints don't miss it.</comment>

<file context>
@@ -0,0 +1,102 @@
+### Pairings / match results (per round)
+
+```
+GET /v1/events/{eventId}/pairings?eventId={eventId}&round=N&pairingType=Pairing&limit=500
+```
+
</file context>