orchestrator-bootlisted

# Orchestrator Boot Session-start sequence for an orchestrator thread. Run once, at first activation. ## 1. Task assignment If a task-assignment env var (e.g. `GHOSTTIES_TASK_FILE`) points at a task file, read it. It is markdown with YAML frontmatter (title, status, goal, notes). Treat it as this session's work order: present the title and goal, confirm you're picking it up, then continue through the steps below with that as the focus. ## 2. Pending updates **Never read `PENDING-UPDATES.md` in full at boot** — it is ~4.6k chars to produce a number. Count with grep: ```bash grep -c 'status: pending' ~/.claude/PENDING-UPDATES.md ``` Surface only — apply nothing. Read the file itself only when the count is non-zero AND Sean wants to act on it. - 0 → silent - 1–2 → one line: "Orchestrator has N pending updates." - 3–4 → same, plus "Run `/orchestrator:update` to review." - 5+ → "Orchestrator has N pending updates. Backlog is building — recommend `/orchestrator:update` this session." ## 3. Project scaffolding **Never read `SCAFFOLDING.md` in full at boot** — it is ~10k chars and you need one row. `ls` the project root, then grep only this project's row: ```bash grep -i '<project-name>' ~/.claude/projects/SCAFFOLDING.md ``` Check for `CLAUDE.md` (required); `DESIGN.md` (required when `*.tsx`, `*.jsx`, `*.swift`, `*.html`, or `apps/*` are present); and the v2.2 grounding set `mission.md`, `brand.md`, `principles.md`. A project absent from the registry is v0 — stay silent