Second Pass — UI Notes

Commit is local nownew

The orange count in each guide row was inert — it told you which project was dirty and then made you use a global button that swept up everything. It is a menu now: Commit N Changes in Stellar, scoped to that guide's paths only.

One thing I did not let it swallow: changes under framework/ and categories/ belong to no guide. A purely per-guide commit would strand them silently, so the corpus chip names them — "12 uncommitted · 3 outside a guide" — with its own commit action.

The app says its own name

"Press Raven" existed only in the window title bar, so the sidebar opened on a bare Dashboard with nothing above it. There is now a header row with the logo and the name.

Export and New, at the topnew

Export (the share glyph) opens the export modal. The + holds New Seed and one entry per kind.

I also put a + on each kind heading, because with the taxonomy in place New Project and New Guide are genuinely different acts and a single global + said neither. The sheet now knows its kind: it offers only that kind's categories, titles itself accordingly, and skips the category picker entirely when the kind has just one (Game is the only project category, so asking was a click to dismiss).

The active tab is visiblebug

Cause above. onBand now falls through to the contrast-checked pole when its accent does not separate from the band it sits on — the machinery already existed for the masthead (onBandInk) and this reuses it. I also dropped inactive tabs from 0.85 to 0.55 opacity and made the active one heavier, so active and inactive are not two shades of the same white.

Ways In is no longer a menunew

You said it looked like system chrome, and it was: a stock macOS popup with a door glyph, in a toolbar whose whole job is artifact fidelity — sitting top-right while you work four hundred entries down.

It is now a strip anchored to the foot of the document, drawn entirely in the guide's resolved tokens (paper_raised, rule, accent), so it belongs to the page. Always in reach regardless of scroll. It hides in read mode, on frozen guides, and while a sculpting session owns the foot of the document.

I rejected putting it in the nav strip on its own terms: that band only renders when a guide has two or more sections, so a brand-new guide would have no doors at all — precisely when you need them most.

Each mini game states itself where its entries are

The roster at the top is the index; scroll into the third mini game's two hundred items and the heading was a bare name. Its mechanic and description now sit directly under the section header.

You can pick entries nownew

You were right that it did not exist. The navigator's list was bound to a single optional id, so the only scopes were "one entry" and "a whole group" — nothing in between.

It is a multi-select list now (⌘-click, ⇧-click). Picking one behaves exactly as before. Picking two or more raises a bar: Session…, Packet…, isolate-in-document, and clear.

The packet path already accepted an entry subset. The session path did not, and threading a scope through all five phase contexts would have been out of proportion — so the packet gains an explicit THE ENTRIES I'M ASKING ABOUT block that renders the picked entries in full and tells Claude the rest is context, not subject. It reuses PacketService.entryMarkdown rather than adding a second renderer that would drift.

Empty fields stop shoutingneeds you

Two halves. The app half is done; the corpus half is written, tested, and waiting — see below.

The app. Empty fields that are not required collapse into one quiet line: "2 optional fields empty — spots, near spots". Click it, or the ellipsis menu's Show Empty Optional Fields, to bring them back. It names what it hid rather than hiding it silently — silent omission is exactly the failure mode that buried your 87-entry rules bank.

The corpus. required has always existed on every field, and 9 of 226 fields in the whole corpus set it — none of Stellar's 77. So the app had nothing to believe. tools/declare-required.py reads requiredness off the exporter rather than off my opinion: a field is required when its builder subscripts it unguarded (e["situation"] — KeyError without it), optional when the builder guards it (e.get("spots", {}) — defined behaviour without it). It marks 31 fields across 8 mini games, and leaves tag-the-photo, the-streak and called-shot alone because nothing consumes them yet, so there is no evidence to read.

whiteboard required:  correct_positions, phase, rotation, verification
whiteboard optional:  near_positions, near_spots, provenance, spots, voice_source

The app opens where you left off

Last-opened guide, restored on launch. It lives in UserDefaults, not the corpus — the Prime Directive governs content, and which guide you had open is session state; delete the app and nothing is lost.

Restored on corpus load rather than on appear, because guides arrive asynchronously and an on-appear restore would run against an empty list and silently fall back to the dashboard. First run still opens on the dashboard.