Settings — by section

The console's Settings tab regrouped onto the product's own sections — Persona · FP · Chat · The app · Tools & games — the five the room2 map is built on, in the order the product is built. One card shape, one row shape, no paragraph under any row, and a word where there is no choice. Who sees what is a stop of its own, every row ending in a one-line sample of the thing it hides.

1 · What is contrived today

The live tab has nine headings that grew one feature at a time — Spend caps · Rooms · The turn · Room tools · Room language · Feedback · Seen · Experiments · Who sees what. They are not a taxonomy; they are the order things were added. Four faults follow from that:

1. The floor producer is in five places. Its on/off sits under Rooms, its manner (v1/v2) beside it, the silence door under The turn, the gesture guard under Experiments, the ratings that steer it under Feedback — and its model on another tab. Nobody reading the tab can tell what the FP is.
2. A paragraph under every row. Twelve rows carry a 60–120-word explanation in 11px mono — the war story, the env var, the rollback, the cost. The owner's rule for the Style Guide applies here too: the explanation lives on the design page, the row carries its name.
3. Two ways to save. Switches commit on change; the numbers have Save buttons; the grid has its own. The reader has to learn which is which.
4. A disabled switch for a pinned box. When an env var holds a setting, the tab shows a greyed switch plus a ⚠ sentence. The Models mock settled this already: a switch where it is a choice, a word where it is not.

The four rules of the regrouping

1. The product's five sections, in build order. The same five as the room2 index — Persona · FP · Chat · The app · Tools & games — with the same numbers. A setting sits in the section whose design page explains it. A section rail under the tab title, one chip per section; click to jump, and it follows the scroll. Who sees what rides the rail after a separator — a stop of its own, the way prices is on the Models tab.
2. One card, one row. A card is a topic with a Design › link in its head — the hop to the room2 page — and nothing else. A row is the label · a reach word · the control. The control is a switch, a number with its unit, or a checked radio; every row carries its call kind — the ledger's group.leaf, in the group's chart colour, the same key as Usage and Models (all kinds, grey, where a setting moves the whole ledger); the reach word is one of three — admins only · new chats · set by the box — on the row, or once on the card head when it covers the whole card; absent when none applies.
3. A word where there is no choice. A setting an env var holds shows on or off as a word with set by the box beside it — no greyed switch, no ⚠ sentence. A setting that has no switch at all (memory, the dream, the growth sweep) gets the same word-row, so the section is complete.
4. Everything saves on change. No Save button anywhere — a number commits when you leave the field, a grid cell when you tick it. One rule, said once, at the top.

2 · The tab

Classes from lib/admin.html where they exist (the card, the switch, the radio); the rail, the section head, the reach word, the word-row and the Design › link are the new pieces.

3 · The map — every setting, its card

Every control on the live tab, where it sits today, and where it goes. Three switches are dropped — no longer needed; three word-rows are added so the Persona section is not empty.

4 · What changes

• Nothing on the server. Every row posts to the endpoint it posts to today; the tab is a re-layout of one function in lib/admin.html. The caps dialog goes — two number fields in a row do what it did.
• The explanations move, they don't vanish. Each card's Design › link opens the room2 page that carries the full story — the floor producer, the seven steerings, the harness, deliberate first, the toolbox UI. Where a page is thin on a setting (the silence door, the 👍 cue, the verify tail), the paragraph being cut from the tab is pasted into that page in the same commit.
• The reach word replaces three kinds of small print. admins only for the five experiments; new chats for the two stamped at creation; set by the box wherever an env var holds the value — and then the control is a word, not a greyed switch.
• Save on change, everywhere. Numbers commit on blur or Enter and toast the server's answer, as the switches already do; the who-sees-what grid saves per cell. The three Save buttons and the grid's footer go.
• Three switches go outright. Convene auto-fire, fake convene and the Vibes feed were scaffolding for features that are finished — the switch goes, and its endpoint retires with it.
• Tabs become modules. The grid's「Tabs」group is renamed Modules — Studio, Vibes, Notes and Seen — and every grid row ends in a one-line sample of the thing it hides, so the reader never has to guess what「cache bar」looks like.
• The kind pill ties the three tabs together. Every settings row now names the call kind it moves, in the group's chart colour — read a bar on Usage, find the knob on Models, find the behaviour switch here, all under one key. The three setup beats (deliberate first · the coda · the verify tail) collapse to one「Game setup rhythm」switch, on by default — three endpoints stay, one switch drives them.
• Backup and Models stay their own tabs. Backup is an action, not a setting; Models is the ledger's eight, already mocked.
• Docs: this page flips to BUILT in the ship commit; console-redesign's Settings section gets a「superseded by」note.