Files
bambuddy/backend
maziggy e899022116 fix(profiles): read the companion files that hold a preset's real gcode
A bundled preset can keep a setting in `<preset> template <key>.json`, a
    file the preset itself does not reference -- the desktop slicer finds it
    by name. Walking only `inherits` never reached it, so every one of the 56
    instantiable BBL machine presets resolved `machine_start_gcode` to the
    577-character generic block on fdm_machine_common instead of its own
    6.5-21 KB one. That block holds the M620 AMS load and the M1002
    gcode_claim_action calls, so a print sliced from it heats the bed, moves
    the toolhead and extrudes nothing (bambuddy#2838).

    Companions are now folded into each ancestor as the chain is walked, at
    that ancestor's precedence, so a caller's own value still wins and the
    0.2/0.6/0.8 variants reach their 0.4 sibling's companion. They are found
    by listing rather than by a fixed set of keys.

    Covered against the shipped bundle, not fixtures: a new e2e spec resolves
    all 56 presets inside the image and fails on any that still lands on the
    generic block.
2026-08-15 15:03:28 +02:00
..