🍊😺 obot
Launched
Commit6ab6d6b

changelog v4.29.2 is current with this build

What changed · full log

← All goals

Objective: A fast check — safety.viz's required check in about six minutes, with every test still run

Goal issue #412 · slug fast-check

1/2 member issues closed

Other open members 1

no readiness label yet.

✅ Done 1

closed members.

Direction

Intent

@jwildfire, 2026-10-09: "safety.viz CI/CD is slow. ~22 minutes to run the test for each PR. Do a design/research spike to see if we can optimize." After reading the spike the same day: "Sounds good! Build out the objective. Run a security assessment in parallel and fold in any concerns from that before we start the build." Asked in the session whether it should wait for release 1.12, he chose to land it now, in release 1.11.

Every pull request to safety.viz waits on one check, "Build, format, and test". On 9 October it took a median of 22.6 minutes, twice what it took two days earlier. The spike found why, and measured the fix on GitHub's runners (CI speed spike):

This objective makes the check and the evidence refresh run fast without removing, skipping or weakening a single test, and closes what the security assessment of the new layout found before any of it is built.

Definition of done

End state: on safety.viz's dev, the check "Build, format, and test" runs each unit test and each browser test once, compares the result with all 14 evidence files, and finishes in a median of 8 minutes or less; it reports success only when every test ran and passed; the ruleset on dev is as it was on 9 October 2026; the evidence refresh run finishes in 8 minutes or less and commits from a job that runs no test code; every finding of the security assessment that the new layout introduces or worsens is closed by a merged change with a test.

Proof: a command printed in the closing comment lists the length of the five most recent successful checks on pull requests and each is under 8 minutes; the gate job's log shows the guard's line for each of the 14 evidence files; a link to each deliberately broken run that the gate turned red; scripts/github-flows.sh check on the hub prints that safety.viz's rules still match; every requirement below is closed with its proof comment.

Ships in: safety.viz v1.11.0, milestone 2026-10-talk.

Requirements

In session order:

  1. The required check runs every test once, on parallel runners, and answers in about six minutes (#410).
  2. The evidence refresh run takes the same split and finishes in about the time the check does (#411).

Boundaries


This issue was drafted by Claude Code using Opus 5.5 from @jwildfire's request of 2026-10-09 and the spike it links. The tree is signed off only by his comment here.


Members are generated from the objective issue's sub-issue links at build time; priority is the selecting session's judgment, not list order (#53 v2). The --auto policy binding — active/paused, grant profile, repo-level backlog feeds — lives in obot.agent/goals/registry.json. Readiness labels: auto = ready for autonomous implementation, draft = needs @jwildfire steering.