pi-weave 0.2.0 → 0.2.1

package/README.md

@@ -147,15 +147,19 @@ Renaming or moving a note rewrites its inbound links automatically, so its backl
 The browser workspace has four connected views:
 
 - **Tree** — notes, folders, and repository structure, with text and provenance filters.
-- **Note** — rendered Markdown with clickable `[[wikilinks]]`, link previews, tags, authorship, and an action to open the source in
-  `$EDITOR`.
+- **Note** — rendered Markdown with clickable `[[wikilinks]]`, link previews, tags, authorship, click-to-edit, and an action to open the
+  source in `$EDITOR`.
 - **Graph** — a navigable map of notes, links, mentions, modules, and repository relationships. Selecting something updates every view.
 - **Context** — links, backlinks, tags, and code mentions for the current selection.
 
 Search with `⌘K` / `Ctrl K`. Press `?` for all shortcuts. The workspace updates as notes change on disk, so a note written by Pi appears
 without a reload. It follows the system theme by default and can be switched between light and dark.
 
-The browser is read-only. Edit with `$EDITOR`, Obsidian, or the `weave_note` tool; unknown front-matter fields remain preserved.
+**Click the note text to edit it** — the prose swaps for its Markdown source; `⌘S` / `Ctrl S` saves, `Esc` or **Done** closes. Selecting
+text to copy and clicking a `[[wikilink]]` do what they always did; neither opens the editor. A save rewrites the body and nothing
+else — unknown front-matter fields, key order, and the append-only `## Raw` tail of a dictated note all survive untouched, so a note edited
+here and a note edited in Obsidian stay byte-compatible. Editing with `$EDITOR`, Obsidian, or the `weave_note` tool works as before; the
+last writer wins, and the workspace picks up outside changes within a couple of seconds.
 
 `/weave-view tui` is the smaller, read-only terminal explorer: tree, focused neighborhood, details, and link health over the same graph.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-weave",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "An agent-native knowledge workspace for your life and your code. Smart notepad + repository exploration, readable by humans and agents alike.",
   "type": "module",
   "sideEffects": false,

package/src/core/index.ts

@@ -59,6 +59,7 @@ export {
   resolveHtmlPath,
   resolveNotePath,
   searchNotes,
+  setNoteBody,
   upsertNote,
   type LinkRepairResult,
 } from "./vault";

package/src/core/links/repair.ts

@@ -99,7 +99,7 @@ const RAW_HEADING_RE = new RegExp(`^${RAW_NOTES_HEADING}[ \\t]*\\r?$`, "m");
  * inside a ```` block would too — and each mistake ends the protected region
  * early, exposing example links in documentation to rewriting.
  */
