Bernardo Magri
39c8b3e0eb
All checks were successful
Check / eval (push) Successful in 7m20s
Bernardo saw the Recovery labels ellipsize on a 2560x1440 external, which falsifies both halves of this item's model (width: 40% + Inter 11 → "only below ~1920, confirm on the Acer"): - text menus render through themes/<slug>/rofi.rasi, and boreal (his) + neon-glass pin `width: 620px` — fixed, so a wide panel buys nothing; the other seven use 40%. launcher.rasi's 780px is a red herring (it themes -show drun only). - the font is whatever that file sets — boreal GeistMono 11, summer/ kanagawa JetBrainsMono 14, nord/lumon/retro-82 13 — mostly MONOSPACE, much wider than the Inter the item measured. Only the generated theme follows fonts.ui. - so the modelled 40% + Inter 11 is shipped by no theme, and truncation is most theme x monitor pairs, not an edge case. Measured for boreal (9.33px/char off kitty at the same font/size, 518px room): 3 of 4 rows cut, "What changed" fits — "some of the submenus", exactly as reported. Names the decision instead of taking it: fitting the narrowest combo we ship (40% @ 1366 + JBMono 14) is ~39 chars, which cannot hold scope AND cost — so "just shorten the labels" would gut #111 for everyone on a big screen. Options: (a) width in `ch` so the window scales with the font (fixes the class, 9 theme files), (b) cost to a rofi -mesg line, (c) shorten and lose the hint. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Agent instructions + loop state
Everything an AI agent needs to work on Nomarchy, vendor-neutral and git-tracked. Protocol: LOOP.md. Entry point for every harness: repo-root AGENTS.md.
Instructions (how to work)
| File | Who writes | Role |
|---|---|---|
| LOOP.md | Human | One-iteration protocol (orient → pick → work → verify → commit → record) + the V0–V3 ladder |
| VERIFICATION.md | Human (agents propose) | Enforcement: preflight, honesty rules, visual protocol, hardware-blocked checks, reporting |
| DELEGATION.md | Human (agents propose) | Capability tiers, scout/runner roles, token economy, parallel fan-out |
| GOALS.md | Human (agents propose) | Pillars, quality bars, non-goals |
| CONVENTIONS.md | Human (agents propose) | How to write code/menu/state while shipping |
| THEME-DESIGN.md | Human (agents propose) | Theme/visual design instructions |
State (what's happening)
| File | Who writes | Role |
|---|---|---|
| BACKLOG.md | Both | Prioritized queue — only executable work list |
| JOURNAL.md | Agents | Append-only iteration log (read last 3–5 entries; older → JOURNAL-ARCHIVE.md) |
| MEMORY.md | Agents | Curated durable gotchas |
| HARDWARE-QUEUE.md | Agents append, human checks | On-hardware V3 tests only Bernardo can run |
Product / design docs (not a queue)
| File | Role |
|---|---|
| ../docs/VISION.md | v1.0 product themes — agents slice into BACKLOG PROPOSED |
| ../docs/ROADMAP.md | Design history + shipped log |
| ../docs/README.md | Full docs map |
Harness adapters (vendor-specific, thin)
Shared content never lives in an adapter — adapters only register/route into the files above, in whatever format their harness requires.
| Path | Harness | Role |
|---|---|---|
| ../AGENTS.md | any | Entry point (CLAUDE.md is a symlink to it) |
| ../.claude/settings.json | Claude Code | Tool permissions |
| ../.claude/agents/ | Claude Code | nomarchy-scout / nomarchy-runner role defs (contracts in DELEGATION.md) |
Do not put backlog items, vision text, or policy under an adapter directory — it is not shared with other agent runners.
Rules of thumb
- Execute from BACKLOG only (NOW → NEXT; never PROPOSED without human triage).
- Orient with GOALS + CONVENTIONS + MEMORY + last journal + BACKLOG; when the task is product-shaped, also read the relevant VISION §.
- Record lasting design in ROADMAP ✓ when something ships that future humans should know; delete the BACKLOG line.
- v1 branch is human-only — never advance from an agent session.