Development record
2026-08-31 — The cold-reading evals' CI job is NOT added to the branch
2026-08-31 — The cold-reading evals' CI job is NOT added to the branch
ruleset's required-check list yet, and the sequencing is the decision rather
than the delay. The job and its make target exist only on
experiment/cold-reading; neither is on main, which was checked rather than
assumed. A required status check blocks a pull request until that context
reports, and a context no workflow on the base branch produces never reports —
so arming cold-reading-evals on the active main protection ruleset before
the workflow reaches main would wedge every merge to main, including the
very pull request that would deliver the workflow. The order is therefore:
merge the workstream to main first, confirm the job runs and reports its
context on a real pull request, and only then add it to the live ruleset and
to the committed mirror at .abcd/work/rulesets/main-protection.json in one
change. Rejected: updating the mirror now to record the intent, because a
mirror asserting a required check that is not required is a false record of
exactly the kind this phase spent the day removing, and it would read as
done. Until the arming lands, itd-186's always-run lane runs on every pull
request and gates none of them, which is a green for work that did happen but
binds nothing — the weaker half of the failure spc-64 was written against.
Tracked at iss-2608311051046981.
Frontmatter
| id | dcn-2608310000000010 |
|---|---|
| type | decision |
| date | 2026-08-31 |
.abcd/work/decisions/dcn-2608310000000010-the-cold-reading-evals-ci-job-is-not.md
open on GitHub ↗ · commit history ↗
mentions3
- iss-2608311051046981The new cold-reading-evals CI job is not a required status check: .abcd/work/rulesets/main-protection.json lists attribution, check (macos-latest), check (ubuntu-latest), external-review, gitleaks, record-lint, smoke and zizmor, and the job spc-64 lands reports a conclusion without gating the merge. The whole point of the always-run lane is that a record-only pull request cannot reach main with warm content in included material, and an unrequired check does not stop one. Add cold-reading-evals to the ruleset and to its committed mirror.
- itd-186The read-block eval falsifies the firewall — planted warm content that reaches a reading fails the build loudly
- spc-64The read-block eval falsifies the firewall