@go-labs-sg/rsvp 1.4.0 → 1.6.0

package/README.md

@@ -262,6 +262,14 @@ Replace illustrative IDs and revisions with current readback values. Deploy API
 policy enforcement before clients; an old API does not understand this field.
 No authentication, consent flags, command names, or credential protocol changes.
 
+### Registration-flow choice labels
+
+`SINGLE_SELECT`, `VISUAL_SINGLE_SELECT` and `MULTI_SELECT` choices accept a
+trimmed `label` of 1–500 characters, so a required single-choice `MULTI_SELECT`
+can show a full-sentence declaration beside its tick box. Choice `value` stays a
+stable machine value of 1–160 characters. Older APIs reject labels over 160
+characters; deploy the API before saving longer labels.
+
 ### Registration-flow date-limit messages
 
 `DATE` and `DATETIME` custom fields accept optional
@@ -744,8 +752,9 @@ High-impact payment and retention commands remain protected by their matching fi
 
 ## Registration master list export
 
-`export request` queues the single **Registration master list** Excel workbook
-(one **Master List** sheet; question columns follow the event's form). The
+`export request` queues the **Registration master list** Excel workbook
+(**Master List** by default; optional registration/attendance tabs follow event
+settings and permissions; question columns follow the event's form). The
 payload is `organizationId`, `eventId` and an audit `reason`; the old `dataset`,
 `format` and `filters` fields are ignored. See the RSVP app README for columns.
 
@@ -767,8 +776,40 @@ population. Non-operational statuses remain excluded, and permissions, payment
 gates, duplicate protection, and undo behavior are unchanged. The web panel's
 realtime connection and manual refresh controls do not add a CLI subscription.
 
+Set `registrationMasterList.includeAttendanceSheets: true` with an approved
+`event setup step update` (`section: "REGISTRATION_RULES"`) to add response-based
+**Attending**, **Not attending** (explicit declines only), and **All** tabs,
+plus the retained **Registered**, **Not Registered**, **Attended** and
+**Not Attended** views. It defaults off. All matches every Master List person,
+including guests and nonrespondents; attending/declined subsets use canonical
+completed responses and never treat nonresponse as a decline.
+Registered includes attending, legacy submitted and declined completed responses;
+actual check-in tabs include only attending/legacy-submitted people and require
+`check-in.view`. An undone check-in returns a person to Not Attended. Preserve
+the other current master-list settings when editing this object.
+
 Deploy matching API and export-worker versions together; an old worker would build the retired
-registration-records report for master-list jobs.
+registration-records report for master-list jobs. See the
+[follow-up contract](../../../apps/rsvp/reporting-follow-up.md) for exact tab
+populations, worker-order/rollback gates and the separate later post-draw merge.
+
+## Seat-change email presentation
+
+In an approved `event setup step update` for `REGISTRATION_RULES`,
+`seatChangeNotification.includeTablemates` controls saved same-table display
+names (default off), and `seatChangeNotification.includeFloorPlanImage` controls
+the inline highlighted floor-plan image (default on). Both accept explicit
+`true` or `false` independently. Preserve the current notification subject/body,
+enabled/automatic state, other registration rules and expected configuration
+version when editing. Omitting either property preserves its stored value.
+
+Explicit event presentation values apply to manual and automatic seat-change
+notices, overriding saved-form presentation only; omissions inherit the form.
+These switches do not enable notices, change seats or send/resend email. With
+the image off, text assignments remain and the worker skips map/image work.
+Deploy compatible workers before relying on the switches; old workers do not
+honor the image off-switch. Tablemate-name disclosure still needs privacy
+approval. The web exposes both switches in Registration rules.
 
 ## Seating updates
 
@@ -911,6 +952,49 @@ rsvp people registration update \
   --payload '{"organizationId":"org_123","eventId":"evt_123","registrationId":"reg_123","expectedVersion":4,"reason":"Moved to finance table","seats":[{"registrationAttendeeId":"att_1","seatId":"seat_9"},{"registrationAttendeeId":"att_2","seatId":"seat_2"}],"seatChangeNotice":{"idempotencyKey":"4d68a320-013d-43c7-bfcc-d1126827d8c5"}}'
 ```
 
+### Archive or cancel registrations
+
+`people registration archive` and `people registration cancel` forward the same
+permissioned, audited `event.bulkManageRegistrations` operation as the web app.
+Both require server-side `rsvp.manage` permission and `--allow-state-change`;
+`--target` must match the payload's **event ID**, not a registration ID.
+
+Supply `organizationId`, `eventId`, an audit `reason` (3–500 characters after
+trimming), and 1–100 unique `registrations`, each with `id` and its current
+positive-integer `expectedVersion`. Get revisions from `people registration list`
+or `people registration edit get`. The command sets `action` to `ARCHIVE` or
+`CANCEL` when omitted; explicitly supplying any other action is rejected. Missing
+or invalid fields, duplicate IDs and oversized batches fail before dispatch.
+Stale revisions are checked by the server; refresh and review before retrying.
+
+```sh
+rsvp people registration archive \
+  --allow-state-change --target evt_123 \
+  --payload '{"organizationId":"org_123","eventId":"evt_123","reason":"Remove refunded test registrations","registrations":[{"id":"reg_123","expectedVersion":6},{"id":"reg_456","expectedVersion":2}]}'
+
+rsvp people registration cancel \
+  --allow-state-change --target evt_123 \
+  --payload '{"organizationId":"org_123","eventId":"evt_123","reason":"Participant withdrew","registrations":[{"id":"reg_789","expectedVersion":3}]}'
+```
+
+- **Archive** sets `archivedAt` and removes the registrations from default lists
+  and exports. It also cancels active registrations through the normal release
+  path; this is not merely hiding an attending registration.
+- **Cancel** cancels active registrations without changing `archivedAt`. Cancelled
+  registrations remain visible unless already archived.
+- Both release consumed event capacity, active seat bookings and holds, cancel
+  session selections and waiting/offered waitlist entries, and run the existing
+  event/session waitlist maintenance. Released places may generate waitlist
+  offers and **emails to other participants**; neither command sends a
+  cancellation email to the affected registrants. No `--allow-email` flag is
+  required by these commands' existing `state-change` contract.
+- Neither command automatically refunds a payment or deletes records. Payment,
+  refund and audit history are retained. Pending checkouts linked to a provider,
+  processing payments and payments requiring review must be reconciled first;
+  unlinked pending payment attempts are cancelled by the existing server logic.
+- Use **Unarchive** below for archive visibility/fresh-response recovery, or
+  **Restore** for attending recovery. Unarchive does not undo cancellation.
+
 ### Unarchive for a fresh response versus attending Restore
 
 `people registration unarchive` forwards the permissioned, audited
@@ -1011,6 +1095,25 @@ previous effects.
 
 Optional `registrationEmail` and `registrationMasterList` presentation settings
 are also written through `REGISTRATION_RULES`; omitted settings are preserved.
+
+### Registration email sender
+
+Confirmation and seat-change emails send from the server default
+(`RSVP_EMAIL_FROM`) unless the event sets a sender in `registrationEmail`:
+
+- `senderName` changes only the display name.
+- `senderLocalPart` and `senderDomain` (set both or neither) change the address,
+  for example `"senderLocalPart": "nelbd", "senderDomain": "getout.sg"` sends
+  from `"NELBD Quest" <nelbd@getout.sg>`. `senderDomain` must be a Resend domain
+  that is verified with sending enabled when the update is saved; list them with
+  `rsvp event email sender-domains`. Invalid local parts, a missing half of the
+  pair or an unverified domain are rejected.
+
+`registrationEmail` replaces the whole presentation object, so read the current
+event first and resend every key you want to keep. Reply-to and support email
+are unchanged. If a saved domain is later unverified in Resend, those emails
+fail and are recorded as failed deliveries; they never fall back silently to a
+different sender. Fix the domain or remove the address fields to resume.
 See `examples/amgen-rsvp-copy/registration-presentation-patch.json` and its README
 for a reviewed activation fragment, output-key semantics, receipt/header behavior
 and the separate deployment/configuration/live-send approval gates. No event

package/dist/index.js

@@ -7726,11 +7726,13 @@ var flowBlockBaseShape = {
   title: string2().trim().min(1).max(240).optional(),
   visibleWhen: eventFlowConditionGroupSchema.optional()
 };
+var maxEventFlowChoiceLabelLength = 500;
+var maxEventFlowChoiceValueLength = 160;
 var customFieldChoiceSchema = object({
   assetId: eventFlowEntityIdSchema.optional(),
   description: string2().trim().max(500).optional(),
-  label: string2().trim().min(1).max(160),
-  value: string2().trim().min(1).max(160)
+  label: string2().trim().min(1).max(maxEventFlowChoiceLabelLength),
+  value: string2().trim().min(1).max(maxEventFlowChoiceValueLength)
 });
 var maxEventFlowDateBoundMessageLength = 500;
 var eventFlowDateBoundMessageSchema = string2().trim().min(1).max(maxEventFlowDateBoundMessageLength);
@@ -7955,6 +7957,8 @@ var defaultEventSeatChangeNotification = {
 var eventSeatChangeNotificationSchema = object({
   body: string2().trim().max(1e4).default(""),
   automatic: boolean2().optional(),
+  includeTablemates: boolean2().optional(),
+  includeFloorPlanImage: boolean2().optional(),
   enabled: boolean2().default(false),
   subject: string2().trim().max(240).default("")
 }).superRefine((notification, ctx) => {
@@ -10109,10 +10113,17 @@ var PUBLIC_EVENT_VALIDATED_FONT_FAMILIES = [
   "Zilla Slab Highlight"
 ];
 
+// ../validators/src/email-sender.ts
+var emailSenderLocalPartSchema = string2().trim().max(64, "Sender address must be 64 characters or fewer").regex(/^(?!.*\.\.)[a-z\d](?:[a-z\d._+-]{0,62}[a-z\d])?$/i, "Enter a valid sender address before @");
+var emailSenderDomainSchema = string2().trim().toLowerCase().regex(/^(?:[a-z\d](?:[a-z\d-]{0,61}[a-z\d])?\.)+[a-z]{2,63}$/, "Select a valid sending domain");
+var EMAIL_SENDER_PAIR_MESSAGE = "Choose a sender address and domain together";
+
 // ../validators/src/registration-email-presentation.ts
 var registrationEmailPresentationSchema = strictObject({
   layout: _enum(["DEFAULT", "GROUPED"]).default("DEFAULT"),
   senderName: string2().trim().min(1).max(120).regex(/^[^<>\r\n]+$/).optional(),
+  senderLocalPart: emailSenderLocalPartSchema.optional(),
+  senderDomain: emailSenderDomainSchema.optional(),
   introText: string2().trim().min(1).max(1e4).optional(),
   menuDetailOutputKeys: array(string2().trim().min(1).max(120)).max(100).default([]),
   submittedConsentOutputKeys: array(string2().trim().min(1).max(120)).max(100).default([]),
@@ -10120,6 +10131,13 @@ var registrationEmailPresentationSchema = strictObject({
   useResubmissionFooter: boolean2().default(false),
   supportEmail: email2().optional(),
   showLuckyDrawId: boolean2().optional()
+}).superRefine((value, ctx) => {
+  if (Boolean(value.senderLocalPart) !== Boolean(value.senderDomain))
+    ctx.addIssue({
+      code: "custom",
+      message: EMAIL_SENDER_PAIR_MESSAGE,
+      path: [value.senderDomain ? "senderLocalPart" : "senderDomain"]
+    });
 });
 
 // ../validators/src/registration-master-list-presentation.ts
@@ -10129,7 +10147,8 @@ var outputKeysSchema = array(string2().min(1).max(160).regex(/^[A-Za-z][A-Za-z0-
 var eventRegistrationMasterListSchema = object({
   omittedOutputKeys: outputKeysSchema.default([]),
   finalOutputKeys: outputKeysSchema.default([]),
-  showEligibilityCutoffInHeading: boolean2().default(false)
+  showEligibilityCutoffInHeading: boolean2().default(false),
+  includeAttendanceSheets: boolean2().default(false)
 }).strict().refine((config) => !config.finalOutputKeys.some((key) => config.omittedOutputKeys.includes(key)), { message: "Omitted output keys cannot also be final output keys" });
 
 // ../validators/src/event.ts
@@ -10734,8 +10753,8 @@ var emailCampaignDraftFieldsSchema = object({
   audienceMode: _enum(["SEGMENT", "SELECTED"]).optional(),
   selectedInviteeIds: array(string2().min(1)).max(1e4).optional(),
   fromName: string2().trim().max(120, "From name must be 120 characters or fewer").regex(/^[^\r\n<>]*$/, "From name contains unsupported characters").optional(),
-  fromSubDomain: string2().trim().max(64, "Sender address must be 64 characters or fewer").regex(/^(?!.*\.\.)[a-z\d](?:[a-z\d._+-]{0,62}[a-z\d])?$/i, "Enter a valid sender address before @").optional(),
-  fromDomain: string2().trim().toLowerCase().regex(/^(?:[a-z\d](?:[a-z\d-]{0,61}[a-z\d])?\.)+[a-z]{2,63}$/, "Select a valid sending domain").optional(),
+  fromSubDomain: emailSenderLocalPartSchema.optional(),
+  fromDomain: emailSenderDomainSchema.optional(),
   html: string2().trim().min(1, "Email body is required").max(1e5, "Email body is too long"),
   name: string2().trim().min(1, "Campaign name is required").max(160, "Campaign name must be 160 characters or fewer"),
   previewText: string2().trim().max(240, "Preview text must be 240 characters or fewer").optional(),
@@ -10753,7 +10772,7 @@ var validateSelectedCampaignAudience = (input, ctx) => {
     ctx.addIssue({
       code: "custom",
       path: [input.fromDomain ? "fromSubDomain" : "fromDomain"],
-      message: "Choose a sender address and domain together"
+      message: EMAIL_SENDER_PAIR_MESSAGE
     });
 };
 var createEmailCampaignInputSchema = organizationEventByIdInputSchema.extend(emailCampaignDraftFieldsSchema.shape).superRefine(validateSelectedCampaignAudience);
@@ -12343,7 +12362,7 @@ var commands = {
     effects: ["sensitive-data", "state-change"],
     operation: (api, input) => api.export.requestExport.mutate(input),
     payloadOnly: true,
-    summary: "Request the registration master list XLSX (--payload JSON: eventId, organizationId, reason)."
+    summary: "Request the event-configured master list XLSX with optional attendance tabs (--payload JSON: eventId, organizationId, reason)."
   },
   "export list": {
     effects: ["sensitive-data"],
@@ -12393,18 +12412,21 @@ var commands = {
     summary: "Update a user's global role (--payload JSON)."
   }
 };
-var unarchiveRegistrationsInputSchema = bulkManageRegistrationsInputSchema.safeExtend({
-  action: bulkManageRegistrationsInputSchema.shape.action.extract([
-    "RESTORE"
-  ])
-});
-var parseUnarchiveRegistrationsInput = (input) => {
+var parseRegistrationManagementInput = (input, expectedAction) => {
+  const inputSchema = bulkManageRegistrationsInputSchema.safeExtend({
+    action: bulkManageRegistrationsInputSchema.shape.action.extract([
+      expectedAction
+    ])
+  });
   const action = input ? Reflect.get(input, "action") : undefined;
-  const parsed = unarchiveRegistrationsInputSchema.safeParse(input ? { ...input, action: action === undefined ? "RESTORE" : action } : input);
+  const parsed = inputSchema.safeParse(input ? { ...input, action: action === undefined ? expectedAction : action } : input);
   if (!parsed.success)
     throw new CliUsageError(parsed.error.issues.map((issue) => `${issue.path.join(".")}: ${issue.message}`).join("; "));
   return parsed.data;
 };
+var parseArchiveRegistrationsInput = (input) => parseRegistrationManagementInput(input, "ARCHIVE");
+var parseCancelRegistrationsInput = (input) => parseRegistrationManagementInput(input, "CANCEL");
+var parseUnarchiveRegistrationsInput = (input) => parseRegistrationManagementInput(input, "RESTORE");
 var payloadCommand = (operation, summary, effects = [], targetKey) => ({
   effects,
   operation,
@@ -12491,6 +12513,7 @@ Object.assign(commands, {
   "event seating table delete": payloadCommand((api, input) => api.event.deleteSeatTable.mutate(input), "Delete a seating table (--payload JSON).", ["delete", "state-change"]),
   "event seating layout update": payloadCommand((api, input) => api.event.updateSeatTableLayout.mutate(input), "Update the seating layout and floor plan (--payload JSON).", ["state-change"], "eventId"),
   "event seating table update": payloadCommand((api, input) => api.event.updateSeatTable.mutate(input), "Update a seating table (--payload JSON).", ["delete", "state-change"], "tableId"),
+  "event email sender-domains": eventScopeQueryCommand((api, input) => api.event.getEmailSenderDomains.query(input), "List verified Resend sending domains for campaign and registration email sender addresses."),
   "event audience-tier list": eventScopeQueryCommand((api, input) => api.event.listAudienceTiers.query(input), "List event audience tiers and assignment counts."),
   "event audience-tier create": payloadCommand((api, input) => api.event.createAudienceTier.mutate(input), "Create an event audience tier (--payload JSON).", ["state-change"], "eventId"),
   "event audience-tier update": payloadCommand((api, input) => api.event.updateAudienceTier.mutate(input), "Update an event audience tier (--payload JSON).", ["state-change"], "tierId"),
@@ -12523,6 +12546,14 @@ Object.assign(commands, {
       { effect: "email", whenPayloadField: "seatChangeNotice" }
     ]
   },
+  "people registration archive": {
+    ...payloadCommand((api, input) => api.event.bulkManageRegistrations.mutate(parseArchiveRegistrationsInput(input)), "Archive up to 100 unique registrations with expectedVersion and reason (3\u2013500 characters); action defaults to ARCHIVE and other actions are rejected. Requires rsvp.manage; target the eventId. Cancels active registrations, releases capacity, seats and holds, cancels session selections and waitlist entries/offers, and hides archived rows from default lists/exports. Unresolved checkouts must be reconciled first; no automatic refund. Not a delete: payment, refund and audit history remain. No cancellation email; released places may trigger waitlist-offer emails (--payload JSON).", ["state-change"], "eventId"),
+    validateInput: parseArchiveRegistrationsInput
+  },
+  "people registration cancel": {
+    ...payloadCommand((api, input) => api.event.bulkManageRegistrations.mutate(parseCancelRegistrationsInput(input)), "Cancel up to 100 unique registrations with expectedVersion and reason (3\u2013500 characters); action defaults to CANCEL and other actions are rejected. Requires rsvp.manage; target the eventId. Cancels active registrations, releases capacity, seats and holds, and cancels session selections and waitlist entries/offers without changing archive visibility. Unresolved checkouts must be reconciled first; no automatic refund. Not a delete: payment, refund and audit history remain. No cancellation email; released places may trigger waitlist-offer emails (--payload JSON).", ["state-change"], "eventId"),
+    validateInput: parseCancelRegistrationsInput
+  },
   "people registration unarchive": {
     ...payloadCommand((api, input) => api.event.bulkManageRegistrations.mutate(parseUnarchiveRegistrationsInput(input)), "Unarchive up to 100 unique registrations with expectedVersion and reason; action defaults to RESTORE and other actions are rejected. Target the eventId. Eligible cancelled nonattending invitees can submit afresh; historical registration, payment and QR are not reinstated. Fresh submissions use normal checks and new payment/credentials; attending recovery uses people registration restore (--payload JSON).", ["state-change"], "eventId"),
     validateInput: parseUnarchiveRegistrationsInput
@@ -12536,7 +12567,7 @@ Object.assign(commands, {
   "event mine list": payloadCommand((api, input) => api.event.listMyEvents.query(input), "List the caller's events (--payload JSON)."),
   "event reminder list": payloadCommand((api, input) => api.event.listReminderSegments.query(input), "List reminder segments (--payload JSON).", ["sensitive-data"]),
   "event rsvp submit": payloadCommand((api, input) => api.event.submitRsvp.mutate(input), "Submit the caller's registration (--payload JSON).", ["sensitive-data", "state-change"]),
-  "event setup step update": payloadCommand((api, input) => api.event.updateSetupStep.mutate(input), "Update one revision-checked event setup step (--payload JSON). REGISTRATION_RULES accepts registrationEmail presentation, registrationMasterList output-key ordering/omissions and seatChangeNotification automatic policy; omitted settings are preserved.", ["state-change"]),
+  "event setup step update": payloadCommand((api, input) => api.event.updateSetupStep.mutate(input), "Update one revision-checked event setup step (--payload JSON). REGISTRATION_RULES accepts registrationEmail presentation (including senderName and a senderLocalPart+senderDomain address on a verified Resend sending domain), registrationMasterList output-key ordering/omissions and includeAttendanceSheets, and seatChangeNotification automatic/includeTablemates/includeFloorPlanImage policy (tablemate names default off; floor-plan image defaults on); omitted settings are preserved.", ["state-change"]),
   "event page update": payloadCommand((api, input) => api.event.updateSetupStep.mutate({
     ...input,
     section: "DETAILS_PAGE"

package/examples/amgen-rsvp-copy/README.md

@@ -145,6 +145,33 @@ to events without automatic notices; the flag grants approval but does not
 itself enable sending. Non-seating profile/menu updates and saving or discarding
 a draft do not acquire an email effect.
 
+## Follow-up reporting and tablemates (#1657)
+
+The optional workbook tabs (`registrationMasterList.includeAttendanceSheets`)
+and tablemate display names (`seatChangeNotification.includeTablemates`) are
+off by default. The existing example fragment intentionally does not activate
+them. Preserve the full current configuration and obtain event privacy approval
+before opting in. Clients omitting `includeTablemates` retain the stored value;
+explicit `false` disables it. See the
+[generic follow-up contract](../../../../../apps/rsvp/reporting-follow-up.md)
+for exact tab populations and delivery privacy boundaries. The web also exposes
+independent **Include tablemate names** and **Include floor-plan image** switches.
+The latter is `seatChangeNotification.includeFloorPlanImage` (default on; false
+omits map loading, image generation and attachment while retaining text seats).
+Explicit current-event presentation values apply to manual and automatic notices
+without changing notice enablement or copy. Deploy all email workers before
+relying on the image off-switch. Post-draw results
+will later merge the RSVP export with the Event Tech lucky-draw export; this
+change does not infer winners from eligibility or create result placeholders.
+
+**Worker-order warning:** upgrade/fence all email workers before enabling
+automatic policy for historical forms. An old worker can skip a new notice
+using old saved-form settings and mark it complete. Deploy matching export
+workers before requesting optional tabs as well. For rollback, pause/fence
+producers and workers, disable the new policies with a compatible API after
+approval, and reconcile queued/in-flight messages before old workers consume
+them. Never automatically resend skipped/completed jobs.
+
 Production deployment, event configuration writes, live submissions/reseating,
 export jobs, resends and any real provider send require explicit approval and
 readback. Local HTML/XLSX and synthetic browser checks are not live acceptance.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@go-labs-sg/rsvp",
-  "version": "1.4.0",
+  "version": "1.6.0",
   "description": "RSVP CLI for authorized event operations.",
   "type": "module",
   "main": "./dist/index.js",