Two things that were not in the original submission
Two captures from the current build, to visually show some of the improvements.
A room that runs as a sequence
The goal was "Dinner outdoors, then drinks nearby". The header now reads The Barn ยท somewhere for drinks NOW: a filled dot for the step the group already settled, a hollow ring for the one it is working on. The moment the organizer committed the dinner agreement, the room re-centred its search circle on The Barn and drew a fresh pool of bars around it. Same map, no reload, no second room.
The count block is honest about the new pool: 22 still work of 60, 9 of them likely, 12 unsure. The one seeded need for this step, wheelchair access, already shows what it costs at the bottom left: +47 places if it went optional.
Following one agent turn through the system
The { } drawer, expanded. The stream on the left is a causal graph across five lanes: page, agent, tool, HTTP, socket. Two WebMCP tool calls (sync_session, get_spatial_context) each connect to the HTTP request they caused. The selected row is the person asking their built-in agent to "Put The Barn forward for the group."
The inspector on the right shows what actually happened. The agent called propose_destination once, and the result is awaiting your approval; no change applied. The room's revision did not move. Behind the drawer you can see the review card that the turn produced, with the exact arguments and Approve change / Dismiss.
That is the security boundary added since submission, visible on the wire instead of asserted in a README: a model can suggest, only the owner's page can apply.
Log in or sign up for Devpost to join the conversation.