Generated reports

Happy path

1. Organizer navigates to the report center.

   From the admin shell, Reports section. Lists the organizer's recent jobs with status pills (queued / running / completed / failed / expired) and timestamps.

2. Click "Generate new report" and pick a report type from the catalog.

   Catalog shows: Guest list summary (EF-087), Activity log (EF-088), Email deliverability (EF-089), Graphical check-in (EF-090), Specialized ticketing reports (EF-091), and the in-scope-for-this-branch generic reports (attendance, registration timeline, sponsor lead export, ticket-block utilization).

3. Configure the report.

   Modal asks for parameters specific to the report type: event, date range, format (CSV / PDF), recipients for email notification. Submit.

4. Job is queued.

   UI immediately shows the new job in the list with status "queued." A subtle progress indicator. The organizer can leave the page; the job continues in the background.

5. Job completes (async, typically 5-60 seconds).

   When the organizer returns to the page, status pill is "completed" with a download button. If they configured email notification, an email arrives via Cloudflare Email Sending (EF-051) with a signed download link.

6. Click download.

   Signed URL fetches the artifact from R2. Browser starts the download. The job's "last downloaded" timestamp updates server-side for audit.

Failure modes

Edge cases

Page evaluation

Acceptance signals

• POST /v1/admin/events/:eventId/reports/jobs returns 201 with a job_id.
• D1 row exists in event_report_jobs with the submitted type + params + organizer's id as requested_by.
• Job list endpoint is paginated (page/limit/total/hasMore).
• Completed job has at least one row in event_report_job_artifacts with a non-null r2_key.
• Signed download URL is keyed off REPORT_DOWNLOAD_SIGNING_SECRET and includes a TTL parameter.
• Notification email queued via notification_outbox (per EF-051) when notify_emails was provided.
• Sweeper marks 30+ day artifacts as expired AND deletes the R2 object.
• document.title for the report center matches "Reports · <workspace>".
• No console errors at severity ≥ warn.

Stable test attributes

Branch-specific only; trunk and component attributes inherited.

Visibility teeth. Each attribute must be present AND effectively visible when the relevant state is active.

Agent test plan

- report-center-renders: navigate to /admin/events/${fixture.eventId}/reports, assert report-center visible AND generate-report-cta interactive
- report-jobs-paginated: assert report-jobs-pagination visible AND ui-form pagination response shape
- generate-report-flow: click generate-report-cta, pick a type, fill params, submit, assert API POST returns 201 AND new report-job-row visible with status pill = "queued"
- job-completes: stub job runner to complete in 2s, assert status pill transitions to "completed" AND report-job-download-cta visible
- download-with-signed-url: click report-job-download-cta, assert signed URL fetched (path matches /v1/admin/.../reports/jobs/[a-z0-9]+/download)
- job-stuck-note: stub job to remain queued, advance clock 6 minutes, assert report-job-stuck-note visible
- job-failed-with-reason: stub job to fail with reason "Dataset too large", assert report-job-status-pill = "failed" AND report-job-failure-reason visible AND report-job-retry-cta visible
- job-retry-creates-new-job: click retry, assert API POST creates new job with same params
- expired-link-page: navigate to a deliberately-expired signed URL, assert expired-download-page visible AND expired-download-regenerate-cta visible
- expired-link-regenerate: click regenerate, assert new signed URL produced AND download initiates
- swept-artifact-distinct-state: stub artifact deletion, click download on a 31-day-old job, assert expired (not "not found") UI
- two-organizers-distinct-jobs: simulate two parallel POSTs from different users, assert two distinct job rows
- large-dataset-failure: stub job to fail with "exceeded 50MB" reason, assert report-job-failure-reason text matches "narrower date range"
- email-bounce-indicator: stub email-event for the notification to bounce, assert report-job-bounce-indicator visible on the job row
- cancel-running-job: click cancel on a running job, assert status transitions to "cancelled" within 5s
- cancel-too-late: cancel a job that completes during cancellation, assert UI states "Cancellation requested — may complete anyway" OR final status reflects completion
- permission-gated-catalog: log in as read-only user, assert audit-log type absent from report-type-catalog
- permission-deep-link: navigate directly to /admin/reports/new?type=audit-log as read-only user, assert permission-required-page visible
- list-survives-logout: create job, log out, log back in, assert job still in list with current status