-function fenceRanges(body: string): [number, number][] {
+export function fenceRanges(body: string): [number, number][] {
   const ranges: [number, number][] = [];
   let open: { at: number; marker: string; length: number } | null = null;
   for (const match of body.matchAll(FENCE_RE)) {
@@ -134,7 +134,7 @@ function fenceRanges(body: string): [number, number][] {
  * refuse to repair — every link below it. Matching a whole heading line also
  * keeps `## Rawhide` from starting a tail.
  */
-function rawTailStart(body: string, fences: readonly [number, number][]): number {
+export function rawTailStart(body: string, fences: readonly [number, number][]): number {
   let from = 0;
   for (;;) {
     const rest = body.slice(from);

package/src/core/vault.ts

@@ -10,7 +10,7 @@ import {
   unquoteField,
   upsertFrontMatterFields,
 } from "./frontmatter";
-import { auditLinks, rewriteLinks, RAW_NOTES_HEADING, type LinkAudit, type LinkFix } from "./links/repair";
+import { auditLinks, fenceRanges, rawTailStart, rewriteLinks, RAW_NOTES_HEADING, type LinkAudit, type LinkFix } from "./links/repair";
 import { withMutationQueue } from "./mutex";
 import { NOTES_DIR, OKF_MANIFEST } from "./paths";
 import { slugify, uniqueSlug } from "./slug";
@@ -596,6 +596,51 @@ export async function repairVaultLinks(root: string, options: { apply?: boolean
   });
 }
 
+/**
+ * Keep the on-disk `## Raw` tail whatever the body says — it is append-only.
+ * `rawTailStart`, not `extractRawTail`: fence-aware, for untrusted input.
+ */
+function preserveRawTail(currentBody: string, nextBody: string): string {
+  const tail = currentBody.slice(tailBoundary(currentBody)).trimEnd();
+  const head = nextBody.slice(0, tailBoundary(nextBody)).trim();
+  if (tail === "") return head;
+  // An emptied head leaves the tail alone, not a leading blank line.
+  return head === "" ? tail : `${head}\n\n${tail}`;
+}
+
+/** A `---` rule, alone on the line, with only blank space after it. */
+const TAIL_RULE_RE = /(?:^|\n)-{3,}[ \t]*\r?\n\s*$/;
+
+/**
+ * Where the tail's text begins — the `---` rule, not the heading
+ * `rawTailStart` returns. Splitting at the heading orphans the rule.
+ */
+function tailBoundary(body: string): number {
+  const heading = rawTailStart(body, fenceRanges(body));
+  if (heading === body.length) return heading;
+  const rule = TAIL_RULE_RE.exec(body.slice(0, heading));
+  if (rule === null) return heading;
+  // `index` is the newline before the rule when there is one; step over it.
+  return rule.index === 0 && !body.startsWith("\n") ? 0 : rule.index + 1;
+}
+
+/**
+ * Replace a note's Markdown body; unknown front matter rides on
+ * `note.frontMatter` and only `updated` moves. Last write wins — no
+ * `expectedRevision`; docs/weave-workspace.md §11 P5.3 argues the trade.
+ */
+export async function setNoteBody(root: string, slug: string, body: string, now = new Date()): Promise<VaultMutationResult> {
+  const path = resolveNotePath(root, slug);
+  if (path === null) return { ok: false, reason: "invalid" };
+  return withVaultLock(root, async () => {
+    const note = await getNote(root, slug);
+    if (note === null) return { ok: false, reason: "missing" };
+    const next = preserveRawTail(note.body, body);
+    await writeNote(path, slug, { ...note, updated: now.toISOString() }, next, note.frontMatter);
+    return { ok: true, slug };
+  });
+}
+
 /** Rename a note in place and keep its front-matter title in sync. */
 export async function renameNote(root: string, slug: string, name: string, now = new Date()): Promise<VaultMutationResult> {
   const from = resolveNotePath(root, slug);

package/src/web/client/api.ts

@@ -323,6 +323,12 @@ function mutation(fetchImpl: FetchLike, url: string, method: string, body?: unkn
 const noteUrl = (slug: string, suffix = ""): string => `/api/note/${encodeURIComponent(slug)}${suffix}`;
 const folderUrl = (path: string, suffix = ""): string => `/api/folder/${path.split("/").map(encodeURIComponent).join("/")}${suffix}`;
 
+/**
+ * `POST /api/note/:slug` — save the note's Markdown body. No revision
+ * (last-write-wins, see core's `setNoteBody`), and a `MutationResult` rather
+ * than the note: the poll is what puts the new text back on screen.
+ */
+export const saveNote = (fetchImpl: FetchLike, slug: string, body: string) => mutation(fetchImpl, noteUrl(slug), "POST", { body });
 export const renameNote = (fetchImpl: FetchLike, slug: string, name: string) => mutation(fetchImpl, noteUrl(slug, "/rename"), "POST", { name });
 export const moveNote = (fetchImpl: FetchLike, slug: string, folder: string | null) => mutation(fetchImpl, noteUrl(slug, "/move"), "POST", { folder });
 export const deleteNote = (fetchImpl: FetchLike, slug: string) => mutation(fetchImpl, noteUrl(slug), "DELETE");