cool-workflow 0.1.79 → 0.1.81

package/skills/deploy-check/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: deploy-check
+description: >-
+  Verify Cool Workflow release, publish, deploy, or package readiness. Use when
+  Codex must check build/test gates, generated manifests, project index sync,
+  dist/source contract, changelog/release notes, npm package contents, or
+  pre-tag risk before shipping.
+---
+
+# Deploy Check
+
+## Overview
+
+Deploy check is the verifier side of release work. It confirms the artifact a
+user receives matches the source, docs, manifests, and stated capability.
+
+## Workflow
+
+1. Confirm the intended capability and release scope.
+2. Inspect branch status and generated artifact drift.
+3. Run the deterministic gates.
+4. Check docs/man-page coverage for shipped behavior.
+5. Check package contents and `dist/` policy.
+6. Report risk before any tag or publish step.
+
+## Commands
+
+```bash
+npm run build
+npm test
+npm run gen:manifests -- --check
+npm run index:check
+npm run version:sync
+npm run release:check
+git diff --check
+```
+
+For package inspection:
+
+```bash
+npm pack --dry-run
+```
+
+## Red Lines
+
+- Do not tag without test evidence.
+- Do not write reviewer verdict files by hand.
+- Do not silently skip `dist/` drift if the package still ships `dist/`.
+- Do not publish undocumented behavior.
+- Do not call a release ready if generated manifests or project index drift.
+
+## Output Rules
+
+Return a ship/no-ship verdict, gate results, artifact risks, and the next
+operator action.

package/skills/deploy-check/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Deploy Check"
+  short_description: "Verify release and deploy readiness."
+  default_prompt: "Use $deploy-check to verify deploy readiness."

package/skills/design-qa/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: design-qa
+description: >-
+  Evaluate Cool Workflow architecture, product design, operator UX,
+  context-pack, workflow-app, MCP/CLI, or release-process proposals. Use when
+  Codex must decide whether a design respects FreeBSD/POLA,
+  mechanism-not-policy, stable JSON surfaces, evidence, and verifier boundaries
+  before implementation.
+---
+
+# Design QA
+
+## Overview
+
+Design QA checks whether a proposed capability belongs in the kernel,
+userland, a manifest, a wrapper, a routine, or an eval before implementation.
+
+## Workflow
+
+1. State the user capability in one sentence.
+2. Identify the contract surface: CLI, MCP, `.cw/` state, file layout, docs,
+   package contents, or external wrapper.
+3. Separate mechanism from policy. Move policy into data, apps, wrappers, env,
+   or docs.
+4. Check POLA: existing outputs, flags, exit codes, and file layouts stay
+   byte-identical unless a new opt-in surface is used.
+5. Define verifier evidence: tests, manifests, screenshots for UI, replay, or
+   logs.
+6. Decide whether the work needs a new eval case or skill update.
+
+## Checks
+
+- Does it preserve stdout-as-data?
+- Does it fail closed instead of guessing?
+- Does it avoid vendor-specific parsing in `src/`?
+- Does it keep generated files verifiable?
+- Does it have a man page or docs contract?
+- Can maker and verifier run in separate worktrees?
+
+## Output Rules
+
+Return:
+
+1. Verdict: acceptable, revise, or reject.
+2. Required contract shape.
+3. Verification plan.
+4. Risks and non-goals.
+
+Do not turn design QA into implementation unless the user asks to proceed.

package/skills/design-qa/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Design QA"
+  short_description: "Check architecture and UX design quality."
+  default_prompt: "Use $design-qa to evaluate this design."

package/skills/pr-review/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: pr-review
+description: >-
+  Review Cool Workflow pull requests or branch diffs. Use when Codex must
+  inspect code changes for bugs, regressions, FreeBSD/POLA violations, missing
+  tests, generated artifact drift, release-contract risk, or CI implications,
+  and return findings first with file/line citations.
+---
+
+# PR Review
+
+## Overview
+
+Review for correctness and release risk before style. Findings lead; summaries
+are secondary. Treat missing tests and POLA drift as real risks.
+
+## Workflow
+
+1. Read the diff and identify touched contracts: CLI, MCP, `.cw/` state, docs,
+   dist, manifests, tests, release flow, or public package files.
+2. Inspect the surrounding code for behavioral expectations.
+3. Check whether tests exercise the changed behavior and fail closed.
+4. Look for stdout chatter, silent fallback, hidden policy in core, untracked
+   generated drift, and accidental public-output changes.
+5. Report findings first, ordered by severity, with file and line references.
+6. Include open questions only when they block confidence.
+
+## Review Rules
+
+- Do not request cosmetic rewrites unless they hide a bug.
+- Do not approve undocumented shipped behavior.
+- Do not accept type-only additions without runtime behavior.
+- Do not accept `dist/` edits without matching `src/` changes.
+- For UI work, require screenshots or browser verification.
+
+## Output Shape
+
+Use this order:
+
+1. Findings
+2. Open questions
+3. Test gaps
+4. Short summary
+
+If there are no findings, say so clearly and name residual risk.

