fix: Use runtime struct matching for cross-package error types

[GitJuhb]

Problem

The v2 branch fails to compile when used as a dependency because lib/jido/error.ex uses compile-time struct pattern matching on external packages (jido_signal, jido_action).

error: Jido.Signal.Error.InvalidInputError.__struct__/0 is undefined
lib/jido/error.ex:710:31: Jido.Error.determine_unified_type/1

Root Cause

Patterns like %Jido.Signal.Error.InvalidInputError{} require the struct module to be compiled before the pattern is expanded. When jido is pulled as a hex/git dependency, compilation order isn't guaranteed relative to the external packages.

Key Finding: The modules DO exist in jido_signal 1.1.0 and jido_action 1.0.0. This is NOT a missing module - it's a compile-time vs runtime struct expansion issue.

The v2 branch works fine when developing locally (because the maintainers have jido_signal/jido_action as local path deps), but fails when used as an external dependency.

Fix

Replace %Module.Name{} with %{__struct__: Module.Name} for cross-package structs. This defers struct checking to runtime instead of compile-time, allowing the code to compile before external packages are loaded.

# BEFORE (compile-time struct expansion - breaks cross-package)
defp determine_unified_type(%Jido.Signal.Error.InvalidInputError{}), do: :validation_error

# AFTER (runtime struct check - works cross-package)
defp determine_unified_type(%{__struct__: Jido.Signal.Error.InvalidInputError}), do: :validation_error

Testing

• Tested compilation as a dependency in AgentTUI project
• Jido v2 instance starts successfully and agent operations work

---

🤖 Generated with Claude Code

[mikehostetler]

Thanks!!! I have some changes to push on this today too - it's coming together nicely