@go-labs-sg/rsvp 1.9.0 → 1.10.0

package/README.md

@@ -861,6 +861,21 @@ 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.
 
+## Daily sign-ups
+
+`report signups` returns the same aggregate series as the web
+**Reports > Sign-ups** page: one count per response on the day it was first
+submitted, in the event time zone, split by current status (attending, payment
+pending or failed, waitlisted, not attending). Walk-ins, drafts, cancelled and
+archived responses are excluded; guests are not counted separately. The series stops at
+the registration close date once it has passed (falling back to the event end,
+then start), unless later responses extend it. It needs `report.aggregate` and
+returns counts only.
+
+```sh
+rsvp report signups --organization-id org_123 --event-id evt_123
+```
+
 ## Seat-change email presentation
 
 In an approved `event setup step update` for `REGISTRATION_RULES`,

package/dist/index.js

@@ -12446,6 +12446,12 @@ var commands = {
     scope: "event",
     summary: "Get event reporting overview (--organization-id --event-id; sensitive data acknowledgement required)."
   },
+  "report signups": {
+    effects: [],
+    operation: (api, input) => api.event.getSignupTrend.query(input),
+    scope: "event",
+    summary: "Get daily sign-up counts in the event time zone (--organization-id --event-id; aggregate counts only)."
+  },
   "user list": {
     effects: ["sensitive-data"],
     operation: (api, input) => api.user.list.query(input),

package/package.json

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