v1.0.2.post1
v1.0.2.post1: validation boundary correction.
v1.0.2 added cross-provider model validation but the validation
fired at first-run time rather than at the binding moments
(Runtime construction and behavior registration) that CONTRACT
v1.0.2 #1 promised. External spot-check caught the gap: users
who constructed a Runtime with a registered conflicting behavior
got no signal until they called run_goal(), which is the wrong
discovery moment for a configuration error.
v1.0.2.post1 moves the validation to both binding moments:
- Runtime.init validates against the existing global registry
- register() and @llm_behavior decoration validate against live
Runtimes (tracked via WeakSet)
Cross-provider model mismatches now raise InvalidRuntimeConfiguration
at the moment the conflict comes into existence, not at first use.
The error message itself is unchanged and remains specific about
the model, the configured provider, and the fix.
This is a post-release fix to v1.0.2's broken promise, not a new
feature. The other v1.0.1 user-test findings remain scheduled for
v1.0.3.
See CHANGELOG.md for full notes.