@supacloud/compiler 0.55.0 → 0.56.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/DELIVERY.md CHANGED
@@ -552,3 +552,29 @@ it cannot bypass platform SQL policy or grant database privileges. Platform
552
552
  runtime prerequisites are separately managed, not implicitly bundled.
553
553
  Building an archive is not evidence of backward compatibility, applied migrations,
554
554
  successful activation, application rollback or recovered data.
555
+
556
+ ## Compiled execution contract migration
557
+
558
+ Delivery builds now validate `app.manifest.json.executionPlan` against explicit
559
+ `commandCapabilities` before emitting a bundle. Applications with commands must
560
+ declare the capabilities of the adapters actually wired by their host; omitted
561
+ capabilities are unavailable at this boundary. For a named database adapter:
562
+
563
+ ```ts
564
+ commandCapabilities: {
565
+ requirePersistentAdapters: true,
566
+ permission: true,
567
+ rpc: {
568
+ orders: { boundary: "database", audit: true, idempotency: true, transaction: true },
569
+ },
570
+ }
571
+ ```
572
+
573
+ Declare every RPC branch. External adapters need reconciliation and must not
574
+ claim a database transaction around a remote effect. These declarations are
575
+ checked structurally; deployment still needs runtime adapter verification.
576
+
577
+ Upgrade compiler and Elysia adapter together, regenerate artifacts, and rebuild
578
+ the bundle. HTTP modules require the generated `registerRoutes` callback; old
579
+ route-array fallback has been removed. See the [adapter migration](../elysia/README.md#static-route-registration-migration)
580
+ and [command boundary migration](../app/EXECUTION.md#command-boundary-migration-sc4029).