Office Agent Runtime — Error Handling Contract Requirements

Overview

When an agent run fails mid-turn (invalid model, auth failure, malformed response, transient upstream), today's UX is:

Intent: When an agent run fails mid-turn (invalid model, auth failure, malformed response, transient upstream), today's UX is:

AC-OFFICE-RUNTIME-001.1: No automatic retry. Every adapter error is terminal for the wakeup that produced it.
AC-OFFICE-RUNTIME-001.2: The wakeup row is stamped with status = failed and error_message. No follow-up wakeup is queued from the failure path.
AC-OFFICE-RUNTIME-001.3: Re-runs only happen via explicit user action: Resume session in chat, Mark fixed on an inbox entry, or task reassignment to a different agent.
AC-OFFICE-RUNTIME-001.4: agent_run_failed - one entry per failed (task, agent) wakeup while the agent is below threshold. Title: " failed on ". Action: Mark fixed -> dismiss + retry.
AC-OFFICE-RUNTIME-001.5: agent_paused_after_failures - one entry per auto-paused agent. Title: " auto-paused after failures (tasks A, B, C)". Action: Mark fixed -> unpause + retry the affected tasks.
AC-OFFICE-RUNTIME-001.6: Changing assignee_agent_instance_id on a task fires the existing reactivity pipeline, which queues a fresh task_assigned wakeup for the new agent.
AC-OFFICE-RUNTIME-001.7: The existing staleness check (recovery-reliability spec) cancels the prior wakeup for the (task, old agent) since the assignee has changed.
AC-OFFICE-RUNTIME-001.8: Any per-task agent_run_failed inbox entry tied to the old (task, agent) auto-dismisses - the failure is no longer actionable on this task.

The migrated technical source is split into part 1, part 2.