@ruvnet/agent-harness-generator 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 RuvNet (https://ruv.io)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,91 @@
+# @ruvnet/agent-harness-generator
+
+> Library / core package for the **Agent Harness Generator**. Pair with
+> [`metaharness`](https://www.npmjs.com/package/metaharness) for the CLI.
+
+## What this is
+
+The **library** half of the dual-package model. If you want to **run** the
+generator, use `metaharness`. If you want to **import** it from your own code,
+use this package.
+
+```bash
+# Run it (CLI)
+npx metaharness my-bot --template vertical:coding
+
+# Import it (library)
+npm install @ruvnet/agent-harness-generator
+```
+
+```ts
+import {
+  scaffold,
+  validateHarnessName,
+  HOSTS,
+  TEMPLATES,
+} from '@ruvnet/agent-harness-generator';
+
+// Generate a harness programmatically:
+const result = await scaffold({
+  name: 'my-bot',
+  template: 'vertical:coding',
+  host: 'claude-code',
+  targetDir: '/tmp/my-bot',
+  force: true,
+  generatorVersion: '0.1.0',
+});
+console.log(`wrote ${result.files.length} files`);
+```
+
+## What's exported
+
+| Group | Exports |
+|---|---|
+| **Scaffold pipeline** | `scaffold`, `parseArgs`, `main`, `detectRufloProject`, `templateDir` |
+| **Catalog surface** | `HOSTS`, `TEMPLATES`, `loadCatalog`, `formatCatalog` |
+| **Rendering** | `render`, `extractVarReferences`, `validateHarnessName`, `walkTemplate`, `asFileMap`, `writeAtomic` |
+| **Manifest / fingerprinting** | `emptyManifest`, `sha256`, `fingerprintFiles`, `diffFingerprints` |
+| **Types** | `Host`, `TemplateId`, `CatalogEntry`, `CliArgs`, `ScaffoldOptions`, `ScaffoldResult`, `TemplateVars` |
+
+The full per-subcommand surface (validate / sbom / audit / score / genome /
+threat-model / …) lives in `metaharness`. We re-export the *generation*
+primitives here; per-subcommand commands stay CLI-only because they assume
+the harness has already been written to disk and is being inspected.
+
+## How the dual-package model works
+
+```
+  ┌─────────────────────────────────┐
+  │ metaharness                       │   ← the published CLI
+  │  • bin: metaharness, harness      │     `npx metaharness`
+  │  • full implementation          │     `npx metaharness score ./my-bot`
+  │  • full JS API                  │
+  └────────────┬────────────────────┘
+               │ depends on
+  ┌────────────┴────────────────────┐
+  │ @ruvnet/agent-harness-generator │   ← this package: thin re-export
+  │  • no bin                       │     `import { scaffold } from …`
+  │  • re-exports the library API   │
+  └─────────────────────────────────┘
+```
+
+One source of truth. Two published names. The wrapper has no
+implementation — if logic ever leaks into this package, it's a bug.
+
+## When to use which
+
+- **`metaharness`** — you want the command-line tool, full subcommand
+  surface, marketplace plugin, Codex skills.
+- **`@ruvnet/agent-harness-generator`** — you're embedding the generator
+  in a build script, a web service, or another tool, and don't want the
+  `bin` baggage.
+
+## Version pinning
+
+This package always depends on the same minor version of `metaharness`. A
+patch release of `metaharness` doesn't bump us automatically — we cut a
+matching patch and re-publish so the dependency stays tight.
+
+## License
+
+MIT — see [LICENSE](LICENSE).

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+export { scaffold, parseArgs, main, detectRufloProject, templateDir, HOSTS, TEMPLATES, loadCatalog, formatCatalog, render, extractVarReferences, validateHarnessName, walkTemplate, asFileMap, writeAtomic, emptyManifest, sha256, fingerprintFiles, diffFingerprints, } from 'metaharness';
+export type { Host, TemplateId, CatalogEntry, CliArgs, ScaffoldOptions, ScaffoldResult, TemplateVars, } from 'metaharness';

package/dist/index.js

@@ -0,0 +1,27 @@
+// SPDX-License-Identifier: MIT
+//
+// @ruvnet/agent-harness-generator — library/core API for the harness generator.
+//
+// The actual implementation lives in the `metaharness` package (which is the
+// published CLI). This package re-exports the JS API surface so consumers can
+// import it cleanly without depending on the CLI's `bin` entry:
+//
+//     import { scaffold, validateHarnessName, HOSTS, TEMPLATES }
+//       from '@ruvnet/agent-harness-generator';
+//
+// Why split? Per the user's iter-108 naming directive:
+//   - `metaharness`                     — the CLI, what users run (`npx metaharness`)
+//   - `@ruvnet/agent-harness-generator` — the library, what code imports
+//
+// One source of truth (metaharness), two published names. The wrapper has no
+// implementation of its own — if you find yourself adding logic here, that
+// logic belongs in metaharness and gets re-exported.
+export { 
+// Core scaffold pipeline.
+scaffold, parseArgs, main, detectRufloProject, templateDir, 
+// Catalog surface.
+HOSTS, TEMPLATES, loadCatalog, formatCatalog, 
+// Rendering primitives.
+render, extractVarReferences, validateHarnessName, walkTemplate, asFileMap, writeAtomic, 
+// Manifest + fingerprinting (used by `harness compare`).
+emptyManifest, sha256, fingerprintFiles, diffFingerprints, } from 'metaharness';

package/package.json

@@ -0,0 +1,56 @@
+{
+  "name": "@ruvnet/agent-harness-generator",
+  "version": "0.1.0",
+  "description": "Library/core package for the Agent Harness Generator. Pair with `metaharness` for the CLI. Re-exports scaffold(), validate(), and the deterministic-analysis pipeline from `metaharness` so consumers can `import { scaffold } from '@ruvnet/agent-harness-generator'` without shelling out to the CLI.",
+  "homepage": "https://github.com/ruvnet/agent-harness-generator",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ruvnet/agent-harness-generator.git",
+    "directory": "packages/agent-harness-generator-lib"
+  },
+  "license": "MIT",
+  "author": "rUv <ruv@ruv.net>",
+  "type": "module",
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist/**",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "build": "tsc",
+    "test": "vitest run --passWithNoTests",
+    "lint": "tsc --noEmit"
+  },
+  "keywords": [
+    "agent-harness",
+    "agent-harness-generator",
+    "metaharness",
+    "scaffold",
+    "mcp-server",
+    "claude-code",
+    "codex",
+    "library"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "dependencies": {
+    "metaharness": "0.1.0"
+  },
+  "devDependencies": {
+    "@types/node": "^20.0.0",
+    "typescript": "^5.4.0",
+    "vitest": "^2.0.0"
+  },
+  "engines": {
+    "node": ">=20.0.0"
+  }
+}