mr-onion

Phase 23 — sre-release + sre-toil Trial: test-assist’s Update/Rollback Path

Version: 1.0 Date: 2026-09-16 Status: Trial complete, TFP-052 landed — desktop proposal implemented (rollback marker through UpdateChecker.interpret()’s existing seam, 9 new tests) and toil-classified both builds. Findings live in test-assist/docs/RELEASE_ROLLBACK_TRIAL.md, merged to test-assist’s main via test-assist#24 (merge commit b91c79b). Gate A below is satisfied.

Context

Reviewing skills/proposed/’s overlap table raised a specific question: verified-release-pipeline (the existing account skill) and sre-release (Martin’s proposed candidate) were flagged as overlapping on ch. 8, with sre-release also carrying “launch coordination and progressive rollout” that the existing skill doesn’t cover. Checked precisely, not by inference — read both skills’ full text. The line is exact: verified-release-pipeline proves a built artifact runs correctly before it’s attached to a release and stops there; sre-release continues past that point into staged rollout, canarying, feature flags, and rollback.

Checked against test-assist’s real setup (not hypothetically) because Emil described this as an actual, felt pain point — “frustrating trying to get a proper update or rollback working” — not a theoretical gap:

Scope (this phase)

In scope

  1. Apply sre-release’s rollback/staged-rollout material and sre-toil’s toil-ledger framework to test-assist’s real update/rollback situation — both builds, findings printed and recorded, same pattern as TFP-039’s CALIBRATION.md and TFP-036’s INTROSPECT_CRAWL_SPIKE.md.
  2. Propose (not necessarily fully build) a concrete rollback path for each build, scoped to what actually fits a manual-update, no-telemetry, corporate-constrained tool — not a generic “add feature flags” prescription that assumes infrastructure this project doesn’t have and, per its own stated constraints, shouldn’t.

Out of scope

Backlog

TFP-052 - Trial sre-release + sre-toil against test-assist’s real update/rollback gap

Single ticket.

Suggested Milestone Gates

Gate A - The felt pain point has an actual answer

Status update (2026-09-17)

TFP-052 ran for real, not deferred: both builds toil-classified against sre-toil’s six-property test (desktop 5-6/6, browser 5/6), zero rollback mechanism confirmed by reading update_check.py and pages.yml directly, and two proposals scoped to what a manual-update, no-telemetry, solo-maintainer project actually supports. The desktop proposal was implemented — a KNOWN_GOOD: marker read through UpdateChecker.interpret()’s existing pure seam, with 9 new tests. skills/proposed/README.md already points its verified-release-pipeline/sre-release overlap note at this result (commit 97e3ef2).

Done (2026-09-17): test-assist PR #24 (branch docs/ta-250-release-rollback-trial, commit 9479425) reviewed and merged to main there (merge commit b91c79b). Reviewed for real before merging: the 9 new tests were confirmed by name in the diff and their pass count (405 passed, 2 skipped, 3 deselected, 1 xfailed) verified directly against the PR’s own CI log, not just its description; the update_check.py diff is a pure-function addition through interpret()’s existing seam with no new network call; the browser-build proposal’s file list confirmed doc-only (no pages.yml change). The PR’s “visual” check showed as failing at merge time — confirmed to be a pre-existing flake also present on main’s own tip (7f0c284), unrelated to this PR’s changes, before merging past it. The rollback marker and RELEASE_ROLLBACK_TRIAL.md are now on test-assist’s main. This backlog’s Gate A is satisfied.