P2: Close Notes, Journal, Tasks and Calendar workflow gaps across CLI and tools #839

Open
opened 2026-10-02 13:23:11 +00:00 by kayg · 0 comments
Owner

Research follow-up under #484. Source snapshot: c4a61e8cf090170f35b1bed3350d9de20c83ecd5.

These areas have raw generated adapters and several named CLI commands. They still need intent-level parity.

Evidence:

  • Named CLI Note commands are new/open/append; Task commands are new/done/reopen. Calendar named commands cover feeds/subscriptions; Event CRUD, metadata and range queries remain raw actions.
  • NoteView.svelte:makeNoteFromBlock creates a Note, then rewrites its source editor and polls for save. It is not one server intent.
  • Block format/move/duplicate/delete use editor transactions; update_body provides only full-body parity.
  • settings/editor/EditorSection.svelte stores makeNoteChildren only in the browser. It changes data behavior and is not a looks-only exemption.
  • Calendar/Files Undo uses browser inverse state; agent-turn and wikilink Undo have dedicated routes.

Acceptance:

  1. Reuse the registry for discoverable Note metadata/retitle/move/trash, Journal edits/attachments, Task scheduling/recurrence and Event/range operations. Do not duplicate business logic.
  2. Move the decided Make-a-Note/block intent to a single server operation with stable identities, revision checks and appropriate Undo; expose it through all surfaces.
  3. Add the behavior preference through the server, retaining its current safe default.
  4. Prove stale revisions, concurrent source changes, successful edits and linked results through every adapter.
  5. Keep presentation/cursor gestures exempt and OPEN editor decisions unbuilt. Coordinate the concrete schema collision with the contract gap issue.

Matrix N1–N12, T1–T2, C1–C6; #484 and DESIGN §§41–42. Full-body raw writes do not prove stable block workflow parity.

Full evidence and decisions: docs/research/agent-surfaces.md on branch job/research-surfaces. No runtime change was made by the research job.

Research follow-up under #484. Source snapshot: `c4a61e8cf090170f35b1bed3350d9de20c83ecd5`. These areas have raw generated adapters and several named CLI commands. They still need intent-level parity. Evidence: - Named CLI Note commands are new/open/append; Task commands are new/done/reopen. Calendar named commands cover feeds/subscriptions; Event CRUD, metadata and range queries remain raw actions. - `NoteView.svelte:makeNoteFromBlock` creates a Note, then rewrites its source editor and polls for save. It is not one server intent. - Block format/move/duplicate/delete use editor transactions; `update_body` provides only full-body parity. - `settings/editor/EditorSection.svelte` stores `makeNoteChildren` only in the browser. It changes data behavior and is not a looks-only exemption. - Calendar/Files Undo uses browser inverse state; agent-turn and wikilink Undo have dedicated routes. Acceptance: 1. Reuse the registry for discoverable Note metadata/retitle/move/trash, Journal edits/attachments, Task scheduling/recurrence and Event/range operations. Do not duplicate business logic. 2. Move the decided Make-a-Note/block intent to a single server operation with stable identities, revision checks and appropriate Undo; expose it through all surfaces. 3. Add the behavior preference through the server, retaining its current safe default. 4. Prove stale revisions, concurrent source changes, successful edits and linked results through every adapter. 5. Keep presentation/cursor gestures exempt and OPEN editor decisions unbuilt. Coordinate the concrete schema collision with the contract gap issue. Matrix N1–N12, T1–T2, C1–C6; #484 and DESIGN §§41–42. Full-body raw writes do not prove stable block workflow parity. Full evidence and decisions: `docs/research/agent-surfaces.md` on branch `job/research-surfaces`. No runtime change was made by the research job.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#839
No description provided.