feat(delegate-task): session_break authoring field [v0.2.2]

Add the authoring side of the `session_break` marker whose consumer
side shipped in using-tasks v1.2.0. At delegation time the author can
now mark a task so that, after it closes, an autonomous runner pauses
instead of chaining the next task.

- Pre-flight gate 5->6 questions: new Q (item 5, after notify) —
  "Session-break после этой задачи? (domain-switch / milestone /
  heavy infra)". Yes -> set session_break in body; no -> omit
  (default unchanged).
- Template trailer gains optional `[**session_break:** true |
  "<hint>"]` with inline comment (same lowercase frontmatter key
  using-tasks reads).
- Usage-guidance block: three set-it cases + tie to using-tasks
  Task-completion step 6 / SESSION BOUNDARY line.
- What-NOT-to-do bullet: don't set it routinely (real-boundary
  marker, not a default).
- Wiki concept page concepts/delegate-task-session-break.md
  (links using-tasks-session-break) + index + log.

PATCH bump: additive optional field + one pre-flight question, no
existing behaviour changed. Markdown policy artifact — no test
surface (TDD N/A). Closes [session-break-delegate-task].

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.tasks/STATUS.md

@@ -608,10 +608,7 @@ needs-claude
 
 ---
 
-## 🔴 [session-break-delegate-task] — ## Goal
-**Owner:** DESKTOP-NSEF0UK:claude-opus:18704
-**Claim token:** 4394473c-c9de-4c70-ba35-2f246c716ff7
-**Claim expires at:** 2026-06-09T13:44:31.150Z
+## 🟢 [session-break-delegate-task] — ## Goal
 Add `session_break` as optional field to `delegate-task` task body template v0.2.1 → v0.2.2.
 
 ## Design
@@ -646,12 +643,13 @@ Usage guidance (три случая):
 ## Weight
 needs-claude
 
-**Status:** ready
-**Where I stopped:** (not started)
+**Status:** done
+**Where I stopped:** Shipped — `skills/delegate-task/SKILL.md` 0.2.1→0.2.2 (PATCH). Authoring side of the `session_break` marker (consumer = using-tasks v1.2.0). (1) Pre-flight gate 5→6 questions: new Q (item `5.`, after `4. notify`) — "Session-break после этой задачи? (domain-switch / milestone / heavy infra)"; if yes → set `session_break` in body, if no → omit (default unchanged). (2) Template trailer gains optional `[**session_break:** true | "<hint>"]` with inline comment (next to weight/notify/allow_upgrade; `session_break` = same lowercase frontmatter key using-tasks reads). (3) Usage-guidance block after the template lists the three set-it cases + ties to using-tasks Task-completion step 6 / SESSION BOUNDARY line. (4) What-NOT-to-do bullet warns against setting it routinely. Wiki: `concepts/delegate-task-session-break.md` (links [[using-tasks-session-break]]) + index + log. All 4 acceptance criteria met by inspection (markdown policy artifact — no test surface). NB on numbering: SKILL numbers pre-flight 0-indexed (0–4), so the task's "Q6" lands as item `5.` after the "Q5 notify" (= item `4.`).
 **Weight:** needs-claude
-**Next action:** Прочитать skills/delegate-task/SKILL.md, добавить Q6 в pre-flight и поле session_break в template, поднять версию до v0.2.2
+**Next action:** (none — kept until merged; paired review task `session-break-delegate-task-review` unblocked)
 **Branch:** n/a
 <!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-06-09T10:15:32.125Z -->
+<!-- closed-by: DESKTOP-NSEF0UK:claude-opus:18704 / 2026-06-09 / 0.2.1→0.2.2 PATCH; session_break authoring field (pre-flight Q6 + optional template trailer field + 3-case usage guidance + What-NOT bullet); wiki concept page; 4/4 acceptance met by inspection (markdown policy, no test surface) -->
 
 ---