Configuration settling
Setting template, sampling parameters, or calling reset() right before respond no longer races the response: configuration changes settle before generation starts, so the stop sequence, parameters, and context state a respond sees are always the ones you just set. Same seed after reset() now reproduces the same output. No API changes — the ordering is guaranteed internally (supersedes the awaitable variants proposed in #80; thanks @0xtommythomas-dev for the field report).
Structured output
@Generatable schemas now forbid undeclared keys (additionalProperties: false), so grammar-constrained generation produces exactly the declared fields instead of padding arbitrary extras that could truncate output at the context limit.
Contributors
0xtommythomas-dev