@go-labs-sg/rsvp 1.5.0 → 1.6.0

package/README.md

@@ -752,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.
 
@@ -775,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
 

package/dist/index.js

@@ -7957,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) => {
@@ -10145,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
@@ -12359,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"],
@@ -12564,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 (including senderName and a senderLocalPart+senderDomain address on a verified Resend sending domain), 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.5.0",
+  "version": "1.6.0",
   "description": "RSVP CLI for authorized event operations.",
   "type": "module",
   "main": "./dist/index.js",