skillscript-runtime 0.15.7 → 0.16.1

package/examples/connectors/SkillStoreTemplate/SkillStoreTemplate.ts

@@ -27,7 +27,7 @@
  * suite the entire skillscript surface (skill_write / skill_list /
  * execute_skill / etc.) reads + writes against your substrate.
  *
- * **v0.15.0 — `SkillStoreMcpConnector` bridge auto-wires against your impl.**
+ * **`SkillStoreMcpConnector` bridge auto-wires against your impl.**
  * The runtime's `defaultRegistry` wraps your registered SkillStore in a
  * `SkillStoreMcpConnector` instance and registers it under the connector
  * names `skill_read` + `skill_write`, so `$ skill_read` / `$ skill_write` from
@@ -39,14 +39,14 @@
  * worth knowing:
  *   - **In-skill writes arrive Draft-stamped.** The bridge layer applies a
  *     `# Status: Draft` override to the body before calling your `store()`.
- *     This is the v0.15.0 trust boundary — autonomously-generated skill
- *     bodies (e.g., `~ qwen prompt="generate a skill"` → `$ skill_write`)
- *     shouldn't bypass human review by landing Approved + immediately
- *     executable. See `src/connectors/skill-store-mcp.ts` header for the
- *     threat-model rationale. Outside-MCP `skill_write` (cold-author agents
- *     authoring directly via the wire surface) keeps the existing "body
- *     declares status, you auto-stamp via store()" path — that's the path
- *     your `store()` honor-the-body-Status logic addresses.
+ *     This is the trust boundary — autonomously-generated skill bodies
+ *     (e.g., `$ llm prompt="generate a skill"` → `$ skill_write`) shouldn't
+ *     bypass human review by landing Approved + immediately executable.
+ *     See `src/connectors/skill-store-mcp.ts` header for the threat-model
+ *     rationale. Outside-MCP `skill_write` (cold-author agents authoring
+ *     directly via the wire surface) keeps the existing "body declares
+ *     status, you auto-stamp via store()" path — that's the path your
+ *     `store()` honor-the-body-Status logic addresses.
  *   - **Substrate-level lint runs at `store()` entry.** If you mirror
  *     `FilesystemSkillStore` / `SqliteSkillStore`, you'll run tier-1 lint
  *     on the body before persisting + throw `LintFailureError` on rejection.

package/examples/custom-bootstrap.example.ts

@@ -1,9 +1,9 @@
 // Worked example: writing a custom bootstrap that wires adopter-specific
-// substrates against skillscript-runtime's public APIs. v0.7.3.
+// substrates against skillscript-runtime's public APIs.
 //
 // **When to write your own bootstrap.** The bundled `bootstrap()` from
 // `skillscript-runtime` wires `FilesystemSkillStore` + `OllamaLocalModel` +
-// `SqliteDataStore` + the v0.7.2 bridges. If your deployment uses
+// `SqliteDataStore` + the typed-contract bridges. If your deployment uses
 // different substrates (your own data store, a hosted LLM API, an MCP
 // server for agent delivery, etc.), write your own bootstrap rather than
 // modifying the bundled one. Prevents merge conflicts on every upstream
