Pull the current shared working state for a project segment (and its sub-segments). Call this FIRST, before doing anything on the project: it returns the open tasks, open questions, recent decisions/changes/notes, and your inbox of handoffs. Treat it as the current truth about where the work stands.

segment is a dotted path, e.g. "myproject" or "myproject/backend/auth"; a parent pulls all descendants. Treat status entries ("fixed"/"done") as CLAIMS to verify against git (see context_verify), not facts.

Append an entry to the shared working state so other tools see it: type = decision | change | question | task | note. refs is optional JSON (e.g. {"files": ["..."], "commit": "abc123"}). Returns the new entry id.

Store WHAT/WHY (facts, decisions, intent), not HOW (procedure). A change is "done" only when merged in git — include refs.commit/refs.pr; without a ref it is recorded as a CLAIM (verify with context_verify).

Mark an open question or task resolved so it stops surfacing in context_pull.

Full-text search the project's history (decisions/changes/questions/notes) to recover past context. FTS5 does not stem — add a prefix wildcard (auth*) if a bare term seems too narrow.

Completion integrity: list 'change' entries and classify each against GIT (the ground truth) — 'merged', 'present-unmerged', 'missing', or a bare 'CLAIM (no git ref)'. A tool logging "fixed" is NOT done; done = merged in git. Checks commits in the repo the server runs in.

Post a handoff to another tool's inbox (to = cursor | claude-code | claude-desktop). It lands in the target's inbox and stays PENDING until the receiver resolves it. If AION_DELIVERY is enabled and the target has a verified deeplink (today: cursor), a doorbell also summons that tool with a fixed nudge — the URL never carries your content. Returns the entry id and delivery outcome.

Add a node to the roadmap tree. kind = project | segment | phase | epic | task. parent_id nests under another node (0 = top-level); a child inherits its parent's segment unless set. priority is 1..5 (1 = highest; 0 = none). Returns the id.

Update a roadmap node: set priority (1..5), reparent (parent_id), or set status ('open'/'resolved'). Pass only what you want to change (0/empty = leave as is). Resolving a task/epic is what makes progress roll up.

Record a DEPENDENCY edge: node blocked_id is blocked by blocked_by_id. Use this for real dependencies instead of overloading parent_id (parent_id = decomposition). Surfaced in roadmap_view as a node's blocked_by.

Show the hierarchical roadmap (project > segment > phase > epic > task) with done/total rollup per node, sorted by priority. Optionally scope to a segment.

Progress summary: per top-level segment and overall, how many leaf work nodes are done vs total, with percentages.

Before implementing a task, get every decision and open question that may CONSTRAIN it — from the task's segment, its ancestors, and its descendants (not recency-limited). Surface any conflict with your plan BEFORE coding.

Reuse an approach from ANOTHER project: search that project's history for a topic and adapt the matching decisions/notes instead of starting from scratch. FTS5 does not stem — add a prefix wildcard (auth*) if a bare term is too narrow.