yes. bernstein run plan.yaml --non-interactive --json-status exits non-zero if any task ends up in the dead-letter queue, which makes it a normal failing ci step. for the github app path, bernstein responds to /bernstein slash-commands in pr comments via src/bernstein/github_app/, and the autofix daemon (bernstein autofix) watches bernstein-opened prs, reads the ci log on failure, spawns an agent against the failing worktree, and pushes a fix commit. the runbook for ci-mode lives under templates/. running inside ephemeral runners works (worktrees are local files); long-running orchestration is happier on a persistent box.
canonical answer