@@ -52,7 +52,7 @@ class MyAdopterConnector implements McpConnector {
   constructor(private readonly config: Record<string, unknown>) {}
 
   async call(toolName: string, args: Record<string, unknown>, _ctx?: McpDispatchCtx): Promise<unknown> {
-    // Dispatch to your substrate. Auth/credentials per the v0.8.x passthrough
+    // Dispatch to your substrate. Auth/credentials per the passthrough
     // model: the substrate enforces; runtime threads credentials via ctx.
     void toolName; void args;
     return { ok: true };
@@ -102,7 +102,7 @@ registry.registerSkillStore("primary", skillStore);
 //     registry.registerMcpConnector("data_read", dataBridge);
 //     registry.registerMcpConnector("data_write", dataBridge);
 //   }
-//   // v0.15.0 — SkillStore-as-bridge. Makes `$ skill_write` / `$ skill_read`
+//   // SkillStore-as-bridge. Makes `$ skill_write` / `$ skill_read`
 //   // dispatchable from inside an executing skill (Lisp-shape: skills program
 //   // skills). In-skill writes are Draft-forced at the bridge layer; outside-MCP
 //   // skill_write keeps the existing "body declares status" behavior.

package/examples/onboarding-scaffold/bootstrap.ts

@@ -1,5 +1,5 @@
 // Onboarding scaffold: complete bootstrap wiring file-backed data store +
-// OpenAI LLM + tmux-shell AgentConnector. v0.7.3.
+// OpenAI LLM + tmux-shell AgentConnector.
 //
 // Copy this file into your deployment and modify substrate choices to
 // match your environment. The shape is:
@@ -74,12 +74,12 @@ registry.registerMcpConnector("llm", new LocalModelMcpConnector(openai));
 const dataBridge = new DataStoreMcpConnector(dataStore);
 registry.registerMcpConnector("data_read", dataBridge);
 registry.registerMcpConnector("data_write", dataBridge);
-// v0.15.0 — SkillStore-as-bridge. Makes `$ skill_write` / `$ skill_read`
-// dispatchable from inside an executing skill (Lisp-shape: skills program
-// skills). In-skill writes are forced to `# Status: Draft` at the bridge
-// layer per the v0.15.0 trust boundary — see `src/connectors/skill-store-mcp.ts`
-// header for the threat-model rationale. Outside-MCP `skill_write` (via the
-// wire surface) keeps its existing "body declares status" behavior.
+// SkillStore-as-bridge. Makes `$ skill_write` / `$ skill_read` dispatchable
+// from inside an executing skill (Lisp-shape: skills program skills).
+// In-skill writes are forced to `# Status: Draft` at the bridge layer —
+// see `src/connectors/skill-store-mcp.ts` header for the threat-model
+// rationale. Outside-MCP `skill_write` (via the wire surface) keeps its
+// existing "body declares status" behavior.
 const skillBridge = new SkillStoreMcpConnector(skillStore);
 registry.registerMcpConnector("skill_read", skillBridge);
 registry.registerMcpConnector("skill_write", skillBridge);

package/examples/onboarding-scaffold/file-data-store.ts

@@ -1,13 +1,11 @@
-// Onboarding scaffold: file-backed DataStore. v0.7.3.
+// Onboarding scaffold: file-backed DataStore.
 //
 // JSON file as the substrate; simple JS substring + token match for "fts"
 // queries; reranks by recency. Adopters copy this file and modify for
 // their concrete substrate (e.g., swap the JSON file for a Postgres
 // table, the substring match for actual full-text search, etc.).
 //
-// **Scope.** Read-only `query()` per the v0.7.2 DataStore contract.
-// `write()` is deferred to v0.8.x bundled with the auth model — when
-// that lands, extend this file with the matching `write()` method.
+// **Scope.** Implements `query()` + `write()` per the DataStore contract.
 
 import { readFileSync, existsSync, writeFileSync } from "node:fs";
 import { randomUUID } from "node:crypto";
@@ -106,7 +104,7 @@ export class FileDataStore implements DataStore {
         file_path: this.config.filePath,
         record_count: this.loadFile().length,
         supports_write: true,
-        // v0.14.1 strict-filters: the bridge enforces every non-base filter
+        // strict-filters: the bridge enforces every non-base filter
         // key in `query()` calls against this declared set, throwing
         // UnsupportedFilterError for unknowns. This reference impl's
         // substring scorer doesn't actually filter on any field (it

package/examples/onboarding-scaffold/openai-local-model.ts

@@ -1,17 +1,16 @@
-// Onboarding scaffold: OpenAI-API-backed LocalModel. v0.7.3.
+// Onboarding scaffold: OpenAI-API-backed LocalModel.
 //
 // HTTP client to OpenAI's Chat Completions endpoint. Implements the
-// `LocalModel.run(prompt, opts)` typed contract so the v0.7.2 bridge
-// (`LocalModelMcpConnector`) surfaces it as canonical `$ llm prompt=...`
-// for skills.
+// `LocalModel.run(prompt, opts)` typed contract so the
+// `LocalModelMcpConnector` bridge surfaces it as canonical
+// `$ llm prompt=... [maxTokens=N] [model="..."] -> R` for skills.
 //
 // **Prompt-vs-messaging caveat.** `LocalModel.run()` takes a single
 // `prompt` string; Chat Completions expects a list of messages with roles.
 // This adapter wraps the prompt as a single `user` message. Skills that
-// need multi-turn or system-prompt isolation should treat this as a
-// limitation of the v0.7.x contract and pair the LLM dispatch with `$set`
-// + accumulation in the skill body for now. v0.8.x is a likely venue
-// for a richer message-shaped LocalModel contract.
+// need multi-turn or system-prompt isolation should pair the LLM dispatch
+// with `$set` + accumulation in the skill body — the LocalModel contract
+// is intentionally narrow (prompt-in, text-out).
 
 import type {
   LocalModel,

package/examples/onboarding-scaffold/tmux-shell-agent-connector.ts

@@ -1,12 +1,12 @@
-// Onboarding scaffold: tmux-shell AgentConnector. v0.7.3.
+// Onboarding scaffold: tmux-shell AgentConnector.
 //
 // Delivers skill output to a named tmux session via `tmux send-keys`.
 // Matches what nanoclaw-style agent harnesses do internally — adopters
-// with agents running in tmux sessions can wire `# Output: prompt-context:
-// <agent>` end-to-end against this impl.
+// with agents running in tmux sessions can wire `# Output: agent: <agent>`
+// end-to-end against this impl.
 //
 // **Scope.** Implements `deliver()` + `list_agents()` + `wake()` +
-// `manifest()` per the v0.7.x AgentConnector contract. `wake()` is a no-op
+// `manifest()` per the AgentConnector contract. `wake()` is a no-op
 // here (tmux panes are always live; wake is for harnesses with sleep modes).
 
 import { spawn } from "node:child_process";

package/examples/skillscripts/hello-world.skill.provenance.json

@@ -2,7 +2,7 @@
   "provenance_version": "1.0",
   "language_version": "1.0",
   "compiler_version": "0.1.0-dev",
-  "compiled_at": "2026-06-01T21:58:27.234Z",
+  "compiled_at": "2026-06-02T16:19:52.549Z",
   "source_skill": {
     "name": "hello-world"
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skillscript-runtime",
-  "version": "0.15.7",
+  "version": "0.16.1",
   "description": "Runtime, compiler, lint, CLI, and dashboard for Skillscript — a small declarative language for authoring agent workflows.",
   "license": "MIT",
   "author": "Scott Shwarts <scotts@pobox.com>",

package/examples/skillscripts/cut-release-tag.skill.md

@@ -1,40 +0,0 @@
-# Skill: cut-release-tag
-# Status: Approved v1:d3c2a91b
-# Description: Run when the user says "ship a release" or "cut a tag" on the current branch; collects commit-list since last tag, asks the user to confirm the version bump, applies the tag, and pushes it
-# Vars: BUMP_KIND=patch
-# Output: text
-
-last_tag:
-    shell(command="git describe --tags --abbrev=0") -> PREV_TAG
-else:
-    $set PREV_TAG = "(no prior tags)"
-    emit(text="no previous tag found; treating this as the first release")
-
-commits_since:
-    needs: last_tag
-    shell(command="git log --oneline \"${PREV_TAG}\"..HEAD") -> COMMITS
-else:
-    $set COMMITS = "(unable to read commit log; proceeding without preview)"
-
-propose:
-    needs: commits_since
-    $ llm prompt="Propose the next semver tag given prev tag '${PREV_TAG}', bump kind '${BUMP_KIND}', and commits below. Return ONLY the new tag string (e.g. v1.4.3). No commentary.\n\nCommits:\n${COMMITS}" maxTokens=30 -> PROPOSED_TAG
-
-confirm:
-    needs: propose
-    emit(text="Previous tag: ${PREV_TAG}")
-    emit(text="Commits since:")
-    emit(text="${COMMITS}")
-    emit(text="Proposed new tag: ${PROPOSED_TAG|trim}")
-    ask(prompt="Cut tag ${PROPOSED_TAG|trim}?") -> APPROVED
-
-apply:
-    needs: confirm
-    shell(command="git tag \"${PROPOSED_TAG|trim}\"") -> TAG_OUT
-    shell(command="git push origin \"${PROPOSED_TAG|trim}\"") -> PUSH_OUT
-    emit(text="Tagged and pushed ${PROPOSED_TAG|trim}")
-else:
-    emit(text="Tag/push failed; rolling back local tag")
-    shell(command="git tag -d \"${PROPOSED_TAG|trim}\"") -> ROLLBACK
-
-default: apply