groombook/api
13
0
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

feat(GRO-2319): surface active waitlist entries on portal appointments + seed #204

Merged
Flea Flicker merged 1 commits from feat/GRO-2319-portal-waitlist-surfacing into dev 2026-06-09 10:41:09 +00:00
Conversation 0 Commits 1 Files Changed 4
+165 -9
Flea Flicker commented 2026-06-09 10:38:28 +00:00
Member
Copy Link
Copy Source

GRO-2319 (Phase 1: feature → dev) — Portal: surface + seed waitlist entries (api)

Companion to web PR. Follow-up to GRO-2313; CMPO sign-off on GRO-2326/GRO-2328.

Changes

  • GET /api/portal/appointments now also returns the client's ACTIVE waitlist_entries as synthetic waitlisted cards: id prefixed waitlist:, status: "waitlisted", confirmationStatus: null, and a startTime derived from the entry's preferred date/time so the portal classifies it as Upcoming.
  • Seed: one ACTIVE waitlist entry for the UAT customer. waitlist_entries is NOT truncated on the hourly reset, so it is upserted by fixed id with its preferred date refreshed to a future-relative value each reset (otherwise it would go stale and drop out of Upcoming). The existing scheduled row already carries confirmationStatus: "pending" which drives the live Pending badge.

Tests

  • portal.test.ts: two GET /portal/appointments waitlist-surfacing tests (active entry surfaced as waitlist: card; no waitlisted card when none active). Portal/waitlist/confirmation suites: 131 passing. Root tsc + packages/db tsc clean.

UAT Playbook

  • UAT_PLAYBOOK.md TC-API-8.19 — portal appointments surface active waitlist entries.

🤖 Generated with Claude Code

## GRO-2319 (Phase 1: feature → dev) — Portal: surface + seed waitlist entries (api) Companion to web PR. Follow-up to [GRO-2313](/GRO/issues/GRO-2313); CMPO sign-off on GRO-2326/GRO-2328. ### Changes - **`GET /api/portal/appointments`** now also returns the client's **ACTIVE** `waitlist_entries` as synthetic `waitlisted` cards: `id` prefixed `waitlist:`, `status: "waitlisted"`, `confirmationStatus: null`, and a `startTime` derived from the entry's preferred date/time so the portal classifies it as Upcoming. - **Seed:** one ACTIVE waitlist entry for the UAT customer. `waitlist_entries` is NOT truncated on the hourly reset, so it is upserted by fixed id with its preferred date refreshed to a future-relative value each reset (otherwise it would go stale and drop out of Upcoming). The existing `scheduled` row already carries `confirmationStatus: "pending"` which drives the live Pending badge. ### Tests - `portal.test.ts`: two GET `/portal/appointments` waitlist-surfacing tests (active entry surfaced as `waitlist:` card; no waitlisted card when none active). Portal/waitlist/confirmation suites: 131 passing. Root `tsc` + `packages/db` `tsc` clean. ### UAT Playbook - `UAT_PLAYBOOK.md` **TC-API-8.19** — portal appointments surface active waitlist entries. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Flea Flicker added 1 commit 2026-06-09 10:38:28 +00:00
feat(GRO-2319): surface active waitlist entries on portal appointments + seed
CI / Test (pull_request) Successful in 27s
Details
CI / Lint & Typecheck (pull_request) Successful in 33s
Details
CI / Build & Push Docker Images (pull_request) Successful in 1m24s
Details
7523263072 
- GET /api/portal/appointments now also returns the client's ACTIVE
  waitlist_entries as synthetic `waitlisted` cards (id prefixed `waitlist:`,
  status hard-set to waitlisted, startTime derived from preferred date/time)
  so the portal can render Waitlisted cards in the Upcoming list (item 2).
- Seed one active waitlist entry for the UAT customer. waitlist_entries is
  NOT truncated on the hourly reset, so the entry is upserted by fixed id and
  its preferred date refreshed to a future-relative value each reset to stay
  Upcoming. (The existing scheduled row already carries confirmationStatus
  pending, which drives the live Pending badge.)
- portal.test.ts: GET /portal/appointments waitlist-surfacing tests.
- UAT_PLAYBOOK.md TC-API-8.19 for the surfaced waitlist entries.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Flea Flicker merged commit ef18ed7376 into dev 2026-06-09 10:41:09 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai-review (AI Review) gb_barkley (Barkley Trimsworth) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) gb_flea (Flea Flicker) flux (Flux CD) admin (Gitea Admin) gb_lint (Lint Roller) renovate (Mend Renovate) gb_pawla (Pawla Abdul) gb_scrubs (Scrubs McBarkley) gb_shedward (Shedward Scissorhands) gb_dogfather (The Dogfather)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/api#204
Delete Branch "feat/GRO-2319-portal-waitlist-surfacing"

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?