webloom-framework 0.2.0 → 0.3.0

package/dist/react.d.ts

@@ -1,7 +1,7 @@
 import * as react_jsx_runtime from 'react/jsx-runtime';
 import * as react from 'react';
 import { ReactNode } from 'react';
-import { s as PluginHost, aj as PluginState, a as PluginGraph, c as PluginReverseDep, ag as PluginIntentSubmissionResult, P as PluginManifest, aF as ResourceStoreApi, aD as ResourceSnapshot } from './createPluginHost-ChJNBTsX.js';
+import { m as PluginHost, ad as PluginState, a as PluginGraph, c as PluginReverseDep, aa as PluginIntentSubmissionResult, P as PluginManifest, aF as ResourceStoreApi, aD as ResourceSnapshot } from './createPluginHost-BVsUCDKN.js';
 
 declare const PluginHostContext: react.Context<PluginHost | undefined>;
 interface PluginHostProviderProps {

package/dist/resourceRegistry-BFnjmeGE.d.ts

@@ -0,0 +1,267 @@
+import { i as PluginSetup, aL as RuntimeUnitImplementationRegistry, R as RuntimeKind, ae as PluginStateKind, r as RemoteServiceReference, s as RemoteServiceMessageCodec, ah as PluginUnitState, au as RemoteServiceProxy, m as PluginHost, L as LifecycleDisposeResult, M as MessageBus, K as LifecycleScopeKind, o as LifecycleScopeIdentity, n as LifecycleScope, a9 as PluginIntentSnapshot, a7 as PluginIntentController, ax as RemoteServiceTransport, am as RemoteServiceBridge, ao as RemoteServiceCallContext, aC as ResourceRegistry, aA as ResourceDefinition } from './createPluginHost-BVsUCDKN.js';
+
+interface RuntimeUnitImplementation {
+    /** 产品标识。 */
+    pluginId: string;
+    /** 稳定运行单元标识。 */
+    unitId: string;
+    /** 当前环境的可执行入口。 */
+    setup: PluginSetup;
+}
+/** 创建一个拒绝重复注册、按产品和单元查找实现的运行时注册表。 */
+declare function createRuntimeUnitImplementationRegistry(implementations?: readonly RuntimeUnitImplementation[]): RuntimeUnitImplementationRegistry & {
+    register(implementation: RuntimeUnitImplementation): void;
+    unregister(pluginId: string, unitId: string): void;
+};
+
+declare const RUNTIME_PROTOCOL_VERSION = "webloom.runtime.v2";
+declare const RUNTIME_SNAPSHOT_TYPE = "webloom.runtime.snapshot";
+declare const RUNTIME_ERROR_TYPE = "webloom.runtime.error";
+interface RuntimeErrorMessage {
+    type: typeof RUNTIME_ERROR_TYPE;
+    protocolVersion: string;
+    code: "runtime_initialization_failed" | "protocol_mismatch" | "transport_unavailable";
+    message: string;
+    pluginId?: string;
+    unitId?: string;
+    phase?: "startup" | "snapshot";
+}
+interface RuntimeSnapshot {
+    type: typeof RUNTIME_SNAPSHOT_TYPE;
+    protocolVersion: string;
+    runtimeId: string;
+    runtimeKind: RuntimeKind;
+    runtimeInstanceId: string;
+    revision: number;
+    state: "starting" | "ready" | "stopping" | "failed" | "disposed";
+    units: readonly RuntimeSnapshotUnit[];
+    services: readonly RemoteServiceReference[];
+}
+interface RuntimeSnapshotUnit {
+    pluginId: string;
+    unitId: string;
+    runtime: RuntimeKind;
+    instanceId?: string;
+    state: PluginStateKind;
+}
+declare function createRuntimeMessageCodec(): RemoteServiceMessageCodec;
+/** 只验证外层结构；协议版本接受由 RuntimeHandle 单独处理。 */
+declare function isRuntimeSnapshot(input: unknown): input is RuntimeSnapshot;
+declare function isRuntimeSnapshotProtocol(input: RuntimeSnapshot): boolean;
+declare function isRuntimeError(input: unknown): input is RuntimeErrorMessage;
+/** 将 Host 的 PluginUnitState 映射成不会泄露领域配置的运行时快照。 */
+declare function unitSnapshotFromState(state: PluginUnitState, runtime: RuntimeKind): RuntimeSnapshotUnit;
+
+type RuntimeAppState = "starting" | "ready" | "stopping" | "failed" | "disposed" | "disconnected";
+interface RuntimeStatusSnapshot {
+    runtimeId: string;
+    runtimeKind: RuntimeKind;
+    runtimeInstanceId: string;
+    state: RuntimeAppState;
+    revision: number;
+    units: readonly RuntimeSnapshotUnit[];
+    services: readonly RemoteServiceReference[];
+    error?: string;
+}
+type RuntimeStatusListener = (snapshot: RuntimeStatusSnapshot) => void;
+interface WindowApp {
+    readonly runtimeKind: "window-main";
+    readonly runtimeId: string;
+    readonly runtimeInstanceId: string;
+    /** 已由 createWindowApp 装配并注册完成的本地 Host。 */
+    readonly host: PluginHost;
+    state(): RuntimeStatusSnapshot;
+    /** 获取当前本地 capability；停止或销毁后同步抛错。 */
+    capability<T>(capabilityId: string): T;
+    subscribe(listener: RuntimeStatusListener): () => void;
+    dispose(reason?: string): Promise<LifecycleDisposeResult>;
+}
+interface RuntimeHandle {
+    readonly runtimeKind: "shared-worker";
+    readonly runtimeId: string;
+    /** 当前已观察到的 Worker 启动身份；首份快照前为 undefined。 */
+    readonly runtimeInstanceId?: string;
+    state(): RuntimeStatusSnapshot;
+    capability<T = unknown>(capabilityId: string, options?: {
+        contractVersion?: string;
+    }): RemoteServiceProxy & {
+        readonly serviceType?: T;
+    };
+    subscribe(listener: RuntimeStatusListener): () => void;
+    dispose(reason?: string): Promise<void>;
+}
+/** 跨 realm 初始化失败；不把 required 插件错误包装成成功状态。 */
+interface RuntimeInitializationErrorDetails {
+    pluginId?: string;
+    unitId?: string;
+    phase: "validate" | "register" | "startup" | "snapshot";
+    error: string;
+}
+declare class RuntimeInitializationError extends Error {
+    readonly code: "runtime_initialization_failed";
+    readonly details: RuntimeInitializationErrorDetails;
+    constructor(details: RuntimeInitializationErrorDetails);
+}
+declare class RuntimeUnavailableError extends Error {
+    readonly code: "transport_unavailable";
+    constructor(message?: string);
+}
+
+interface SharedWorkerLike {
+    readonly port: MessagePort;
+    onerror?: (event: Event) => void;
+    addEventListener?(type: "error", listener: (event: Event) => void): void;
+    removeEventListener?(type: "error", listener: (event: Event) => void): void;
+}
+type SharedWorkerFactory = (url: string | URL, options: {
+    type: "module";
+    name?: string;
+    credentials?: RequestCredentials;
+}) => SharedWorkerLike;
+/**
+ * 临时迁移接缝：下游 typed transfer API 完成前允许领域代码在同一
+ * 物理端口安装 listener。它不参与 Runtime 授权，也不传 connectionId。
+ */
+interface SharedWorkerConnectionContext {
+    readonly worker: SharedWorkerLike;
+    readonly port: MessagePort;
+}
+interface ConnectSharedWorkerOptions {
+    id: string;
+    url: string | URL;
+    name?: string;
+    credentials?: RequestCredentials;
+    defaultCallTimeoutMs?: number;
+    /** SWCF-009 完成前的临时同端口迁移接缝。 */
+    onConnection?: (context: SharedWorkerConnectionContext) => void;
+}
+/** 创建生产 RuntimeHandle；测试工厂不属于生产公共选项。 */
+declare function connectSharedWorker(options: ConnectSharedWorkerOptions): RuntimeHandle;
+/** 仅由 `webloom-framework/testing` 暴露的 SharedWorker 工厂注入入口。 */
+declare function connectSharedWorkerForTesting(options: ConnectSharedWorkerOptions, workerFactory: SharedWorkerFactory): RuntimeHandle;
+
+declare function createMessageBus(): MessageBus;
+
+interface CreateResourceScopeOptions {
+    /** 可选固定作用域标识；生产代码通常省略，让实现生成不可复用 ID。 */
+    scopeId?: string;
+    /** 运行实例标识；省略时与 scopeId 同源生成。 */
+    instanceId?: string;
+    /** 作用域类型。 */
+    kind: LifecycleScopeKind;
+    /** 绑定插件和宿主只读属性。 */
+    metadata?: Omit<Partial<LifecycleScopeIdentity>, "scopeId" | "instanceId" | "kind">;
+    /** 测试或宿主诊断使用的状态变更回调。 */
+    onChange?: (scope: LifecycleScope) => void;
+    /** 子作用域生成最终清理结果后的内部通知；用于更新父级登记。 */
+    onDisposeResult?: (result: LifecycleDisposeResult) => void;
+}
+/**
+ * 创建一个可嵌套的生命周期作用域。
+ *
+ * `createResourceScope` 是 `createLifecycleScope` 的同义入口，方便不同
+ * 模块按“作用域”或“资源”语义调用；两者不代表两套实现。
+ */
+declare function createLifecycleScope(options: CreateResourceScopeOptions): LifecycleScope;
+/** 语义别名：资源管理代码通常以 ResourceScope 称呼同一原语。 */
+declare const createResourceScope: typeof createLifecycleScope;
+type ResourceScopeOptions = CreateResourceScopeOptions;
+
+interface CreatePluginIntentControllerOptions {
+    /** 当前控制面启动身份；Worker 重启时应传入新值。 */
+    authorityInstanceId?: string;
+    /** Worker 恢复后读取的平台意图。 */
+    initial?: Partial<PluginIntentSnapshot>;
+    /** 将候选快照原子写入平台存储；缺省表示内存控制面（测试用）。 */
+    persist?: (snapshot: PluginIntentSnapshot) => Promise<void>;
+    /** 有界去重记录数量，避免 commandId 永久增长。 */
+    maxCommandRecords?: number;
+}
+/** 创建单一控制面上的插件意图控制器。 */
+declare function createPluginIntentController(options?: CreatePluginIntentControllerOptions): PluginIntentController;
+
+interface CreateServiceBridgeOptions {
+    /** 要接受的精确服务协议版本。 */
+    protocolVersion: string;
+    /** 实际端口 RPC 传输；桥不负责重放请求。 */
+    transport: RemoteServiceTransport;
+    /** 默认总 deadline；必须有限且大于零。 */
+    defaultCallTimeoutMs?: number;
+}
+/** 创建一个无连接握手、无增量 revision 状态机的服务桥。 */
+declare function createServiceBridge(options: CreateServiceBridgeOptions): RemoteServiceBridge;
+
+interface RemoteServicePortCallMessage {
+    type: string;
+    protocolVersion: string;
+    callId: string;
+    capabilityId: string;
+    contractVersion: string;
+    serviceInstanceId: string;
+    operationId?: string;
+    grantId?: string;
+    request: unknown;
+}
+interface RemoteServicePortResultMessage {
+    type: string;
+    protocolVersion: string;
+    callId: string;
+    serviceInstanceId: string;
+    result: unknown;
+}
+interface RemoteServicePortErrorMessage {
+    type: string;
+    protocolVersion: string;
+    callId: string;
+    serviceInstanceId: string;
+    error: {
+        name?: string;
+        message: string;
+        code: string;
+        details?: Readonly<Record<string, unknown>>;
+    };
+}
+interface RemoteServicePortCancelMessage {
+    type: string;
+    protocolVersion: string;
+    callId: string;
+    serviceInstanceId: string;
+}
+type RemoteServicePortResponseMessage = RemoteServicePortResultMessage | RemoteServicePortErrorMessage;
+interface CreateMessagePortServiceTransportOptions {
+    /** 已由实际 Worker / Window 连接产生的双工端口。 */
+    port: MessagePort;
+    /** 可选 transferable 提取器；默认只发送结构化克隆数据。 */
+    transferForRequest?: (request: unknown, context: RemoteServiceCallContext) => readonly Transferable[];
+    /** dispose 时是否关闭端口；默认不关闭，由端口所有者决定。 */
+    closeOnDispose?: boolean;
+    /** wire 消息 codec；默认 webloom.remote-service.v2。 */
+    codec?: RemoteServiceMessageCodec;
+    /** 直接使用 transport 时的默认总 deadline。 */
+    defaultCallTimeoutMs?: number;
+}
+/** 创建一条不携带连接身份、不会自动重放的 MessagePort transport。 */
+declare function createMessagePortServiceTransport(options: CreateMessagePortServiceTransportOptions): RemoteServiceTransport & {
+    dispose(): void;
+};
+/** Provider 侧调用消息的结构化输入。 */
+interface MessagePortServiceCallInput {
+    message: RemoteServicePortCallMessage;
+    /** Provider 的权威目录命中的服务引用。 */
+    reference: RemoteServiceReference;
+    signal: AbortSignal;
+}
+
+/**
+ * 资源注册表实现
+ *
+ * 设计缘由：管理资源定义的注册和查询，支持 owner-aware 生命周期。
+ * 重复 id 抛错，disable 时可回收。
+ */
+
+/** 资源注册表实现 */
+declare function createResourceRegistry(): ResourceRegistry;
+/** Internal runtime hook; deliberately absent from ResourceRegistry's public type. */
+declare function registerOwnedResource(registry: ResourceRegistry, ownerId: string, definition: ResourceDefinition<any, any>): void;
+
+export { createMessageBus as A, createMessagePortServiceTransport as B, type ConnectSharedWorkerOptions as C, createPluginIntentController as D, createResourceRegistry as E, createResourceScope as F, createRuntimeMessageCodec as G, createRuntimeUnitImplementationRegistry as H, createServiceBridge as I, isRuntimeError as J, isRuntimeSnapshot as K, isRuntimeSnapshotProtocol as L, type MessagePortServiceCallInput as M, registerOwnedResource as N, unitSnapshotFromState as O, type SharedWorkerFactory as P, connectSharedWorkerForTesting as Q, type RuntimeHandle as R, type SharedWorkerConnectionContext as S, type WindowApp as W, type RuntimeStatusSnapshot as a, type RuntimeStatusListener as b, type CreateMessagePortServiceTransportOptions as c, type CreatePluginIntentControllerOptions as d, type CreateResourceScopeOptions as e, type CreateServiceBridgeOptions as f, RUNTIME_ERROR_TYPE as g, RUNTIME_PROTOCOL_VERSION as h, RUNTIME_SNAPSHOT_TYPE as i, type RemoteServicePortCallMessage as j, type RemoteServicePortCancelMessage as k, type RemoteServicePortErrorMessage as l, type RemoteServicePortResponseMessage as m, type RemoteServicePortResultMessage as n, type ResourceScopeOptions as o, type RuntimeAppState as p, type RuntimeErrorMessage as q, RuntimeInitializationError as r, type RuntimeInitializationErrorDetails as s, type RuntimeSnapshot as t, type RuntimeSnapshotUnit as u, RuntimeUnavailableError as v, type RuntimeUnitImplementation as w, type SharedWorkerLike as x, connectSharedWorker as y, createLifecycleScope as z };

package/dist/testing.d.ts

@@ -1,6 +1,6 @@
-import { ar as RemoteServiceCallContext, C as CreatePluginHostOptions, s as PluginHost, aw as RemoteServiceTransport } from './createPluginHost-ChJNBTsX.js';
-export { z as CapabilityRegistry, A as ContextExtensionInput, B as ContributionAdapter, D as ContributionAdapterInput, E as ContributionHandle, a6 as PermissionPolicyInput, a7 as PermissionPolicyResult, a9 as PluginConfigStore, aG as RuntimeUnitAttributesInput, aH as RuntimeUnitAvailabilityInput, aM as RuntimeUnitParentScopeInput, aN as RuntimeUnitSnapshot, aR as StartupCapabilityError, aT as StartupPluginError, b1 as createCapabilityRegistry, b2 as createInMemoryPluginConfigStore, b3 as createPluginHost, b5 as createResourceStore } from './createPluginHost-ChJNBTsX.js';
-export { C as CreateMessagePortServiceTransportOptions, a as CreatePluginIntentControllerOptions, b as CreateResourceScopeOptions, c as CreateServiceBridgeOptions, R as RemoteServicePortCallMessage, d as RemoteServicePortCancelMessage, e as RemoteServicePortErrorMessage, f as RemoteServicePortResponseMessage, g as RemoteServicePortResultMessage, h as ResourceScopeOptions, i as RuntimeUnitImplementation, j as createLifecycleScope, k as createMessageBus, l as createMessagePortServiceTransport, m as createPluginIntentController, n as createRemoteServiceBridge, o as createResourceRegistry, p as createResourceScope, q as createRuntimeUnitImplementationRegistry, r as createServiceBridge } from './resourceRegistry-MNM1c7od.js';
+import { ao as RemoteServiceCallContext, C as CreatePluginHostOptions, m as PluginHost, ax as RemoteServiceTransport } from './createPluginHost-BVsUCDKN.js';
+export { t as CapabilityRegistry, u as ContextExtensionInput, v as ContributionAdapter, w as ContributionAdapterInput, x as ContributionHandle, a0 as PermissionPolicyInput, a1 as PermissionPolicyResult, a3 as PluginConfigStore, aG as RuntimeUnitAttributesInput, aH as RuntimeUnitAvailabilityInput, aM as RuntimeUnitParentScopeInput, aN as RuntimeUnitSnapshot, aR as StartupCapabilityError, aT as StartupPluginError, b1 as createCapabilityRegistry, b2 as createInMemoryPluginConfigStore, b3 as createPluginHost, b5 as createResourceStore } from './createPluginHost-BVsUCDKN.js';
+export { c as CreateMessagePortServiceTransportOptions, d as CreatePluginIntentControllerOptions, e as CreateResourceScopeOptions, f as CreateServiceBridgeOptions, M as MessagePortServiceCallInput, j as RemoteServicePortCallMessage, k as RemoteServicePortCancelMessage, l as RemoteServicePortErrorMessage, m as RemoteServicePortResponseMessage, n as RemoteServicePortResultMessage, o as ResourceScopeOptions, w as RuntimeUnitImplementation, P as SharedWorkerFactory, Q as connectSharedWorkerForTesting, z as createLifecycleScope, A as createMessageBus, B as createMessagePortServiceTransport, D as createPluginIntentController, E as createResourceRegistry, F as createResourceScope, H as createRuntimeUnitImplementationRegistry, I as createServiceBridge } from './resourceRegistry-BFnjmeGE.js';
 
 interface FakeTransportCall {
     /** 调用请求体。 */

package/dist/testing.js

@@ -1,5 +1,5 @@
-import { createPluginHost } from './chunk-URY3E6UH.js';
-export { StartupCapabilityError, StartupPluginError, createCapabilityRegistry, createInMemoryPluginConfigStore, createLifecycleScope, createMessageBus, createMessagePortServiceTransport, createPluginHost, createPluginIntentController, createRemoteServiceBridge, createResourceRegistry, createResourceScope, createResourceStore, createRuntimeUnitImplementationRegistry, createServiceBridge } from './chunk-URY3E6UH.js';
+import { createPluginHost } from './chunk-76BGPI6M.js';
+export { StartupCapabilityError, StartupPluginError, connectSharedWorkerForTesting, createCapabilityRegistry, createInMemoryPluginConfigStore, createLifecycleScope, createMessageBus, createMessagePortServiceTransport, createPluginHost, createPluginIntentController, createResourceRegistry, createResourceScope, createResourceStore, createRuntimeUnitImplementationRegistry, createServiceBridge } from './chunk-76BGPI6M.js';
 
 // src/testing/fakes.ts
 function createFakeRemoteServiceTransport(options = {}) {

package/docs/api.md

@@ -2,15 +2,15 @@
 
 ## 浏览器 Runtime
 
-WebLoom v1 只支持两个真实 JavaScript realm：`window-main` 和
+WebLoom 0.3.0 只支持两个真实 JavaScript realm：`window-main` 和
 `shared-worker`。`runtime` 是受限的 `RuntimeKind`，不是可自由填写的环境标签；
-不支持的 runtime 在装配边界 fail closed。v1 不实现 Server、Service Worker 或
+不支持的 runtime 在装配边界 fail closed。不实现 Server、Service Worker 或
 其它服务端 PluginHost。
 
 一次 Runtime 启动会生成不可复用的 `runtimeInstanceId`。每个插件运行单元启动
-会生成不可复用的 `unitInstanceId`（在 Host 的兼容状态接口中表现为
-`instanceId`）。同一 SharedWorker 接收多个 Window 连接时，Worker 单元仍只有
-一个实例；每条端口连接拥有独立的 `connectionId`、请求和取消空间。
+会生成不可复用的运行单元 `instanceId`。同一 SharedWorker 接收多个 Window 连接
+时，Worker 单元仍只有一个实例；端口本身隔离请求和取消空间，物理端口身份不进入
+公共 Runtime 或 RemoteService wire。
 
 ## 普通插件 API
 
@@ -70,7 +70,7 @@ Window 入口：
 import coordinatorWorkerUrl from "./coordinator.worker.ts?sharedworker&url";
 import { connectSharedWorker } from "webloom-framework";
 
-const runtime = await connectSharedWorker({
+const runtime = connectSharedWorker({
   id: "coordinator",
   url: coordinatorWorkerUrl,
 });
@@ -79,10 +79,11 @@ const storage = runtime.capability("storage.service");
 await storage.call({ key: "hello" });
 ```
 
-连接入口必须创建真实的 `new SharedWorker(url, { type: "module" })`。握手成功
-后必须先收到完整 baseline；后续快照 revision 必须连续。断线、revision gap、
-Worker 重启或 Provider 实例变化都会同步撤销旧代理。重连只建立新连接和新代理，
-不会重放可能产生外部副作用的调用，也不会静默替换旧代理的绑定。
+连接入口必须创建真实的 `new SharedWorker(url, { type: "module" })`，并同步返回
+本地 `RuntimeHandle`。Worker 只发布完整 `RuntimeSnapshot`；`capability()` 总是
+返回惰性代理，第一次 `call()` 在同一个有限 deadline 内等待目录和远程执行。断线、
+协议不兼容、Worker 重启或 Provider 实例变化都会同步撤销旧代理。显式重建只建立
+新句柄和新代理，不会重放可能产生外部副作用的调用，也不会静默替换旧代理的绑定。
 
 这里的 `url` 必须是 Bundler 产出的 JavaScript Worker URL。Vite 使用
 `?sharedworker&url` 或等价的独立 Rollup entry；不要把
@@ -95,10 +96,8 @@ Worker 重启或 Provider 实例变化都会同步撤销旧代理。重连只建
 | --- | --- |
 | `runtimeId` | Worker 的逻辑标识 |
 | `runtimeInstanceId` | 当前 Worker 物理启动身份 |
-| `connectionId` | 当前 Window 物理连接身份 |
-| `state()` | `connecting / ready / disconnected / failed / disposed` 快照 |
-| `ready()` | 等待握手和完整 baseline；不可自动重连的断线、failed 或 disposed 后持续拒绝 `RuntimeUnavailableError`，自动重连时只等待新的 readiness generation |
-| `capability()` | 获取绑定 Runtime、Provider、契约版本和 revision 的代理 |
+| `state()` | `starting / ready / disconnected / failed / stopping / disposed` 快照 |
+| `capability()` | 立即获取惰性代理；第一次 `call()` 精确绑定 Runtime/service instance |
 | `subscribe()` | 观察 Runtime/Unit/服务快照 |
 | `dispose()` | 同步撤销本句柄，异步关闭连接资源 |
 
@@ -117,21 +116,23 @@ const app = await createWindowApp({
       contractVersion: "coordinator.service.v1",
       sourceRuntime: "shared-worker",
     }],
-    async setup(ctx) {
+    setup(ctx) {
       const coordinator = ctx.serviceBridge?.requireProxy({
         capabilityId: "coordinator.service",
         contractVersion: "coordinator.service.v1",
         runtime: "shared-worker",
       }, ctx.scope);
-      ctx.provide("window.coordinator", await coordinator.call({ type: "health" }));
+      if (!coordinator) throw new Error("Remote service bridge is unavailable");
+      ctx.provide("window.coordinator", coordinator);
     },
   })],
 });
 ```
 
-`remoteRuntime` 只向 Host 投影当前 baseline/revision 中的服务和单元状态；setup
-函数不会进入 Worker。断线时 Host 同步撤销页面插件的 Scope 和远程代理，重连后的
-新代理必须重新取得，不会静默重绑旧引用。
+`remoteRuntime` 只向 Host 投影当前完整快照中的服务和单元状态；setup 函数不会进入
+Worker。这里的 `coordinator` 是惰性代理，业务在调用边界执行
+`await coordinator.call({ type: "health" })`。断线时 Host 同步撤销页面插件的 Scope
+和远程代理，显式重建后的新代理必须重新取得，不会静默重绑旧引用。
 
 ## 生命周期和 Scope
 

package/docs/migration-baseline.md

@@ -8,7 +8,7 @@
 | WebLoom 起始提交 | `f1c801655c3132c57b66045ff6d5e642fba4a8ea` |
 | Node | `v22.13.1` |
 | pnpm | `11.5.1` |
-| 下一发布包版本 | `0.2.0` |
+| 下一发布包版本 | `0.3.0` |
 | npm 包名 | `webloom-framework` |
 | 发布来源提交 | `a5ace48` |
 | 已发布基线标签 | `v0.1.0` |
@@ -20,7 +20,7 @@
 
 ## 当前工作区发布状态
 
-当前工作区正在准备 `webloom-framework@0.2.0`，但该版本尚未发布到 npm；下游在发布
+当前工作区正在准备 `webloom-framework@0.3.0`，但该版本尚未发布到 npm；下游在发布
 责任人完成正式发布前继续使用本地工作区依赖。`v0.1.0` / npm `0.1.0` 是已发布基线，
 不是本轮未发布代码的验收替代品。
 

package/docs/proposals/browser-runtime-v1/implementation-plan.md

@@ -1,10 +1,16 @@
 # WebLoom 浏览器双运行时施工单
 
+> SharedWorker 的 `hello`、RemoteService `handshake`、`baseline/resync`、握手超时和
+> 自动重连要求，已被[SharedWorker call-first 消融施工单](../shared-worker-call-first/implementation-plan.md)
+> 覆盖。其余 Runtime、PluginHost、生命周期和安全边界继续有效。
+
 ## 1. 施工目标
 
 把 WebLoom 从字符串运行标签和手工初始化装配，升级为真实的 `window-main + shared-worker` 浏览器双运行时；删除无执行语义的 `lifetime` 与插件分类 `kind`；用高层 API 封装 SharedWorker、MessagePort 和远程 capability。
 
-需求基线见[浏览器双运行时迭代需求](./requirements.md)。本施工单是未来实施顺序，不表示任何工单已经完成。
+需求基线见[浏览器双运行时迭代需求](./requirements.md)。本施工单保留基础双运行时的
+历史实施顺序；SharedWorker 连接相关条款已由上方 call-first 施工单取代，不再作为
+当前 hello/handshake/baseline/reconnect 行为的真值。
 
 ## 2. 施工边界
 

package/docs/proposals/browser-runtime-v1/requirements.md

@@ -1,10 +1,15 @@
 # WebLoom 浏览器双运行时迭代需求
 
+> SharedWorker 连接协议现已采用 call-first 方向。本文涉及 `hello`、握手、baseline、
+> resync、`ready()` 和自动重连的条款，由
+> [SharedWorker call-first 消融施工单](../shared-worker-call-first/implementation-plan.md)
+> 覆盖；其他产品目标和安全要求不变。
+
 ## 1. 文档信息
 
 - 项目：WebLoom
 - 迭代：浏览器双运行时 v1
-- 状态：需求已确认，待实施
+- 状态：基础 Runtime 已实施；SharedWorker 连接部分由 call-first 施工单收口
 - 文档性质：破坏性简化迭代；不代表当前代码已经具备本文能力
 - 关联施工单：[浏览器双运行时施工单](./implementation-plan.md)
 

package/docs/proposals/browser-runtime-v1/verification.md

@@ -1,11 +1,11 @@
-# 浏览器双运行时 v1 验证记录
+# 浏览器双运行时验证记录
 
 更新时间：2026-09-09
 
 ## 当前已通过
 
-- WebLoom TypeScript typecheck：通过。
-- Vitest：17 个测试文件、112 个测试通过；SharedWorker 的 Node 部分明确使用
+- WebLoom 0.3.0 TypeScript typecheck：通过。
+- Vitest：16 个测试文件、107 个测试通过；SharedWorker 的 Node 部分明确使用
   `MessageChannel` transport simulation。
 - `pnpm lint:boundaries`：通过。
 - `pnpm build`：通过。
@@ -14,19 +14,22 @@
 - `git diff --check`：通过。
 
 本轮还覆盖了 Window Host 的 `remoteRuntime` 投影、跨 Runtime 精确契约依赖、
-断线后 blocked/reconnect reconcile、required 元数据防降级、显式 `unitId` 投影、
-握手超时、SharedWorker 错误连接收敛，以及不可重连断线/dispose 后 `ready()`
-持续拒绝。
+断线后 blocked/reconcile、required 元数据防降级、显式 `unitId` 投影、
+惰性 call deadline、SharedWorker 错误连接收敛、stopping/disposed 后拒绝新连接，
+以及 dispose 后旧代理永久失效。
 
 ## 真实浏览器证据
 
 仓库新增 `scripts/browser-runtime-fixture/` 和 `pnpm run test:browser`。fixture
 先由 Vite 生产构建，再从临时 dist preview 启动真实 HTML Window、module
 SharedWorker 和两个页面，断言 Window/Worker realm marker、Worker setup 只执行
-一次、共享 Worker 实例身份和独立 connectionId；同时覆盖真实重连、协议版本不兼容
-和构建后 Worker URL。
+一次、共享 Worker/runtime/service 实例身份；同时覆盖显式 dispose 后重建新句柄和新
+代理、旧代理失效、协议版本不兼容和构建后 Worker URL。
 
-当前执行结果：通过。仓库声明 Playwright 1.63.0，已安装 Chromium；runner 会在
+当前执行结果：通过；最终 fixture 连续 10/10 次通过。terminal 场景先等待触发页和观察页
+都报告 connected、ready、subscription installed，再触发 shutdown；两端均收到
+`ready → stopping → disposed`。另有末态后连接页面收到 `starting → disposed`，不补发
+历史 `stopping`。仓库声明 Playwright 1.63.0，已安装 Chromium；runner 会在
 每次验收前执行 `playwright install chromium`，缺少浏览器时仍 fail closed 为
 `unsupported`/退出码 2，不回退为 Node 或同页面 MessageChannel。
 
@@ -43,7 +46,11 @@ SharedWorker 和两个页面，断言 Window/Worker realm marker、Worker setup
   client 通过 `connectSharedWorker()` 复用同一物理端口，保留原有 Coordinator RPC、
   私钥隔离、session epoch、owner fence、final-I/O lease 和 localStorage bridge。
   Keymaster typecheck、production build 以及 215-file Vitest batch 已通过。
-- `webloom-framework@0.2.0` 仍是待发布工作区版本；npm registry 当前没有该版本，
-  Keymaster 仍保留本地 `file:` 依赖，release-boundary 仍锁定已发布的 `0.1.0`。
-  因此“npm 0.2.0 发布后重新安装并验收”的发布门禁尚未宣称通过，也没有在本轮
-  伪造 registry 版本或自动发布。
+- `webloom-framework@0.3.0` 仍是待发布工作区版本；npm registry 当前没有该版本，
+  下游使用本地 tarball 完成消费者验证，release-boundary 已切换为精确 `0.3.0`。
+  Keymaster 的 release-boundary 现在还会动态查询 registry 的精确版本、tarball
+  integrity，并与 frozen lockfile 比对；当前门禁因 registry 404 失败。因此“npm
+  0.3.0 发布后重新安装并验收”尚未完成。Keymaster 另有
+  `pnpm verify:webloom-registry`，会在全新临时目录生成 lockfile、执行 registry-only
+  `npm ci` 并导入三个公共入口；当前同样因 404 fail closed。没有在本轮伪造 registry
+  版本或自动发布。

package/docs/proposals/shared-worker-call-first/SWCF-009-typed-transfer-follow-up.md

@@ -0,0 +1,34 @@
+# SWCF-009 typed capability/transfer 后续施工单
+
+## 状态与版本边界
+
+本施工单从 `webloom-framework@0.3.0` 的 call-first 迁移中正式拆出，目标后续
+版本（暂定 `0.4.0`）。因此 0.3.0 保留 `connectSharedWorker()` 的
+`onConnection` 和 `startSharedWorkerApp()` 的 `onPortConnect` 作为 Keymaster
+迁移接缝，但不得把这两个接缝描述成最终公共架构。
+
+0.3.0 的已完成范围是 Runtime v2、惰性 ServiceBridge、call/result/error/cancel
+传输、完整快照、Provider/revocation fence、Demo 和 Keymaster 的 v2 service wire。
+0.3.0 不宣称 SWCF-009 或 npm registry 发布完成。
+
+## 后续不变量
+
+- capability method 必须声明 request transferables 和 result transferables；未声明的
+  capability 只能走 structured clone。
+- transfer list 由 capability 适配器产生，调用方不得取得裸 Runtime `MessagePort`，也
+  不得用 `any` 或全局消息监听绕过 capability 边界。
+- request/result 的 transferable 所有权、取消、deadline、dispose、Worker 重启和
+  late-result fence 都必须有类型级和真实浏览器测试。
+- Keymaster Coordinator 的主请求、事件和 Local `localStorage` page bridge 必须迁入
+  typed API；owner/session/grant/handover/final-I/O fence 与 `UpgradeGate.handshake`
+  必须保持原顺序和语义。
+
+## 收口门禁
+
+1. 先实现并导出 typed request/result transfer descriptor 和测试入口。
+2. 迁移 Keymaster Coordinator 的所有主 RPC、事件及 transferable 操作；保留领域
+   `connectionId` 仅在其自身协议中使用。
+3. 通过真实浏览器双 Tab、断线/重启、lock/unlock、A → B → A、Local bridge、迟到
+   result 和安全 fence 回归。
+4. 从生产入口删除 `onConnection`、`onPortConnect`；把 worker factory 保持在 testing
+   入口，并重新执行三仓 typecheck、build、pack/registry consumer 和发布验收。