a-card-works-its-own-tasks

[VeryComplexAndLongName]

Implements a-card-works-its-own-tasks (ADR 0026 amended 2026-10-05: a change's own worktree is worked from its card, and only there).

• A task is shown whole. A row's hint holds all of it, with what is written under it; selecting it opens the task whole in a panel over the board (not in the card, whose height core derives from what it lists).
• In the change's own worktree (the working directory on the branch named after the change; the host resolves it from the name, never from a path in the request), a card:
  • closes or reopens a task with a note under it. The note is required for Human-only and delegated tasks, so the merge gate counts them recorded;
  • commits that tasks.md alone and pushes the branch;
  • runs a delegated task on its agent, with runners built for that worktree.
    All refused while a run works there.
• The change's name opens its task list where it is worked: tasks.md from the worktree in VS Code, plus proposal, design, specs, a new window and the path. It used to look only in this checkout, so a change not yet merged opened nothing. In the standalone app: a page of its own in a new browser tab.
• Hide done (kept with the view; the card's height follows) and the task in hand scrolled into view.
• openspec-ui-cli task done|reopen <change> <number> [--note] and task commit <change>.

Checks: typecheck and lint 0. Every test project passes, run per package and git files one at a time (see tasks 5.1: one load-sensitive core test timed out only while another package ran beside it, and passes alone). openspec validate --strict passes; the gate owes only 5.4 (Human-only). Live (5.3): a Human-only task refused without a note, closed with one, committed alone and pushed to a bare remote; the gate counts it recorded.

Rebased on main after #816; the two conflicts (a HARNESS.md row and a core export) keep both sides.

🤖 Generated with Claude Code