Repository navigation
Commit 4b5a9cb
docs: cite the red-push proof that Render follows
Item 13's notes say the first promoted run cannot distinguish
autoDeploy-from-main from autoDeploy-from-release: both branches hold the
same sha, so the wire looks identical either way. The discriminator is a
RED push, and this host produced one by accident.
Run 33337712632: ee75b5b reached main at 21:55:01Z and the matrix went red
at 21:57:01Z on ci/lint, so the deploy job SKIPPED and `release` never
moved — it went bdd8e77 -> 625c91c and never held ee75b5b. Those are this
session's own readings. The ops seat's sampler, which this session did NOT
run, shows the wire holding bdd8e77 across the whole window
21:54:34-22:01:29. On a host whose promote->wire time is about 90 seconds,
a Render watching `main` would have built the red sha inside that window.
It did not.
Both halves are needed and the fence says which is whose: the run evidence
is mine, the in-window wire sampling is the seat's. Recorded because
`deploy: release-branch` can now be cited as measured rather than
consistent-with, and because the next fork to adopt item 13 can reproduce
it deliberately instead of waiting for a lint failure to hand it over.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EjfiNPKsgLwAxtN3BexPSJrelease on this host1 parent c462973 commit 4b5a9cb
1 file changed
Lines changed: 19 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
187 | 187 | | |
188 | 188 | | |
189 | 189 | | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
190 | 209 | | |
191 | 210 | | |
192 | 211 | | |
| |||
0 commit comments