darkprint 0.1.0 → 0.1.2

package/README.md

@@ -12,7 +12,7 @@ session. One package, three things:
 ```bash
 npx -y darkprint skill install            # Claude Code
 npx -y darkprint skill install --codex    # Codex
-npx -y darkprint clone darkprint/starter-software-factory --out starter
+npx -y darkprint clone autogen/starter-software-factory --out starter
 npx -y darkprint clone spec-planner@1.0.0 # one card, as cards/spec-planner@1.0.0.yaml
 npx -y darkprint validate ./starter
 npx -y darkprint --help

package/dist/cli.js

@@ -15274,7 +15274,7 @@ var DIGEST = {
 var HARNESS = {
   type: "string",
   enum: [...HARNESSES],
-  description: "Shapes the instantiation notes only. It filters nothing: the files are the same whichever you name, and `generic` is the default."
+  description: "Shapes the instantiation notes only. It filters nothing, it is never required, and the `run` contract does not vary by it: the files and the contract are the same whichever you name, and `generic` is the default."
 };
 var LIMIT = {
   type: "integer",
@@ -15316,7 +15316,7 @@ var TOOL_DEFINITIONS = [
   {
     name: "get_blueprint",
     title: "Get a whole blueprint",
-    description: "Return one blueprint in a single call: every file of the release (topology.dot, cards/*.yaml, README.md, and ontology/extensions.yaml when the blueprint declares local terms), its manifest, its scorecard, its provenance, and numbered notes for instantiating it under the harness you name. Without `digest` you get the current release; with one you get exactly those bytes, and they keep answering after a newer release is cut. Call this once `find_blueprints` has found the blueprint you want. With an API key sent as a bearer token, your own private blueprints are reachable here too.",
+    description: "Return one blueprint in a single call: every file of the release (topology.dot, cards/*.yaml, README.md, and ontology/extensions.yaml when the blueprint declares local terms), its manifest, its scorecard, its provenance, and numbered notes for instantiating it under the harness you name. Without `digest` you get the current release; with one you get exactly those bytes, and they keep answering after a newer release is cut. The answer also carries `run`: the contract for executing the graph, which every caller gets whether or not they name a harness, because a card's ports, prohibitions and retry bound mean the same thing whoever runs them. Show the graph and the scorecard to your user and get their agreement before running any of it. Call this once `find_blueprints` has found the blueprint you want. With an API key sent as a bearer token, your own private blueprints are reachable here too.",
     inputSchema: {
       type: "object",
       properties: { owner: OWNER, slug: SLUG, digest: DIGEST, harness: HARNESS },

package/package.json

@@ -1,9 +1,18 @@
 {
   "name": "darkprint",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "private": false,
   "description": "The DarkPrint registry from your terminal and from an agent session: clone, validate, export and import blueprints, report runs, serve the registry over MCP on stdio, and carry the blueprint-writing skill.",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/darkprint/darkprint.git",
+    "directory": "packages/mcp"
+  },
+  "homepage": "https://www.darkprint.io",
+  "bugs": {
+    "url": "https://github.com/darkprint/darkprint/issues"
+  },
   "bin": {
     "darkprint": "dist/cli.js"
   },

package/skill/darkprint/SKILL.md

@@ -490,7 +490,7 @@ registry is searched first for the same reason.
 2. **Search with the addition as the task.** `find_blueprints` with that sentence, or the
    anonymous GET from Phase 1. Show the top hits in the author's words, `ref`, `title` and
    `score`, and recommend one. When a live page is open, send them as `hits`. The tutorial's
-   case, observability on a node, is `darkprint/pipeline-observability`.
+   case, observability on a node, is `autogen/pipeline-observability`.
 3. **Fetch the one they chose.** `get_blueprint` with its owner and slug, or
    `GET https://www.darkprint.io/api/mcp/blueprints/<owner>/<slug>/bundle`. The answer lists
    the release's files by path, with the version and the digest that name those bytes.