@brainervirus/workit-opencode 1.3.1 → 2.0.0
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/README.md +20 -4
- package/dist/plugin.js +934 -5011
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
[](https://www.npmjs.com/package/@brainervirus/workit-opencode)
|
|
5
5
|
[](../../LICENSE)
|
|
6
6
|
|
|
7
|
-
OpenCode plugin for
|
|
7
|
+
OpenCode plugin for Workit — optional coordination, policy, delegation, handoff, and read-only context. Native OpenCode tools execute Git, hosting, YouTrack and documentation effects.
|
|
8
8
|
|
|
9
9
|
## Install
|
|
10
10
|
|
|
@@ -16,22 +16,25 @@ OpenCode plugin for workit — workflow rails for agentic coding (specs, plans,
|
|
|
16
16
|
}
|
|
17
17
|
```
|
|
18
18
|
|
|
19
|
-
|
|
19
|
+
OpenCode V2 uses `"plugins"`; V1 uses `"plugin"`.
|
|
20
|
+
|
|
21
|
+
Local dev variant (absolute path to this repo; use `plugins` on V2):
|
|
20
22
|
|
|
21
23
|
```jsonc
|
|
22
24
|
{
|
|
23
25
|
"$schema": "https://opencode.ai/config.json",
|
|
24
|
-
"plugin": ["file:///path/to/workit/packages/workit-opencode
|
|
26
|
+
"plugin": ["file:///path/to/workit/packages/workit-opencode"]
|
|
25
27
|
}
|
|
26
28
|
```
|
|
27
29
|
|
|
28
|
-
Requirements: OpenCode 1.18.30+ (V1) or 2.0.18 (V2), Node ≥ 24. The published
|
|
30
|
+
Requirements: OpenCode 1.18.30+ (V1) or 2.0.18+ (V2), Node ≥ 24. The published
|
|
29
31
|
plugin is a self-contained Node bundle; its default export is a dual entry
|
|
30
32
|
(`server()` for V1, `setup()` for V2), so the same pin works on both hosts.
|
|
31
33
|
|
|
32
34
|
## What it provides
|
|
33
35
|
|
|
34
36
|
- **Eight native operation tools** — `workit_task`, `workit_policy`, `workit_evidence`, `workit_finding`, `workit_decision`, `workit_worker`, `workit_writer`, and `workit_state`.
|
|
37
|
+
- **Read-only context and init tools** — `workit_context` accepts `{ "kind": "git" }` and the existing PR/YouTrack/changelog/release/affected context fields; `workit_init_apply` keeps confirmed configuration initialization.
|
|
35
38
|
- **Fourteen policy-selected method skills** — challenge, behavioral TDD, review, plan, implement, debug, handoff,
|
|
36
39
|
babysit, blast-radius, deslop, diagram, mockup, green-run, and steer.
|
|
37
40
|
- **Native lifecycle hooks** — host-observed question receipts, direct-child task workers, compact task bootstrap/restoration, and known-surface writer checks.
|
|
@@ -42,6 +45,19 @@ plugin is a self-contained Node bundle; its default export is a dual entry
|
|
|
42
45
|
- **Delegation** — native `task` workers are direct-child-only; nested or uncertain lineage is denied (`delegation_lineage_denied`).
|
|
43
46
|
- **Continuity** — compact task context is injected once on session start and once after compaction; unobservable shell surfaces are labeled `agent_guided`.
|
|
44
47
|
|
|
48
|
+
Workit does not register `workit_external_action` on either OpenCode version.
|
|
49
|
+
Use native tools for mutations under the host permissions and target conventions;
|
|
50
|
+
no Workit task, writer or decision is needed merely to run an ordinary command.
|
|
51
|
+
Old action/decision history is preserved. Inspect and reconcile any uncertain
|
|
52
|
+
effect before retrying; removal does not settle or migrate it.
|
|
53
|
+
|
|
54
|
+
## Upgrade from Workit 1.x
|
|
55
|
+
|
|
56
|
+
Workit 2.0 removes the managed external-action tool on both OpenCode versions.
|
|
57
|
+
Use native host tools for mutations and `workit_context` for read-only context.
|
|
58
|
+
Existing task and action history remains untouched; reconcile uncertain effects
|
|
59
|
+
before retrying them.
|
|
60
|
+
|
|
45
61
|
## Bundle / runtime model
|
|
46
62
|
|
|
47
63
|
The build bundles the `@opencode-ai/plugin` (V1) and `@opencode/plugin` (V2) SDK surfaces used by the adapters into `dist/plugin.js`, so the published plugin has **no** runtime dependency on either SDK (both stay development/build-only pins). The plugin loads through its real package entry `dist/plugin.js`; only the fourteen method skills ship under `assets/`.
|