package/skills/pr-review/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "PR Review"
+  short_description: "Review pull requests with cited findings."
+  default_prompt: "Use $pr-review to review this pull request."

package/dist/capability-dispatcher.js

@@ -1,86 +0,0 @@
-"use strict";
-// Capability Dispatcher — the thin MECHANISM pipe that routes a capability id
-// to its registered handler function. It knows nothing about which capabilities
-// exist (that's POLICY, declared elsewhere via registerCapabilityHandler).
-//
-// BSD discipline:
-//  - ONE THING: map (capability id, args, ctx) -> handler output.
-//  - SEPARATE MECHANISM FROM POLICY. The Map is mechanism; which entries are
-//    registered is policy (callers registerCapabilityHandler at import time).
-//  - FAIL CLOSED. Unknown capability id -> CapabilityError with a named refusal.
-//  - COMPOSABLE. The dispatcher is a pure router; CLI and MCP surfaces compose
-//    their own formatting/protocol wrapping around it. No surface knows how to
-//    format — the handler returns raw data, the surface renders it.
-//  - NO HIDDEN STATE. The registry is a plain Map; no lazy loading, no magic.
-//
-// From v0.1.53: this replaces the "manual switch in cli.ts + mcp-server.ts"
-// anti-pattern for NEW capabilities. Existing hardcoded capabilities remain in
-// the switch until they are progressively migrated; the fallback path in both
-// surfaces first checks the switch, then falls through to this dispatcher.
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.registerCapabilityHandler = registerCapabilityHandler;
-exports.getCapabilityHandler = getCapabilityHandler;
-exports.dispatchCapability = dispatchCapability;
-exports.resolveCliPath = resolveCliPath;
-exports.resolveMcpTool = resolveMcpTool;
-exports.listCapabilityIds = listCapabilityIds;
-class CapabilityError extends Error {
-    code;
-    capabilityId;
-    constructor(capabilityId, reason, code) {
-        super(`Capability "${capabilityId}": ${reason}`);
-        this.name = "CapabilityError";
-        this.code = code;
-        this.capabilityId = capabilityId;
-    }
-}
-const _handlerRegistry = new Map();
-/** Register a capability handler. Later registrations with the same capability
- *  id overwrite earlier ones (last-write-wins dedup). */
-function registerCapabilityHandler(handler) {
-    _handlerRegistry.set(handler.descriptor.capability, handler);
-}
-/** Look up a handler by capability id. Returns undefined when not found. */
-function getCapabilityHandler(capabilityId) {
-    return _handlerRegistry.get(capabilityId);
-}
-/** Dispatch a capability by id. Resolves the handler, invokes `run()`.
- *  Fail-closed: throws CapabilityError when no handler is registered. */
-function dispatchCapability(capabilityId, args, ctx) {
-    const handler = _handlerRegistry.get(capabilityId);
-    if (!handler)
-        throw new CapabilityError(capabilityId, "no handler registered", "not-found");
-    return handler.run(args, ctx);
-}
-/** Resolve a CLI path (e.g. ["gc", "plan"]) to a capability id by matching
- *  registered handlers' `cli.path` bindings. Returns undefined when no match. */
-function resolveCliPath(cliPath) {
-    if (!cliPath.length)
-        return undefined;
-    for (const handler of _handlerRegistry.values()) {
-        if (!handler.descriptor.cli)
-            continue;
-        const expected = handler.descriptor.cli.caseTokens || handler.descriptor.cli.path;
-        if (pathsMatch(expected, cliPath))
-            return handler.descriptor.capability;
-    }
-    return undefined;
-}
-/** Resolve an MCP tool name to a capability id by matching registered handlers'
- *  `mcp.tool` bindings. Returns undefined when no match. */
-function resolveMcpTool(toolName) {
-    for (const handler of _handlerRegistry.values()) {
-        if (handler.descriptor.mcp?.tool === toolName)
-            return handler.descriptor.capability;
-    }
-    return undefined;
-}
-/** List all registered capability ids. */
-function listCapabilityIds() {
-    return [..._handlerRegistry.keys()].sort();
-}
-function pathsMatch(expected, actual) {
-    if (expected.length !== actual.length)
-        return false;
-    return expected.every((token, i) => actual[i] === token);
-}