chore: ratchet CodeScene thresholds to 9.45/9.29

Previously, clicking a suggested property slot (Status, Date, URL) would add
an empty property to frontmatter but fail to open the editor. This was due
to a race condition where:

1. handleSuggestedAdd() called onAddProperty() which is async
2. The useEffect tried to detect when the property appeared in frontmatter
3. But frontmatter updates asynchronously after onAddProperty resolves
4. By the time frontmatter is updated, the useEffect had already run

The fix is to directly set the editing key immediately when clicking a
suggested slot, rather than relying on the useEffect to detect the property
being added. This is more reliable because we know we're adding the property
- we don't need to wait for it to appear in frontmatter.

.codescene-thresholds

@@ -1,2 +1,2 @@
-HOTSPOT_THRESHOLD=9.33
-AVERAGE_THRESHOLD=9.27
+HOTSPOT_THRESHOLD=9.45
+AVERAGE_THRESHOLD=9.29

CLAUDE.md

@@ -10,6 +10,8 @@
 
 Run `/laputa-next-task` — fetches next task (To Rework first, then Open), moves to In Progress, returns full description.
 
+**Before writing a single line of code:** run `mcp__codescene__code_health_score` to check the current codebase health against `.codescene-thresholds`. If the score is already below the threshold, **stop and refactor first** — find the worst files with the MCP, improve them, commit, then start the task. Never start feature work on a codebase that is already below the gate.
+
 - Read task description and all comments fully
 - For To Rework: the ❌ QA failed comment tells you exactly what to fix
 - Check `docs/adr/` for relevant architecture decisions before structural choices
@@ -45,7 +47,15 @@ bash ~/.openclaw/skills/laputa-qa/scripts/screenshot.sh /tmp/qa-native.png
 
 Use `osascript` for keyboard interactions. Write result as Todoist comment (✅ or ❌). **⚠️ WKWebView:** `osascript keystroke` blocked inside editor — rely on Playwright for text input features.
 
-After both phases pass, run `/laputa-done <task_id>` → moves to In Review, notifies Brian, self-dispatches next task.
+After both phases pass, add a **completion comment** to the Todoist task before running `/laputa-done`. The comment must include:
+- What was implemented (1–2 lines)
+- QA: what was tested and how (Playwright / native screenshot / osascript)
+- Refactoring: any files refactored to meet the CodeScene gate (or "none needed")
+- ADRs: any new/updated ADRs (or "none")
+- Docs: any updated docs (ARCHITECTURE.md, ABSTRACTIONS.md, etc.) (or "none")
+- Code health: final Hotspot and Average scores after push
+
+Then run `/laputa-done <task_id>` → moves to In Review, notifies Brian, self-dispatches next task.
 
 ---
 
@@ -61,7 +71,7 @@ After both phases pass, run `/laputa-done <task_id>` → moves to In Review, not
 
 Red → Green → Refactor → Commit. One cycle per commit. For bugs: write failing regression test first, then fix. Exception: pure CSS/layout changes.
 
