@polderlabs/bizar-omp 0.2.0

package/docs/releases/npm-publishing.md

@@ -0,0 +1,22 @@
+# npm publishing
+
+Package: `@polderlabs/bizar-omp` (public). Repository remains private.
+
+Configure the package's npm **Trusted Publisher** as:
+
+| Field | Value |
+| --- | --- |
+| Provider | GitHub Actions |
+| Organization or user | `PolderLabsVOF` |
+| Repository | `BizarHarness-OMP` |
+| Workflow filename | `release.yml` |
+| Environment | Leave blank |
+| Allowed actions | Direct `npm publish` |
+
+The first release uses the authenticated maintainer CLI to create the package. After npm configuration, `.github/workflows/release.yml` uses GitHub-hosted runners, Node 24, npm 11.16.0, and `id-token: write`; no npm token secret is required. Do not use `npm whoami` to test OIDC: token exchange happens during publication.
+
+Release procedure: increment package/package-lock/baseline versions together, update notes, open a PR, pass CI, merge, then push an exact `vX.Y.Z` tag from main. The release job checks tag/version identity and main ancestry, typechecks, tests, verifies docs, and exercises the packed installer before publishing. Published versions cannot be overwritten. A manual workflow dispatch must select an existing release tag.
+
+The repository is private, so npm provenance is disabled; OIDC authentication still works. Do not advertise provenance for this release. If repository visibility changes, reevaluate provenance separately.
+
+Reference: [npm trusted publishing documentation](https://docs.npmjs.com/trusted-publishers/).

package/docs/releases/rollback.md

@@ -0,0 +1,3 @@
+# Rollback
+
+The package has no user-state migration in beta. Workflow state is append-only JSONL under the Git common directory and is not deleted by uninstall. A failed migration is dry-run by default; the current `--apply` path remains non-destructive until an item-specific handler exists. Rollback therefore means selecting the prior plugin version and retaining the journal/artifacts for inspection.

package/docs/releases/support-matrix.md

@@ -0,0 +1,11 @@
+# Support matrix
+
+| Surface | Qualification |
+| --- | --- |
+| Node | 22.x and 24.x in CI |
+| Bun | 1.3.14 compatibility job |
+| OMP | 18.2.2 at commit `60c9a115b2e8decc0f75825459362d14188a8bc0` |
+| Install | `omp plugin link <checkout>` and `omp plugin install <package-spec>` are the intended host paths |
+| Security | Trusted in-process extension; native task isolation required for managed editing |
+
+Upstream API changes require a new baseline entry and contract run; the package does not widen a version range to hide an unqualified runtime.

package/docs/security/qualification.md

@@ -0,0 +1,3 @@
+# Security qualification
+
+The automated suite verifies schema validation, path-scope admission, stale-target rejection, idempotency, journal ownership, and no-auto-application policy. It does not prove hostile-code containment. OMP extension modules remain trusted in-process code, and a task's isolated workspace is not equivalent to a complete filesystem/network/credential sandbox.

package/docs/security/threat-model.md

@@ -0,0 +1,5 @@
+# Threat model and trust presets
+
+The extension is trusted local code and runs in the OMP host process. Markdown, repository files, model output, worker messages, and web pages are data; none can change Bizar configuration or journal ownership. JSONL journal paths are resolved from the repository identity, never from generated task text.
+
+The installer selects trusted-development behavior: ordinary tools are auto-approved, while explicit user deny/prompt rules remain in effect. The core contains policy helpers for restricted-managed and untrusted-repository modes, but this release does not intercept every native task/eval route. Do not treat those helpers as an enforced sandbox. Untrusted code requires a separate OS/container boundary. Symlink, nested-repository, ignored-file, credential, and subprocess risks require separate qualification.

package/optional/openkan/index.ts

@@ -0,0 +1,3 @@
+import { spawn } from "node:child_process";
+export function openkanCommand(args: string[]) { if (args.some(arg => arg.startsWith("--" ) && arg.includes("storage"))) throw new Error("OpenKan storage internals are not a supported adapter surface"); return ["ok", ...args]; }
+export async function runOpenKan(args: string[], cwd: string): Promise<{ code: number; stdout: string; stderr: string }> { const argv = openkanCommand(args); return new Promise(resolve => { const child = spawn(argv[0], argv.slice(1), { cwd, stdio: ["ignore", "pipe", "pipe"] }); let stdout = ""; let stderr = ""; child.stdout.on("data", data => { stdout += data; }); child.stderr.on("data", data => { stderr += data; }); child.on("close", code => resolve({ code: code ?? 1, stdout, stderr })); }); }

package/package.json

@@ -0,0 +1,59 @@
+{
+  "name": "@polderlabs/bizar-omp",
+  "version": "0.2.0",
+  "description": "Native oh-my-pi engineering workflow extension with typed evidence and serialized integration.",
+  "type": "module",
+  "engines": {
+    "node": ">=22",
+    "bun": ">=1.3.14"
+  },
+  "bin": {
+    "bizar-omp": "dist/cli/main.js"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./extension": "./dist/extension.js"
+  },
+  "omp": {
+    "extensions": [
+      "./dist/extension.js"
+    ]
+  },
+  "files": [
+    "dist/",
+    "agents/",
+    "skills/",
+    "rules/",
+    "prompts/",
+    "schemas/",
+    "optional/",
+    "README.md",
+    "LICENSE",
+    "docs/"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.build.json",
+    "typecheck": "tsc -p tsconfig.json --noEmit",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "verify:package": "npm run build && node scripts/verify-package.mjs",
+    "verify:docs": "node scripts/check-generated-docs.mjs",
+    "verify:omp": "bun scripts/verify-omp-install.mjs",
+    "pack:check": "npm pack --dry-run",
+    "prepack": "npm run verify:package"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/PolderLabsVOF/BizarHarness-OMP.git"
+  },
+  "license": "MIT",
+  "publishConfig": { "access": "public", "registry": "https://registry.npmjs.org/" },
+  "devDependencies": {
+    "@types/node": "^22.0.0",
+    "typescript": "^5.6.0",
+    "vitest": "^4.1.9"
+  }
+}

package/prompts/bizar-system.md

@@ -0,0 +1,3 @@
+# Bizar system prompt
+
+You are operating the Bizar engineering layer inside oh-my-pi. Work directly when a task is contained; delegate only when isolation, independence, or specialization changes the outcome. Keep workflow state, evidence, and integration admission explicit. OMP owns execution and credentials. Verify before claiming completion, and report limitations plainly.

package/rules/bizar-core.md

@@ -0,0 +1,7 @@
+# Bizar core rules
+
+- Only the run owner writes authoritative workflow transitions.
+- Every consequential effect gets a durable intent before its observed result.
+- Evidence is target-bound, source-attributed, and stale after relevant changes.
+- Unknown outcomes block completion and are reconciled from host state.
+- Managed editing is isolated and never auto-applied.

package/rules/bizar-native-omp.md

@@ -0,0 +1,6 @@
+# Native OMP rules
+
+- Register extension handlers during factory load; perform actions from lifecycle, command, or tool execution.
+- Use OMP's native task/eval and model/auth surfaces; do not create a second worker runtime.
+- Do not treat OMP extension code as sandboxed.
+- Use `omp.extensions` in the package manifest and qualify exact runtime baselines.

package/schemas/evidence-record.schema.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://github.com/PolderLabsVOF/BizarHarness-OMP/schemas/evidence-record.schema.json",
+  "title": "Bizar OMP evidence record",
+  "type": "object",
+  "required": ["id", "runId", "type", "checkId", "result", "targetDigest", "stale", "provenance"],
+  "properties": {
+    "id": { "type": "string" },
+    "runId": { "type": "string" },
+    "type": { "enum": ["test", "lint", "typecheck", "review", "research", "worker", "git", "manual"] },
+    "result": { "enum": ["passed", "failed", "blocked", "cancelled", "unknown"] },
+    "targetDigest": { "type": "string", "minLength": 1 },
+    "stale": { "type": "boolean" }
+  },
+  "additionalProperties": true
+}

