@brainervirus/workit-cursor 5.0.0 → 6.0.1
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/.cursor-plugin/plugin.json +1 -1
- package/README.md +20 -94
- package/assets/templates/workit-contract.md +3 -2
- package/dist/cursor-session-start.js +2651 -4340
- package/dist/mcp-server.js +2200 -3931
- package/dist/workit-hook.js +2377 -4106
- package/package.json +3 -3
- package/rules/workit-contract.mdc +6 -6
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@brainervirus/workit-cursor",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "6.0.1",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "Workit Cursor plugin — shared MCP transport, native hooks, and sixteen method skills",
|
|
6
6
|
"keywords": [
|
|
@@ -44,8 +44,8 @@
|
|
|
44
44
|
"build": "bun scripts/build.ts"
|
|
45
45
|
},
|
|
46
46
|
"dependencies": {
|
|
47
|
-
"@brainervirus/workit-core": "^
|
|
48
|
-
"@brainervirus/workit-mcp": "^
|
|
47
|
+
"@brainervirus/workit-core": "^6.0.1",
|
|
48
|
+
"@brainervirus/workit-mcp": "^6.0.1"
|
|
49
49
|
},
|
|
50
50
|
"engines": {
|
|
51
51
|
"node": ">=24"
|
|
@@ -4,7 +4,7 @@ alwaysApply: true
|
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Workit is an optional coordinator, not a permission system. Ordinary questions,
|
|
7
|
-
investigation, and reversible edits need no Workit task, assessment,
|
|
7
|
+
investigation, and reversible edits need no Workit task, assessment,
|
|
8
8
|
reviewer, or close call; follow Cursor's native permissions. When a step has one
|
|
9
9
|
right answer, run the `workit` CLI verb for it (`workit check`, `workit git …`,
|
|
10
10
|
`workit pr …`, `workit ledger …`). Use one compact
|
|
@@ -14,19 +14,19 @@ host or merge distinct intents because their titles look similar.
|
|
|
14
14
|
|
|
15
15
|
Workit policy may narrow an action, but it never grants host access or overrides
|
|
16
16
|
a host deny. Check the actual target checkout, configured account, branch and
|
|
17
|
-
commit conventions, protected refs,
|
|
18
|
-
|
|
17
|
+
commit conventions, protected refs, and expected remote state before a delivery
|
|
18
|
+
verb; merge and release need a workspace grant (`workit grant show`). Report unsupported shell coverage honestly.
|
|
19
19
|
|
|
20
20
|
Cursor hooks provide evidence only where their documented input and blocking
|
|
21
21
|
behavior support it. AskQuestion answers are policy-only; `sessionStart` and
|
|
22
22
|
`preCompact` cannot block; `subagentStop` has no stable child identity; arbitrary
|
|
23
|
-
shell writes and Tab edits are unavailable. Never invent a
|
|
24
|
-
identity
|
|
23
|
+
shell writes and Tab edits are unavailable. Never invent a caller
|
|
24
|
+
identity or cross-process caller channel. For native subagents in tracked
|
|
25
25
|
Workit work, begin the task payload with exactly one assigned role marker:
|
|
26
26
|
`[workit-role: implementer]`, `[workit-role: reviewer]`, or
|
|
27
27
|
`[workit-role: investigator]`.
|
|
28
28
|
|
|
29
|
-
Cursor cannot
|
|
29
|
+
Cursor cannot attribute subagent writes, so Workit never enforces a
|
|
30
30
|
subagent's write scope here. Fanout writers (workit-fanout) are agent-guided:
|
|
31
31
|
each runs in its own git worktree with a fixed brief, and its file scope is
|
|
32
32
|
checked at fan-in with `git diff --name-only <base>...<branch>`, not enforced
|