List the Efforts in a repo, each with its Ticket count and which header docs it holds.

An Effort's Destination, then one line per Ticket — id, title, kind, status, Edges — with the Frontier marked. Never returns bodies; fetch those with get_tickets.

Full bodies for a list of Ticket ids, in one call. Use after get_board, only for the Tickets you actually work.

Publish a whole breakdown in one call. Edges may name a sibling by a temporary key you choose; the server mints repo-unique ids, numbers the files, and resolves the keys atomically — a partial failure creates nothing. Cycles are refused. An unknown Effort needs create.

Change one Ticket. Lifecycle: claim, resolve with a one-line gist, or drop with a reason — at most one of those per call. Graph: replace the Edges, refused if they close a cycle. Annotations: triage role, a comment, ticking acceptance criteria; these touch no part of the graph. Any of the three groups may accompany the others or stand alone.

Read a Map's Destination and Notes, or edit one typed section — set Destination or Notes, add or graduate a fog patch, rule something out of scope — without rewriting the others. Decisions-so-far is generated from resolved Tickets and never accepted as input. Mutations pass expected_revision from a prior read so concurrent sessions cannot clobber each other.

Get or put a Spec as a whole opaque document (conventionally with YAML frontmatter). Nothing edits a Spec section by section — an Effort may hold both a Map and a Spec. Puts pass expected_revision from a prior read so concurrent sessions cannot clobber each other.

Normalize Legacy Tickets in an Effort: schema frontmatter, preserve existing ids, mint ids for Tickets that have none, turn prose Edges into blocked_by. Preview writes nothing. Filename rewriting is opt-in. Unrecognized files in the Effort directory are ignored.