jotbook-inklisted

# Ink the jotbook This is the primary jotbook entry point. It has two shapes, both gated on initialization: - **`/jotbook-ink` (no arguments)** — guided curation session. Review the backlog, mark decisions, then ink or pencil the chosen ones. - **`/jotbook-ink <slug>[,<slug>]`** — ink one or more specific reviewed jots into finished long-form entries (the targeted form). If the plugin hasn't been initialized in this project (no `.claude/jotbook.local.md`), either shape routes to `jotbook-init` first. After init completes, the user re-invokes whichever flow they actually wanted. ## Entry-point dispatch Read the invocation arguments and route as follows. Do this **before** reading the rest of the skill: 1. **Plugin not yet initialized** (no `.claude/jotbook.local.md` in the project) → invoke the `jotbook-init` skill. After init completes, stop. Do not auto-chain into curation or the per-slug procedure — let the user re-invoke once they're set up. 2. **No slug arguments** → the curation session. Hand off to `jotbook-review`, which owns the full decision loop: it inventories jots, takes the user's free-form decisions (drop / merge / tweak / ink / pencil / keep, the latter two accepting their respective slugs and any `--html` flag), applies structural changes in place, and dispatches into this skill's per-slug procedure (for `ink`) or `jotbook-pencil` (for `pencil`) directly. Do not duplicate that orchestration here — let the review skill drive end-to-end. When the per-