@aryaminus/controlkeel-opencode 0.3.16 → 0.3.19

package/.opencode/skills/align/references/workflow.md

@@ -0,0 +1,28 @@
+# Governed Workflow
+
+Use this reference with `controlkeel-governance`.
+
+## Start
+
+1. `ck_context` to load mission, task, risk, budget, proof summary, memory hits, workspace snapshot, and recent transcript events.
+2. Identify whether the task is implementation, review, compliance, benchmark, or policy work.
+3. Load a more specific CK skill if the task has a narrower workflow.
+
+## Before mutations
+
+1. Validate the exact code, config, shell, or text with `ck_validate`.
+2. Respect `block` immediately.
+3. Note `warn` in your reply and continue carefully.
+
+## During work
+
+1. Keep changes small.
+2. Call `ck_budget` before expensive multi-agent or long-context work.
+3. Use `ck_route` when another agent would be materially better.
+4. Create a `ck_finding` entry for any issue not automatically detected.
+
+## Before completion
+
+1. Re-check active findings.
+2. Re-check budget and proof state.
+3. If the session is high or critical risk, summarize decisions and unresolved items explicitly.

package/.opencode/skills/cloudflare-agent/SKILL.md

@@ -225,6 +225,11 @@ export class DBEnabledAgent extends Agent {
 
 ## Tools Reference
 
+> **Note:** The tool names below are the Cloudflare agent's *local* abstractions,
+> not direct CK MCP dispatch tool names. The agent maps these to CK MCP calls
+> internally (e.g., `ck_budget_check` wraps `ck_budget`, `ck_validate` maps directly).
+> Do not call these names against the CK MCP server directly.
+
 ### MCP Tools (serve to agents)
 
 | Tool | Description | Parameters |
@@ -236,7 +241,7 @@ export class DBEnabledAgent extends Agent {
 | `ck_context` | Get governance context | - |
 | `ck_delegate` | Delegate to sub-agent | `agent`, `task` |
 
-### CK to Agent Tools
+### CK to Agent Tools (agent-local, not CK MCP dispatch)
 
 | Tool | Description |
 |------|-------------|

package/.opencode/skills/plan-slice/references/workflow.md

@@ -0,0 +1,28 @@
+# Governed Workflow
+
+Use this reference with `controlkeel-governance`.
+
+## Start
+
+1. `ck_context` to load mission, task, risk, budget, proof summary, memory hits, workspace snapshot, and recent transcript events.
+2. Identify whether the task is implementation, review, compliance, benchmark, or policy work.
+3. Load a more specific CK skill if the task has a narrower workflow.
+
+## Before mutations
+
+1. Validate the exact code, config, shell, or text with `ck_validate`.
+2. Respect `block` immediately.
+3. Note `warn` in your reply and continue carefully.
+
+## During work
+
+1. Keep changes small.
+2. Call `ck_budget` before expensive multi-agent or long-context work.
+3. Use `ck_route` when another agent would be materially better.
+4. Create a `ck_finding` entry for any issue not automatically detected.
+
+## Before completion
+
+1. Re-check active findings.
+2. Re-check budget and proof state.
+3. If the session is high or critical risk, summarize decisions and unresolved items explicitly.

package/package.json

@@ -35,5 +35,5 @@
     "url": "git+https://github.com/aryaminus/controlkeel.git"
   },
   "type": "module",
-  "version": "0.3.16"
+  "version": "0.3.19"
 }