ScottW514 298abf8a12 Item 3: fold the debug kernel into the closing build ...

kas/forgefirm-glowforge-debug.yml builds one dev image on the debug
kernel (FORGEFIRM_KERNEL_DEBUG=1, tagged dev-debug) beside the closing
release and dev images; the debug options never touch either.
scripts/bench/debug_kernel_drills.py runs the two drills (three
load/unload cycles under DEBUG_MUTEXES, a forced -EPROBE_DEFER unwind),
each read against dmesg for lock splats, refusing on a non-debug kernel
or a non-idle machine; it is registered as a board bench tool. BRINGUP
item 3 names the mechanism and stays remaining work (run it on the
closing burn); the site's Build page documents the variant.

2026-08-31 15:54:28 -04:00

..

ci.yml

CI: dispatch-only cold-build reproducibility workflow

2026-08-08 13:32:00 -04:00

forgefirm-glowforge-debug.yml

Item 3: fold the debug kernel into the closing build

2026-08-31 15:54:28 -04:00

forgefirm-glowforge.lock.yml

kas: record the push/release order and lock upstream layers

2026-07-26 13:30:47 -04:00

forgefirm-glowforge.yml

Move the build, release, and acceptance docs to the documentation site

2026-08-26 10:00:42 -04:00