refactor: move Apple platform family into package - #2118
Conversation
Size Report
npm unpacked components
Startup median (7 runs, lower is better):
Top changed chunks:
Top changed packed files
|
|
|
Reviewed
Family landing order: #2116 first, #2117 second, #2118 rebased last against both; then validate the combined tip. |
|
Current head |
02d7e1a to
8179540
Compare
|
Addressed in
I also rebased onto current The final local |
|
Re-reviewed exact head |
8179540 to
a3c9d57
Compare
|
Rebased and published at
The stale Apple production tree is deleted with no compatibility shim or fallback. Local |
|
Reviewed exact head P2 — update ADR 0019 before merging. ADR 0019 still states that Apple exposes only the root façade plus Otherwise the W6 loader injection, focused host ports, sync contracts, generalized family policy, lazy production route, size result, mergeability, and all exact-head checks look good. |
Summary
Move the complete Apple family, including core and colocated tests, behind
@agent-device/platform-apple's exports map for W4 of #2082.mainafter W5 (refactor: move Android family behind package exports #2117) and W6 (refactor: move W6 platform families behind package facades #2116), preserving W6's injected snapshot-loader seam and focused host-file port.src/platforms/appleproduction tree with no compatibility shim or fallback, and routed production consumers through named Apple facades.Refs #2082
Validation
pnpm install --frozen-lockfilepnpm formatand format checkpnpm check:quickpnpm check:layering: 161 tests passed; the named-facade violation was observed red against the planted root-import shape, then green after restorationpnpm check:fallow --base origin/main: passed changed scopepnpm check:affected --run: 56 checks selected; all runnable checks passed, including 562 Vitest files / 4,535 tests, package, typecheck, layering, integration-node, macOS coverage, replay/wire compatibility, dependency, fixture, documentation, and mutation-model checksLocal proof covers TypeScript/unit/integration, packaging shape, layering, exports closure, and structural gates. GitHub remains authoritative for exact-head native/device/provider/full-coverage lanes; those lanes are not substituted by local proof. The local environment uses pnpm 11.21.0 while the repository pins 11.17.0.
Adversarial review residual risk: native/device/provider/full-coverage evidence depends on current-head GitHub checks and cannot be replaced by this host's local tests.