feat(runtime): add slice entrypoints and release evidence

Author: PatrickJS

.async-pipeline/tasks.lock.json

@@ -127,5 +127,5 @@
     }
   ],
   "hash": "sha256:a1c7ccd8157fb3d57d743d34dabc6ef0707128933927ad88bbf5115d54cb5fce",
-  "generatedAt": "2026-06-19T06:33:36.393Z"
+  "generatedAt": "2026-06-19T20:11:34.666Z"
 }

.github/async-pipeline.lock.json

@@ -4,7 +4,7 @@
   "config": "pipeline.ts",
   "workflow": ".github/workflows/async-pipeline.yml",
   "hash": "sha256:ff505c9546fbc9043e54232d7642a1d6a2c6189b7263c0a4b1b8dd13ecf769b6",
-  "generatedAt": "2026-06-19T04:42:19.199Z",
+  "generatedAt": "2026-06-19T20:11:34.486Z",
   "triggers": {
     "pull_request": {},
     "push": {

.github/workflows/async-pipeline.yml

@@ -65,12 +65,12 @@ jobs:
       - name: Install dependencies
         run: pnpm install --frozen-lockfile
 
-      - name: Run pipeline task pack
+      - name: Run pipeline task release-evidence
         uses: async/actions/run@v0
         with:
-          command: "pnpm async-pipeline github check && pnpm async-pipeline run-task pack"
+          command: "pnpm async-pipeline github check && pnpm async-pipeline run-task release-evidence"
           check-generated: false
-          artifact-name: async-pipeline-${{ github.job }}-pack-runs
+          artifact-name: async-pipeline-${{ github.job }}-release-evidence-runs
         env:
           CI: true
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

AGENTS.md

@@ -26,7 +26,7 @@ root workspace `AGENTS.md` still applies.
   path, no implicit fetches during startup, and no server-only state or cache
   contents leaking into browser snapshots.
 - Keep Layer 1 and Layer 1.5 understandable without future compiler layers.
-  System 2 or compiler-required work must compile down to the same HTML,
+  L2 or compiler-required work must compile down to the same HTML,
   registry, snapshot, server-envelope, route-partial, cache, and boundary
   protocol.
 
@@ -37,19 +37,20 @@ Use these abbreviations in ADRs, issues, review notes, and Codex prompts:
 - `L1`: Layer 1, the no-build browser runtime core. It owns DOM scanning,
   attribute prefixes, event binding, signals, command handlers, startup, and the
   smallest usable runtime.
-- `L1.5`: Layer 1.5, the ordering layer above the runtime core. It owns the
-  scheduler, async signal settling, boundary ordering, route partial activation,
-  stream sequencing, and reveal/OOS coordination that still works without a
-  compiler.
-- `L2`: Layer 2, the app/server integration layer. It owns server functions,
-  routes, SSR output, build adapters, cache partitions, and higher-level
-  conventions layered onto L1 and L1.5 protocols.
+- `L1.5`: Layer 1.5, the no-build/low-build server and streaming bridge above
+  the runtime core. It owns scheduler ordering, async signal settling, SSR
+  activation, route partials, browser/server cache split, boundary patches,
+  stream sequencing, and reveal/OOS coordination without requiring a compiler.
+- `L2`: Layer 2, the build-required authoring/compiler profile. It owns JSX/TSX
+  authoring, build adapters, optimizer reports, generated plans, generated
+  registries, and chunk/manifest decisions that lower onto L1 and L1.5
+  protocols.
 - `NB`: no-build profile. Author HTML and JavaScript run directly with
   `Async.start(...)`, default shorthand attributes, and no compiler.
 - `BR`: build-required profile. Author JSX/TSX uses imports such as
-  `@async/framework/jsx`; the compiler/optimizer emits L1/L1.5/L2-compatible
+  `@async/framework/jsx`; the compiler/optimizer emits L1/L1.5-compatible
   output.
-- `OOOS`: out-of-order streaming/rendering. Chunks may become ready in a
+- `OOS`: out-of-order streaming/rendering. Chunks may become ready in a
   different order than source order.
 - `Suspense`: async boundary ownership for fallback and final content.
 - `Reveal`: OOS commit policy for sibling boundaries, such as `as-ready`,

CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.11.16 - 2026-06-19
+
+- Added runtime slice entrypoints for `@async/framework/runtime`,
+  `@async/framework/runtime/signals`, and `@async/framework/runtime/events`.
+- Added generated package artifacts and installed-package coverage for runtime
+  slice subpaths.
+- Added deterministic scenario-size fixtures and checks for runtime, router,
+  server-call, and boundary receiver examples.
+- Added package-owned release evidence checks before release ensure so generated
+  release workflows verify bundle and scenario evidence before publishing.
+- Bundle size from bundled TypeScript source: `browser.ts` raw 197,173 B (197.2 KB / 0.197 MB), gzip 37,198 B (37.2 KB / 0.037 MB), br 30,914 B (30.9 KB / 0.031 MB) -> `browser.min.js` raw 84,013 B (84.0 KB / 0.084 MB), gzip 24,894 B (24.9 KB / 0.025 MB), br 22,079 B (22.1 KB / 0.022 MB); delta raw -113,160 B (-113.2 KB / -0.113 MB), gzip -12,304 B (-12.3 KB / -0.012 MB), br -8,835 B (-8.8 KB / -0.009 MB).
+
 ## 0.11.15 - 2026-06-19
 
 - Made the source package private and kept its public surface to the minimal

README.md

@@ -43,10 +43,10 @@ Async.start({ root: document });
 
 ## What It Is
 
-`@async/framework` is the Layer 1 runtime plus the first Layer 2 app/server
-primitives. It keeps the runtime small and explicit:
+`@async/framework` is the L1 runtime plus the first L1.5 app/server and
+streaming primitives. It keeps the runtime small and explicit:
 
-- No build step for Layer 1 consumers.
+- No build step for L1 consumers.
 - No virtual DOM, diff path, hydration runtime, or component rerender loop.
 - Signals are the state boundary.
 - `Async.use(...)` registers app declarations before or after startup.
@@ -68,18 +68,14 @@ to the same runtime registries and HTML protocol.
 Async is designed as layers, so each level can stay useful without forcing the
 next level on every app.
 
-| Layer | Name | Requirement | Purpose |
+| Shorthand | Name | Requirement | Purpose |
 | --- | --- | --- | --- |
-| 1 | Runtime bootloader | No build. CDN or direct ESM import. | Signals, async signals, scheduler, handlers, command events, lifecycle pseudo-events, scoped fragments, and boundary swaps. |
-| 2 | App/server layer | Light server integration. No app compiler required. | `Async.use(...)`, router modes, server function proxy, partial registry, SSR output, browser activation, and split browser/server cache. |
-| 3 | Authoring build | Build step required. | JSX, ESM, and TypeScript authoring that lowers into Layer 1 HTML attributes and Layer 2 registries. |
-| 4 | Chunk and resumability metadata | Build metadata required. | Lazy module manifests, visibility/prefetch hints, resource graphs, and resumability records that the bootloader can consume. |
-| 5 | Framework compiler | Compiler required. | Server/client partitioning, code motion, optimized registry generation, serialized closures, and deeper resumability transforms. |
-| 6 | TSRX and intent layer | Higher-level compiler required. | More declarative author intent, AI/compiler-friendly metadata, and source forms that generate lower-layer Async apps. |
-
-The package in this repository intentionally focuses on Layers 1 and 2. Layers
-3 through 6 are higher authoring surfaces, not extra runtime requirements for
-plain HTML apps.
+| L1 | Runtime bootloader | No build. CDN or direct ESM import. | Signals, async signals, scheduler, handlers, command events, lifecycle pseudo-events, scoped fragments, and boundary swaps. |
+| L1.5 | App/server and streaming bridge | Light server integration. No app compiler required. | `Async.use(...)`, router modes, server function proxy, partial registry, SSR output, browser activation, split browser/server cache, and streamed boundary patches. |
+| L2 | Build-required authoring and compiler profile | Build step required. | JSX, ESM, and TypeScript authoring, optimizer reports, generated plans, generated registries, chunks, manifests, and future resumability records that lower onto L1 and L1.5 protocols. |
+
+The package in this repository intentionally focuses on L1 and L1.5. L2 is a
+higher authoring surface, not an extra runtime requirement for plain HTML apps.
 
 ## Install
 

examples/size/boundary-receiver/index.html

@@ -0,0 +1,15 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <title>Async scenario: boundary receiver</title>
+  </head>
+  <body>
+    <main>
+      <section async:boundary="product">
+        <p>Waiting for streamed HTML...</p>
+      </section>
+    </main>
+    <script type="module" src="./main.js"></script>
+  </body>
+</html>

examples/size/boundary-receiver/main.js

@@ -0,0 +1,11 @@
+import { Async, createBoundaryReceiver } from "../../../dist/browser.min.js";
+
+const runtime = Async.start({ root: document, router: false });
+const receiver = createBoundaryReceiver({
+  loader: runtime.loader,
+  signals: runtime.signals,
+  cache: runtime.browser.cache,
+  scheduler: runtime.scheduler
+});
+
+globalThis.boundaryReceiverScenario = receiver;

examples/size/boundary-receiver/scenario.json

@@ -0,0 +1,12 @@
+{
+  "id": "boundary-receiver",
+  "entry": "main.js",
+  "scripts": [
+    "../../../dist/browser.min.js",
+    "main.js"
+  ],
+  "budget": {
+    "mode": "baseline",
+    "maxGzipBytes": 26500
+  }
+}

examples/size/events-counter/index.html

@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <title>Async scenario: events counter</title>
+  </head>
+  <body>
+    <main>
+      <button type="button" on:click="increment">Add</button>
+      <strong signal:text="count">0</strong>
+    </main>
+    <script type="module" src="./main.js"></script>
+  </body>
+</html>