mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-28 01:01:12 -07:00
ScottW514
0ef2047625
The campaign log gains the F1 entry: the question was which of three carriers the factory uses for the progress bar, and the answer is that two of them collapse into one. Progress rides an outbound WSS type:"progress" frame that is itself the periodic settings report, every 30 s. The write-up lives in CLOUD.md; the log records how it was gotten and what else the capture proved, including a factory progress total that grew 256 KiB per interval because the factory live-appends to its own ring. BRINGUP's cloud item now lists F2 among the open work with the carrier settled, so what is owed is emitting the frame against the feeder's job total rather than the kernel byte counter. Documentation only, no behavior change, so no acceptance-catalog consequence.