@go-labs-sg/rsvp 0.6.1 → 0.9.0

package/examples/amgen-feedback-20260909/verification.md

@@ -0,0 +1,126 @@
+# Verification and handoff
+
+**Update:** Noah subsequently authorized Registration CLI (`rsvp`) configuration changes. Event details, dietary/receipt settings and the venue layout are now applied; see [applied configuration](applied-configuration.md). The table below records the earlier local implementation verification.
+
+Work was completed on `codex/amgen-feedback-20260909`, created from freshly fetched `origin/dev` at `f7c6cbb95fd742ede4821b8a56c082ca34b3db6f`. The primary checkout was preserved. At that initial handoff, no deployment, live configuration/data mutation, participant email or QR send had been performed. Email source reads used `gog`.
+
+## Feedback status
+
+| Item | Status | Evidence and remaining work |
+| --- | --- | --- |
+| 1. OTP and event access | Fixed locally; staging integration remains | Employee-ID email OTP verification now creates the verified event participant session in the same response. It no longer depends on a second browser request seeing newly changed auth cookies. Current user verification, ban state, roster identity, ownership and eligibility are checked before issuing the participant cookie. The OTP screen is expected; getting stuck there after valid verification is not. Invalid/expired codes retain the change-ID/request-new-code recovery. |
+| 2. Submission and highlighting | Fixed locally | The blank guest-name state from the screenshot is reproduced: the client previously accepted an empty name that the server rejected. Required-answer validation now runs across the reachable path on final submission. It returns to the answer, highlights it and focuses its control. Server field issues survive tRPC formatting and reach the same navigation. Form defaults now use the reconciled answers that Review displays. Entered valid answers remain intact. Existing registration idempotency and receipt deduplication are preserved. |
+| 3. Dates, venue and entry copy | Dates/venue applied; entry copy awaits deployment | 27 November 2026, 6–10:30pm; specified ballroom; 6 November 11:59pm Singapore cutoff; requested entry CTA and description. Only this event opts into the new presentation overrides. Existing response-editing rules remain unchanged. |
+| 4. Menus and dietary answers | Dietary flow applied; menu icons fixed locally | Readable existing menu names now have decorative accessible icons. The existing custom-field architecture supplies participant dietary Yes/No and required text only for Yes on Step 3. Saved answer models support review and receipt. No new menus or guest dietary questions were added. |
+| 5. Venue and seats | Venue applied; seat behavior fixed locally | The PDF arrangement contains 55 ten-seat tables. Tables 1 and 2 are VIP at stage centre. Available seats remain green at the party limit; clicking another replaces the last selected seat. Held/booked/restricted seats remain unavailable. The dense overview and enlarged table detail preserve navigation. CLI read-back verified all original table/seat IDs and bookings were preserved during application on 10 September. |
+| 6. Confirmation and receipt | Receipt and later QR delivery implemented locally; activation pending | The detailed receipt includes identity, attendance, menu, dietary, guest and seating information. Exact requested QR timing copy is prepared. The scheduled-campaign QR delivery path is now implemented locally. This test event still has no active QR schedule; release/send times remain unspecified. Timing copy is saved in draft 22, not published. |
+| 7. Admin and sample report | Dashboard/access already correct; combined export gap | Dashboard and reports routes were verified. The synthetic sample demonstrates supported saved fields. Existing exports do not join all V2 menu/dietary answers; that gap is documented without expanding reporting scope. |
+
+## Reproduction and evidence limits
+
+- The original Review screenshot shows a blank guest-name value despite selecting Yes to bringing a guest. That state is reproduced in the DOM fixture: the client accepted the list, while the server returned `INVALID_ANSWER` for the guest answer. Submit now returns to the preserved guest input and focuses it. We do not have the original failing request payload or server logs, so we do not claim to identify every answer in that request.
+- A separate reproduced case had four stale seat IDs in initial form data while Review displayed the two reconciled seats. Initializing the form with those same reconciled answers removes the mismatch.
+- The actual installed tRPC library discarded an array passed as an error cause. The server previously threw its detailed validation issues that way, and the formatter did not expose them. A typed `Error` now carries only projected public issue fields; the actual router formatter is regression-tested with a real procedure failure.
+- The seat inconsistency was rendering/interaction logic: reaching party size put otherwise available seats into `disabledSeatIds`, which the renderer treated as unavailable. Selection limits now replace the final selection while booking/hold/eligibility checks remain enforced.
+- The original OTP screenshot shows the post-verification “Continue to registration” state and an admission error. The code had two separate requests. The patch removes that dependency and tests the combined boundary, but the precise cause of Claudia's historical request cannot be proven without its logs.
+
+## Safe verification
+
+Regression fixtures use synthetic identities, in-memory persistence and outbox state, and a synthetic email sink. Tests do not contact a participant email provider. OTP challenge expiry, invalid OTP rejection, mapping changes, eligibility and same-response cookies are tested at procedure boundaries. Better Auth's OTP provider and returned auth headers are mocked: real browser cookie handling, real database contention and provider delivery still require an approved staging check.
+
+Local browser checks use the actual event entry page with the prepared configuration, and the actual seat viewer with synthetic seats. Desktop/mobile entry checks verified copy, CTA destination, no horizontal overflow and no page errors. Seating checks exercised table selection and replacement through actual controls. These are isolated local UI fixtures, not a full authenticated production RSVP run.
+
+The full RSVP test run also identified two unrelated baseline failures in unchanged source:
+
+- `tests/rsvp/cli/procedure-parity.test.ts:127`: the CLI lacks `event.createBackgroundUpload` and `event.updateBackground` references already mounted by the baseline router.
+- `tests/rsvp/ui/attendee-layout-priority.test.ts:45`: the unchanged legacy confirmation page does not put “Check-in references” before “When”, as that source-order assertion expects.
+
+Final command results:
+
+- Focused authentication/configuration/receipt/entry tests: **68 passed** across 9 files.
+- Focused submission/navigation/seating/reservation tests: **125 passed** across 14 files, including isolated DOM scenarios.
+- `bun --filter @go-labs/rsvp-tests test`: **970 passed, 2 baseline failures**, across 174 files. Both failures are identified above; their relevant baseline source is unchanged.
+- `bun check:all`: **passed**, including formatting, repository standards, TypeScript checks and native Swift typechecking. Missing generated clients were regenerated with the repository workflow using a dummy local database URL; no database was contacted.
+- Complete tracked and new-file diff reviewed; `git diff --check` passed. No version bumps, production dependencies, migrations or raw Prisma SQL were introduced.
+
+Neither baseline failure was hidden or relaxed. The last fixture-only type corrections do not change the tested behavior.
+
+## Approval boundaries and remaining questions
+
+Refresh revision/version checks before applying any payload. Test-event setup and draft saves are authorized and recorded in applied-configuration.md. Code deployment and staging/production sends remain separate rollout actions. The plan has 550 chairs while the existing event admission cap is 500; this patch preserves the cap. The drawing is marked draft and has an inconsistent title date, so its operational approval still needs confirmation. The requested event date remains 27 November.
+
+The QR promise needs deployment of the local delivery mechanism and an explicit release/send timestamp. The combined report needs a separately scoped export change with sensitive-data permissions. These gaps do not prevent reviewing and testing the local fixes.
+
+## 10 September: confirmation and Registration branding
+
+Local follow-up work groups confirmation answers under the published page titles,
+keeps identity separate, promotes seat assignments, and shows the event's full
+start/end time range. On mobile, the venue map expands inline on request and
+retains zoom/table navigation. The app now uses Registration in user-facing
+branding, participant/admin copy and default transactional messages. Terraform,
+subdomains, app directory names and technical contracts remain unchanged.
+
+The UI/UX layout review used Impeccable and the public Pinterest reference
+[Booking Confirmation – Web](https://www.pinterest.com/pin/164944405092037092/).
+Mobbin's connector required a paid plan; direct browser inspection also required
+sign-in, so no Mobbin library screens were used.
+
+Browser checks used synthetic data at 1440×900, 390×844 and 320×640: guest/no-guest,
+declined response, light/dark themes, no horizontal overflow, full event time,
+readable seat assignments, mobile map expansion/zoom/collapse, and desktop dialog
+focus recovery. No live booking, production data or email send was used.
+
+## 10 September: CLI venue application and saved-copy guard
+
+- Added guarded CLI wrappers for the existing table-label and layout APIs; no new server procedure or reservation rule was needed.
+- Applied all 55 tables and the floor objects through the CLI. Verified the exact coordinates, original 50 seat IDs and booking records, unchanged 26 booking count, and unchanged admission cap of 500.
+- Validated the remaining receipt/completion wording and saved draft 22. Active flow 11 remains unchanged, and no emails were queued or sent.
+- Confirmed a publication limitation: sessions are bound to the published version; after re-admission, saved-answer hydration also rejects a previous version. Publishing even copy-only changes would disrupt the existing registrations. The copy stays in the draft until there is a safe compatible-publication implementation.
+- Focused CLI/configuration/venue tests: **68 passed** across four files.
+
+Still requiring rollout work: deploy and stage-check the local fixes; activate the event entry metadata using the compatible API; safely publish draft 22 for existing registrants; and explicitly configure a QR release/send time. No send time was inferred from the registration cutoff.
+
+## Later QR campaign implementation
+
+The reserved `{{checkInQrCodes}}` campaign placeholder now generates labelled PNG
+attachments for the recipient's submitted registration and its guests, using the
+existing shared QR utility. It is separate from the immediate receipt. The worker
+rechecks release policy, event publication, current invitee/email, registration
+status, attendee IDs, credential versions and signed-token hashes before sending.
+
+QR campaigns queue one recipient per outbox message. Exact request hashes and the
+first-attempt time are saved before provider calls with a metadata comparison;
+changed requests and uncertain attempts older than 23 hours require reconciliation.
+Already-accepted recipients are not resent after webhook or retry status changes.
+Arbitrary test-send and initial send-now paths are rejected for QR templates;
+failed scheduled deliveries retain guarded retries.
+
+Verification uses an isolated in-memory database/email sink, plus actual local
+PNG generation and visual inspection with synthetic credentials. It does not prove
+real database contention, deployed font packaging, or provider/client rendering;
+those remain staging checks. No live QR campaign, send, or release was created.
+
+Final follow-up verification on 10 September:
+
+- CLI/configuration/venue regression run: **68 passed**.
+- Final QR policy/delivery wrapper and existing campaign audience/delivery tests: **10 passed** across four files. The isolated delivery fixture executes **7 scenarios, 26 assertions**, including provider acceptance followed by a database-write failure, address changes and cancellation. All messages went to an in-memory sink.
+- `bun check:all`: **passed** after fixing the new fixture's two type errors. Biome checked 5,439 files with no further changes; all 87 TypeScript tasks and native Swift checks passed.
+- Independent final QR review found no remaining concrete issues in the patched paths. Complete tracked/new-file diff and final formatting changes were reviewed; `git diff --check` passed.
+- The previously documented two unrelated full-suite baseline failures were not hidden or changed. The final follow-up ran focused tests, not a new full product test run.
+- Live read-back: configuration version 8, active flow 11, draft 22; 55 tables/550 chairs, 500-person admission cap, all original seat IDs and booking records preserved. No deployment, email send, QR release or QR schedule was performed.
+
+
+## PR #988 integration after PR #986
+
+Rebased onto `origin/dev` at `2fed1a66b590ddac4e289c974010560e1649a5e2`,
+which contains the merged event-settings reorganization from PR #986. Resolved
+all five conflicting files by preserving the retired setup-route deletions and
+the new field editor's roster/current-form behavior. Registration wording was
+carried into the moved builder/operator components and the replacement
+registration, check-in and retention settings screens.
+
+The original participant auth, submission, seating, confirmation and QR delivery
+files are unchanged by this integration. The complete Registration suite on the
+combined code reports **1,001 passed, 2 failed** across 181 files. Both failures
+are the already documented CLI background-procedure parity and confirmation
+source-order assertions. No additional failures were introduced by the rebase.

package/examples/amgen-feedback-20260911/README.md

@@ -0,0 +1,41 @@
+# Amgen disclaimer update — prepared, not applied
+
+Source: Claudia Khng’s 11 September 2026 email, “RE: ASM DnD 2026 - Registration”,
+attachment **Disclaimer B - ASM Indemnity Disclaimer (general activities).pdf**.
+
+[consent-version.json](consent-version.json) contains the full four numbered clauses,
+the bold/underlined title, defined-term emphasis, and confidentiality footer.
+Only PDF line wrapping was normalized; the wording is unchanged. Rich HTML is the
+authoritative display content; the API derives its plaintext fallback.
+
+Target: Amgen’s **test** event `amgen-dinner-and-dance-2026-test`
+(`cmthccwii000501lgluebz2v2`), existing consent document
+`cmtqnemuh000o01lk4t8lxq1l`. This payload does not target the separate production event.
+
+## Prerequisites and application
+
+The `EventConsentDocumentVersion.contentRichText` schema field and corresponding
+API/web changes must be available in the target environment first. Follow the
+normal database/deployment workflow; this change includes no migration files.
+
+After those prerequisites, from the repository root, create the immutable version:
+
+```bash
+bun packages/rsvp/cli/src/index.ts event flow consent version create \
+  --allow-state-change \
+  --target cmthccwii000501lgluebz2v2 \
+  --payload "$(cat packages/rsvp/cli/examples/amgen-feedback-20260911/consent-version.json)"
+```
+
+Read the resource catalog back and verify the returned document/version and rich
+content. Fetch the **latest** flow draft before changing its `indemnity` block’s
+`consentVersionId` to the newly returned ID; preserve all other draft fields and
+use the freshly read revision when saving. No full draft snapshot is provided here
+because replaying one could overwrite unrelated edits.
+
+At inspection on 11 September, the active flow was version **11** and the draft
+revision was **23**. The draft contains other unpublished receipt/completion copy.
+The current publication/session compatibility limitation is documented in
+[the earlier application record](../amgen-feedback-20260909/applied-configuration.md).
+Creating a document version, saving a draft reference, and publishing are separate
+operations. None of those live writes was performed for this prepared update.

package/examples/amgen-feedback-20260911/consent-version.json

@@ -0,0 +1,146 @@
+{
+	"organizationId": "kh27TwiqDX8OJ1a28GJVW4oG9bhP7Ld5",
+	"eventId": "cmthccwii000501lgluebz2v2",
+	"document": {
+		"mode": "EXISTING",
+		"documentId": "cmtqnemuh000o01lk4t8lxq1l"
+	},
+	"content": "DISCLAIMER\n\n1. The participation in the activity is open to all regular full-time employees, and the immediate family members (hereinafter defined as spouse, child, parent or sibling) or guests of regular full-time employees at Amgen Singapore Manufacturing Pte Ltd. (“ASM”) or any of ASM’s parent, subsidiary or affiliated entities (collectively, “Amgen”), as determined and invited at Amgen’s sole discretion.\n\n2. You acknowledge that participation is strictly at your own volition and is undertaken at your own risk, under no coercion or pressure from Amgen or any third party, whether within Amgen or otherwise. It is not a term or condition of your employment with Amgen.\n\n3. Should you participate in this activity, Amgen assumes no responsibility for any liability, damage or injury that may be caused by your own negligent and willful acts and omissions related to or arising from your participation in the activity. You agree to indemnify, defend and hold harmless Amgen, from any loss or liability whatsoever, including reasonable attorneys' fees, associated with or arising from your negligent acts or willful acts and omissions related to or arising from your participation in the activity. You also acknowledge that in the event of liability, damage or injury that Amgen assesses (in its sole discretion) as not caused by your own negligent and willful acts and omissions, you will only be covered to the maximum extent in accordance with Amgen’s policies. Amgen’s decision shall be final and binding on you and you hereby release, waive, relinquish, discharge from liability and covenant not to sue Amgen from any and all claims, demands, actions, suits, causes of action and/or liabilities, of whatever kind or nature, in law, equity or otherwise, related to or arising from your participation in the activity.\n\n4. Immediate family members or guests of a regular full-time employee’s participation in the activity, whether or not supervised, is solely at their own risk and hereby release, waive, relinquish, discharge from liability and covenant not to sue ASM or any of ASM’s parent, subsidiary or affiliated entities, including but not limited to Amgen Inc., as well as their respective directors, officers, employees, representatives, independent contractors, insurers, attorneys and/or agents in their capacity as such or otherwise (the \"Releasees\") from any and all claims, demands, actions, suits, causes of action and/or liabilities, of whatever kind or nature, in law, equity or otherwise, related to or arising from their participation in the activity including but not limited to any negligent act or omission by any of the Releasees and/or any accident, illness or injury incurred as a result of their participation in the activity, save where such accident, illness or injury is directly caused by the gross negligence or willful misconduct of ASM, ASM’s parent, subsidiary or affiliated entities, including but not limited to Amgen Inc., as well as their respective directors, officers, employees or representatives.\n\nConfidential Human Resources",
+	"contentRichText": {
+		"json": {
+			"type": "doc",
+			"content": [
+				{
+					"type": "paragraph",
+					"content": [
+						{
+							"type": "text",
+							"text": "DISCLAIMER",
+							"marks": [
+								{
+									"type": "bold"
+								},
+								{
+									"type": "underline"
+								}
+							]
+						}
+					]
+				},
+				{
+					"type": "orderedList",
+					"attrs": {
+						"start": 1
+					},
+					"content": [
+						{
+							"type": "listItem",
+							"content": [
+								{
+									"type": "paragraph",
+									"content": [
+										{
+											"type": "text",
+											"text": "The participation in the activity is open to all regular full-time employees, and the immediate family members (hereinafter defined as spouse, child, parent or sibling) or guests of regular full-time employees at Amgen Singapore Manufacturing Pte Ltd. ("
+										},
+										{
+											"type": "text",
+											"text": "“ASM”",
+											"marks": [
+												{
+													"type": "bold"
+												}
+											]
+										},
+										{
+											"type": "text",
+											"text": ") or any of ASM’s parent, subsidiary or affiliated entities (collectively, "
+										},
+										{
+											"type": "text",
+											"text": "“Amgen”",
+											"marks": [
+												{
+													"type": "bold"
+												}
+											]
+										},
+										{
+											"type": "text",
+											"text": "), as determined and invited at Amgen’s sole discretion."
+										}
+									]
+								}
+							]
+						},
+						{
+							"type": "listItem",
+							"content": [
+								{
+									"type": "paragraph",
+									"content": [
+										{
+											"type": "text",
+											"text": "You acknowledge that participation is strictly at your own volition and is undertaken at your own risk, under no coercion or pressure from Amgen or any third party, whether within Amgen or otherwise. It is not a term or condition of your employment with Amgen."
+										}
+									]
+								}
+							]
+						},
+						{
+							"type": "listItem",
+							"content": [
+								{
+									"type": "paragraph",
+									"content": [
+										{
+											"type": "text",
+											"text": "Should you participate in this activity, Amgen assumes no responsibility for any liability, damage or injury that may be caused by your own negligent and willful acts and omissions related to or arising from your participation in the activity. You agree to indemnify, defend and hold harmless Amgen, from any loss or liability whatsoever, including reasonable attorneys' fees, associated with or arising from your negligent acts or willful acts and omissions related to or arising from your participation in the activity. You also acknowledge that in the event of liability, damage or injury that Amgen assesses (in its sole discretion) as not caused by your own negligent and willful acts and omissions, you will only be covered to the maximum extent in accordance with Amgen’s policies. Amgen’s decision shall be final and binding on you and you hereby release, waive, relinquish, discharge from liability and covenant not to sue Amgen from any and all claims, demands, actions, suits, causes of action and/or liabilities, of whatever kind or nature, in law, equity or otherwise, related to or arising from your participation in the activity."
+										}
+									]
+								}
+							]
+						},
+						{
+							"type": "listItem",
+							"content": [
+								{
+									"type": "paragraph",
+									"content": [
+										{
+											"type": "text",
+											"text": "Immediate family members or guests of a regular full-time employee’s participation in the activity, whether or not supervised, is solely at their own risk and hereby release, waive, relinquish, discharge from liability and covenant not to sue ASM or any of ASM’s parent, subsidiary or affiliated entities, including but not limited to Amgen Inc., as well as their respective directors, officers, employees, representatives, independent contractors, insurers, attorneys and/or agents in their capacity as such or otherwise (the "
+										},
+										{
+											"type": "text",
+											"text": "\"Releasees\"",
+											"marks": [
+												{
+													"type": "bold"
+												}
+											]
+										},
+										{
+											"type": "text",
+											"text": ") from any and all claims, demands, actions, suits, causes of action and/or liabilities, of whatever kind or nature, in law, equity or otherwise, related to or arising from their participation in the activity including but not limited to any negligent act or omission by any of the Releasees and/or any accident, illness or injury incurred as a result of their participation in the activity, save where such accident, illness or injury is directly caused by the gross negligence or willful misconduct of ASM, ASM’s parent, subsidiary or affiliated entities, including but not limited to Amgen Inc., as well as their respective directors, officers, employees or representatives."
+										}
+									]
+								}
+							]
+						}
+					]
+				},
+				{
+					"type": "paragraph",
+					"content": [
+						{
+							"type": "text",
+							"text": "Confidential Human Resources"
+						}
+					]
+				}
+			]
+		},
+		"html": "<p><strong><u>DISCLAIMER</u></strong></p><ol><li><p>The participation in the activity is open to all regular full-time employees, and the immediate family members (hereinafter defined as spouse, child, parent or sibling) or guests of regular full-time employees at Amgen Singapore Manufacturing Pte Ltd. (<strong>“ASM”</strong>) or any of ASM’s parent, subsidiary or affiliated entities (collectively, <strong>“Amgen”</strong>), as determined and invited at Amgen’s sole discretion.</p></li><li><p>You acknowledge that participation is strictly at your own volition and is undertaken at your own risk, under no coercion or pressure from Amgen or any third party, whether within Amgen or otherwise. It is not a term or condition of your employment with Amgen.</p></li><li><p>Should you participate in this activity, Amgen assumes no responsibility for any liability, damage or injury that may be caused by your own negligent and willful acts and omissions related to or arising from your participation in the activity. You agree to indemnify, defend and hold harmless Amgen, from any loss or liability whatsoever, including reasonable attorneys' fees, associated with or arising from your negligent acts or willful acts and omissions related to or arising from your participation in the activity. You also acknowledge that in the event of liability, damage or injury that Amgen assesses (in its sole discretion) as not caused by your own negligent and willful acts and omissions, you will only be covered to the maximum extent in accordance with Amgen’s policies. Amgen’s decision shall be final and binding on you and you hereby release, waive, relinquish, discharge from liability and covenant not to sue Amgen from any and all claims, demands, actions, suits, causes of action and/or liabilities, of whatever kind or nature, in law, equity or otherwise, related to or arising from your participation in the activity.</p></li><li><p>Immediate family members or guests of a regular full-time employee’s participation in the activity, whether or not supervised, is solely at their own risk and hereby release, waive, relinquish, discharge from liability and covenant not to sue ASM or any of ASM’s parent, subsidiary or affiliated entities, including but not limited to Amgen Inc., as well as their respective directors, officers, employees, representatives, independent contractors, insurers, attorneys and/or agents in their capacity as such or otherwise (the <strong>&quot;Releasees&quot;</strong>) from any and all claims, demands, actions, suits, causes of action and/or liabilities, of whatever kind or nature, in law, equity or otherwise, related to or arising from their participation in the activity including but not limited to any negligent act or omission by any of the Releasees and/or any accident, illness or injury incurred as a result of their participation in the activity, save where such accident, illness or injury is directly caused by the gross negligence or willful misconduct of ASM, ASM’s parent, subsidiary or affiliated entities, including but not limited to Amgen Inc., as well as their respective directors, officers, employees or representatives.</p></li></ol><p>Confidential Human Resources</p>"
+	}
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@go-labs-sg/rsvp",
-  "version": "0.6.1",
+  "version": "0.9.0",
   "description": "RSVP CLI for authorized event operations.",
   "type": "module",
   "exports": {},