blocked-statelisted

# Blocked state The loop must fail loudly and durably, never silently. A blocked task is not a failed task; it is a paused task with enough evidence for a human or later agent to resume. For ownership when a gate fails, follow the canonical **Gate Ownership And Dispatched Contract** section in `agenticloop/AGENTIC_LOOP.md`: a failing gate routes work but does not transfer another role's mutation authority. Use backend-neutral language first: - **task record**: the durable record for the work, - **GitHub projection**: issue labels and comments when the backend is GitHub, - **files projection**: local Markdown task fields when the backend is local files. The default backend is files. Read `.agenticloop/project.md` for `task_backend` before recording a blocked state. For GitHub-backed work, state markers count only when they start a line and appear in comments authored by the loop's GitHub account. The `[[agent: ...]]` trailer from [[github-attribution]] helps identify the role, but it is cooperative text, not security. For files-backed operations, follow `agenticloop/backends/files.md` for task-file shape and frontmatter conventions. ## Transient vs durable - **Transient**: provider outage, rate limit, flaky network, temporary `gh` failure. Retry once or wait if the retry is cheap and safe. If it keeps failing, record a block. - **Durable**: credentials missing, task contradiction, merge conflict, review deadlock, missing human decision, or unavailable external dependen