docs(pipeline-crew): author the plugin Tutorial — stand up your first crew (zero → live crew draining the board)

[usirin]

Fixes #3567

What

Authors the plugin Tutorial (Diátaxis learning quadrant) for the pipeline-crew PLUGIN surface: claude-plugins/pipeline-crew/TUTORIAL.md. A linear, hand-held lesson taking a repo from zero crew → a live crew draining the board: install the plugin, fill one operator config, run /stand-up, attach to the crew tmux window, and watch an engine pull a status:triaged issue off the board and open a PR — no terminal relay.

Grounding (real stand-up flow, not confabulated)

• Install + no-version content-addressing — the plugin README + ADR 0110.
• Config seam — crew.config.template.jsonc (the placeholder keys: operator, controlPlaneApprover, roles, notification, channels) + $CREW_CONFIG/.claude/crew.config.jsonc resolution.
• /stand-up order + fail-loud-no-partial-crew + tracker pid/socket report, and its deliberate exclusion of the HITL cartographer — grounded in commands/stand-up.md and commands/spawn-role.md (tmux crew window, ADR 0189/Cartographer (HITL ideation helper) should not be autobooted with a self-driving cold-start prompt #3524).
• Engine claim (self-assign + claim: session-id comment) — ADR 0115.

House style

• Single-mode Tutorial only (precedent PR Wave 3B — Split the three fused docs by Diátaxis mode #3392) — the same > Diátaxis mode: tutorial callout, Where to go next, and Grounding shape.
• Surface separation: no cross-links into the pipeline-crew-mcp PACKAGE docs tree — that package has its own tutorial; this is the PLUGIN/crew tutorial. All links stay within the plugin (README, REFERENCE, PERSONALIZATION, EXPLANATION, the two commands) + ADRs.

README wiring (minimal, localized)

Added exactly one Layout-tree row + one See-also link for the new doc to README.md — no reorder/reformat of existing rows (kept minimal to avoid conflict with a concurrent sibling README edit).

Merge model

Non-control-plane docs PR (crew surfaces are non-§CP by design) — ships on green.

🤖 Generated with Claude Code

[usirin]

review-code: PASS @ aafdff3

Gate: review-code (routed by class-probe: claude-plugins/pipeline-crew/*.md matches no has-code/has-skills/has-docs class → no-class fail-closed → has-code; single namespace, no UI paths so no review-design). Verified against issue #3567 at head aafdff33, read from the PR-head worktree — not CWD.

Acceptance criteria

#	Criterion	Verdict
1	Single-mode Tutorial in the plugin docs home, zero → a live crew draining the board	PASS
2	Steps concretely followable (config + stand-up), verifiable live-crew end state	PASS
3	Discoverable from a plugin docs entry point; no cross-links into the package docs tree	PASS

AC1 — TUTORIAL.md exists in the plugin home, carries the single > Diátaxis mode: tutorial callout, and walks a linear zero → live-crew arc (install → fill one config → /stand-up → attach → watch an engine claim a triaged issue and open a PR). Single-mode-per-doc (precedent #3392) holds: it links out to REFERENCE.md / PERSONALIZATION.md / EXPLANATION.md for the other quadrants rather than bleeding reference/explanation in.

AC2 — Every step grounds in the real stand-up flow and would work:

• Config keys (operator, controlPlaneApprover, roles with tier/count/wipCap, notification, channels with mode/servers/allowedChannelPlugins) and the $CREW_CONFIG else .claude/crew.config.jsonc resolution — all match crew.config.template.jsonc.
• The /stand-up order (assert CLI version → tracker → derive roster → channel bind + placement → launch), fail-loud-no-partial-crew, and tracker pid/socket report match commands/stand-up.md.
• The cartographer exclusion from stand-up + on-demand /spawn-role cartographer (boots idle) match commands/spawn-role.md (ADR 0189, Cartographer (HITL ideation helper) should not be autobooted with a self-driving cold-start prompt #3524).
• The engine claim (self-assign + claim: session-id comment, ADR 0115) and the four-role flat topology (three bridges + engine pool) match CREW_ROLES in roles.ts (ADR 0189). No confabulated steps or commands found.

AC3 — Discoverable: the README wiring is exactly one Layout-tree row + one See-also link to TUTORIAL.md, minimal and localized (no reorder of existing rows). Surface separation holds — the sole @kampus/pipeline-crew-mcp mention is a backticked "runtime prerequisite" prose note (the lesson explicitly says the channel substrate "has its own separate learning path; this lesson never reaches into it"), not a markdown cross-link into the package docs tree. All 12 in-repo links resolve against the head worktree; no user-local/absolute paths.

Non-blocking note (not a defect)

The Grounding section's line "The four agent defs: agents/" is slightly imprecise: agents/ holds five files — the fifth, crew-investigator.md, is a non-roster agent def (not in CREW_ROLES). The four roles the tutorial names are exactly the ADR-0189 roster, so the roster claim is correct; only the "four agent defs" phrasing undercounts the directory. Cosmetic, does not affect followability or correctness — flagging for a future touch, not gating on it.

Merge model: non-§CP — claude-plugins/pipeline-crew/** is not in the canonical control-plane set (re-resolved from origin/main); auto-mergeable on green. Verdict is a merge-ready signal only; ship-it performs the merge.