Epic: events and bookings by configuration, with Color Me Fun as the acceptance test

Events, registrations and bookings built by configuration, driven by an agent through the barako CLI (#801), with the rules held by barakoCMS rather than by a custom app.

**Acceptance test:** Color Me Fun 2026, the Rotary Club of Koronadal's colour run registration (arnelirobles/ColorMeFun). It is not migrating (#724); it is the bar. Simulated on 14 September 2026 against master, with every step graded against the code: https://claude.ai/code/artifact/05afda1a-6461-431d-aff0-50b30d3b0778

Most of what it needs is generic: any event, clinic, class or booking site has a public form, a status check, a capacity, a reference number and a confirmation email.

## 1. A visitor can register

- [ ] #720 Forms module
- [ ] #802 a file upload, an opening and closing date, and several steps on a public submission
- [ ] #811 verify an email field with a one-time code
- [ ] #810 fields required only when a condition holds (guardian under 18, shirt size for COMPETE)
- [ ] #803 a choice field type (entry type, shirt size, reasons)

## 2. The rules hold on the server

- [ ] #584 numbering: reference series and bib numbers
- [ ] #583 computed fields: the amount from entry type and settings
- [ ] #808 a floor on a counter under concurrent saves: shirt stock, participant cap
- [ ] #812 a token field, generated and never writable: the claim stub
- [ ] #578 header and lines: group batches

## 3. Organizers work the queue

- [ ] #809 a transition that requires fields: a reason to reject
- [ ] BaryoDev/barakoPress#26 operator blocks: queue, record, confirm and reject, bulk verify, scan
- [ ] BaryoDev/barakoPress#7 pages gated by role
- [ ] #813 a rate limit per form, CSV export of a filtered list, MFA required for a role

## 4. Runners hear back and check in

- [ ] #804 a public lookup by reference plus an identifier, named fields only, throttled
- [ ] #805 placeholders that follow a reference and loop over related entries: the batch summary
- [ ] #806 attach stored files to the Email action
- [ ] #807 render a field's value as a QR code
- [ ] #585 generated documents: reference slip, claim stub, printed forms
- [ ] #575 an action that produces a value for the next

## Done when

Claude Code, using only the barako CLI and barakoBrew, builds Color Me Fun on a tenant so that:

- a visitor registers with a verified email and a receipt, and cannot overdraw shirt stock or the cap;
- an organizer confirms or rejects with a reason, and the runner receives the matching email with a claim stub;
- a runner checks status by reference and last name and sees the claim stub only once kit release is open;
- no custom code is deployed, and any rule that still needed a module is listed here with why.

Start with the barako CLI and barakoBrew entry points, then review the linked child issues covering forms, server rules, organizer workflows, notifications, lookup, and documents. Done means the Color Me Fun acceptance test works on a tenant without custom code, and any remaining module dependency is listed with its reason.

Written by the indexing model from the issue text.