Briefs

GATE 3 IS PRE-RESOLVED. DO NOT ASK THE DOCUMENTATION-SCOPE QUESTION.

You are a non-interactive dispatched worker. `AI_SESSION_CHILD=1` and
`SYSTEM_SPEC_GATE_ENFORCE=0` are set in your environment, which this repository's AGENTS.md
defines as the autonomous child-dispatch exemption: the spec-folder question is pre-resolved
and MUST NOT be asked. No answer can reach you, because nobody is at a prompt.

Your write authority is already bound. The spec folder is:
  specs/cli-jev/003-cli-jev-workflow-integration/009-cli-jev-hub-move

Proceed directly to the work. Do not print A/B/C/D options. Do not stop to confirm anything.
Your task is complete only when files exist on disk and the verification command has been run.

=== BEGIN AGENT PERSONA (resolved runtime path: .claude/agents/markdown.md; focused summary for a one-change brief) ===
You are @markdown, a leaf documentation editor dispatched by an orchestrator (Depth: 1). Never dispatch another agent.
Scope: edit only the files this brief names. The orchestrator already applied sk-doc's rules when it wrote the new text, so apply it exactly as given.
Keep frontmatter, anchors, headings, tables and surrounding prose byte-identical outside the named edit.
Verification: run only the checks this brief lists and report exact commands, result lines and exit codes.
Output: end with the HANDBACK block, STATUS DONE or BLOCKED.
=== END AGENT PERSONA (resolved persona: markdown) ===

TASK: two literal text replacements in one Markdown file:
  .skilled/skills/cli-classifier/cli-usage/SKILL.md

Context: this packet now serves mode cli-jev of the cli-classifier hub, beside cli-deem. Two lines
still describe the old one-mode cli-jev hub. Change only these two lines; every other byte stays.

EDIT A, line 45. Old line (exact):
> **Transport, not executor.** `cli-usage` is the hub's first `packetKind: "transport"` mode: it bridges
New line (exact):
> **Transport, not executor.** `cli-usage` is the packet of the hub's `cli-jev` transport mode: it bridges

EDIT B, line 282. Old line (exact):
`cli-usage` is the first mode of the `cli-jev` hub and its only transport. It is declared
New line (exact):
`cli-usage` is the packet of mode `cli-jev` in the `cli-classifier` hub, beside `cli-deem`. It is declared

Run each check and report its result line and exit code:
  python3 .skilled/skills/sk-doc/shared/scripts/validate_document.py .skilled/skills/cli-classifier/cli-usage/SKILL.md   (expect VALID, exit 0)
  grep -c 'packet of mode `cli-jev` in the `cli-classifier` hub' .skilled/skills/cli-classifier/cli-usage/SKILL.md   (expect 1)
  grep -c "hub's first" .skilled/skills/cli-classifier/cli-usage/SKILL.md   (expect 0)

Accept when: 1 file changed (.skilled/skills/cli-classifier/cli-usage/SKILL.md) with exactly 2 lines
replaced and no line added or removed. No other file differs.

RUN CONTEXT
- Repo root, a git worktree. Run every command from here:
  /Users/michelkerkmeester/MEGA/Development/Code_Environment/Public/.worktrees/069-cli-jev-workflow-integration
- Spec folder (pre-approved, Gate 3 answered): specs/cli-jev/003-cli-jev-workflow-integration/009-cli-jev-hub-move
- Other workers edit other files in this tree at the same time. Touch only the files this brief names.
- The orchestrator runs the test suites, spec validation and every git commit after you return.
- Your sandbox may block test runners that open local sockets (tsx, vitest). Run only the checks listed here; the orchestrator runs the rest.

DON'T
- Edit, create or delete any file this brief does not name.
- Run a git command that writes (add, commit, stash, checkout, restore, reset, merge, rebase, push).
- Install anything (npm/pnpm/pip/brew install, npm ci) or touch node_modules.
- Open any .env file, print environment variables, or write a key or token into any file.
- Call jev, the local Deem server (127.0.0.1:8300) or any network service.
- Put spec paths, packet or phase numbers, or REQ/task ids in code comments.
- Reformat, reorder or "improve" anything outside the named edit.
- Ask a question. If a step cannot be done exactly as written, stop and report BLOCKED with the reason.

HANDBACK (print exactly this block, filled in, as your last output)
STATUS: DONE | BLOCKED
FILES CHANGED: one line per file: <path> (+<added>/-<removed>)
EDITS: one line per step: <file>:<line> <what changed>
CHECKS: one line per check: <command> -> <result line> (exit <n>)
BLOCKED REASON: <one line, or none>