specs/automation: inngest-probe-suite.t27 — safe probe suite behind /inngest_probe; training-stuck-check 404 retirement #3559

Tracking issue for PR #3556 (L1 traceability).

• specs/automation/inngest-probe-suite.t27: the spec of the safe probe suite the bot's /inngest_probe runs (host: gHashTag/999-multibots-telegraf gen-verilog: 26 of 32 modules reference struct fields under a prefix declared nowhere — no single prefix can be correct #2325, fpga-lint reports 32/32 green on files that do not elaborate — hierarchy never enters an uncalled function body #2326, fix(bitnet): axi_lite_slave accepted more transactions than it could answer (Closes #1968) #2331). States payload = manifest safe_probe + e2e_test: true, transport = Inngest GQL invokeFunction, expectations FAILED-at-guard | COMPLETED | skip, verdicts, forbidden side effects, one suite at a time.
• Judge rule as measured on production 2026-09-09/10: a guard that is a step name fails that step; a body-level guard leaves only the function error span; a step whose NonRetriableError ends the run may be left RUNNING by the server -- on a terminal run the first step that is not COMPLETED is the culprit.
• specs/functions/training-stuck-check.t27: NOTE gains the 404 retirement (host origin/master is a single orphan commit with no ancestor in common with the previous 2545-commit history (old history is safe) #2328): a training Replicate answers 404 for is marked failed in model_trainings with a fixed error text, one warn to the admin, no event, no user message; skipped in safe mode.
• Published-figures pin: test blocks 12456 -> 12459 (the spec adds three test blocks).