diff --git a/dist/mappa-knowledge.skill b/dist/mappa-knowledge.skill
index cb4ea02..7a57ae8 100644
Binary files a/dist/mappa-knowledge.skill and b/dist/mappa-knowledge.skill differ
diff --git a/dist/mappa-task-work.skill b/dist/mappa-task-work.skill
index 9390ccc..398d553 100644
Binary files a/dist/mappa-task-work.skill and b/dist/mappa-task-work.skill differ
diff --git a/skills/mappa-knowledge/SKILL.md b/skills/mappa-knowledge/SKILL.md
index 833e5c5..85f6f99 100644
--- a/skills/mappa-knowledge/SKILL.md
+++ b/skills/mappa-knowledge/SKILL.md
@@ -1,7 +1,7 @@
 ---
 name: mappa-knowledge
 author: ours
-version: 1.5.2
+version: 1.5.3
 description: >
   The cycle of working with a project's knowledge in Mappa (Karpathy LLM Wiki,
   channel = mappa entities): ingest → query → lint + a graph layer for
@@ -70,7 +70,7 @@ don't improvise the structure, the first ingest creates `AGENTS`
 | Search pages | `mcp__mappa__entity_search(q, type='wiki', project?, scope?, limit)` | ILIKE over body/title (full bodies) |
 | Card search | `mcp__mappa__wiki.search(q, scope?, project?, projects?, limit?)` | cards {ref, project, slug, title, summary, snippet, related} — without bodies (wiki:2661) |
 | Create a page | `mcp__mappa__wiki_create(project, slug, body)` | **carve-out without a lease** |
-| Update a page | `mcp__mappa__wiki_update(project, id, title?, body?, version)` | **version-based**: conflict → 409 → retry with the fresh version from wiki_get |
+| Update a page | `mcp__mappa__wiki_update(project, id, title?, body?, version)` | id = num \| ref wiki:N \| uuid (канон task:1221); **version-based**: conflict → 409 → retry with the fresh version from wiki_get |
 | Path between entities | `mcp__mappa__graph_path({from, to})` | shortest chain, BFS |
 | Neighbors / outgoing | `mcp__mappa__graph_neighbors({id})` | node edges with target resolution |
 | Incoming links | `mcp__mappa__graph_backlinks({id})` | who references the node |
@@ -175,7 +175,7 @@ Question form → tool:
 **Addressing: slug → num/ref/uuid.** Resolve the key via `wiki_get`/`entity_search`
 (ref/num/uuid — публичная адресация, канон task:1221; internal id не используем). Graph
 responses carry per-type refs by full names (`task:N`/`inbox:N`/`wiki:N`, convention #1028) —
-reference them, not ids. An empty `path` = the link genuinely doesn't exist —
+reference them, not internal ids. An empty `path` = the link genuinely doesn't exist —
 say so; don't invent a chain from textual proximity.
 
 **Precondition — the graph is actually connected.** If unsure — first
diff --git a/skills/mappa-task-work/SKILL.md b/skills/mappa-task-work/SKILL.md
index 6d164dc..bd22003 100644
--- a/skills/mappa-task-work/SKILL.md
+++ b/skills/mappa-task-work/SKILL.md
@@ -1,7 +1,7 @@
 ---
 name: mappa-task-work
 author: ours
-version: 1.5.0
+version: 1.5.1
 description: >
   The central cycle of working with tasks in Mappa: orientation → work
   selection (priority/due) → execution → handover (close + review-umbrella) +
@@ -72,9 +72,9 @@ is active while session X is alive (end-state≠clean, not stale;
 (create/update/close) require no leases/claims — only version on update/close
 (409 on conflict).
 
-**Refs and ids (#1037/#1028).** Tasks carry `ref: "t:N"` by full name as the
-first field (`task:N`, convention #1028), `num` next, the global `id` —
-internal (last, for addressing in tools). Reference a task as
+**Refs and ids (#1037/#1028, канон task:1221).** Tasks carry `ref: "t:N"` by full name as the
+first field (`task:N`, convention #1028), `num` next, the global `id` — internal
+(last; наружу не используем — адресация по num/ref/uuid, канон task:1221). Reference a task as
 `[[task:N]]`/`task:N` in prose (slug/name first, ref as anchor: "the task
 `mappa-task-work` (task:1062)"), never `#<global id>`.
 
@@ -171,9 +171,11 @@ Don't confuse: 🟢 — *done*, not "ready". Ready is ⚪.
    close → review (paired, done) → all follow-up tasks closed. Order
    irreversible. All deploys go strictly through `.admin` (secrets and
    runbooks are service-use; other agents must NOT look into them — only
-   `secret:<path>` refs). Admin gets a task + covering letter (canon
-   `mappa-delegation`). Never deploy yourself.
-6. Add a summary line to the handoff/wiki if present.
+   `secret:<path>` refs). The .admin task + covering letter are created via
+   `mappa-delegation` (canon task + letter) — for self-assigned deploys you
+   create them yourself (target `.admin`, not your own board). Never deploy
+   yourself.
+7. Add a summary line to the handoff/wiki if present.
 
 ### Pause / switch / session end