Spun out of PR #72 review (OverviewPane.tsx).
The Overview almanac used to surface repo.dirty as a "(uncommitted changes)" marker, but the city itself doesn't visualize dirty/uncommitted state — so the marker was reporting something the world can't show. Removed it in #72.
Question to explore: should the city render uncommitted changes at all, and how? Ideas:
- A subtle highlight/outline on buildings whose file is dirty (modified-but-uncommitted).
- A HEAD-state indicator (e.g. the island/sky tinted while the working tree is dirty).
- Surface dirty files in a dedicated almanac/section once the world supports it.
If we add a visual encoding, the almanac can resurface the dirty signal (and it'd be earned, not a dangling stat). Until then there's nothing for it to point at.
Backend already exposes repo.dirty (and the signature includes a dirty bit), so the data is available; this is a rendering/UX exploration.
Spun out of PR #72 review (OverviewPane.tsx).
The Overview almanac used to surface
repo.dirtyas a "(uncommitted changes)" marker, but the city itself doesn't visualize dirty/uncommitted state — so the marker was reporting something the world can't show. Removed it in #72.Question to explore: should the city render uncommitted changes at all, and how? Ideas:
If we add a visual encoding, the almanac can resurface the dirty signal (and it'd be earned, not a dangling stat). Until then there's nothing for it to point at.
Backend already exposes
repo.dirty(and the signature includes a dirty bit), so the data is available; this is a rendering/UX exploration.