Three dashboard SPEC.md files name the branch agent-data, where the tickets and the queue live

packages/framework/dashboard/components/ProjectErrorBanner.SPEC.md

@@ -2,7 +2,7 @@ The warning banner at the top of a project's page, listing every project error t
 
 ## Glossary
 
-- **project error** - a condition the daemon has found broken about a project and keeps recorded until the condition is gone. Today the only kind is one of the project's two bookkeeping branches failing to converge with origin — the `tickets` branch, holding the tickets and the agent queue, or the `agents-logs` branch, holding the agent archives and the routine locks — headlined "Not syncing with the remote".
+- **project error** - a condition the daemon has found broken about a project and keeps recorded until the condition is gone. Today the only kind is one of the project's two bookkeeping branches failing to converge with origin — the `agent-data` branch, holding the tickets and the agent queue, or the `agents-logs` branch, holding the agent archives and the routine locks — headlined "Not syncing with the remote".
 
 ## Business logic — TL;DR
 

packages/framework/dashboard/components/ProjectHome.SPEC.md

@@ -23,7 +23,7 @@ The project error banner sits between the project's action bar and the start for
 
 #### Rationale
 
-An agent started on a project whose `tickets` branch cannot reach origin works from stale tickets and writes into an agent queue nobody else will ever see. Naming that failure after the start form would be too late.
+An agent started on a project whose `agent-data` branch cannot reach origin works from stale tickets and writes into an agent queue nobody else will ever see. Naming that failure after the start form would be too late.
 
 ### Every parked agent, answerable here
 

packages/framework/dashboard/lib/queue-entry.SPEC.md

@@ -1,6 +1,6 @@
 Decides how one agent queue entry reads on screen and where clicking it goes.
 
-Entries are lines of the agent queue, `TODO_AGENTS.md` on the project's `tickets` branch, so they are markdown, and a ticket queued from the dashboard is written as a link back to its ticket. An entry that starts with a link shows that link's text as its title; anything written after the link is the agent's own note, which is detail for a tooltip rather than for a one-line list that would truncate the title away to make room for it. A link further into the line is part of a sentence rather than the name of the work, so it does not count as the title. An entry with no leading link shows as its own text.
+Entries are lines of the agent queue, `TODO_AGENTS.md` on the project's `agent-data` branch, so they are markdown, and a ticket queued from the dashboard is written as a link back to its ticket. An entry that starts with a link shows that link's text as its title; anything written after the link is the agent's own note, which is detail for a tooltip rather than for a one-line list that would truncate the title away to make room for it. A link further into the line is part of a sentence rather than the name of the work, so it does not count as the title. An entry with no leading link shows as its own text.
 
 The link's destination decides where the entry points: a target under `tickets/` names a ticket and opens that ticket's page, an absolute web address is kept as an outbound link, and anything else — a plain path inside the repo, say — keeps the title but points nowhere, since the dashboard has no page for it and a dead destination is worse than none.