8000 V0-07: Reconnect tiling and kanban to durable projections by kiran-brahma · Pull Request #26 · kiran-brahma/nodepad-app · GitHub
[go: up one dir, main page]

Skip to content

V0-07: Reconnect tiling and kanban to durable projections - #26

Merged
kiran-brahma merged 1 commit into
mainfrom
claude/github-issue-8-ef713a
Jul 23, 2026
Merged

kiran-brahma merged 1 commit into
mainfrom
claude/github-issue-8-ef713a

Conversation

@kiran-brahma
Copy link
Copy Markdown
Owner

Closes #8.

What this does

Tiling and kanban are two ways of reading the same committed Notes. Both consume one projection of the active Thinking Workspace and both place the same Note card, so a view can decide where a Note appears but never what may be done to it.

  • src/note-views.ts (new) holds every arrangement decision as pure functions over committed Notes: the active-Workspace result set (pinned first, stable creation order, narrowed by any search), the tiling pages and their halving arrangement, the kanban columns, and whether a selection survives a view switch.
  • src/App.tsx gains a view chooser and the two layouts. The Note card became one closure both layouts place, so mutation policy has a single home.
  • Tiling arranges each page by repeated halving, alternating direction with depth. Kanban gives one column per Note Type present, in the order NOTE_TYPES declares, so no empty or stale column can appear.
  • Nothing about arrangement is committed: no coordinate, page, column, or view choice. A restart reconstructs both views from SQLite alone.

Decisions worth reviewing

  • Search now narrows both views instead of rendering its own list of snippets. A search result contributes only a noteId; Note content is always read from the committed Note, so a found Note is never a second copy of the thinking. Note Type and matched Labels still show, on the Note card itself.
  • The task-typed sticky header and the "Enriching" column from the pre-durable views are dropped. Neither has a referent in the durable model — task is one of fourteen equal Note Types and enrichment is not in V0.
  • Minimap and animation are not carried over. The issue permits them ("may be retained") but they need scroll observers and layout measurement that can only be tested by asserting on pixels, which the testing decisions rule out. Nothing here blocks adding them later: a minimap reads the same page projection the view renders.
  • Note cards carry role="article", not role="listitem". Neither view nests a card directly under its group, so list semantics would have claimed an ownership that does not exist in the DOM.

Testing

  • src/note-views.test.ts — the projections as pure outcomes from a committed snapshot: Workspace isolation, pinned order, search narrowing, page filling, arrangement of one and many Notes, column order and grouping, selection preservation.
  • src/App.test.tsx — through the DOM: edit in one view and read it in the other, grouping by Note Type, selection kept across a switch and let go when the Note leaves, search filtering with pinned order in both views, empty/one-Note/many-Note states, and a restart. No test asserts a pixel, a size, or an animation.
  • npm run check passes (typecheck, lint, vitest, cargo test, Tauri smoke build).

Notes for review

The pre-implementation audit is at docs/v0/audits/08-tiling-kanban.md. Scoped fallow reports App and the Note card as large, complex functions; both are the pre-existing shape of the surface rather than something this slice introduced, and splitting the card is what would duplicate mutation policy.

🤖 Generated with Claude Code

Tiling and kanban are two ways of reading the same committed Notes. Both
consume one projection of the active Thinking Workspace — pinned first,
stable creation order, narrowed by any active search — and both place the
same Note card, so mutation policy has one home and a view can only decide
where a Note appears, never what may be done to it.

Tiling arranges each page by repeated halving, alternating direction with
depth. Kanban gives one column per Note Type present, in the fixed order
the durable interface declares. Neither stores a coordinate, a page, a
column, or the view choice itself, so a restart reconstructs both views
from SQLite alone.

Search now narrows both views instead of rendering a separate list of
snippets, so a found Note is never a second copy of the thinking.

Closes #8
@kiran-brahma
kiran-brahma merged commit 93dca1a into main Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

V0-07: Reconnect tiling and kanban to durable projections

1 participant

0