@aryaminus/controlkeel-pi-extension 0.1.20 → 0.1.21
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/PI.md +2 -2
- package/package.json +1 -1
- package/pi-extension.json +1 -1
package/PI.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
# ControlKeel Companion Instructions
|
|
2
2
|
|
|
3
|
-
This project is governed by ControlKeel. Prefer the ControlKeel MCP server for validation, findings, budgets, proof context, and routing.
|
|
3
|
+
This project is governed by ControlKeel. Prefer the ControlKeel MCP server for validation, findings, budgets, proof context, workspace snapshots, transcript state, and routing.
|
|
4
4
|
|
|
5
5
|
Project root: `.`
|
|
6
6
|
Target: `pi`
|
|
7
7
|
|
|
8
8
|
Required workflow:
|
|
9
|
-
1. Call `ck_context` at the start of a task.
|
|
9
|
+
1. Call `ck_context` at the start of a task for mission, workspace, transcript, and resume context.
|
|
10
10
|
2. Call `ck_validate` before writing code, config, shell, or deploy content.
|
|
11
11
|
3. Submit plans or approval packets with `ck_review_submit` and check `ck_review_status` before execution.
|
|
12
12
|
4. Record any human-review issue with `ck_finding`.
|
package/package.json
CHANGED
package/pi-extension.json
CHANGED