mirror of
https://github.com/Klipper4FlashForge/firmware.git
synced 2026-10-21 21:02:16 -05:00
Oleksandr ShyshatskyiandClaude Opus 5
d05565284d
E -- values and counts. The START_PRINT prologue has no M400 and an idle timeout of 864000, not 1800000. The nozzle-clean temperature comes from the material table FIRST, so NOZZLE=240 with no per-tool temp cleans at 220 -- documented backwards before. TOOLS is the paired 0:220,2:240 form. The wipe Z is the raw eddy frame, not the homed one. The runout M117 strings are "T<n> clog" / "T<n> out of filament", not E-codes. Grab-verify raises E0051+tool, not E0143. Docks are at X~297; 250/280 are staging waypoints. The grab sequence is documented in the order _grab actually emits it. ff_print exposes seven status fields, not nine, and never emits TOOLS=. Package sizes reconciled against the real artifacts (62MB built, ~93MB stock, ~370MB of CI assets, ~60s not 90s). testing.md's sample output block matched no header the code prints, so it is replaced with the real ones; its pytest row listed two of six suites. F -- stale claims. _FF_PREFLIGHT is not "missing". SDCARD_SET_CHANNEL is not still issued (764af2a). The app and Moonraker do not coexist; the app is gone. TOOLCHANGE_STATUS has nothing to compare against since the JSON reader was removed. The JSON is re-imported every boot until a nozzle is saved, not once. The 23-check render harness was deleted in91604c2. PURGE now wipes by default. 50-print-lifecycle.md gained the section on how the sequences are actually entered now -- [ff_print], not the slicer. The dead "profiles" concept is gone from three files, one of which printed it on every replica run. G -- overclaims. The README no longer says a stock reflash puts the printer back "exactly as it was": it says what is restored and what survives inert, which is what test-recovery actually asserts. The random ssh password is conditional on ROOT_PW_HASH being unset. verify.sh no longer warns "ssh will not start" on every build for a dropbear we deliberately do not ship -- the check now reads the way round it means. case-install.sh's read-only block says it asserts nothing. An uncalibrated tool contributes z_adjust, not zero, in three operator-facing places. offset_base does not cancel out in X/Y. The safe-moves file's Z50 promise is scoped to its own lines, with the implicit prepare's G1 Z10 spelled out. 48 passed, 5 skipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>