M11-T05: Evaluate shared runtime seams after the third-engine proof #114
Description
Summary
After reservation-core is stable, compare allocdb-core, quota-core, and reservation-core and decide whether a shared runtime extraction is justified.
Questions
- which modules are copied nearly unchanged across all three engines
- which modules still only look similar
- is there now a coherent shared runtime worth extracting
- would quota/credits become materially easier to build atop that extracted layer
Required output
- one short seam evaluation document
- one clear decision: extract now, defer again, or abandon the library thesis
Canonical docs
- docs/reservation-engine-plan.md
Blocked by
- M11 umbrella issue
- M11-T04