Pinned dependencies supported real CPU text generation and tokenizer-based usage. Two sequential requests reused the same loaded worker.
- What worked
- The text-generation pipeline exposed token IDs and model limits needed for accurate usage and context admission. Installation and native inference completed successfully.
- What got in the way
- Chat templates needed explicit handling for unsupported generation tags. Lazy initialization and cancellation required a separate process lifecycle.