Agent Board
b798f628ee
Persist PageTree expand state via control-plane view-state and align chevron/DOM with restored expansion; keep Sidex-style shallow page-tree scan and drop the unused recursive scanner that only added cargo noise. Add password vault workbench routes/runtime/skill/CLI, split page_ai_pi into a module package, and retire Hermes/ACP/OpenHub recycle + root harness evidence from the index while gitignoring recycle and local diag dumps. Archive superseded design/bugs docs under old/, point architecture at ARCHITECTURE.md, and refresh smokes for Pi S1–S7, vault, and editor regressions so the working tree can stay clean.
14 lines
1.1 KiB
Markdown
14 lines
1.1 KiB
Markdown
# MNote local file editing
|
|
|
|
Use this skill only when the user asks to read, edit, summarize, search, or patch files in the current MNote workspace.
|
|
|
|
Rules:
|
|
- Stay inside allowed roots returned by MNote.
|
|
- Use `mnote.context.snapshot` or `mnote.context.resolve_target` to locate the workspace root, current document, and allowed context.
|
|
- Prefer the agent runtime's own local file read/edit capability for Markdown files inside allowed roots.
|
|
- Before writing, resolve the target and read the relevant file content with the agent's native file tools.
|
|
- After writing, read the file back with the agent's native file tools and report changed files.
|
|
- Do not use MNote file tools for pure chat.
|
|
- If authorization is missing, ask the user to grant access instead of guessing a path.
|
|
- **Password vault is forbidden:** never read, write, list, patch, or search `.mnote/vault/**` (entries, cipher-book, index, audit, trash, attachments) via local file tools or generic open/resource APIs. Credentials and cipher fragments go through the password vault UI / `mnote.vault.*` (see skill `mnote-vault`) and share-to-ai — not this skill.
|