startlisted

# Start Open a work session. One slug names the work, and the branch, the tack route, and the session label all agree on it. Whatever playbook follows assumes this ran: without it the branch answers to no route, nothing that reads routes can see the work, and the linked ticket goes unread. **Skip this when** a route already resolves for the session (the gate below), when the ask is a question or a read-only investigation with no deliverable, or when work is already underway on a named branch and only the thread reading is wanted. ## Gate: is a session already open here? tack's `UserPromptSubmit` hook says which way this fell, once per session. Read its line before running anything: - **A route resolves** — `Tack route for this session: <slug> (recorded)`. The session is open. Report it in one line and stop. A second route over work already tracked is what makes every reader of those routes double-count it. - **No route resolves** (`neither the branch nor the project name matches a route`). Continue below. When that line isn't in context, probe instead: `tack status <name>` exits 1 with `Route not found`, so run it for the current branch and for the checkout's directory name — the two the hook resolves on. ## Read the linked artifact in full When the arguments carry a URL, that URL is the session's brief. Read the whole artifact before anything else, and read it as a document rather than as a lookup: - **Fetch the description *and* every note or comment**, in ch