After the first pingl flow worked live, the next pass was about product shape: make the desktop pending page and mobile action page feel like a clear RABS login authorisation experience rather than a raw technical test.
That refinement matters because this flow sits directly in the login path. The user needs to understand what is happening, why the phone is involved, and what approving the request does.
Type 2 agents -- Reggie and Henry -- run on remote VMs under OpenClaw, and OpenClaw publishes a new minor release roughly every three days. Each release tends to add, rename, or restructure config keys. If you tried to keep a hand-rolled admin page in sync with that, you would lose. The Type 2 Agent CONFIG page in RABS solves it the only way that scales: it does not know about specific settings at all. Each time it loads, it asks each VM "what is your config schema right now?", walks the answer, and renders a row for every settable variable -- titles, descriptions, types, validation hints, and current values, all the way down. When OpenClaw 2026.4.30 adds a new field next week, the page just shows it. No code change, no deploy. That's the design intent and tonight we made it actually work end-to-end.
The Care Profile tab on the Participant page has been completely rewritten. Previously it dumped raw JSON for most data types and had broken tables for medications and schedules. Now every category renders in a purpose-built format with collapsible sections, condition flags, and document downloads.
A housekeeping session that tackled three related problems: an unreadable build output, recurring dark-theme colour bugs, and seven specific UI issues across the forum, messenger, and user tasks pages. The build went from 821 warning lines to a clean output, and a colour system was created to prevent the theme bugs from recurring.
April 25 did not look like a single product sprint. It looked like Brett turning the project back on itself and asking whether several recent stories were actually true. That meant reviewing the Type 2 agent runner architecture, re-reading recent blog posts for continuity, checking whether the profile review had gotten the risks right, and cleaning up a few smaller UI bugs that had surfaced after broader launches.