Flesh out `PersonalTrainings/Bookings` (past+future in one list, client-side
`startDate` filtering, per-field notes, `timestamp` delta-sync) and the
`PersonalTrainingsTypes` / `Instructors/Instructors` enrichment endpoints.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add a Checks section (`py_compile` + `nix build`), note the `brand/` assets
and their source, broaden the backtick-quoting rule, refine the token-expiry
guidance, and explain using decompiled APK output if provided.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Catalogue every endpoint from the capture (account, classes, products,
instructors, tracking, lifecycle), add the white-label-id and companyId
notes, and an agent-authored caveat. PII anonymised.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Send the hardcoded West Wood white-label tenant ID on API requests, matching
the app. The server doesn't require it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
With has_entity_name the device name is prepended, so the API's
'West Wood Club <club>' names rendered as 'West Wood Club West Wood
Club <club>'. Strip the prefix to show e.g. 'West Wood Club Dun
Laoghaire'.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Prefer `direnv exec .` (cached dev shell) over `nix develop --command`,
which re-evaluates the flake every call.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Token-authenticated custom component exposing live per-club member counts
as sensors under a single "West Wood Club" device, fed by one coordinator
polling `/v1/Clubs/WhoIsInCount`.
Packaged via `buildHomeAssistantComponent` with a flake package + overlay so
it can be used in `services.home-assistant.customComponents`.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
jackos1998