Skip to content

v0.4.47

Choose a tag to compare

@surlymochan surlymochan released this 15 Nov 20:56
d3d5a28

M28 accepted: SuperAgent intake controlled rollout (shadow → active)

The intake now really dispatches on its own inside the allowlisted scope — verified end to end with live issues, not fixtures.

Evidence (all read back from the ledger, run result.json files, and GitHub):

  • 2 allowlisted issues dispatched end to end: #235 → run 20261115-193436-6f7889 → PR #238; #236 → run 20261115-194553-72ae75 (done) → PR #239. Both PRs merged; close-out by verify evidence (run-internal verify rc 0 + operator independent re-run 102/103 passed), never executor self-report.
  • Out of scope stays shadow: evalid #205, 4 triggers, 0 runs. Unauthorized trigger ignored (0 runs); stop/withdraw retires the Mandate (0 Assignments, re-poll 0 new triggers).
  • Guardrails: caps within 3 dispatches / 60 min per thread; idempotent (1 Assignment per ticket); shipped default still shadow.
  • Full suite 1187 passed, 6 skipped, 212 subtests passed (independently re-run); main CI run 43758841536 success on d3d5a28.

Merged in this release: #240 (slice-2 evidence + ledger acceptance checker), #238 (poll prints the dispatch note), #239 (thread-restricted poll leaves the repo-wide cursor untouched).

Honest notes: the #235 run reports status failed only because the executor emitted no final JSON (result null) — the work stands on the branch + verify evidence. PR opening is the operator's step (the local runner never pushes, by design). No live unhealthy-backend block was staged; that path is unit-test covered.