SoftFever 40cc3340b1 Content-address Bambu filament ids and check profiles against the catalog map ...

Every vendor's filament_id declarations, Bambu's own bundle included, are now
minted and checked the same way: the GF* catalog space is reserved but
ownerless, format is validated unconditionally with no snapshot or BBL
exemption, and both --remint and the default assign pass treat a non-OF
declaration as one needing a fresh mint (so a future BambuStudio sync
self-heals instead of needing a manual pass). A new check validates
resources/printers/bambu_filament_ids.json against the tree it describes:
that it parses, carries its header, keys only OF ids, maps each Bambu id once,
and agrees with the tree on every product it shares. The redundant BBL/OFL
carve-out in the profile checker's length check is dropped too, so it runs
the same way for every vendor.

The BBL bundle itself hasn't been touched yet and still declares its old GF
ids, so TestRealTree.test_shipped_snapshot_matches_tree is expected to fail
here (209 declarations flagged) until the next commit re-mints the bundle
onto OF ids.

2026-09-04 14:25:00 +08:00

..

__init__.py

filament_id: deterministic mint rule, sanctioned-state ledger, validator hardening

2026-07-02 23:17:15 +08:00

test_filament_id.py

Content-address Bambu filament ids and check profiles against the catalog map

2026-09-04 14:25:00 +08:00