create()'s cache pre-warm carries request-typed scalars instead of DB column types

[alexstandiford]

Split out of #28 (flagged in its audit as a knowingly-shipped follow-up).

create() hydrates the model it caches from Arr::merge($attributes, $ids) — the write-consistent hydration from #25, which is correct and stays. But the caller's scalar types ride along: an int written into a VARCHAR column serves as an int from the pre-warmed cache entry and as a string from a DB read, so a value's type can flap with cache state.

Siren contains the one observed case at the model boundary (Novatorius/siren#196, Config::getValue()), but the general fix belongs here: attribute hydration should normalize values to column types (via the Table column definitions) before building the model, so cache hits and DB reads are byte-identical. Driver differences (PDO native prepares vs emulated, DECIMAL-as-string, etc.) are the hard part and why this wasn't folded into #28.

🤖 Generated with Claude Code

[alexstandiford]

Update from #28's audit loop: create()'s cache pre-warm was removed outright (round-11 commit) after a second real hazard surfaced — a pre-warm keyed under create's own post-insert bump can seed the newest generation with a row a concurrent writer already overwrote. That moots the cache-entry half of this issue. What remains is the RETURNED MODEL: create() still hands back a model hydrated from request-typed attributes, so $model->getX() immediately after create can differ in scalar type from the same getter after a re-read. Driver-aware typed hydration is still the fix for that half.