@springbrand/agent-runtime 0.2.0-alpha.18 → 0.2.0-alpha.20

package/src/skills/springbrand-worker-website/index.ts

@@ -0,0 +1,73 @@
+export const SPRINGBRAND_WORKER_WEBSITE_SKILL = {
+  name: "springbrand-worker-website",
+  description:
+    "Use when an Agent creates, restructures, previews, verifies, or deploys a Website in a SpringBrand Workspace; provide the complete Cloudflare Worker project layout, asset conventions, and browser validation workflow.",
+  body: [
+    "# SpringBrand Worker Website",
+    "",
+    "Keep the Website in one stable project directory under `/creations/<website-name>/`. Treat that directory as the complete deployable Website project, not as a directory containing only one HTML file.",
+    "",
+    "## Recommended layout",
+    "",
+    "When creating a new Website and no existing project structure needs to be preserved, prefer:",
+    "",
+    "```text",
+    "/creations/<website-name>/",
+    "├── wrangler.json",
+    "├── package.json",
+    "├── src/",
+    "│   ├── worker.ts",
+    "│   ├── routes/",
+    "│   ├── lib/",
+    "│   └── client/",
+    "└── public/",
+    "    ├── index.html",
+    "    ├── about/",
+    "    │   └── index.html",
+    "    ├── products/",
+    "    │   └── index.html",
+    "    ├── assets/",
+    "    │   ├── css/",
+    "    │   ├── js/",
+    "    │   ├── images/",
+    "    │   ├── fonts/",
+    "    │   └── icons/",
+    "    ├── data/",
+    "    ├── favicon.ico",
+    "    ├── robots.txt",
+    "    └── manifest.webmanifest",
+    "```",
+    "",
+    "This is a recommended default, not a required layout. Preserve an existing valid framework or project convention such as `dist/`, `build/`, another Worker entry path, or another static asset directory, and configure Wrangler accordingly.",
+    "",
+    "## Project rules",
+    "",
+    "- Keep Worker configuration, package metadata, and build configuration at the Website project root.",
+    "- Keep Worker code, routes, application logic, and editable source files under `src/`.",
+    "- Keep browser-accessible, deployment-ready static files under `public/`.",
+    "- Use `public/index.html` as the recommended home page. Put additional pages under clear routes such as `public/about/index.html` and `public/products/index.html`.",
+    "- Put stylesheets, browser scripts, images, fonts, icons, and other static resources under the corresponding `public/assets/` subdirectory.",
+    "- Put publicly accessible static data under `public/data/` when needed.",
+    "- Keep every file required to build and deploy the Website inside its project directory.",
+    "- Do not duplicate the same entry page at both the project root and `public/`.",
+    "- Do not place secrets, temporary files, logs, raw tool output, or unprocessed attachments inside the Website project.",
+    "",
+    "## Worker and browser requirements",
+    "",
+    "- Configure Wrangler `main` to point to the actual Worker source file.",
+    "- Export `class App extends DurableObject` from that module when the Website uses the SpringBrand App Facet.",
+    "- Configure `assets.directory` to point to the actual browser asset directory, preferably `public/`.",
+    "- Use `./` or `../` for local Website files, never a root-relative Workspace path, so preview and deployed URL prefixes both work.",
+    "- Load CSS from HTML instead of importing it from browser JavaScript.",
+    "- Without a build step, load browser-native third-party ESM through a full pinned HTTPS URL or an import map to a pinned CORS-enabled CDN.",
+    "- With a build step, produce deployment-ready assets before preview instead of depending on a development server.",
+    "",
+    "## Workflow",
+    "",
+    "1. Inspect the existing Website directory before changing it and preserve valid conventions.",
+    "2. Create or update the complete project rather than only an entry HTML file.",
+    "3. Build when the project requires a build step.",
+    "4. Preview the Website through the available Workspace or Space capability.",
+    "5. When `browser_execute` is available, check runtime errors, failed resources, CSP violations, responsive layout, clipping, overlap, and visual hierarchy. Capture a screenshot when visual appearance matters, fix discovered problems, and verify once more.",
+  ].join("\n"),
+};

package/src/tool-registry.ts

@@ -1,51 +1,34 @@
-import type { ExecutionLevel } from "./lib/execution-level";
 import type {
-  RuntimeCodeExecutionPort,
+  RuntimeCodeExecutionFactory,
   RuntimeMemoryPort,
   RuntimeSubagentPort,
   WorkspacePort,
 } from "./kernel/bindings";
 import type { RuntimeExtensionConfig } from "./kernel/extensions";
 import type { RuntimeDegradation } from "./kernel/degradation";
+import type {
+  ToolContext,
+  ToolRegistry,
+  ToolSpec,
+} from "./kernel/tool-surface";
 import type { PiToolCandidate } from "./pi/tool/compiler";
 import { validateToolArguments } from "@earendil-works/pi-ai";
 
+// Tool Surface 的形状类型住在 `kernel/tool-surface.ts`：bindings 也要用它们，放在这里
+// 会让 `bindings → tool-registry → bindings` 成环。这里继续导出是为了保持调用方不变。
+export type {
+  RuntimeCodeExecutionFactory,
+  ToolContext,
+  ToolRegistry,
+  ToolSpec,
+};
+
 /** Tool Surface 筛选策略（不含 Manifest deny 列表）。 */
 export interface ToolSurfaceSelectionPolicy {
   readonly allowsTool?: (name: string) => boolean;
   readonly allowsExtension?: (extension: RuntimeExtensionConfig) => boolean;
 }
 
-/** 模型调用 Tool 时传给 `execute` 的上下文。 */
-export interface ToolContext {
-  readonly toolCallId: string;
-  readonly signal: AbortSignal;
-}
-
-/** Definition 作者声明的一个 Tool。 */
-export interface ToolSpec extends Partial<
-  Omit<PiToolCandidate, "tool" | "requiredExecutionLevel">
-> {
-  readonly label: string;
-  readonly description: string;
-  readonly parameters: unknown;
-  readonly requiredExecutionLevel: ExecutionLevel;
-  /** Require a fresh human decision for every call, regardless of execution level. */
-  readonly alwaysRequiresApproval?: boolean;
-  readonly execute: (
-    input: unknown,
-    ctx: ToolContext,
-  ) => Promise<unknown>;
-}
-
-/** 一次装配声明的全部 Tool，键即模型可见的工具名。 */
-export type ToolRegistry = Record<string, ToolSpec>;
-
-/** 延迟到最终 Tool Surface 完成后再创建 Code Mode 执行能力。 */
-export interface RuntimeCodeExecutionFactory {
-  create(tools: ToolRegistry): RuntimeCodeExecutionPort;
-}
-
 export function emptyToolRegistry(): ToolRegistry {
   return {};
 }