[shovon]

Closes #112. Closes #113.

What changed

Builders (packages/pages/pages.ts): blockEdited(id, text), blockDeleted(id), blockIndented(payload) and blockOutdented(payload) join blockCreated. Each returns { v, type, payload }, with the payload typed against the schema and v from HANDLES, and reads no clock and no randomness.

Commands: editBlock, deleteBlock, indentBlock and outdentBlock (and addBlock) now check against the fold, build and dispatch. append stays as a one-line wrapper that dispatches a built event.

How predict takes them: a builder returns the schema's own variant of PageEvent with v added (blockCreated used to return the whole PageEvent["type"] union, which did not narrow). That is a PageEvent by width, so predict is unchanged and takes a builder's result as it is. PageEvent stays the one shape for "an event this fold reads".

Renderer: the [event, send] pairs move to app/src/renderer/project/PageView/steps/steps.ts, one function per write: add, edit, remove, indent and outdent. Each builds its event with the package's builder and takes only the bridge call it makes (Pick<PagesApi, …>). PageView.tsx no longer writes any `${NAMESPACE}block.*` literal. moving is now a one-line choice between indent and outdent.

Queries (#113): getPage, getPages, getReferences, getPreviews, searchPages and locateBlock take Pages, not PagesView. getPage absorbs pageOf, which was the same function. The PagesView comment loses the line about leaving dispatch throwing. Call sites in pages-store.ts, pages-session.ts, the CLI test and the store test pass view.state.

Docs: app/CLAUDE.md and the package README name the builders and say the queries take the state.

For the reviewer

• Pages, not { state }: the bare state made every call site the same or simpler. pages-session.ts reads (await open.require()).state, and the CLI test and blocks.test.ts lose a stub dispatch.
• No behaviour change. The predicted events are the same as before plus a v field, which predict and reduce don't read.
• steps is only about pairing an event with its call, so Pull block placement and caret rules out of PageView and ProjectView #116 can build on it. indent and outdent resolve the move with indented/outdented, since the event can't be built without that.
• Left alone: getState in pages-store.ts still takes the app's PagesView and reads only .state from it. It's the app's function, not one of the package queries, so it's outside pages: queries take the fold state, not the whole view #113. It could be narrowed the same way later.
• Move the open-project and pages-session logic out of the IPC files (#114) #122 had already merged when this branch was cut, so this is on top of pages-session.ts and there's nothing to merge in.

Tests

• pages.test.ts:
  • Each command, run on a small outline, writes exactly its builder's event.
  • That event, folded through pagesFold.reduce over the state before, gives the same pages the command left.
  • Each builder's v equals HANDLES[type], and there is one builder for every type in HANDLES.
• steps.test.ts (new):
  • Each step's event equals the package builder's.
  • Its send makes the matching bridge call with the same arguments.
  • A move with nowhere to go is no step.
• Existing tests updated to the new query shape (pages.test.ts, blocks.test.ts, pages-store.test.ts, cli.test.ts).
• npm test at the root (all workspaces pass), plus npm run typecheck and npm run lint in app/, all pass.
• Not run in the app or Storybook. The change to PageView is covered by the typecheck and the steps test.

🤖 Generated with Claude Code