@wntic/ocm 0.1.0

package/src/report.ts

@@ -0,0 +1,13 @@
+import { OCM_REGISTRY_FILE } from "./paths"
+
+export function reportWarnings(warnings: string[]): void {
+  for (const warning of warnings) console.error(`  warning: ${warning}`)
+}
+
+export function reportRestart(changed: number): void {
+  if (changed > 0) console.log("restart opencode to activate")
+}
+
+export function reportUpgrade(wasV1: boolean): void {
+  if (wasV1) console.error(`registry upgraded v1 → v2 (${OCM_REGISTRY_FILE})`)
+}

package/src/types.ts

@@ -0,0 +1,70 @@
+export type ComponentType = "agent" | "command" | "skill" | "plugin" | "mcp"
+
+// the merged manifest cached in the registry: marketplace entry >
+// plugin.json > filesystem inference (spec 06)
+export type PluginManifest = {
+  description?: string
+  category?: string
+  tags?: string[]
+  keywords?: string[]
+  version?: string
+  homepage?: string
+  license?: string
+  defaultEnabled?: boolean
+  mcpServers?: string
+  // fields where marketplace.json and plugin.json disagreed; the marketplace
+  // entry won by precedence, and info annotates them (spec 09)
+  conflicts?: string[]
+}
+
+export interface DiscoveredPlugin {
+  name: string
+  dir: string
+  source: string
+  components: Partial<Record<ComponentType, string[]>>
+  manifest: PluginManifest
+}
+
+export interface MarketplacePlugin {
+  source: string
+  components: Partial<Record<ComponentType, string[]>>
+  enabled: boolean
+  // names the marketplace that already provides this plugin name; set only
+  // while the collision exists, and the plugin stays disabled until it clears
+  collision?: string
+  installedAt: string | null
+  version: string | null
+  manifest: PluginManifest
+}
+
+export interface MarketplaceEntry {
+  url: string
+  dir: string
+  local: boolean
+  addedAt: string
+  mode: "auto" | "explicit"
+  ref: string | null
+  // set when the source was a github tree url: discovery roots here while
+  // git operations run against the clone root
+  subdir?: string | null
+  revision: string | null
+  syncIntervalMs: number | null
+  trust: {
+    code: "none" | "granted" | "denied"
+    grantedAt?: string
+    fingerprint?: string
+    // per-component hashes recorded at grant time; absent on grants written
+    // before spec 07, which approve everything (spec 07)
+    components?: Record<string, string>
+  }
+  // set by the loader when executable components changed since the grant;
+  // cleared by the next trust decision (spec 07)
+  trustPending?: boolean
+  lastSync: { at: string; ok: boolean; error: string | null } | null
+  plugins: Record<string, MarketplacePlugin>
+}
+
+export interface Registry {
+  version: 2
+  marketplaces: Record<string, MarketplaceEntry>
+}

package/template/marketplace.json

@@ -0,0 +1,17 @@
+{
+  "$schema": "https://raw.githubusercontent.com/wntic/ocm/main/schema/marketplace-v1.json",
+  "name": "demo-marketplace",
+  "description": "Example ocm marketplace",
+  "plugins": [
+    {
+      "name": "demo-kit",
+      "source": "./plugins/demo-kit",
+      "description": "One component of every type ocm ships"
+    },
+    {
+      "name": "release-kit",
+      "source": "./plugins/release-kit",
+      "description": "Release helpers, authored for both opencode and Claude Code"
+    }
+  ]
+}

package/template/plugins/demo-kit/agents/reviewer.md

@@ -0,0 +1,20 @@
+---
+description: Reviews code for correctness, security and readability before merge
+mode: subagent
+tools:
+  read: true
+  edit: false
+  bash: false
+model: inherit
+---
+
+You are a strict code reviewer.
+
+Review the provided changes and report:
+
+1. **Correctness** — logic errors, edge cases, race conditions
+2. **Security** — injection, secrets exposure, unsafe deserialization
+3. **Readability** — naming, dead code, misleading comments
+
+For every finding give: file:line, severity (critical/warning/note), and a suggested fix.
+End with a verdict: approve, approve-with-comments, or request-changes.

package/template/plugins/demo-kit/commands/tdd.md

@@ -0,0 +1,12 @@
+---
+description: Write a failing test first, then minimal implementation
+agent: build
+---
+
+Implement the following using strict TDD: $ARGUMENTS
+
+Workflow:
+1. Write a failing test that captures the requirement
+2. Run the test, confirm it fails for the expected reason
+3. Write the minimal implementation that makes it pass
+4. Refactor while keeping the test green

package/template/plugins/demo-kit/mcp.json

@@ -0,0 +1,3 @@
+{
+  "time": { "type": "local", "command": ["date"], "enabled": true }
+}

package/template/plugins/demo-kit/plugin/notify.js

@@ -0,0 +1,4 @@
+export default {
+  id: "demo-kit-notify",
+  server: async () => ({}),
+}

package/template/plugins/demo-kit/plugin.json

@@ -0,0 +1,6 @@
+{
+  "description": "One command, agent, skill, plugin and mcp server — the demo kit",
+  "version": "0.1.0",
+  "category": "example",
+  "tags": ["demo"]
+}

package/template/plugins/demo-kit/skills/code-review/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: code-review
+description: Structured checklist for reviewing pull requests
+license: MIT
+compatibility: opencode
+---
+
+## What I do
+
+Guide a structured code review using this checklist:
+
+1. Tests — are new behaviors covered?
+2. Errors — are failures handled explicitly?
+3. Contracts — do types and APIs match usage?
+4. Performance — any obvious N+1 or unbounded work?
+5. Docs — are public interfaces documented?
+
+## When to use me
+
+Use when reviewing a PR, a diff, or freshly written code.
+Produce findings as `file:line — severity — suggestion`.

package/template/plugins/release-kit/commands/ship.md

@@ -0,0 +1,11 @@
+---
+description: Cut a release for the current project
+agent: build
+---
+
+Ship a release: $ARGUMENTS
+
+Workflow:
+1. Confirm the version bump (patch, minor, major) with the user
+2. Draft the release notes from the commits since the last tag
+3. Tag the release and push the tag

package/template/plugins/release-kit/commands.claude/ship.md

@@ -0,0 +1,11 @@
+---
+description: Cut a release for the current project
+argument-hint: <patch|minor|major>
+---
+
+Ship a release: $ARGUMENTS
+
+Workflow:
+1. Confirm the version bump (patch, minor, major) with the user
+2. Draft the release notes from the commits since the last tag
+3. Tag the release and push the tag

package/template/plugins/release-kit/plugin.json

@@ -0,0 +1,6 @@
+{
+  "description": "Ship a release and write its notes — the cross-tool demo kit",
+  "version": "0.1.0",
+  "category": "example",
+  "tags": ["release"]
+}

package/template/plugins/release-kit/skills/release-notes/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: release-notes
+description: Draft release notes from a commit range
+---
+
+## What I do
+
+Draft release notes from the commits between two refs, grouped as
+Added, Changed and Fixed.
+
+## When to use me
+
+Use when preparing a release. Produce notes as a markdown file with one
+section per group and a bullet per commit, quoting the commit subject.