Updates

docs/obsidian.md

@@ -58,10 +58,44 @@ another process running as the same user. Avoid concurrent automated writers:
 revision checks detect edits made before the check, not every possible filesystem
 race with another application.
 
-Files are limited to 2 MiB per bridge operation. Listings stop at 10,000 visited
-entries or 32 levels. Search scans Markdown, up to 32 MiB and 50 matches, and
-reports truncation. Larger attachments can remain in the vault but cannot be
-read or managed through this bounded bridge.
+Reads have no total file-size limit. Each read returns up to 1 KiB, with byte
+`offset`, `nextOffset`, `complete`, total `bytes`, and a full-file SHA-256
+`revision`. Continue with `offset: nextOffset` and that revision until
+`complete: true`; changed revisions require restarting the read. UTF-8 pages
+preserve character boundaries. Decode each base64 page separately before joining
+binary data. Writes remain limited to 2 MiB. Listings and searches return pages
+of up to 20 directory entries; continue with `nextOffset` until null, even when a
+search page has no matches. Search scans full Markdown files, including large
+notes, and memory search covers the entire accessible vault.
+
+Vault results receive a separate 16,000-character harness allowance so ordinary
+read pages and their continuation metadata survive voice tool-result clipping.
+Context compaction and turn budgets still apply: the agent must disclose partial
+coverage and resume by path, revision and offset instead of claiming completeness.
+Hidden configuration and linked files remain excluded by the existing boundary.
+
+## Note and memory conventions
+
+The agent searches vault memory at the start of tasks and reads relevant notes
+fully. Its system guidance requires explicit authorization for concrete writes,
+including saving memory; a user request to save specified content provides that
+authorization. These semantic rules are agent guidance, not filesystem ACLs.
+Existing built-in tool permission gates also remain in effect.
+
+Conflicting historical folder/naming policies are reconciled by preserving
+existing notes and preferring their established folders. New categories default
+to `articles/`, `memorandums/`, `notes/`, and `memory/`; new filenames use
+kebab-case. Three directory levels and twenty direct subfolders are the guidance
+limits. Existing notes are not automatically migrated. New notes use YAML title,
+created, lastModified, category and tags (a list). Daily entries are append-only.
+
+Search before creating duplicate notes; use meaningful, verified
+[[vault-relative/note|label]] links and project indexes. Obsidian automatically
+provides backlinks; renaming through this bridge still requires explicit updates
+to referencing notes. See Obsidian's [internal links](https://obsidian.md/help/links)
+and [properties](https://obsidian.md/help/properties) documentation. Article notes
+retain sourceUrl and distinguish original text from summaries. Base64 is encoding,
+not encryption; secrets belong in an approved encrypted store.
 
 ## Configuration and verification