1 Commits
Author SHA1 Message Date
5a64af938e fix(modules): follow workspace globs for a module's name and name the mod (#28)
A support module declared in a crate root that re-exports another workspace
crate (`pub use horizon_client_lib::*;` in Horizon's client after the crate
split) was refused as E_MODULE_CONFLICT for any unresolved glob, so a mod
like official_hitbox_plus failed on every newer Horizon. Planning now follows
a glob to the workspace module it names (crate, self, super, another
workspace crate, a child), up to 8 levels, and only refuses when the name is
really brought in or the glob can't be followed. The transform re-check keeps
to the module's own names on the same fingerprinted source.

Every module diagnostic now carries the declaring mod's id and the module
file, so a launcher can leave out the mod that caused it.

Co-authored-by: Horizon agent <[email protected]>
Co-authored-by: Claude Opus 5.5 <[email protected]>
2026-11-05 20:46:05 +01:00