[roboco-app]

Generalize the #685 strike-breaker into a task-scoped wedge ledger in roboco/services: (1) at every status transition, regardless of actor or verb, compare the #685 progress fingerprint (commit count, revision_count, terminal children — extend it task-scoped and verb-agnostic; do NOT invent a second fingerprint) and record a strike when a task returns to a status it previously held with no fingerprint movement; counting is status-keyed, not actor-keyed, per the intake's "across any actor"; (2) reset rule — any of the three fingerprint signals moving clears the wedge counter; (3) past a configurable threshold N (default aligned with the #685 strike threshold — record the resolved default in your journal), transition the task to blocked-for-human and emit a CEO notification carrying the full cycle — actors, verbs, timestamps — so the CEO sees the shape of the loop, not just that one exists. Routes stay thin. Context: the September mixed-verb loop (unblock-OK → complete not_authorized → escalate bounce → pool reclaim) accumulated zero strikes under the per-unblock counter; that is the shape this must catch.

[github-actions]

Thanks for opening your first pull request on RoboCo!

Quick checklist before review (most of these are enforced by CI, but worth a glance):

• make quality — ruff format check, ruff check, mypy, pytest (≥80% coverage), and the rest of the gate
• Panel changes pass pnpm lint and pnpm exec tsc --noEmit (run from panel/)
• No # noqa / # type: ignore shortcuts; pre-existing violations in touched files are fixed
• Added an entry under ## [Unreleased] in CHANGELOG.md
• Signed the CLA (the bot will prompt you on this PR)
• Signed your commits — master requires verified signatures (SSH signing setup)
• Updated any affected docs under docs/

See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow.

Welcome aboard — a maintainer will review shortly.

[roboco-app]

In-path PR-review gate — CHANGES REQUESTED 🔴

Reviewed by pr_reviewer (RoboCo PR reviewer). Posted by the project bot account; the gate verdict is authoritative in RoboCo.

[F-dbe52f00] roboco/services/task.py:13984 (blocker) — Exactly one wedge-ledger check scheduled per status transition, so one arrival adds one strike → _emit_status_transition_audit calls _maybe_schedule_wedge_ledger_check twice (lines 13948 and 13984): two strikes per arrival, so the default N=5 trips on the 3rd static arrival → Delete one of the two calls and add a test that runs the real _emit_status_transition_audit and asserts exactly one run_wedge_ledger_check task is scheduled
[F-d0ac020c] panel/lib/lifecycle.json (blocker) — Generated artifacts stay byte-identical to what the branch's lifecycle.py and role_config produce; this task has no lifecycle changes → Diff deletes cancel_leaf, the devops role and its verbs, and task_time, and drops 'start' from i_will_plan/i_will_work_on composes, although lifecycle.py still defines cancel_leaf and DEVOPS → Rebase onto the current root branch and regenerate (scripts/regenerate_verb_tables.py and the lifecycle export), or revert these files; the diff should then touch none of them
[F-a5795a7f] roboco/services/notification.py:312 (major) — CEO notification names actor, VERB and timestamp for each step of the cycle → Each line renders only timestamp, actor, role and from->to; the audit event (the verb proxy, e.g. task.pr_fail or task.request_changes) is collected in _transition_cycle but never shown → Include the event/verb in each rendered line. If the transition verb is not recoverable from the audit row, record it in the audit details at the chokepoint
[F-360d8ebe] roboco/services/task.py:14000 (major) — The ledger check runs after the transition commits, and its marker write cannot be clobbered by the caller's transaction → The check is scheduled with asyncio.create_task mid-transaction on a fresh session. It can read pre-commit state, force BLOCKED before the caller commits its own status, or have its wedge_ledger marker overwritten when the caller later flushes task.markers → Run the check post-commit (an after-commit hook or the outbox), or do the ledger fold in the caller's session and only defer the trip
[F-36f665f3] roboco/services/notification.py:318 (minor) — Body ordering label matches the data → Body says 'Full cycle (oldest last)', but _transition_cycle reverses a DESC query, so rows come oldest FIRST → Change the label to 'oldest first' (also in the _transition_cycle and wedge_cycle docstrings)