package/schemas/workflow-run.schema.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://github.com/PolderLabsVOF/BizarHarness-OMP/schemas/workflow-run.schema.json",
+  "title": "Bizar OMP workflow run",
+  "type": "object",
+  "required": ["schemaVersion", "runId", "projectId", "objectiveHash", "revision", "phase"],
+  "properties": {
+    "schemaVersion": { "const": 1 },
+    "runId": { "type": "string", "pattern": "^run_" },
+    "projectId": { "type": "string", "minLength": 1 },
+    "objectiveHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+    "revision": { "type": "integer", "minimum": 0 },
+    "phase": { "enum": ["created", "orienting", "researching", "planning", "ready", "executing", "integrating", "verifying", "reviewing", "complete", "blocked", "failed", "cancelled"] }
+  },
+  "additionalProperties": true
+}

package/skills/bizar-architecture/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bizar-architecture
+description: Design native OMP boundaries without importing private runtime internals.
+---
+
+OMP owns sessions, providers, tools, workers, isolation, and artifacts. Bizar owns workflow intent, evidence, acceptance, and integration eligibility. Use public extension seams; record an upstream gap and disable an uncovered route rather than importing a private executor.

package/skills/bizar-planning/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bizar-planning
+description: Write bounded implementation plans that cannot perform implementation effects.
+---
+
+Plans contain objective, non-goals, constraints, acceptance, dependencies, ownership, verification, material unknowns, risks, and stop conditions. Plan mode is read-only; it cannot write implementation files or auto-apply native task results.

package/skills/bizar-research/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bizar-research
+description: Record primary-source research without turning assumptions into policy.
+---
+
+For version-sensitive OMP behavior, record the exact source URL, commit/tag, location, retrieval date, and supported claim. Label repository facts, external facts, inferences, and unknowns separately. Stop when additional sources are unlikely to change the decision.

package/skills/bizar-review/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bizar-review
+description: Review and refute findings on the exact candidate revision.
+---
+
+Preserve the full finding handoff: target revision, path/location, scenario, severity, evidence, reproduction, and why the change introduces or exposes it. Refutation must attempt to disprove the finding with counter-evidence.

package/skills/bizar-security/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bizar-security
+description: Apply honest trust and isolation language to workflow decisions.
+---
+
+Path scopes and tool policies are not an OS sandbox. Require a real host isolation backend for untrusted repositories and keep extension code trusted. Protect credentials, reject path traversal, and never accept journal paths supplied by generated task text.

package/skills/bizar-testing/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bizar-testing
+description: Produce fresh, target-bound proving evidence.
+---
+
+Use exact command arguments, working directory, toolchain identity, target digest, exit status, bounded output, and artifact hashes. Re-run invalidated checks after integration. Never infer a pass from a missing result or prose.

package/skills/bizar-workflow/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bizar-workflow
+description: Use the native Bizar workflow/evidence lifecycle safely.
+---
+
+The workflow tool is the source for the next admissible action. Create an objective with acceptance criteria, preserve revision checks, admit managed editing with `apply: false`, reconcile the observed native result, verify the exact target, and integrate only through the serialized path. A task acknowledgment is not completion.