docs: VISION for v1.0 + clarify docs/ vs agent/ vs .claude

Add docs/VISION.md (product themes, v1.0 bar, agent slice hints) and
README maps under docs/ and agent/. Point ROADMAP, BACKLOG, LOOP,
CLAUDE, HARDWARE, and the root README at the split: VISION = intent,
BACKLOG = executable queue, ROADMAP = design history, .claude = harness
only. Mark v1.0 track in BACKLOG PROPOSED for human triage.

docs/ROADMAP.md

@@ -1,15 +1,20 @@
 # Roadmap & changelog
 
-Forward-looking plans, plus a running log of shipped fixes (the
-"Known issues & follow-ups" section). Split out of the README so that
-stays a focused entry point — what Nomarchy is, how to install it, and
-how to override it. Items marked ✓ are shipped.
+Design/decision records and a running log of shipped work (items marked
+✓). Split out of the README so that stays a focused entry point.
 
-> **The live, prioritized queue now lives in [`agent/BACKLOG.md`](../agent/BACKLOG.md)**
-> (part of the autonomous-agent loop, `agent/LOOP.md`). This file remains
-> the detailed design/decision record and the shipped log — backlog items
-> reference it as "ROADMAP § <item>". When a backlog item ships, its
-> lasting design notes get a ✓ entry here.
+> **Where to look**
+>
+> | Need | File |
+> |------|------|
+> | Product themes toward **v1.0** (not a queue) | [`docs/VISION.md`](VISION.md) |
+> | **What agents execute next** | [`agent/BACKLOG.md`](../agent/BACKLOG.md) |
+> | Docs map | [`docs/README.md`](README.md) |
+> | Agent loop protocol | [`agent/LOOP.md`](../agent/LOOP.md) |
+>
+> Backlog items may reference this file as **ROADMAP § \<item\>**. When
+> something ships, lasting design notes get a ✓ entry here; the BACKLOG
+> line is deleted.
 
 ## Roadmap
 - **Menu system** (apps launcher + theme switching + system actions), built