Record stable Forge compiler baseline

Record stable Forge compiler baseline

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

built: 0 modules in 13.3 s
deployed: live · 0 modules on 3 nodes · push→live —

Changed files

modified docs/operations/forge-hot-loop.md

Diff

1 file changed, +10 -1

- The exact-SHA release gate passed all 13 stages in 163 seconds, including
  2,040 tests, direct transaction, relup, rolling replacement, infrastructure
  contracts, and disposable PostgreSQL release smoke tests.
- All three production nodes run structural baseline revision `3479f12` from
- All three production nodes first ran structural baseline revision `3479f12` from
  immutable application digest
  `sha256:f85db0085f33d8ad9f0b5823ec8276d5d4ee6b9b09765d98f5480a7be9009459`
  with builder digest
  `sha256:a259afaa7899e535e08edf78782be15871939beea67730553572189928c87642`.
- The fleet then moved to compiler-workspace baseline `2ab95a2`, application
  digest
  `sha256:2f992f90222068dbe4d3d31db20b0c28e2cd786be18047ff36342f3dbd8309f5`,
  and builder digest
  `sha256:fadd181dd0cde5efaa848090b7513dc9e08110ae7a1bafb132b1bae1109376de`.
  The exact-SHA gate passed 2,042 tests. The operator rebuilt the same SHA
  once with the new builder and settled that no-byte-change target against
  the already-running image. This records a manifest whose compiler source
  paths use the stable repository workspace before measuring direct loads.
- Forge classified the activation change as `needs_rolling_replace`, and the
  operator settled it as `live` only after every node reported revision
  `3479f12`, complete cluster membership, and local health. Later compatible

231	231		`- The exact-SHA release gate passed all 13 stages in 163 seconds, including`
232	232		`2,040 tests, direct transaction, relup, rolling replacement, infrastructure`
233	233		`contracts, and disposable PostgreSQL release smoke tests.`
234		-	- All three production nodes run structural baseline revision `3479f12` from
	234	+	- All three production nodes first ran structural baseline revision `3479f12` from
235	235		`immutable application digest`
236	236		`sha256:f85db0085f33d8ad9f0b5823ec8276d5d4ee6b9b09765d98f5480a7be9009459`
237	237		`with builder digest`
238	238		`sha256:a259afaa7899e535e08edf78782be15871939beea67730553572189928c87642`.
	239	+	- The fleet then moved to compiler-workspace baseline `2ab95a2`, application
	240	+	`digest`
	241	+	`sha256:2f992f90222068dbe4d3d31db20b0c28e2cd786be18047ff36342f3dbd8309f5`,
	242	+	`and builder digest`
	243	+	`sha256:fadd181dd0cde5efaa848090b7513dc9e08110ae7a1bafb132b1bae1109376de`.
	244	+	`The exact-SHA gate passed 2,042 tests. The operator rebuilt the same SHA`
	245	+	`once with the new builder and settled that no-byte-change target against`
	246	+	`the already-running image. This records a manifest whose compiler source`
	247	+	`paths use the stable repository workspace before measuring direct loads.`
239	248		- Forge classified the activation change as `needs_rolling_replace`, and the
240	249		operator settled it as `live` only after every node reported revision
241	250		`3479f12`, complete cluster membership, and local health. Later compatible