Repository navigation
Packvium 1.3.0
Portable operational artifacts for the Rust core, and execution plans that match the other
engines beyond the test corpus. Nothing breaks 1.2.0.
Added
packvium_core::artifacts::build_artifact_json(request_json, result_json, loading_orders_json)
builds onepackvium-operational-artifact/v1document: the execution plan, exact geometry,
the values a work order shows, and the request that produced it. Every Packvium
engine builds the same bytes from the same result. Errors areArtifactErrorwith an
ArtifactErrorCode.packvium_core::artifact_exports—export_json,export_csv(RFC 4180, 18 columns) and
export_work_order_html: a printable work order in one HTML file with no scripts and no
external resources.examples/artifacts.rs.
Fixed
execution::build_plan_jsondisagreed with the other engines on results outside the test
corpus. Score terms are now copied and compared by value, anullstatus is refused, a
nullloading order means no order and a non-integer entry is refused, and a missing
unplaced reason is written as the other engines write it. Floats are read exactly: the
default JSON parser could read one a step off and write different digits back.- The plan is written as RFC 8785, and a number beyond 2^53 − 1 is refused instead of written.
Changed
- The beam search caches its sort keys and the incumbent's key. Results are byte-identical.
On the wide cases measured (48 items, beam width 12) it took 18–26% less time for about
0.5 MB more resident memory. - A pinned catalog version resolves without scanning the version history.