atm task events: team-wide event-log enumeration and paging for oversight (queue view unchanged)

[randlee]

Ruling (Rand, 2026-09-12, comment below)

Not an oversight gap in the queue. The task queue is a snapshot of planned, ordered work for one agent/mailbox; tasks move between queues and are reassigned, so the queue carries no history. Oversight reads two things:

• What has occurred: the task event log, the immutable record of every state transition.
• What is planned: the task queue.

No closed-task listing, queue history, or --closed/--state view is requested. The earlier "requested shape" in this issue is withdrawn.

Remaining request (event log only)

Today atm task events <id> needs a known task id and is capped at 200 rows (TaskPage::Bounded { limit: 200 }; TaskPage::All exists in task_query.rs but no CLI flag reaches it). A monitor that never saw a task while it was queued cannot discover its events.

Follow-on sprint after the Phase BA stack lands (not BA.4, not the BA.6 docs):

• Team-wide event-log enumeration: events for a team (optional member, optional --since <iso> / --after-seq <n>) without a task id, ordered by sequence.
• Paging on atm task events: --limit N / --all-rows mapping to TaskPage::Bounded/TaskPage::All, with a stable cursor (event seq) so a consumer can resume.
• HTTP API minor bump per ADR-061 (additive); --json shape stays Vec<TaskEventRow>.

Queue-view semantics (atm task list, --all) are unchanged by this issue.

Interim for monitors

Record every task id seen in task list --all while queued and fetch its events after it leaves the queue. Tasks that open and close between two polls are a coverage gap until team-wide enumeration ships; report it as such.

Refs: #1408, #1410; amon messages 01M29KMNSV8QFDDEAY14R30TZR, 01M2A0587JNNE6J2J0Z8CKFZ9X.

[github-actions]

🤖 Hi @randlee, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[github-actions]

🤖 I'm sorry @randlee, but I was unable to process your request. Please see the logs for more details.

[randlee]

This is not an oversight gap. The task queue is a snapshot of tasks that are ordered and queued for a particular agnet/mailbox. Tasks can get moved between queues, and a task can be re-assigned to other agents. Trying to maintain history for a queue would be difficult and confusing. If agent-a started task-1 and couldn't finish, task-1 could then be queued for agent-b to do at some point in the future. How do you even record this in a way that makes sense.

For oversight, what you need to know is:
What has occurred: The task even log records every state transition and is an immutable record of what has occured historically.
What is planned: task queue

[randlee]

Revised per the ruling above: queue = planned work, event log = history. The closed-task listing request is withdrawn; the issue now asks only for team-wide event-log enumeration and paging on atm task events, as a follow-on sprint after the Phase BA stack lands.