Battery validation

Grok16 5.2.0 gates releases through layered batteries. Run locally before tagging or deploying a prefix.

Smoke — `test-battery`

./scripts/grok16-toolchain.sh test-battery

paths · discern · status · verify · manifest · ironclad sanity · hostess gate

./scripts/grok16-toolchain.sh test-battery-expert

Smoke + ironclad verify + linker verify + RTX gate + expert profile compile

G16_RELEASE_PROFILE=1 ./scripts/grok16-toolchain.sh test-battery-heavy

Expert chain + profile=heavy bench + field-bench under release profile

G16_RELEASE_PROFILE=1 ./scripts/grok16-toolchain.sh test-battery-release

Step	What it proves
heavy	Release-profile compile + bench
py-battery	`tests/test_g16_battery.py`
forever-battery	Hostess7 forever profile contract
binutils-battery	g16-as / g16-ld / g16-objdump
verify	Full verify incl. linker link smoke

./scripts/grok16-toolchain.sh test-battery-belt

Doctrine data/grok16-single-fabric-doctrine.json · profiles belt_1_0 / belt_2_0 · tests/test_g16_belt_battery.py · triad artifact optional.

Linker / libgcc_s — ensure file lib64/libgcc_s.so.1 shows shared object, not PIE executable
LTO — profile flags normalize -flto=thin per compiler capability
PGO — use flags only when data/pgo/*.gcda exist
g16-ld missing — ./scripts/grok16-binutils.sh install