docs(integrations): document OpenClaw note metadata

Signed-off-by: Beru <beru@lastguru.lv>

Author: beru-ant-king

integrations/openclaw/CLAUDE.md

@@ -198,7 +198,12 @@ read_note(identifier="decisions/auth-strategy", project="backend")
 ### `write_note`
 **Purpose**: Create new notes in the knowledge graph
 **When to use**: When users share important information, make decisions, or want to save insights for later
-**Best practices**: Use clear titles, organize in appropriate folders, structure with headings
+**Best practices**: Use clear titles, organize in appropriate folders, structure the Markdown body with headings, and pass frontmatter through the dedicated parameters instead of embedding YAML in `content`
+
+**Frontmatter parameters**:
+- `tags`: A string array or comma-separated string
+- `note_type`: The note type stored as `type`; defaults to `note`
+- `metadata`: Additional frontmatter fields, including nested objects
 
 **Examples**:
 ```
@@ -231,6 +236,12 @@ We chose JWT tokens with refresh token rotation.
 write_note(
   title="Client Meeting - February 8, 2024",
   folder="meetings",
+  tags=["client", "planning"],
+  note_type="Meeting",
+  metadata={
+    "status": "complete",
+    "attendees": ["John", "Sarah"],
+  },
   content="""
 # Client Meeting - February 8, 2024
 
@@ -256,6 +267,7 @@ write_note(
 **Purpose**: Modify existing notes incrementally
 **When to use**: To add updates, fix information, or organize existing content
 **Operations**: append, prepend, find_replace, replace_section
+**Frontmatter updates**: Pass `metadata` to merge custom frontmatter fields in the same call. Provided keys replace existing values, unrelated fields remain unchanged, and nested objects are supported.
 
 **Examples**:
 ```
@@ -276,6 +288,7 @@ edit_note(
   identifier="weekly-review",
   operation="replace_section",
   section="## This Week",
+  metadata={"status": "review", "progress": {"completed": 4, "total": 6}},
   content="""## This Week
 - Completed API authentication
 - Client meeting went well

integrations/openclaw/MEMORY_TASK_FLOW.md

@@ -104,14 +104,10 @@ This fallback behavior keeps tasks discoverable even if the graph index is stale
 write_note(
   title="migrate-auth-routes",
   folder="tasks",
-  content="""---
-title: migrate-auth-routes
-type: Task
-status: active
-current_step: 1
----
-
-## Context
+  note_type="Task",
+  tags=["auth", "migration"],
+  metadata={"status": "active", "current_step": 1},
+  content="""## Context
 Starting auth route migration.
 
 ## Plan
@@ -122,12 +118,35 @@ Starting auth route migration.
 
 ### Advance a task
 
-- Update plan checkboxes with `edit_note` + `replace_section`
-- Bump step with `edit_note` + `find_replace` (for `current_step`)
+Update the plan and its frontmatter state together:
+
+```
+edit_note(
+  identifier="tasks/migrate-auth-routes",
+  operation="replace_section",
+  section="## Plan",
+  metadata={"current_step": 2},
+  content="""## Plan
+- [x] Implement middleware
+- [ ] Add tests"""
+)
+```
 
 ### Complete a task
 
-Use `edit_note` (`find_replace`) to change `status: active` to `status: done`.
+Record the outcome while setting the structured status field:
+
+```
+edit_note(
+  identifier="tasks/migrate-auth-routes",
+  operation="append",
+  metadata={"status": "done"},
+  content="""
+
+## Outcome
+Migration completed and verified."""
+)
+```
 
 ## Operational Tips
 

integrations/openclaw/README.md

@@ -161,8 +161,8 @@ All tools accept an optional `project` parameter for cross-project operations.
 | `memory_get` | Read a specific note by title or path |
 | `search_notes` | Search the knowledge graph directly |
 | `read_note` | Read a note by title, permalink, or `memory://` URL |
-| `write_note` | Create or update a note |
-| `edit_note` | Append, prepend, find/replace, or replace a section |
+| `write_note` | Create or overwrite a note with optional tags, note type, and custom frontmatter metadata |
+| `edit_note` | Append, prepend, replace content, and merge custom frontmatter metadata |
 | `delete_note` | Delete a note |
 | `move_note` | Move a note to a different folder |
 | `build_context` | Navigate the knowledge graph — follow relations and connections |
@@ -172,6 +172,22 @@ All tools accept an optional `project` parameter for cross-project operations.
 | `schema_infer` | Analyze notes and suggest a schema |
 | `schema_diff` | Detect drift between schema and actual usage |
 
+Use the dedicated frontmatter parameters when creating structured notes:
+
+```
+write_note(
+  title="auth-middleware-rollout",
+  folder="tasks",
+  note_type="Task",
+  tags=["auth", "rollout"],
+  metadata={"status": "active", "current_step": 2},
+  content="""## Context
+Rolling JWT middleware to all API routes."""
+)
+```
+
+`edit_note` accepts `metadata` alongside any edit operation, so content and frontmatter state can be updated in one call. Metadata keys supplied by the caller are merged into existing frontmatter; unrelated fields remain unchanged.
+
 ## Slash commands
 
 | Command | Description |