-**Test quality (Kent Beck's Desiderata):** Isolated · Deterministic · Fast · Behavioral · Structure-insensitive · Specific · Predictive. Fix flaky tests before adding new ones. Prefer E2E over unit tests for user flows.
+**Test quality (Kent Beck's Desiderata):** Isolated · Deterministic · Fast · Behavioral · Structure-insensitive · Specific · Predictive. Fix flaky tests first. Prefer E2E over unit tests for user flows.
 
 ### Code health (mandatory)
 
@@ -75,22 +85,15 @@ Pre-commit and pre-push hooks enforce **Hotspot Code Health** and **Average Code
 
 ### Check suite (runs on every push)
 ```bash
-pnpm lint && npx tsc --noEmit
-pnpm test
-pnpm test:coverage        # frontend ≥70%
-cargo test
-cargo llvm-cov --manifest-path src-tauri/Cargo.toml --no-clean --fail-under-lines 85
+pnpm lint && npx tsc --noEmit && pnpm test && pnpm test:coverage  # frontend ≥70%
+cargo test && cargo llvm-cov --manifest-path src-tauri/Cargo.toml --no-clean --fail-under-lines 85
 ```
 
-### Architecture Decision Records (ADRs)
+### ADRs & docs
 
-ADRs live in `docs/adr/`. Check before structural choices. Create the ADR **in the same commit as the code**. Never edit existing ADRs — create a new one that supersedes. Use `/create-adr` for template.
+ADRs live in `docs/adr/`. Create in the same commit as the code. Never edit existing — create a new one that supersedes. Use `/create-adr`. **When:** new dependency, storage strategy, platform target, core abstraction, cross-cutting pattern. **Not for:** bug fixes, styling, refactors.
 
-**When to create one:** new dependency, storage strategy, platform target, core abstraction change, cross-cutting pattern. **Not for:** bug fixes, UI styling, refactors, test additions.
-
-### Keep docs/ in sync
-
-After Tauri command, new component/hook, data model change, or new integration: update `docs/ARCHITECTURE.md`, `docs/ABSTRACTIONS.md`, and/or `docs/GETTING-STARTED.md` in the same commit.
+After any Tauri command, new component/hook, data model change, or new integration: update `docs/ARCHITECTURE.md`, `docs/ABSTRACTIONS.md`, and/or `docs/GETTING-STARTED.md` in the same commit.
 
 ---
 
@@ -102,9 +105,7 @@ Default to `demo-vault-v2/`. If you must use `~/Laputa/` for testing: **never co
 
 ### UI design
 
-1. Open `ui-design.pen` first — study existing frames for visual language
-2. Design in light mode. Create `design/<slug>.pen` for the task
-3. On completion: merge frames into `ui-design.pen`, delete `design/<slug>.pen`
+Open `ui-design.pen` first (light mode). Create `design/<slug>.pen` for the task; on completion merge into `ui-design.pen` and delete it.
 
 ### UI components — mandatory rules
 

adr.md

@@ -1,10 +0,0 @@
----
-type: Type
-"sidebar label": ADRs
-icon: article
-color: red
-title: Adr
----
-
-# ADR
-

custom-views-as-yml-files-with-client-side-filter-engine.md

@@ -1,5 +0,0 @@
----
-title: Custom views as .yml files with client-side filter engine
-type: Note
-status: Active
----

demo-vault-v2/responsive-rename-test-renamed.md

@@ -1,5 +1,5 @@
 ---
-type: Project
+type: Note
 status: Active
 ---
 

demo-vault-v2/untitled-note-1775496473.md

@@ -1,5 +1,4 @@
 ---
-title: Untitled note 213
 type: Note
 status: Active
 ---

demo-vault-v2/untitled-note-1775496825.md

@@ -1,5 +1,5 @@
 ---
-title: Untitled note 215
 type: Note
 status: Active
 ---
+My Custom H1 Heading

demo-vault-v2/untitled-note-1775497099.md

@@ -0,0 +1,7 @@
+---
+type: Note
+status: Active
+---
+[[2024-03|March 2024]]
+
+[[2024-03|March 2024]]

demo-vault-v2/untitled-note-1775541952.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542285.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542291.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542296.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542431.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542439.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542446.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542459.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542467.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542474.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542676.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542684.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542692.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542700.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542708.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542716-renamed.md

@@ -0,0 +1,7 @@
+---
+type: Project
+status: Active
+---
+
+
+Appended by raw editor test

demo-vault-v2/untitled-note-1775542923.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542931.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542938.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542951.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542959.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542967.md

@@ -0,0 +1,4 @@
+---
+type: Note
+status: Active
+---

demo-vault-v2/untitled-note-1775542981.md

@@ -0,0 +1,7 @@
+---
+type: Note
+status: Active
+---
+[[2024-03|March 2024]]
+
+[[2024-03|March 2024]]

demo-vault-v2/untitled-project-1775497094.md

@@ -1,11 +1,8 @@
 ---
-title: Untitled video
 type: Project
 status: Active
 ---
 
-# Untitled project 13
-
 ## Objective
 
 

demo-vault-v2/untitled-project-1775542975.md

@@ -1,11 +1,8 @@
 ---
-title: Untitled project 7
 type: Project
 status: Active
 ---
 
-# Untitled project 7
-
 ## Objective
 
 

docs/DESIGN-SYSTEM-PROPOSAL.md

@@ -1,352 +0,0 @@
-# Design System Proposal for Laputa
-
-## Current State Assessment
-
-### What exists today
-- **53 top-level frames** scattered across a ~6800x11400px canvas with no spatial logic
-- **0 reusable components** (every frame is ad-hoc)
-- **~40 design variables** with light/dark theme support (colors, radii, fonts)
-- **2 foundation frames**: Color Palette and Typography & Spacing Specs
-- **1 full-app layout** frame (light mode only)
-- **4 sidebar-collapse variations** showing different panel states
-
-### Recurring patterns that should be components (but aren't)
-By analyzing the 53 frames, these patterns are duplicated 3-10x each:
-
-| Pattern | Where it appears | Times duplicated |
-|---------|-----------------|-----------------|
-| Inspector section header (label + action icon) | rbF01-03, reF01-03, pi01 | 7x |
-| Note list item (title + snippet + date + dot) | dp01-04, mni01-04, trNL1 | ~10x |
-| Tab bar tab (label + close + dot indicator) | dp10, mni10, full layout | 3x |
-| Sidebar filter item (icon + label + count) | trSB1, full layout sidebar | 4x |
-| Sidebar section group (chevron + icon + label) | full layout, drag frames | 4x |
-| Breadcrumb bar (icon + path + badges) | dp20, archBtnNorm/Arc, full layout | 4x |
-| Modal shell (header + body + footer) | ghv01-04, iogBH (settings) | 5x |
-| Property row (label + value) | urlDefault/Hover/Edit, pi01 | 4x |
-| Relationship pill (icon + label + X) | trRI1, reF01-03, rbF01-03 | 6x |
-| Status badge (colored dot/pill) | dp01, dp10, dp20, dp30 | 4x |
-| Status bar (version + branch + sync) | mni20, full layout | 2x |
-| Search bar (dark themed) | 3aG9b, K1O2x, nrIcZ | 3x |
-| Warning/info banner | trW30 | 1x (but will recur) |
-
-Every time a new feature is designed, these get rebuilt from scratch.
-
----
-
-## Proposed Structure
-
-### Single file: `ui-design.pen`
-
-Multiple files creates friction (can't reference components cross-file, harder to maintain). Keep one file, organized into logical **sections** using large container frames as visual grouping. Each section is a horizontal band across the canvas.
-
-### Canvas Layout (top to bottom)
-
-```
-y ≈ 0      ┌─────────────────────────────────────────────┐
-            │  0. COVER                                    │
-            │  App name, version, last updated, TOC        │
-            └─────────────────────────────────────────────┘
-
-y ≈ 200    ┌─────────────────────────────────────────────┐
-            │  1. FOUNDATIONS                               │
-            │  Color palette, Typography scale, Spacing,    │
-            │  Border radius, Shadows, Iconography          │
-            └─────────────────────────────────────────────┘
-
-y ≈ 1800   ┌─────────────────────────────────────────────┐
-            │  2. COMPONENTS (Reusable)                     │
-            │  Atoms → Molecules → Organisms                │
-            │  Each component: default + states side by side│
-            └─────────────────────────────────────────────┘
-
-y ≈ 5000   ┌─────────────────────────────────────────────┐
-            │  3. PATTERNS / COMPOSITIONS                   │
-            │  Panel Inspector, Panel NoteList, Panel Editor│
-            │  Modal shell, Popover/dropdown shell          │
-            └─────────────────────────────────────────────┘
-
-y ≈ 7000   ┌─────────────────────────────────────────────┐
-            │  4. FULL LAYOUTS                              │
-            │  Default state, Sidebar collapsed, Editor     │
-            │  only, etc. (full 1440x900 frames)            │
-            └─────────────────────────────────────────────┘
-
-y ≈ 12000  ┌─────────────────────────────────────────────┐
-            │  5. FEATURE SPECS                             │
-            │  Grouped by feature area — all current 53     │
-            │  frames reorganized here                      │
-            └─────────────────────────────────────────────┘
-```
-
-Each section starts with a **section label frame** (large text, description, horizontal rule). Within each section, frames flow **left to right, wrapping down**, with 100px spacing.
-
----
-
-## Section 1: Foundations
-
-### What to keep
-- **Color Palette** (frame `mOf4J`) — already good. Move to top of file.
-- **Typography & Spacing** (frame `HZonq`) — already good. Place next to color palette.
-
-### What to add
-- **Spacing Scale** — explicit 4px grid reference (4, 8, 12, 16, 20, 24, 32, 40, 48, 64) with visual boxes
-- **Shadow Tokens** — overlay shadow, dialog shadow, dropdown shadow (currently only documented in CSS, not in the design file)
-- **Icon Reference** — small grid showing common Lucide + Phosphor icons used in the app, at 14px and 16px sizes
-
-### Variables to add
-The .pen file already has `--radius-sm/md/lg` but is missing spacing variables. Add:
-
-| Variable | Value | Usage |
-|----------|-------|-------|
-| `--space-xs` | 4 | Tight gaps (icon-to-label) |
-| `--space-sm` | 8 | Standard gap |
-| `--space-md` | 12 | Section padding |
-| `--space-lg` | 16 | Panel padding |
-| `--space-xl` | 24 | Large section gaps |
-| `--space-2xl` | 32 | Page padding |
-| `--space-3xl` | 48 | Section dividers |
-
----
-
-## Section 2: Component Library
-
-### Atomic Design Hierarchy
-
-#### Atoms (smallest building blocks)
-
-| Component | Variants/States | ID Prefix |
-|-----------|----------------|-----------|
-| **Button/Primary** | default, hover, active, disabled | `c/btn-pri` |
-| **Button/Secondary** | default, hover, active, disabled | `c/btn-sec` |
-| **Button/Ghost** | default, hover, active | `c/btn-ghost` |
-| **Button/Destructive** | default, hover, disabled | `c/btn-dest` |
-| **Button/Icon** | default, hover (icon-only button, e.g. close, settings) | `c/btn-icon` |
-| **Input/Text** | empty, filled, focused, error, disabled | `c/input` |
-| **Input/Search** | empty, with query, with clear button | `c/input-search` |
-| **Badge** | default, secondary, outline, destructive, status colors (green/orange/red/blue/purple) | `c/badge` |
-| **Status Dot** | green (new), orange (modified), none (clean) | `c/status-dot` |
-| **Checkbox** | unchecked, checked, indeterminate | `c/checkbox` |
-| **Toggle** | off, on | `c/toggle` |
-| **Icon** | 14px, 16px, 20px wrapper with Lucide/Phosphor | `c/icon` |
-| **Separator** | horizontal, vertical | `c/sep` |
-| **Avatar/Initial** | letter avatar for Person entities | `c/avatar` |
-| **Tooltip** | top, bottom (container with pointer) | `c/tooltip` |
-
-#### Molecules (composed from atoms)
-
-| Component | Composition | States | ID Prefix |
-|-----------|------------|--------|-----------|
-| **Sidebar/FilterItem** | icon + label + count badge | default, active, hover | `c/sb-filter` |
-| **Sidebar/SectionHeader** | chevron + icon + label + add button | collapsed, expanded, hover, dragging | `c/sb-section` |
-| **Sidebar/SectionItem** | indent + label | default, active, hover | `c/sb-item` |
-| **Sidebar/TopicItem** | hash + label | default, active, hover | `c/sb-topic` |
-| **NoteList/Item** | status dot + title + snippet + date + type pill | default, selected, hover, modified, new | `c/nl-item` |
-| **NoteList/Header** | title + count + sort button | — | `c/nl-header` |
-| **Tab** | label + close btn + modified dot | default, active, hover, modified | `c/tab` |
-| **BreadcrumbBar** | path segments + word count + status badge | new, modified, clean | `c/breadcrumb` |
-| **Property/Row** | label + value | default, hover, editing | `c/prop-row` |
-| **Property/URLRow** | label + link + copy/edit icons | default, hover, editing | `c/prop-url` |
-| **Relationship/Pill** | icon + label + (X remove on hover) | default, hover, trashed, archived | `c/rel-pill` |
-| **Relationship/AddInput** | search input with autocomplete | empty, typing, results | `c/rel-add` |
-| **Inspector/SectionHeader** | label + action button | default, hover | `c/insp-header` |
-| **Git/CommitItem** | hash + message + author + date (timeline style) | — | `c/git-commit` |
-| **Search/ResultItem** | title + path + highlighted snippet | default, selected | `c/search-result` |
-| **Sort/DropdownItem** | label + direction arrow + checkmark | default, selected | `c/sort-item` |
-| **Banner/Warning** | icon + message + optional action | info, warning, error | `c/banner` |
-| **Wikilink** | colored link text (varies by entity type) | 8 type colors | `c/wikilink` |
-
-#### Organisms (panel-level compositions)
-
-| Component | Content | ID Prefix |
-|-----------|---------|-----------|
-| **Panel/Sidebar** | title bar + filters + sections + commit area | `c/panel-sidebar` |
-| **Panel/NoteList** | header + type pills + item list | `c/panel-notelist` |
-| **Panel/Editor** | tab bar + breadcrumb + content area | `c/panel-editor` |
-| **Panel/Inspector** | properties section + relations + backlinks + history | `c/panel-inspector` |
-| **Modal/Shell** | header + tab bar (opt) + body + footer | `c/modal` |
-| **Popover/Dropdown** | list of items + separator + annotation | `c/popover` |
-| **StatusBar** | left info + right info | `c/statusbar` |
-| **TitleBar** | traffic lights (macOS) | `c/titlebar` |
-
----
-
-## Section 3: Patterns / Compositions
-
-These are **non-reusable** reference frames showing how components compose into real UI sections. Think of them as "component playgrounds" — they use component instances to build real UI, but they're documentation, not building blocks.
-
-- **Inspector states**: Properties expanded, Relations with pills, Referenced By with/without entries, Backlinks, Git history
-- **NoteList states**: All Notes view, filtered by section, empty state, search results
-- **Sidebar states**: All sections expanded, one collapsed, dragging reorder, after reorder
-- **Editor states**: Single tab, multiple tabs, modified tabs, diff view
-- **Modal patterns**: GitHub Vault flow (4 states), Settings, Create Note, Commit Dialog
-
----
-
-## Section 4: Full Layouts
-
-| Frame | Description |
-|-------|-------------|
-| **Default — All Panels** | 1440x900, sidebar + notelist + editor + inspector |
-| **Sidebar Collapsed** | Editor area wider, collapse button visible |
-| **Editor + NoteList Only** | No sidebar or inspector |
-| **Editor Only** | Focused writing mode |
-| **AI Chat Open** | Inspector replaced with AI Chat panel |
-| **Quick Open Modal** | Cmd+P overlay on default layout |
-
-Keep the existing 5 layout frames (qHhaj + SC_all/nosb/edonly/ednl). Add AI Chat and Quick Open.
-
----
-
-## Section 5: Feature Specs
-
-Reorganize existing 53 frames into feature groups. Each group gets a **feature label** frame above it:
-
-| Group | Frames to include |
-|-------|-------------------|
-| **Note Status & Indicators** | dp01, dp10, dp20, dp30, mni01, mni10, mni20 |
-| **Trash & Archive** | trSB1, trNL1, trRI1, trW30, archBtnNorm, archBtnArc |
-| **Inspector & Properties** | pi01, pi50, rbF01-03, reF01-03, urlDefault/Hover/Edit |
-| **Sidebar** | dsg01a-04j, csB01, csA01 |
-| **GitHub Vault** | ghv01-04, ghv03 |
-| **Git History** | ghCL1, ghDO1, vc001, vc100, vc200 |
-| **Sort & Search** | srtDD, srtBN, 3aG9b, K1O2x, nrIcZ |
-| **Editor & Wikilinks** | wlc01 |
-| **Settings** | iogBH |
-| **Virtual List** | vl001 |
-
----
-
-## Naming Convention
-
-### Frames
-```
-Section-level:   "== FOUNDATIONS =="
-                 "== COMPONENTS =="
-                 "== FULL LAYOUTS =="
-
-Feature groups:  "Feature: Trash & Archive"
-                 "Feature: Note Status"
-```
-
-### Reusable Components
-```
-component/<category>/<name>
-
-Examples:
-  component/button/primary
-  component/button/ghost
-  component/sidebar/filter-item
-  component/notelist/item
-  component/inspector/section-header
-  component/modal/shell
-```
-
-### States (within a component frame)
-```
-<component-name> — <state>
-
-Examples:
-  Button/Primary — Default
-  Button/Primary — Hover
-  NoteList/Item — Selected
-  NoteList/Item — Modified
-```
-
-### Feature Spec Frames
-```
-<Feature> — <Specific View>
-
-Examples:
-  Trash — Note List View
-  Trash — 30-Day Warning
-  Git History — Commit List
-  Git History — Diff Open
-```
-
----
-
-## Implementation Priority
-
-### Phase 1: Foundation Cleanup (2-3 hours)
-1. Add spacing variables to the .pen file
-2. Move Color Palette and Typography frames to top of canvas (y ≈ 200)
-3. Add section label frames as visual dividers
-4. Reorganize existing 53 frames into the feature-spec section (y ≈ 12000+)
-5. Create cover frame at y ≈ 0
-
-**Impact**: Clean canvas, easy to navigate. Zero component work yet.
-
-### Phase 2: Core Atoms (3-4 hours)
-1. **Button** — 4 variants x 3 states = ~12 sub-frames, all as `reusable: true`
-2. **Badge** — 6 color variants + 4 style variants
-3. **Status Dot** — green, orange, red, none
-4. **Input** — text + search variants
-5. **Separator** — horizontal + vertical
-6. **Icon Button** — close, settings, chevron, etc.
-
-**Impact**: Building blocks exist. Future features can pull from them.
-
-### Phase 3: Core Molecules (4-5 hours)
-1. **Sidebar/FilterItem** — most reused sidebar pattern
-2. **Sidebar/SectionHeader** — with chevron and add button
-3. **NoteList/Item** — the most duplicated pattern in the file
-4. **Tab** — with modified indicator states
-5. **Property/Row** — default/hover/edit states
-6. **Relationship/Pill** — normal/trashed/archived states
-7. **Inspector/SectionHeader** — label + collapse/action
-
-**Impact**: Feature specs can be rebuilt from instances. Consistency guaranteed.
-
-### Phase 4: Organisms (3-4 hours)
-1. **Modal/Shell** — replace 5 ad-hoc modals with instances of one shell
-2. **Panel/Sidebar** — full sidebar composition
-3. **Panel/NoteList** — full notelist composition
-4. **StatusBar** — standardize
-5. **Popover/Dropdown** — for sort, autocomplete, etc.
-
-**Impact**: Full layouts can be composed from panel organisms.
-
-### Phase 5: Rebuild Full Layouts (2-3 hours)
-1. Rebuild "Laputa App — Full Layout (Light)" using component instances
-2. Create remaining layout variants (AI Chat, Quick Open)
-3. Ensure all layouts use the same component instances for consistency
-
-**Impact**: Single source of truth. Change a button component, all layouts update.
-
-### Phase 6: Feature Spec Cleanup (2-3 hours)
-1. Rebuild key feature specs using component instances where possible
-2. Remove frames that are now redundant (covered by component states)
-3. Add any missing feature-specific variations
-
-**Impact**: Clean, maintainable feature documentation.
-
----
-
-## Estimated Total Effort
-
-| Phase | Effort | Cumulative |
-|-------|--------|-----------|
-| 1. Foundation Cleanup | 2-3h | 2-3h |
-| 2. Core Atoms | 3-4h | 5-7h |
-| 3. Core Molecules | 4-5h | 9-12h |
-| 4. Organisms | 3-4h | 12-16h |
-| 5. Full Layouts | 2-3h | 14-19h |
-| 6. Feature Cleanup | 2-3h | 16-22h |
-
-**Recommendation**: Do phases 1-3 first (9-12h). This covers 80% of the value — clean organization + the most reused components. Phases 4-6 can happen incrementally as features are designed.
-
----
-
-## What "World Class" Looks Like
-
-After this work, `ui-design.pen` will:
-
-1. **Open to a cover page** with app identity and section navigation
-2. **Have ~30 reusable components** that match the real implementation 1:1
-3. **Use variables everywhere** — no hardcoded colors, spacing, or radii
-4. **Show every component state** — no guessing what hover/active/disabled looks like
-5. **Compose layouts from instances** — change a component, all layouts update
-6. **Group features logically** — find any feature spec in seconds
-7. **Grow naturally** — new features just add instances of existing components + new feature-specific frames
-
-The key shift: **from "collection of screenshots" to "living system of composable parts"**.

docs/PROJECT-SPEC.md

@@ -1,332 +0,0 @@
-# Laputa App — Personal Knowledge & Life Management App
-
-## Status: V1 Complete! 🎉
-
-## Vision
-Custom desktop + mobile app to manage Luca's life — projects, responsibilities, knowledge, people, events. Built around a specific ontology that no existing app gets right. The current Laputa vault (Obsidian, 9200+ markdown files) is the data layer and predecessor — the app gives it a proper UI.
-
-## Tech Stack
-- **Desktop**: Tauri (Rust shell + system webview)
-- **Frontend**: React + TypeScript
-- **Editor**: CodeMirror 6 — live preview with reveal-on-focus (Obsidian/Bear style)
-- **Mobile**: Capacitor (wraps same web UI for iOS/Android) — later phase
-- **Data**: plain markdown files on disk with YAML frontmatter, git-versioned
-- **Core logic**: Rust (file parsing, git ops, indexing) via Tauri commands
-
----
-
-## Ontology
-
-### Core Entities
-
-#### Year
-- Top-level time container
-- Has: Quarters, Targets
-- Naming convention: `2026` (Laputa legacy: Chinese zodiac names like `2022-tiger`)
-
-#### Quarter
-- Time container within a Year
-- Has: Projects, Targets
-- Natural planning/review cycle
-
-#### Responsibility
-- Long-running duty, possibly indefinite
-- Has clear and measurable KPIs (via Measures)
-- Has an owner (Person)
-- Has: Projects, Procedures, Tasks, Measures
-- Examples: "Grow newsletter", "Manage sponsorships", "Stay healthy"
-
-#### Measure
-- A trackable metric tied to one or more Responsibilities
-- Quantitative and observable
-- Examples: "Resting heart rate", "Newsletter subscribers", "Monthly revenue", "Sponsorship close rate"
-
-#### Target
-- A time-bound goal for a Measure
-- Typically quarterly
-- Examples: "Resting HR < 55 by Q1 2026", "Reach 100k subscribers by Q2 2026"
-- Belongs to: a Quarter (or Year), references a Measure
-
-#### Project
-- Has a beginning and an end
-- Can't be completed in one sitting
-- Has success criteria (key results, described informally in the project page)
-- Has a timeline — at minimum a deadline (default: end of quarter)
-- Advances one or more Responsibilities
-- Has an owner (Person)
-- Belongs to: Quarter (primary), Responsibility
-- Has: Tasks, Notes
-
-#### Experiment
-- Like an unplanned baby project — exploring something promising without expectation of success
-- Can't be completed in one sitting
-- No strict success criteria or deadline
-- Has an owner (Person)
-- Examples: "Vibe-coding a stock screener", "Testing a new content format"
-
-#### Procedure
-- Recurring piece of work, completable in one sitting
-- Has a cadence (daily, weekly, monthly, etc.)
-- Belongs to: a Responsibility (usually) or a Project (less common)
-- Has an owner (Person)
-- Examples: "Weekly sponsorship report", "Morning briefing", "Monthly review"
-
-#### Task
-- One-off piece of work, completable in one sitting
-- Belongs to: a Responsibility or a Project
-- Has an owner (Person)
-
-#### Topic
-- An area of interest — no performance expectations
-- Things link to Topics for categorization/discovery
-- Examples: "AI/ML", "Trading", "Fitness", "Frontend"
-
-#### Note
-- A document, tool, resource, or any material helpful to advance work
-- Can belong to: Procedures, Responsibilities, Projects (one or many)
-- Can be related to: Topics (one or many)
-- Examples: evergreen notes, reference docs, templates, bookmarks
-
-#### Person
-- A real-world person or an AI agent
-- Owner of Projects, Responsibilities, Procedures, Tasks
-- Related to Events
-
-#### Event
-- Something that happened on a given day, stored in long-term memory
-- Examples: conversations, meetings, achievements, personal milestones
-- Can be related to: any entity above
-- Date-based: one specific day
-
----
-
-## Relationships Summary
-
-```
-Year
-  └── Quarter
-        └── Project ──→ Responsibility (advances)
-        └── Target ──→ Measure ──→ Responsibility
-
-Responsibility
-  ├── Project
-  ├── Procedure (recurring)
-  ├── Task (one-off)
-  └── Measure → Target
-
-Project
-  ├── Task
-  └── Note
-
-Procedure
-  └── Note
-
-Note ──→ Topic (categorization)
-Event ──→ anything (loose association)
-Person = owner of Project, Responsibility, Procedure, Task
-```
-
-### Relationship Types
-- **Belongs to**: hierarchical parent (Project→Quarter, Task→Project, Procedure→Responsibility)
-- **Advances**: Project→Responsibility (why this project exists)
-- **Related to**: loose association (Event→anything, Note→Topic)
-- **Owner**: Person who is accountable (single owner per entity)
-
----
-
-## Laputa Legacy Mapping
-
-| Laputa Concept | Life OS Equivalent |
-|---|---|
-| Year | Year |
-| Quarter | Quarter |
-| Goal | Target + Measure |
-| Project | Project |
-| Key Result | Informal in Project page |
-| Responsibility | Responsibility |
-| Procedure | Procedure |
-| Topic | Topic |
-| Person | Person |
-| Event | Event |
-| Evergreen | Note |
-| Note (reading notes) | Note |
-| Readings | Note |
-| Essay | Note (belongs to a Responsibility/Project) |
-| Monday Ideas | Note |
-| Area | Folded into Responsibility or Topic |
-| Month | Removed (Quarter is the planning unit) |
-| Journal | Removed or becomes a Note |
-| Movie/Restaurant/Hotel | Out of scope (or Topic-linked Notes) |
-| Vital | Measure |
-| Video/Buckets | Note (belongs to Project/Responsibility) |
-
----
-
-## UI Design
-
-### Design Reference
-- Wireframes: `/Users/luca/OpenClaw/Laputa-app-design.pen`
-- Inspiration: Bear Notes, Obsidian
-
-### Core Principle: Type-Agnostic UI
-Minimize custom UI behavior per entity type. Everything is a file, everything gets the same treatment. Type only determines which sidebar section an entity appears under (and maybe an icon/color hint). The editor, right panel, and note list behave identically regardless of type.
-
-### Layout: Four Panels
-
-#### 1. Left Sidebar — Navigation
-**Filters** (flat, switch the note list view):
-- All Notes
-- Untagged
-- Favorites
-- People
-- Events
-
-**Section Groups** (expandable, show entity list):
-- PROJECTS +
-- EXPERIMENTS +
-- RESPONSIBILITIES +
-- PROCEDURES +
-
-**Topics** (flat list, not nested):
-- work
-- strategy
-- ideas
-- research
-- drafts
-- archive
-
-#### 2. Note List — Middle Panel
-- Contextual to sidebar selection
-- Title, preview snippet, date, tags as colored pills
-- Status/type indicators
-- Search bar + create button
-- Default sort: last edited (descending)
-- Quick type filter pills: `All | Notes | Events | People | ...`
-- When viewing a section group entity (e.g. a Project): its own page is **pinned at top**, children listed below
-
-#### 3. Editor — Main Panel
-- CodeMirror 6 with live preview (reveal markdown syntax on active line)
-- **Tab bar** at top: multiple open notes, closeable, shows parent context
-- Title + content only — NO properties/frontmatter shown in editor
-- Tags shown as clickable pills below title
-- Created/last edited dates below title
-- Wikilinks rendered as clickable in-app navigation links
-- Frontmatter exists in the file but is hidden from the editor view
-
-#### 4. Right Panel — Inspector
-- **Status** pills (Active, Draft, etc.)
-- **Properties**: Created, Modified, Author, Word Count, custom properties. Editable — writes to YAML frontmatter.
-- **Relationships**: all "belongs to", "related to", "advances" links. Editable.
-- **Backlinks**: notes that reference this note
-- **Revision History**: git commits for this file — hash, message, author, timestamp. "View all revisions" link.
-
-### Key UI Decisions
-- **Editor is sacred** — all metadata/relationships live in the right panel, not above the content. Avoids the Obsidian/Notion problem of properties pushing content down.
-- **Everything is a file** — a Project, Responsibility, Topic are all just notes with a type. Clicking one in the sidebar shows its page pinned at top of note list, children below.
-- **Topics are flat** — no nesting for v1
-- **Saved views / smart filters** — future feature. Saved queries that live under any entity in the sidebar (e.g. "Evergreen 60+ days" under a Procedure). Not in v1.
-- **Tasks stay on Todoist** — no task management in v1
-
-## Design Decisions
-- **Month/Week are NOT entities** — they're time-based views/filters, not containers. Monthly reviews are a Procedure.
-- **Essays, Monday Ideas, Videos, Readings** = Notes (belonging to Responsibility/Project)
-- **Movies, Restaurants, Hotels** = Notes attached to Topics
-- **Key Results** = informal, embedded in Project pages (not a separate entity)
-- **Owner** = single Person per entity (no multi-owner for now)
-- **Type-agnostic UI** — minimize type-specific behavior, keep everything consistent
-- **Metadata in right panel, not in editor** — frontmatter is hidden from the editor, rendered as editable UI in the inspector
-
-## Dev Workflow
-
-> Full process documented in **`dev-workflow` skill** (`~/.openclaw/skills/dev-workflow/SKILL.md`).
-> Below: Laputa-specific details only.
-
-- **Repo**: `~/Workspace/laputa-app/` + GitHub `LucaRonin/laputa-app`
-- **Design file**: `~/OpenClaw/projects/Laputa-app-design.pen`
-- **Mock layer**: `src/mock-tauri.ts` (realistic test data for browser/Playwright testing without Tauri)
-
-### Laputa-Specific MCPs (for Claude Code)
-- **Context7** — up-to-date docs for Tauri v2, CodeMirror 6, React
-- **Pencil MCP** — reads the .pen design file
-
-### Key Lesson from M1
-M1 passed all tests but showed 0 notes — vault path wrong, error silently swallowed. This drove the mandatory verification workflow now captured in the dev-workflow skill.
-
----
-
-## V1 Milestones
-
-### M1: Scaffold & Shell ✅ COMPLETE
-**Goal:** Empty Tauri + React app that opens a window, reads a vault path, and lists files.
-- [x] Init repo at `~/Workspace/laputa-app/`
-- [x] Tauri v2 + React 19 + TypeScript + Vite 7 project setup
-- [x] Configure Vitest (7 tests), Playwright (2 E2E tests), Rust tests (10 tests)
-- [x] Rust backend: `list_vault` command — scans directory, parses YAML frontmatter via `gray_matter` crate
-- [x] Rust backend: extracts type (Is A), aliases, Belongs to, Related to, Status, Owner, Cadence, title from H1
-- [x] React: four-panel layout (Sidebar 250px, NoteList 300px, Editor flex, Inspector 280px), all resizable
-- [x] Tauri mock layer for browser testing (`src/mock-tauri.ts`)
-- [x] Screenshot verification via Playwright (`e2e/screenshot.spec.ts`)
-- [ ] Push to GitHub (not yet done)
-
-**Git log (5 commits):**
-```
-e72d66a Add Tauri mock layer for browser testing and visual verification workflow
-bc75647 Remove unused Vite scaffold files
-7d5c48c Add unit and E2E tests for all panel components
-57083ad Add four-panel layout shell with vault scanning on load
-6b53cf8 Initialize Tauri v2 + React + TypeScript project with vault scanner
-```
-
-### M2: Sidebar & Note List
-**Goal:** Navigate the vault via sidebar, see filtered note lists.
-- [ ] Sidebar: Filters section (All Notes, Favorites)
-- [ ] Sidebar: Section Groups (Projects, Experiments, Responsibilities, Procedures) — populated from frontmatter `type:`
-- [ ] Sidebar: Topics — flat list, populated from `Related to` topic links
-- [ ] Note list: show title, preview snippet, date, type indicator
-- [ ] Note list: sort by last modified (descending)
-- [ ] Note list: search (full-text across vault)
-- [ ] Note list: type filter pills (All | Notes | Events | People | ...)
-- [ ] Clicking a section group entity: pin its page at top, show children below
-- [ ] Filesystem watching: live reload when files change externally
-
-### M3: Editor
-**Goal:** Open and edit markdown files with CodeMirror 6 live preview.
-- [ ] CodeMirror 6 integration with React
-- [ ] Live preview: hide markdown syntax, reveal on active line (Obsidian/Bear style)
-- [ ] Frontmatter hidden from editor view
-- [ ] Tab bar: open multiple notes, close tabs, show parent context
-- [ ] Wikilinks rendered as clickable links → navigate in-app
-- [ ] Save: write markdown + YAML frontmatter to disk
-- [ ] Auto-save (debounced)
-- [ ] Basic markdown features: headings, bold/italic, lists, code blocks, links, images
-
-### M4: Right Panel — Inspector
-**Goal:** View and edit metadata, relationships, and git history.
-- [ ] Properties panel: Created, Modified, Author, Word Count, Status, custom fields
-- [ ] Properties editable → writes to YAML frontmatter
-- [ ] Relationships panel: Belongs to, Related to, Advances — rendered as clickable links
-- [ ] Relationships editable (add/remove)
-- [ ] Backlinks: auto-computed from wikilinks across vault
-- [ ] Git revision history: show commits for current file (hash, message, author, date)
-- [ ] "View all revisions" link
-
-### M5: File Operations & Polish
-**Goal:** Create, rename, delete files. Polish for daily-driver use.
-- [ ] Create new note (with type selector → sets `type:` in frontmatter, created at vault root)
-- [ ] Rename file (updates filename + title)
-- [ ] Delete → permanent delete with confirm dialog
-- [ ] Keyboard shortcuts (Cmd+N new, Cmd+S save, Cmd+P quick open/search)
-- [ ] Quick open palette (Cmd+P) — fuzzy search across all files
-- [ ] People and Events filters in sidebar
-- [ ] Visual polish: match Bear-inspired design from .pen wireframes
-- [ ] E2E tests with Playwright for core flows
-
----
-
-## Open Questions
-- [ ] Migration path from current Laputa vault (legacy cleanup, schema normalization)
-- [ ] Multi-user or just Luca + AI agents?
-- [ ] How does Brian (and other agents) interact with the data?
-- [ ] Mobile: when to start the Capacitor layer?
-- [ ] Year/Quarter navigation in sidebar — dedicated section or time-based filter?
-- [ ] Home/dashboard view — what does it show?

docs/ROADMAP.md

@@ -1,113 +0,0 @@
----
-title: ROADMAP
----
-# Laputa — Product Roadmap
-
-*Strategic directions, not implementation tasks. Each item here represents a direction that will be broken down into many smaller tasks when the time comes.*
-
-*Updated: March 2026.*
-
----
-
-## Consolidation sprint (current priority)
-
-Before building new features, the architectural foundations must be solid. Key structural fixes underway:
-
-- Move vault cache outside the vault directory (→ `~/.laputa/cache/`) with atomic writes
-- Flip `type:` to canonical field in Rust parser (`Is A:` becomes alias)
-- Remove `allContent` from the architecture — derive backlinks from open tabs only
-- ~~Remove hardcoded `RELATIONSHIP_KEYS` — detect wikilink fields dynamically~~ ✅ Done
-- Fix hardcoded vault path in `resolveNewNote` / `resolveNewType` / `resolveDailyNote`
-- Define and enforce the three-source-of-truth contract (filesystem → cache → React state)
-
-These are not features — they are the foundation everything else is built on.
-
----
-
-## Strategic directions
-
-### 1. Semantic properties
-
-**What:** Conventional frontmatter field names (`status:`, `url:`, `start_date:`, `end_date:`, `goal:`, `result:`) trigger rich UI rendering beyond the Properties panel — chips in the note list, progress indicators in the editor header, date range badges.
-
-**Why:** Notes are not just documents. A Project has a start and end. A Responsibility has KPIs. A Procedure has an owner and a cadence. The app should surface this structure visually, not just store it as plain text.
-
-**Convention over configuration:** the rendering rules ship as sensible defaults. Users can override via `config/semantic-properties.md` in the vault — a plain markdown file, editable from within the app.
-
-**Draft tasks:** created in Todoist. To be prioritized after consolidation sprint.
-
----
-
-### 2. Default relationships in Properties panel
-
-**What:** The Properties panel shows a set of relationship fields by default — even when empty — guiding the user toward a connected knowledge graph. Defaults include: Belongs to, Related to, Events, People (Type is already shown).
-
-**Why:** A new note starts with a completely empty Properties panel today. There's no guidance on how to connect it. Laputa is opinionated — it should show you the connections that matter.
-
-**Convention over configuration:** the default list is built in, but can be overridden via `config/relations.md` in the vault.
-
-**Draft tasks:** created in Todoist. Needs design discussion (per-type overrides?) before implementation.
-
----
-
-### 3. Global workspace filter
-
-**What:** A top-level workspace switcher (below the traffic lights) that filters the entire app — sidebar, note list, search — to show only notes belonging to the selected workspace, plus shared notes (those without a Workspace field).
-
-**Why:** A single vault often contains both personal and work content. A workspace filter lets you focus on one context at a time without cognitive overhead.
-
-**How:** Notes opt into a workspace via `Workspace: [[workspace/refactoring]]` frontmatter. Workspace notes are auto-detected from the `workspace/` folder. No setup required.
-
-**Future trajectory:** Workspaces are the seed of a multi-vault, multi-user access control model. In the future, workspaces may map to separate Git repositories — each with their own access permissions. Different people see different workspaces (vaults). Git provides the audit trail. This enables Laputa to grow from a personal tool to a small-team knowledge base without rebuilding the product.
-
-**Draft tasks:** created in Todoist. Lower priority than semantic properties and default relationships.
-
----
-
-### 4. Inbox and capture pipeline
-
-**What:** An Inbox section that surfaces all unorganized notes — those with no outgoing relationships. Replaces "All Notes" as the primary landing section. Capture integrations (Chrome extension, iPhone share sheet, Readwise sync) feed into the inbox automatically.
-
-**Why:** Capture and organize are fundamentally different activities and should be treated separately. Today Laputa has no concept of an unorganized note — everything lands in the same pool. The inbox makes the unorganized state visible and actionable, creating a discipline: Inbox Zero, reached weekly.
-
-**The inbox as a smart filter:** not a folder. Any note without `Belongs to:`, `Related to:`, or other meaningful relationship is automatically in the inbox. Connecting a note to something removes it from the inbox, automatically.
-
-**Capture integrations (future, each a separate feature):**
-- Chrome extension → saves URL/clip as a note to the vault via Git
-- iPhone share sheet → quick capture from any app
-- Readwise / Kindle highlights → synced via Git automation
-- Voice memo → transcribed and dropped into inbox
-
-**Priority:** The Inbox UI is high-value and can be implemented without the capture integrations. Integrations come after.
-
----
-
-### 5. Mobile apps
-
-**What:** Native apps for iPhone and iPad — not ports of the desktop app, but purpose-built for each form factor.
-
-**iPhone:** Optimized for fast capture. Quick note creation, voice memos, brief thoughts. The primary use case is getting something into the vault quickly while away from the desk. Minimal reading and editing.
-
-**iPad:** A more capable mirror of the desktop experience — reading, editing, navigating the vault. Not a full four-panel layout, but enough to work on notes meaningfully. Think "laptop replacement for light work sessions."
-
-**Why it matters:** Laputa's value as a personal knowledge system depends on being able to capture things wherever you are. Without mobile capture, important notes get lost or end up scattered in other apps.
-
-**Sync:** Git-based, same as desktop. The vault is a Git repo — mobile apps commit and pull like any other client.
-
-**Priority:** After the desktop experience is solid. Not before.
-
----
-
-## Principles for this roadmap
-
-- **Foundations before features** — a shaky architecture multiplies the cost of every feature built on top of it
-- **Convention over configuration** — ship strong defaults, allow customization via vault files
-- **File-first** — every strategic direction must be achievable without breaking the markdown-files-on-disk model
-- **AI-readable by design** — conventions that humans find intuitive should also be legible to AI agents navigating the vault
-
----
-
-*For active tasks and bugs, see the Todoist board (Laputa App project).*
-*For architectural decisions and design principles, see [ARCHITECTURE.md](./ARCHITECTURE.md) and [VISION.md](./VISION.md).*
-
-<!-- QA test edit Wed Apr  1 16:17:01 CEST 2026 -->

docs/adr/0007-title-filename-sync.md

@@ -2,8 +2,9 @@
 type: ADR
 id: "0007"
 title: "Title equals filename (slug sync)"
-status: active
+status: superseded
 date: 2026-03-15
+superseded_by: "0044"
 ---
 
 ## Context

docs/adr/0042-trash-auto-purge-safety-model.md

@@ -2,8 +2,9 @@
 type: ADR
 id: "0042"
 title: "Trash auto-purge safety model"
-status: active
+status: superseded
 date: 2026-04-05
+superseded_by: "0045"
 ---
 
 ## Context

docs/adr/0044-h1-as-title-primary-source.md

@@ -0,0 +1,46 @@
+---
+type: ADR
+id: "0044"
+title: "H1 as primary title source — filename as stable identifier"
+status: active
+date: 2026-04-07
+supersedes: "0007"
+---
+
+## Context
+
+ADR-0007 established that the `title:` frontmatter field is the source of truth for display titles, with filenames derived from it via slugification and kept in sync bidirectionally. This model had a key assumption: the user explicitly types a title before writing content.
+
+In practice this created friction: new notes required a title upfront, the TitleField was always visible cluttering the editor, and the "title = filename slug" contract was fragile when users renamed files externally. The team wanted a more natural writing flow where you just start writing — like most text editors — and the title emerges from the document.
+
+A pair of commits on 2026-04-06 (`377a3f8d`, `7daf6898`) implemented a fundamentally different model.
+
+## Decision
+
+**The first `# H1` heading in the note body is the canonical display title. The `title:` frontmatter field is legacy/backward-compat only. New notes are created with filename `untitled-{type}-{timestamp}.md` and no `title:` in frontmatter. On save, if the note has an H1, the file is auto-renamed to a slug derived from it (collision-safe with `-2`, `-3` suffixes).**
+
+Title resolution priority (Rust `extract_title`):
+1. H1 on the first non-empty line of the body
+2. Frontmatter `title:` field (legacy, backward-compat)
+3. Slug-to-title derivation from filename stem
+
+The `has_h1: bool` field on `VaultEntry` signals the frontend to hide `TitleField` and the icon picker when an H1 is present, since the H1 serves as the title surface.
+
+The breadcrumb bar shows the **filename stem** (not display title) so users always know the actual file identifier.
+
+Auto-rename (`auto_rename_untitled` Tauri command) fires on save for `untitled-*` files that gain an H1, converting them to a human-readable slug.
+
+## Options considered
+
+- **Option A — H1 as primary title + auto-rename on save** (chosen): natural writing flow, filename eventually reflects content, TitleField hidden when H1 present. Downside: auto-rename can surprise users; breadcrumb must show filename to stay honest.
+- **Option B — Keep `title:` frontmatter as source of truth** (ADR-0007, now superseded): explicit, deterministic. Downside: forces upfront titling, TitleField always visible, friction for quick capture.
+- **Option C — UUID-based filenames, title only in H1**: filenames never change, no rename logic needed. Downside: vault unreadable in Finder/terminal, breaks the plain-files principle (ADR-0002).
+
+## Consequences
+
+- New notes start as `untitled-note-{timestamp}.md` — the vault may accumulate untitled files if users abandon drafts without writing an H1
+- `TitleField` component is hidden when `has_h1 = true`; icon picker is also hidden (icons only make sense on titled notes)
+- Frontmatter `title:` still parsed for backward-compat; existing vaults with explicit titles continue to work
+- Auto-rename on save introduces a file rename side-effect during editing — wikilinks pointing to the old filename may break until the rename propagates
+- The breadcrumb filename display makes the system more honest but slightly more technical for non-power users
+- Re-evaluate if users find auto-rename disorienting or if wikilink breakage during rename becomes a reliability concern

docs/adr/0045-permanent-delete-no-trash.md

@@ -0,0 +1,37 @@
+---
+type: ADR
+id: "0045"
+title: "Permanent delete with confirm modal — no Trash system"
+status: active
+date: 2026-04-07
+supersedes: "0042"
+---
+
+## Context
+
+ADR-0042 designed a Trash auto-purge safety model (soft-delete with 30-day retention, OS trash via `trash` crate, audit log). This was built on top of a Trash system that treated deletion as a two-phase operation: move to trash → auto-purge after 30 days.
+
+The Trash system was subsequently identified as unnecessary complexity: it required `trashed`/`trashedAt` frontmatter fields, sidebar filtering, editor banners, inspector components, dedicated smoke tests, and a `trash` crate dependency. The safety guarantee users actually need is a **confirmation prompt before irreversible action**, not a soft-delete buffer — especially given notes live in a git repo (vault git history is already a recovery mechanism per ADR-0034 and ADR-0014).
+
+Commit `e581ad36` on 2026-04-06 removed the entire Trash system (123 files changed, ~3164 lines deleted).
+
+## Decision
+
+**Delete is permanent and immediate, gated only by a confirmation modal (`useDeleteActions`). Notes with `trashed: true` in existing vault frontmatter are treated as normal notes (the flag is ignored by the parser). The `trash` crate dependency is removed.**
+
+The confirmation modal is the sole safety gate. No soft-delete, no Trash view, no auto-purge scheduler, no `.laputa/purge.log`.
+
+## Options considered
+
+- **Option A — Permanent delete + confirm modal** (chosen): simple, honest, no hidden state. Git history provides recovery. Removes ~3000 lines of code and a platform-specific dependency. Downside: no in-app recovery path for users who don't know about git.
+- **Option B — OS Trash via `trash` crate** (ADR-0042, now superseded): soft-delete to OS Trash, user can recover from macOS Trash app. Downside: additional dependency, complex auto-purge scheduler, misleading "auto-purge" promise that was never actually implemented.
+- **Option C — `.laputa/deleted/` archive folder**: custom recovery mechanism inside vault. Downside: clutters vault, users wouldn't know to look there, still requires manual cleanup.
+
+## Consequences
+
+- Users who accidentally delete a note must recover from git history (`git checkout HEAD -- path/to/note.md`) — this is a power-user action
+- `trashed`/`trashedAt` frontmatter fields in existing vaults are silently ignored — no migration needed, no data loss
+- The `trash` crate is removed from `Cargo.toml` — build times improve marginally
+- Smoke tests for trash flows are deleted; delete-related test coverage is now purely the confirm modal behavior
+- The Trash view, sidebar filter, note banners, and bulk-trash actions are all gone — simpler UI surface
+- Re-evaluate if user feedback shows significant accidental deletion incidents, or if git-based recovery proves too inaccessible for non-technical users

docs/adr/README.md

@@ -97,4 +97,7 @@ proposed → active → superseded
 | [0039](0039-git-history-for-note-dates.md) | Git history as source of truth for note creation/modification dates | active |
 | [0040](0040-custom-views-yml-filter-engine.md) | Custom Views — .laputa/views/*.yml with YAML filter engine | active |
 | [0041](0041-filekind-all-files-in-vault-scanner.md) | fileKind field — scan all vault files, not just markdown | active |
-| [0042](0042-trash-auto-purge-safety-model.md) | Trash auto-purge safety model | active |
+| [0042](0042-trash-auto-purge-safety-model.md) | Trash auto-purge safety model | superseded → [0045](0045-permanent-delete-no-trash.md) |
+| [0043](0043-reactive-vault-state-on-save.md) | Reactive vault state: editor changes propagate immediately to all UI | active |
+| [0044](0044-h1-as-title-primary-source.md) | H1 as primary title source — filename as stable identifier | active |
+| [0045](0045-permanent-delete-no-trash.md) | Permanent delete with confirm modal — no Trash system | active |

docs/ipad-prototype-2.md

@@ -1,124 +0,0 @@
-# iPad Prototype — Tauri v2 iOS Feasibility Report
-
-**Date:** 2026-03-27\
-\
-**Status:** VERIFIED — App builds, installs, and renders React UI on iPad Pro 13" simulator (iOS 18.3.1)
-
-## Summary
-
-Laputa can be ported to iPad using Tauri v2 iOS (beta) with **minimal code changes**. The React frontend stays identical. The Rust backend compiles for iOS with conditional compilation to gate desktop-only features (git CLI, menu bar, MCP, Claude CLI). Vault read/write operations work without changes.
-
-**Key result:** `tauri ios build --target aarch64-sim` succeeds. The app launches on iPad simulator and the React UI renders correctly (telemetry consent dialog, welcome screen, all styled correctly).
-
-## What Works
-
-| Feature                        | Status           | Notes                                                                 |
-| ------------------------------ | ---------------- | --------------------------------------------------------------------- |
-| Rust backend cross-compilation | VERIFIED         | Zero errors, zero warnings for `aarch64-apple-ios-sim`                |
-| Desktop build (no regressions) | VERIFIED         | 581 Rust tests pass, 2201 frontend tests pass, CodeScene gates pass   |
-| Tauri iOS project generation   | VERIFIED         | `tauri ios init` generates Xcode project successfully                 |
-| Xcode build for simulator      | VERIFIED         | `tauri ios build --target aarch64-sim` — **BUILD SUCCEEDED**          |
-| App launch on iPad simulator   | VERIFIED         | Installs and launches on iPad Pro 13" (M4), PID assigned              |
-| React UI in WebView            | VERIFIED         | Telemetry consent dialog renders with correct styling, fonts, buttons |
-| Vault file read/write          | Expected to work | Pure filesystem operations, no process spawning                       |
-| AI chat (Anthropic API)        | Expected to work | Uses `reqwest` HTTP, no CLI dependency                                |
-| Search                         | Expected to work | Pure Rust in-memory search                                            |
-| Settings persistence           | Expected to work | JSON file read/write                                                  |
-
-## What Doesn't Work (Yet)
-
-| Feature                | Blocker                      | Recommended Solution                                                                    |
-| ---------------------- | ---------------------------- | --------------------------------------------------------------------------------------- |
-| Git operations         | No `git` binary on iOS       | **Option B (Working Copy)** for prototype; **Option A (isomorphic-git)** for production |
-| GitHub clone/push/pull | Depends on git CLI           | Same as above                                                                           |
-| Claude CLI streaming   | No `claude` binary on iOS    | Use Anthropic API directly (requires new implementation)                                |
-| MCP server / WS bridge | Spawns Node.js child process | Skip for mobile; explore in-process MCP later                                           |
-| macOS menu bar         | Desktop-only API             | Touch-native navigation (already handled by React)                                      |
-| Updater plugin         | Desktop-only                 | Use TestFlight for updates                                                              |
-| File open dialog       | Different on iOS             | `tauri-plugin-dialog` supports iOS — needs testing                                      |
-
-## Changes Made
-
-### `src-tauri/src/lib.rs`
-
-* Gated `WsBridgeChild`, `run_startup_tasks`, `spawn_ws_bridge`, `log_startup_result` behind `#[cfg(desktop)]`
-* Mobile build skips MCP registration, WS bridge, and vault migrations at startup
-* Run event handler gated for desktop (child process cleanup)
-
-### `src-tauri/src/commands.rs`
-
-* Git commands: desktop implementations remain unchanged; mobile stubs return graceful errors or empty results
-* GitHub commands: desktop-only; mobile stubs return errors
-* Claude CLI commands: desktop-only; mobile stubs return `installed: false`
-* MCP commands: desktop-only; mobile stubs return `NotInstalled`
-* Menu commands: desktop-only; mobile stub is a no-op
-* Vault, frontmatter, search, AI chat, settings: **unchanged** (work on both platforms)
-
-### `src-tauri/src/lib.rs`
-
-* `pub mod menu` gated behind `#[cfg(desktop)]`
-
-### `src-tauri/capabilities/`
-
-* `default.json`: scoped to desktop platforms (`linux`, `macOS`, `windows`)
-* `mobile.json`: new file with iOS/Android permissions (core, dialog)
-
-### `src-tauri/gen/apple/`
-
-* Full Xcode project generated by `tauri ios init`
-* iPad support: all orientations enabled, arm64 architecture
-
-## Architecture: How Mobile Stubs Work
-
-```text
-Frontend (React) ──invoke──> Tauri Commands ──> Rust Backend
-                                 │
-                      ┌──────────┴──────────┐
-                  #[cfg(desktop)]       #[cfg(mobile)]
-                      │                     │
-                  Real impl            Stub (error/empty)
-                  (git CLI,            (graceful degradation)
-                   menu, MCP)
-```
-
-The frontend code doesn't change at all. Commands that aren't available on mobile return errors that the UI can handle gracefully (e.g., hiding the git sync panel, disabling commit buttons).
-
-## Git Strategy for iPad
-
-### Phase 1: Working Copy (Recommended for prototype)
-
-* User manages vault with [Working Copy](https://workingcopy.app/) (git client for iPad)
-* Laputa opens the vault via iOS Files API / FileProvider
-* Zero git code needed in Laputa — Working Copy handles sync
-* **Pro:** Works immediately, robust git implementation
-* **Con:** Requires separate app, split UX for sync
-
-### Phase 2: isomorphic-git (Production)
-
-* Pure JS git implementation running in the WebView
-* Replace `invoke("git_commit")` etc. with JS-side git operations
-* **Pro:** Integrated UX, no external dependency
-* **Con:** Slower on large vaults (~9200 files), limited advanced git features
-
-### Phase 3: git2-rs / gitoxide (Future)
-
-* Pure Rust git library compiled into the Tauri binary
-* Best performance, no JS bridge overhead
-* **Con:** Larger binary size, more integration work
-
-## Next Steps
-
-1. **Install iOS simulator runtime** — `xcodebuild -downloadPlatform iOS` (downloading ~7GB)
-2. **Full Xcode build** — `npx tauri ios build --target aarch64-sim`
-3. **Launch on iPad simulator** — `npx tauri ios dev`
-4. **Test vault read/write** — open a vault, read/edit a note
-5. **Test AI chat** — verify Anthropic API calls work from iOS WebView
-6. **Evaluate touch UX** — identify layout issues on iPad screen size
-7. **File Provider integration** — test opening vaults from Working Copy via iOS Files
-
-## Prerequisites Installed
-
-* Rust iOS targets: `aarch64-apple-ios`, `aarch64-apple-ios-sim`, `x86_64-apple-ios`
-* Xcode 16.2 with iOS 18.3.1 simulator runtime (downloading)
-* CocoaPods 1.16.2, xcodegen 2.45.3, libimobiledevice 1.4.0
-* Tauri CLI 2.10.0 with iOS support

getting-started-vault/CLAUDE.md

@@ -1,70 +1,59 @@
-# CLAUDE.md — Laputa Vault Guide
+# CLAUDE.md — Laputa Vault
 
-This file explains how Laputa vaults work so you can create and edit notes correctly.
+This is a [Laputa](https://github.com/refactoringhq/laputa-app) vault — a folder of markdown files with YAML frontmatter forming a personal knowledge graph.
 
 ## Note structure
 
-Every note is a markdown file with YAML frontmatter:
+Every note is a markdown file. The **first H1 heading in the body is the title** — there is no `title:` frontmatter field.
 
 ```yaml
 ---
-title: My Note Title        # required — do NOT use H1 in the body
-is_a: TypeName              # the note's type (must match a type file in the vault)
-status: Active              # example property
-url: https://example.com   # example property
-belongs_to: "[[Other Note]]"  # relationship via wikilink
+is_a: TypeName        # the note's type (must match the title of a type file in the vault)
+url: https://...      # example property
+belongs_to: "[[other-note]]"
 related_to:
-  - "[[Note A]]"
-  - "[[Note B]]"
+  - "[[note-a]]"
+  - "[[note-b]]"
 ---
 
-Body content in markdown. No H1 — the title is in the frontmatter.
+# Note Title
+
+Body content in markdown.
 ```
 
-**Key rules:**
-- `title` is the note's display name — never use `# H1` in the body
-- `is_a` must match the `title` of an existing type file
-- Properties are any YAML key-value pairs in the frontmatter
-- System properties are prefixed with `_` (e.g. `_pinned`, `_organized`, `_icon`) — don't show these to users
+System properties are prefixed with `_` (e.g. `_organized`, `_pinned`, `_icon`) — these are app-managed, do not set or show them to users unless specifically asked.
 
 ## Types
 
-A type is a note with `is_a: Type` in the frontmatter. It lives in the vault root:
+A type is a note with `is_a: Type`. Type files live in the vault root:
 
 ```yaml
 ---
-title: Book
 is_a: Type
-_icon: BookOpen          # Phosphor icon name
-_color: "#8b5cf6"        # hex color for sidebar
+_icon: books          # Phosphor icon name in kebab-case
+_color: "#8b5cf6"     # hex color
 ---
-Description of the type.
+
+# TypeName
 ```
 
-To create a new type: create a markdown file with `is_a: Type`.
+To find what types exist: look for files with `is_a: Type` in the vault root.
 
 ## Relationships
 
-Relationships are frontmatter properties whose values are wikilinks:
+Any frontmatter property whose value is a wikilink is a relationship. Backlinks are computed automatically.
 
-```yaml
-belongs_to: "[[Project Name]]"
-related_to:
-  - "[[Note A]]"
-  - "[[Note B]]"
-has:
-  - "[[Child Note]]"
-```
-
-Standard names: `belongs_to`, `related_to`, `has`. Custom names are allowed.
+Standard names: `belongs_to`, `related_to`, `has`. Custom names are valid.
 
 ## Wikilinks
 
-Syntax: `[[Note Title]]` or `[[filename]]`. Used for relationships and inline references.
+- `[[filename]]` or `[[Note Title]]` — link by filename or title
+- `[[filename|display text]]` — with custom display text
+- Works in frontmatter values and markdown body
 
 ## Views
 
-Saved filters stored as `.view.json` in the `views/` folder:
+Saved filters live in `views/` as `.view.json` files:
 
 ```json
 {
@@ -77,13 +66,16 @@ Saved filters stored as `.view.json` in the `views/` folder:
 }
 ```
 
-## What you can do on this vault
+## Filenames
 
-- Create/edit notes with correct frontmatter
+Use kebab-case: `my-note-title.md`. One note per file.
+
+## What you can do
+
+- Create/edit notes with correct frontmatter and H1 title
 - Create new type files
-- Add or modify relationships between notes
+- Add or modify relationships
 - Create/edit views in `views/`
-- Change `_icon` and `_color` on type files
 - Edit `CLAUDE.md` (this file)
 
-**Do not** modify app configuration files — those are local to each installation.
+Do not modify app configuration files — those are local to each installation.

prompt.txt

@@ -1,61 +0,0 @@
-Title/filename sync: derive title from filename, keep in sync via frontmatter
-
-## Goal
-Every note has a `title` field in frontmatter that stores the human-readable title with original casing and spacing. The filename is always the slug of the title. The two are kept in sync at all times within Laputa.
-
-## Current state
-`extract_title` reads the first H1 heading as the display title, with filename as fallback. This approach is fragile: H1 can diverge from the filename, and using filename directly loses casing information.
-
-## Expected behavior
-
-### Title/filename contract
-- `title` frontmatter = human-readable title (e.g. `Career Tracks Depend on Company Shape`)
-- filename = slug of title (e.g. `career-tracks-depend-on-company-shape.md`)
-- The two are always kept in sync within Laputa
-
-### On note open (sync check)
-When Laputa opens a note, it checks for desync:
-- If `title` frontmatter is absent → derive title from filename (hyphens → spaces), write it to frontmatter
-- If `title` frontmatter is present but its slug doesn't match the filename → **filename wins**: overwrite `title` with the filename-derived value
-- If both are in sync → no-op
-
-This means: edits made outside Laputa that change only the filename or only the title frontmatter are auto-corrected on next open. **Filename is the source of truth.**
-
-### On title edit (inside Laputa)
-When the user renames a note inside Laputa:
-- Update `title` frontmatter to the new value
-- Rename the file to the new slug
-- Update all wikilinks in the vault (existing rename flow)
-
-### Title display
-`extract_title` should read `title` from frontmatter (never from H1). H1 in the body is just content.
-
-## Keyboard access
-- No new keyboard interactions — title editing is part of the existing rename flow
-- QA: Cmd+P → open note → verify title in header matches frontmatter `title` field
-
-## Edge cases
-1. Note has no `title` frontmatter → derive from filename on open (silent, idempotent)
-2. `title` frontmatter desync from filename (edited outside Laputa) → filename wins, title overwritten
-3. Filename has hyphens that are actual content (e.g. `e2e-test.md`) → becomes `E2e Test` — acceptable tradeoff
-4. Fresh note created in Laputa → title set immediately from user input, filename = slug
-5. Note renamed outside Laputa (filename changed, title not) → title updated to match new filename on next open
-
-## Acceptance criteria
-- [ ] Every note has `title` in frontmatter after being opened in Laputa
-- [ ] Filename = slug of `title` at all times within Laputa
-- [ ] On open: desync is detected and resolved (filename wins)
-- [ ] `extract_title` reads from frontmatter `title`, never H1
-- [ ] Rename flow updates both `title` frontmatter and filename atomically
-- [ ] **Keyboard access:** open note → rename via title field → file renamed + wikilinks updated
-- [ ] No regressions (`pnpm test` + `cargo test` pass)
-- [ ] **Native app QA (keyboard only):** Open note → edit title → confirm filename changed + wikilinks updated; then manually desync title in a file → reopen in Laputa → confirm title auto-corrected
-
----
-CONTEXT:
-- Worktree: /Users/luca/Workspace/laputa-worktrees/title-filename-sync
-- Dev port: 5393 (use --port 5393 when running pnpm dev)
-- Run pnpm test before finishing
-- Push directly to main when done: git push origin HEAD:main — NEVER open PRs, NEVER --no-verify
-- Finish signal: openclaw system event --text 'laputa-task-done:6g9hCFpjP7qRRhqv:title-filename-sync' --mode now
-- See CLAUDE.md for all coding guidelines

src-tauri/src/vault/config_seed.rs

@@ -159,7 +159,7 @@ mod tests {
 
         assert!(vault.join("AGENTS.md").exists());
         let content = fs::read_to_string(vault.join("AGENTS.md")).unwrap();
-        assert!(content.contains("Vault Instructions for AI Agents"));
+        assert!(content.contains("Laputa Vault"));
         // Must NOT create config/ directory
         assert!(!vault.join("config").exists());
     }
@@ -205,7 +205,7 @@ mod tests {
 
         seed_config_files(vault.to_str().unwrap());
         let content = fs::read_to_string(vault.join("AGENTS.md")).unwrap();
-        assert!(content.contains("Vault Instructions for AI Agents"));
+        assert!(content.contains("Laputa Vault"));
     }
 
     #[test]
@@ -272,7 +272,7 @@ mod tests {
 
         assert!(vault.join("AGENTS.md").exists());
         let root = fs::read_to_string(vault.join("AGENTS.md")).unwrap();
-        assert!(root.contains("Vault Instructions"));
+        assert!(root.contains("Laputa Vault"));
     }
 
     #[test]
@@ -305,7 +305,7 @@ mod tests {
         assert!(!vault.join("config").exists());
 
         let agents = fs::read_to_string(vault.join("AGENTS.md")).unwrap();
-        assert!(agents.contains("Vault Instructions for AI Agents"));
+        assert!(agents.contains("Laputa Vault"));
     }
 
     #[test]

src-tauri/src/vault/getting_started.rs

@@ -18,103 +18,91 @@ struct SampleFile {
     content: &'static str,
 }
 
-/// Content for config/agents.md — vault instructions for AI agents.
-/// This file has no YAML frontmatter — it is a convention file for AI agents,
-/// not a vault note. The vault scanner will still pick it up as a regular entry.
-pub(super) const AGENTS_MD: &str = r#"# AGENTS.md — Vault Instructions for AI Agents
+/// Default AGENTS.md content — vault instructions for AI agents.
+/// Describes Laputa vault mechanics only; no vault-specific structure.
+/// The vault scanner will pick this up as a regular entry.
+pub(super) const AGENTS_MD: &str = r##"# AGENTS.md — Laputa Vault
 
-This is a [Laputa](https://github.com/refactoring-ai/laputa) vault — a folder of markdown files with YAML frontmatter that form a personal knowledge graph.
+This is a [Laputa](https://github.com/refactoringhq/laputa-app) vault — a folder of markdown files with YAML frontmatter forming a personal knowledge graph.
 
-## Structure
+## Note structure
 
-Files are organized in folders by type:
-
-| Folder | Type | Purpose |
-|--------|------|---------|
-| `note/` | Note | General-purpose documents, research, meeting notes |
-| `project/` | Project | Time-bounded efforts with clear goals |
-| `person/` | Person | People — colleagues, collaborators, contacts |
-| `topic/` | Topic | Subject areas that group related notes |
-| `responsibility/` | Responsibility | Long-running duties with KPIs |
-| `procedure/` | Procedure | Recurring workflows (weekly, monthly) |
-| `event/` | Event | Something that happened on a specific date |
-| `quarter/` | Quarter | Time containers (e.g. 24Q1) |
-| `measure/` | Measure | Trackable metrics tied to responsibilities |
-| `target/` | Target | Time-bound goals for a measure |
-| `type/` | Type | Type definitions — icon, color, ordering |
-
-Custom folders are valid — the folder name becomes the type (capitalized).
-
-## Frontmatter
-
-YAML frontmatter between `---` delimiters defines metadata:
+Every note is a markdown file. The **first H1 heading in the body is the title** — there is no `title:` frontmatter field.
 
 ```yaml
 ---
-type: Project
-Status: Active
-Owner: "[[person/jane-doe]]"
-Belongs to: "[[quarter/24q1]]"
-Related to:
-  - "[[topic/growth]]"
-  - "[[note/research-findings]]"
+is_a: TypeName        # the note's type (must match the title of a type file in the vault)
+url: https://...      # example property
+belongs_to: "[[other-note]]"
+related_to:
+  - "[[note-a]]"
+  - "[[note-b]]"
 ---
+
+# Note Title
+
+Body content in markdown.
 ```
 
-### Standard fields
+System properties are prefixed with `_` (e.g. `_organized`, `_pinned`, `_icon`) — these are app-managed, do not set or show them to users unless specifically asked.
 
-| Field | Purpose |
-|-------|---------|
-| `type` | Entity type (usually inferred from folder) |
-| `Status` | Active, Done, Paused, Archived, Dropped |
-| `Owner` | Person responsible (wikilink) |
-| `Belongs to` | Parent relationship(s) |
-| `Related to` | Lateral associations |
-| `Cadence` | For Procedures: Weekly, Monthly, etc. |
-| `aliases` | Alternative names for wikilink resolution |
+## Types
 
-### Custom fields
-
-Any YAML field containing `[[wikilinks]]` becomes a navigable relationship:
+A type is a note with `is_a: Type`. Type files live in the vault root:
 
 ```yaml
-Has Measures: ["[[measure/revenue]]", "[[measure/churn]]"]
-Resources: "[[note/api-docs]]"
+---
+is_a: Type
+_icon: books          # Phosphor icon name in kebab-case
+_color: "#8b5cf6"     # hex color
+---
+
+# TypeName
 ```
 
+To find what types exist: look for files with `is_a: Type` in the vault root.
+
+## Relationships
+
+Any frontmatter property whose value is a wikilink is a relationship. Backlinks are computed automatically.
+
+Standard names: `belongs_to`, `related_to`, `has`. Custom names are valid.
+
 ## Wikilinks
 
-Connect notes with double-bracket syntax:
+- `[[filename]]` or `[[Note Title]]` — link by filename or title
+- `[[filename|display text]]` — with custom display text
+- Works in frontmatter values and markdown body
 
-- `[[note/my-note]]` — link by path
-- `[[My Note Title]]` — link by title or alias
-- `[[note/my-note|display text]]` — link with custom display text
+## Views
 
-Wikilinks work in both frontmatter values and markdown body. Backlinks are computed automatically — linking A to B makes B show a backlink to A.
+Saved filters live in `views/` as `.view.json` files:
 
-## Type definitions
-
-Files in `type/` define entity types and control how they appear in the sidebar:
-
-```yaml
----
-type: Type
-icon: rocket-launch
-color: purple
-order: 1
----
+```json
+{
+  "title": "Active Notes",
+  "filters": [
+    {"property": "is_a", "operator": "equals", "value": "Note"},
+    {"property": "status", "operator": "equals", "value": "Active"}
+  ],
+  "sort": {"property": "title", "direction": "asc"}
+}
 ```
 
-Available colors: red, purple, blue, green, yellow, orange. Icons are Phosphor names in kebab-case.
+## Filenames
 
-## Conventions
+Use kebab-case: `my-note-title.md`. One note per file.
 
-- First `# Heading` in a file becomes its title
-- One entity per file
-- Filenames use kebab-case: `my-note-title.md`
-- Type is inferred from parent folder if not set in frontmatter
-- Relationships are bidirectional via automatic backlinks
-"#;
+## What you can do
+
+- Create/edit notes with correct frontmatter and H1 title
+- Create new type files
+- Add or modify relationships
+- Create/edit views in `views/`
+- Edit `AGENTS.md` (this file)
+
+Do not modify app configuration files — those are local to each installation.
+"##;
 
 const SAMPLE_FILES: &[SampleFile] = &[
     SampleFile {
@@ -519,12 +507,12 @@ mod tests {
         assert!(agents_path.exists(), "AGENTS.md should exist at vault root");
 
         let content = fs::read_to_string(&agents_path).unwrap();
-        assert!(content.contains("Vault Instructions for AI Agents"));
-        assert!(content.contains("## Structure"));
-        assert!(content.contains("## Frontmatter"));
+        assert!(content.contains("Laputa Vault"));
+        assert!(content.contains("## Note structure"));
+        assert!(content.contains("## Types"));
         assert!(content.contains("## Wikilinks"));
-        assert!(content.contains("## Type definitions"));
-        assert!(content.contains("## Conventions"));
+        assert!(content.contains("## Relationships"));
+        assert!(content.contains("## Views"));
         // Must NOT be a stub
         assert!(
             !content.contains("See config/agents.md"),
@@ -540,10 +528,7 @@ mod tests {
 
         let entry = crate::vault::parse_md_file(&vault_path.join("AGENTS.md"), None).unwrap();
         // H1 is now the primary title source
-        assert_eq!(
-            entry.title,
-            "AGENTS.md \u{2014} Vault Instructions for AI Agents"
-        );
+        assert_eq!(entry.title, "AGENTS.md \u{2014} Laputa Vault");
         // Config files have no frontmatter type field — type is None
         assert_eq!(entry.is_a, None);
     }

src/components/DynamicPropertiesPanel.test.tsx

@@ -617,6 +617,43 @@ describe('DynamicPropertiesPanel', () => {
       fireEvent.click(screen.getByText('Status'))
       expect(onAddProperty).toHaveBeenCalledWith('Status', '')
     })
+
+    it('auto-opens editor when property appears after clicking suggested slot', () => {
+      const addProp = vi.fn()
+      const { rerender } = render(
+        <DynamicPropertiesPanel
+          entry={makeEntry()}
+          content=""
+          frontmatter={{}}
+          onAddProperty={addProp}
+          onUpdateProperty={onUpdateProperty}
+        />
+      )
+      // Click the Status suggested slot
+      fireEvent.click(screen.getByText('Status'))
+      expect(addProp).toHaveBeenCalledWith('Status', '')
+
+      // Simulate the frontmatter being updated (as if the backend wrote it)
+      // The useEffect detects the new key in propertyEntries and sets editingKey
+      rerender(
+        <DynamicPropertiesPanel
+          entry={makeEntry()}
+          content=""
+          frontmatter={{ Status: '' }}
+          onAddProperty={addProp}
+          onUpdateProperty={onUpdateProperty}
+        />
+      )
+
+      // The suggested slot for Status should be gone
+      const remainingSlots = screen.getAllByTestId('suggested-property')
+      expect(remainingSlots.length).toBe(2) // Date and URL remain
+      // Status dropdown is portaled to body — check for it there
+      const dropdown = document.querySelector('[data-testid="status-dropdown-popover"]')
+      expect(dropdown).toBeInTheDocument()
+      const searchInput = document.querySelector('[data-testid="status-search-input"]')
+      expect(searchInput).toBeInTheDocument()
+    })
   })
 
   describe('URL property rendering', () => {

src/components/DynamicPropertiesPanel.tsx

@@ -115,9 +115,9 @@ export function DynamicPropertiesPanel({
 
   const handleSuggestedAdd = useCallback((key: string) => {
     if (!onAddProperty) return
+    // Open the editor immediately - no need to wait for frontmatter to update
+    setEditingKey(key)
     onAddProperty(key, '')
-    // Auto-focus the new property value
-    setTimeout(() => setEditingKey(key), 0)
   }, [onAddProperty, setEditingKey])
 
   return (

src/components/Editor.css

@@ -361,13 +361,13 @@
   margin-top: 2px;
 }
 
-/* When TitleField is shown (no H1 in body), hide the first H1 heading in
-   BlockNote to avoid duplicate title display. When hasH1 is set, the
-   TitleField is hidden and the H1 in the editor serves as the title. */
-.title-section:not([data-has-h1]) ~ .editor__blocknote-container [data-node-type="blockContainer"]:first-child [data-content-type="heading"][data-level="1"] {
+/* When the legacy title UI is shown, hide the first H1 heading in BlockNote
+   to avoid duplicate title display. Otherwise the editor's H1 remains visible
+   and serves as the title surface. */
+.title-section[data-title-ui-visible] ~ .editor__blocknote-container [data-node-type="blockContainer"]:first-child [data-content-type="heading"][data-level="1"] {
   display: none;
 }
-.title-section:not([data-has-h1]) ~ .editor__blocknote-container [data-node-type="blockContainer"]:first-child:has([data-content-type="heading"][data-level="1"]) {
+.title-section[data-title-ui-visible] ~ .editor__blocknote-container [data-node-type="blockContainer"]:first-child:has([data-content-type="heading"][data-level="1"]) {
   display: none;
 }
 

src/components/Editor.test.tsx

@@ -182,6 +182,33 @@ describe('Editor', () => {
     expect(screen.getByTestId('blocknote-view')).toBeInTheDocument()
   })
 
+  it('hides the legacy title field for untitled draft notes', () => {
+    const draftEntry: VaultEntry = {
+      ...mockEntry,
+      path: '/vault/untitled-note-1700000000.md',
+      filename: 'untitled-note-1700000000.md',
+      title: 'Untitled Note 1700000000',
+      hasH1: false,
+    }
+    const draftTab = {
+      entry: draftEntry,
+      content: '---\ntype: Note\nstatus: Active\n---\n',
+    }
+
+    render(
+      <Editor
+        {...defaultProps}
+        tabs={[draftTab]}
+        activeTabPath={draftEntry.path}
+        entries={[draftEntry]}
+        getNoteStatus={() => 'unsaved'}
+      />
+    )
+
+    expect(screen.queryByTestId('title-field-input')).not.toBeInTheDocument()
+    expect(screen.getByTestId('blocknote-view')).toBeInTheDocument()
+  })
+
   it('renders diff toggle button when file is modified', () => {
     render(
       <Editor

src/components/EditorContent.tsx

@@ -124,7 +124,7 @@ function bindPath(cb: ((path: string) => void) | undefined, path: string) {
 function ActiveTabBreadcrumb({ activeTab, barRef, props }: {
   activeTab: Tab
   barRef: React.RefObject<HTMLDivElement | null>
-  props: Omit<EditorContentProps, 'activeTab' | 'isLoadingNewTab' | 'entries' | 'editor' | 'onNavigateWikilink' | 'onEditorChange' | 'onRawContentChange' | 'onSave'> & { forceRawMode?: boolean }
+  props: Omit<EditorContentProps, 'activeTab' | 'isLoadingNewTab' | 'entries' | 'editor' | 'onNavigateWikilink' | 'onEditorChange' | 'onRawContentChange' | 'onSave' | 'activeStatus'> & { forceRawMode?: boolean }
 }) {
   const wordCount = countWords(activeTab.content)
   const path = activeTab.entry.path
@@ -157,6 +157,7 @@ export function EditorContent({
   activeTab, isLoadingNewTab, entries, editor,
   diffMode, diffContent, onToggleDiff,
   rawMode, onToggleRaw, onRawContentChange, onSave,
+  activeStatus,
   onNavigateWikilink, onEditorChange, vaultPath,
   rawLatestContentRef, onTitleChange,
   onSetNoteIcon, onRemoveNoteIcon,
@@ -173,6 +174,10 @@ export function EditorContent({
   const showEditor = !diffMode && !effectiveRawMode
   const entryIcon = activeTab?.entry.icon ?? null
   const emojiIcon = entryIcon && isEmoji(entryIcon) ? entryIcon : null
+  const isUntitledDraft = !!activeTab
+    && activeTab.entry.filename.startsWith('untitled-')
+    && (activeStatus === 'new' || activeStatus === 'unsaved' || activeStatus === 'pendingSave')
+  const showTitleSection = !hasH1 && !isUntitledDraft
 
   const titleSectionRef = useRef<HTMLDivElement | null>(null)
   const breadcrumbBarRef = useRef<HTMLDivElement | null>(null)
@@ -233,8 +238,8 @@ export function EditorContent({
       {showEditor && (
         <div className="editor-scroll-area" style={cssVars as React.CSSProperties}>
           <div className="editor-content-wrapper">
-            <div ref={titleSectionRef} className="title-section" data-has-h1={hasH1 || undefined}>
-              {!hasH1 && (
+            <div ref={titleSectionRef} className="title-section" data-title-ui-visible={showTitleSection || undefined}>
+              {showTitleSection && (
                 <>
                   {!emojiIcon && (
                     <div className="title-section__add-icon">

src/hooks/frontmatterOps.ts

@@ -37,9 +37,14 @@ function extractWikilinks(value: FrontmatterValue): string[] {
  */
 export type RelationshipPatch = Record<string, string[] | null>
 
+/** Properties patch: a partial update to merge into `entry.properties`.
+ *  Keys map to their new scalar values. A `null` value means "remove this key". */
+export type PropertiesPatch = Record<string, string | number | boolean | null>
+
 export interface EntryPatchResult {
   patch: Partial<VaultEntry>
   relationshipPatch: RelationshipPatch | null
+  propertiesPatch: PropertiesPatch | null
 }
 
 /** Map a frontmatter key+value to the corresponding VaultEntry field(s). */
@@ -49,7 +54,8 @@ export function frontmatterToEntryPatch(
   const k = key.toLowerCase().replace(/\s+/g, '_')
   if (op === 'delete') {
     const relPatch: RelationshipPatch = { [key]: null }
-    return { patch: ENTRY_DELETE_MAP[k] ?? {}, relationshipPatch: relPatch }
+    const propPatch: PropertiesPatch | null = !(k in ENTRY_DELETE_MAP) ? { [key]: null } : null
+    return { patch: ENTRY_DELETE_MAP[k] ?? {}, relationshipPatch: relPatch, propertiesPatch: propPatch }
   }
   const str = value != null ? String(value) : null
   const arr = Array.isArray(value) ? value.map(String) : []
@@ -73,17 +79,24 @@ export function frontmatterToEntryPatch(
   const wikilinks = value != null ? extractWikilinks(value) : []
   const relationshipPatch: RelationshipPatch | null =
     wikilinks.length > 0 ? { [key]: wikilinks } : null
-  return { patch: updates[k] ?? {}, relationshipPatch }
+  // For unknown keys (custom properties), produce a propertiesPatch
+  const isKnownKey = k in updates
+  const propertiesPatch: PropertiesPatch | null =
+    !isKnownKey && value != null ? { [key]: typeof value === 'string' || typeof value === 'number' || typeof value === 'boolean' ? value : String(value) } : null
+  return { patch: updates[k] ?? {}, relationshipPatch, propertiesPatch }
 }
 
 /** Parse frontmatter from full content and return a merged VaultEntry patch for all known fields. */
 export function contentToEntryPatch(content: string): Partial<VaultEntry> {
   const fm = parseFrontmatter(content)
   const merged: Partial<VaultEntry> = {}
+  const customProps: Record<string, string | number | boolean | null> = {}
   for (const [key, value] of Object.entries(fm)) {
-    const { patch } = frontmatterToEntryPatch('update', key, value)
+    const { patch, propertiesPatch } = frontmatterToEntryPatch('update', key, value)
     Object.assign(merged, patch)
+    if (propertiesPatch) Object.assign(customProps, propertiesPatch)
   }
+  if (Object.keys(customProps).length > 0) merged.properties = customProps
   return merged
 }
 
@@ -117,6 +130,18 @@ export interface FrontmatterOpOptions {
   silent?: boolean
 }
 
+/** Apply a properties patch by merging into the existing properties map. */
+export function applyPropertiesPatch(
+  existing: Record<string, string | number | boolean | null>, propPatch: PropertiesPatch,
+): Record<string, string | number | boolean | null> {
+  const merged = { ...existing }
+  for (const [k, v] of Object.entries(propPatch)) {
+    if (v === null) delete merged[k]
+    else merged[k] = v
+  }
+  return merged
+}
+
 /** Apply a relationship patch by merging into the existing relationships map. */
 export function applyRelationshipPatch(
   existing: Record<string, string[]>, relPatch: RelationshipPatch,
@@ -144,12 +169,17 @@ export async function runFrontmatterAndApply(
   try {
     const newContent = await executeFrontmatterOp(op, path, key, value)
     callbacks.updateTab(path, newContent)
-    const { patch, relationshipPatch } = frontmatterToEntryPatch(op, key, value)
+    const { patch, relationshipPatch, propertiesPatch } = frontmatterToEntryPatch(op, key, value)
     const fullPatch = { ...patch }
-    if (relationshipPatch && callbacks.getEntry) {
+    if ((relationshipPatch || propertiesPatch) && callbacks.getEntry) {
       const current = callbacks.getEntry(path)
       if (current) {
-        fullPatch.relationships = applyRelationshipPatch(current.relationships, relationshipPatch)
+        if (relationshipPatch) {
+          fullPatch.relationships = applyRelationshipPatch(current.relationships, relationshipPatch)
+        }
+        if (propertiesPatch) {
+          fullPatch.properties = applyPropertiesPatch(current.properties, propertiesPatch)
+        }
       }
     }
     if (Object.keys(fullPatch).length > 0) callbacks.updateEntry(path, fullPatch)

src/hooks/useNoteActions.test.ts

@@ -373,9 +373,10 @@ describe('frontmatterToEntryPatch', () => {
     expect(result.relationshipPatch).toEqual({ 'Belongs to': ['[[x]]'] })
   })
 
-  it('returns empty patch for unknown non-wikilink keys', () => {
+  it('returns propertiesPatch for unknown non-wikilink keys', () => {
     const result = frontmatterToEntryPatch('update', 'custom_field', 'value')
     expect(result.patch).toEqual({})
+    expect(result.propertiesPatch).toEqual({ custom_field: 'value' })
     // Non-wikilink value → no relationship change
     expect(result.relationshipPatch).toBeNull()
   })
@@ -417,10 +418,11 @@ describe('frontmatterToEntryPatch', () => {
     expect(result.patch).toEqual({ listPropertiesDisplay: [] })
   })
 
-  it('returns empty patch for unknown key on delete, with relationship removal', () => {
+  it('returns empty patch for unknown key on delete, with relationship and properties removal', () => {
     const result = frontmatterToEntryPatch('delete', 'unknown_key')
     expect(result.patch).toEqual({})
     expect(result.relationshipPatch).toEqual({ unknown_key: null })
+    expect(result.propertiesPatch).toEqual({ unknown_key: null })
   })
 
   it('delete of known key also produces relationship removal', () => {
@@ -490,9 +492,9 @@ describe('contentToEntryPatch', () => {
     expect(contentToEntryPatch(content)).toEqual({ isA: 'Type', sidebarLabel: 'Projects' })
   })
 
-  it('ignores unknown frontmatter keys', () => {
+  it('includes custom frontmatter keys in properties patch', () => {
     const content = '---\ntype: Note\ncustom: value\n---\n'
-    expect(contentToEntryPatch(content)).toEqual({ isA: 'Note' })
+    expect(contentToEntryPatch(content)).toEqual({ isA: 'Note', properties: { custom: 'value' } })
   })
 
   it('preserves _favorite_index as a number (not null)', () => {

untitled-key-result.md

@@ -1,8 +0,0 @@
----
-title: Untitled key result
-type: Key Result
-status: Active
----
-
-# Untitled key result
-

untitled-note-134-2.md

@@ -1,6 +0,0 @@
----
-title: Untitled note 134
-type: Note
-status: Active
----
-# Untitled note 130

untitled-note-134-3.md

@@ -1,6 +0,0 @@
----
-title: Untitled note 134
-type: Note
-status: Active
----
-# This is a very long title that should wrap onto multiple lines in the editor

untitled-note-134-4.md

@@ -1,8 +0,0 @@
----
-title: Untitled note 134
-type: Note
-status: Active
----
-
-# Untitled note 130
-

untitled-note-134.md

@@ -1,8 +0,0 @@
----
-title: Untitled note 134
-type: Note
-status: Active
----
-
-# Untitled note 130
-

untitled-note-23.md

@@ -1,8 +0,0 @@
----
-title: Untitled note 23
-type: Note
-status: Active
----
-
-# Untitled note 23
-

untitled-note-4-2.md

@@ -1,8 +0,0 @@
----
-title: Untitled note 4
-type: Note
-status: Active
----
-
-# Untitled note 18
-

untitled-note-4.md

@@ -1,8 +0,0 @@
----
-title: Untitled note 4
-type: Note
-status: Active
----
-
-# Untitled note 4
-

untitled-project-10.md

@@ -1,18 +0,0 @@
----
-title: Untitled project 10
-type: Project
-status: Active
----
-
-# Untitled project 10
-
-## Objective
-
-
-
-## Key Results
-
-
-
-## Notes
-

untitled-project-11.md

@@ -1,18 +0,0 @@
----
-title: Untitled project 11
-type: Project
-status: Active
----
-
-# Untitled project 11
-
-## Objective
-
-
-
-## Key Results
-
-
-
-## Notes
-

untitled-project-14-2.md

@@ -1,18 +0,0 @@
----
-title: Untitled project 14
-type: Project
-status: Active
----
-
-# Untitled project 15
-
-## Objective
-
-
-
-## Key Results
-
-
-
-## Notes
-

untitled-project-14.md

@@ -1,18 +0,0 @@
----
-title: Untitled project 14
-type: Project
-status: Active
----
-
-# Untitled project 14
-
-## Objective
-
-
-
-## Key Results
-
-
-
-## Notes
-

untitled-project-3.md

@@ -1,18 +0,0 @@
----
-title: Untitled project 3
-type: Project
-status: Active
----
-
-# Untitled project 3
-
-## Objective
-
-
-
-## Key Results
-
-
-
-## Notes
-

untitled-project-8.md

@@ -1,18 +0,0 @@
----
-title: Untitled project 8
-type: Project
-status: Active
----
-
-# Untitled project 8
-
-## Objective
-
-
-
-## Key Results
-
-
-
-## Notes
-

untitled-project-9.md

@@ -1,18 +0,0 @@
----
-title: Untitled project 9
-type: Project
-status: Active
----
-
-# Untitled project 9
-
-## Objective
-
-
-
-## Key Results
-
-
-
-## Notes
-

untitled-video.md

@@ -1,8 +0,0 @@
----
-title: Untitled video
-type: Video
-status: Active
----
-
-# Untitled video
-