loom-pickuplisted

# Pickup (Loom) Get oriented in THIS project, then state a concrete next step. The session is already bound to its repo and board — the **board is the source of truth for tasks**; the vault holds prose. Don't pass a project id anywhere; it's derived server-side. ## Steps 1. **Board** — `tasks_list` (the `loom-tasks` MCP) to see tasks and their columns. Note what's in-progress, in review, and waiting, and surface which cards are **`held`** (an owner brake) vs **`deferred`** (not yet sequenced) so "what's next" respects them. Also drain the **Requests inbox** (`question_pull`) and check `escalation_status` for decisions the human answered while you were away. 2. **Code** — `git log --oneline -20` and `git status` for recent and in-flight work. 3. **Conventions** — read `CLAUDE.md` at the repo root if present. 4. **Your role's anchor** (whichever applies): - *Lead / orchestrator:* read your **living resume doc** — it's the "you are here + what's next" source of truth. Your session's **"Where things live"** context block gives your project's absolute **vault root**; your resume doc is `<vaultRoot>/Projects/<Project>/Orchestrator Log.md` (substitute your project's name). **Read it by that ABSOLUTE path — never Glob, Bash `find`, or Bash `ls` for it** (a broad search from your home directory hits the search timeout). Cross-check it against the board. **Before acting on a handoff's "still to build / un-built" claim, verify it against `git