@williambeto/ai-workflow 1.18.7 → 1.18.8
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/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [1.18.8] - 2026-05-20
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
|
|
14
|
+
- **Discovery gate enforcement**: `opencode/agents/discovery.md` now explicitly blocks execution/delegation requests and routes them to `orchestrator`.
|
|
15
|
+
- **Discovery routing guard docs**: added explicit guard behavior to `opencode/agents/README.md` and `runbooks/agent-delegation-workflow.md` to keep gate behavior consistent across agent docs and runbooks.
|
|
16
|
+
- **Roadmap simplification phases**: added Phase 17/18/19 plan in `ROADMAP.md` for OpenCode-first focus, artifact surface reduction, and consumer-validation/Napkin hardening.
|
|
17
|
+
|
|
18
|
+
### Changed
|
|
19
|
+
|
|
20
|
+
- **Roadmap priority update**: `ROADMAP.md` next sprint, next step, and next recommended PR now point to Phase 17 platform focus as immediate priority.
|
|
21
|
+
|
|
10
22
|
## [1.18.6] - 2026-05-20
|
|
11
23
|
|
|
12
24
|
### Added
|
|
@@ -56,6 +56,11 @@ Orchestrated delivery (automatic routing gates):
|
|
|
56
56
|
orchestrator (gate A/B/C/D) -> next agent by pass/block result
|
|
57
57
|
```
|
|
58
58
|
|
|
59
|
+
Discovery routing guard:
|
|
60
|
+
|
|
61
|
+
- `discovery` is clarification-only.
|
|
62
|
+
- If execution, file edits, validation execution, release actions, or specialist delegation is requested during discovery, the correct behavior is `Blocked` + handoff to `orchestrator`.
|
|
63
|
+
|
|
59
64
|
Delegation policy baseline:
|
|
60
65
|
|
|
61
66
|
- route ownership by dominant task type using `AGENTS.md` delegation matrix;
|
|
@@ -88,7 +93,7 @@ Do not use Napkin as a temporary task log, and never store secrets.
|
|
|
88
93
|
|
|
89
94
|
| Agent | Purpose | Use when | Should not do |
|
|
90
95
|
| ----- | ------- | -------- | ------------- |
|
|
91
|
-
| `discovery` | Turn vague requests into a discovery brief. | Scope, risks, dependencies, and unknowns are unclear. | Estimate price, implement,
|
|
96
|
+
| `discovery` | Turn vague requests into a discovery brief. | Scope, risks, dependencies, and unknowns are unclear. | Estimate price, implement, edit files, perform execution/delegation routing directly (must return `Blocked` and route to `orchestrator`). |
|
|
92
97
|
| `planner` | Turn approved scope into requirements, specs, technical plans, and PR breakdowns. | Scope is approved and implementation needs a handoff. | Implement. |
|
|
93
98
|
| `implementer` | Implement one selected PR. | A PR plan or handoff exists. | Expand scope or do opportunistic refactors. |
|
|
94
99
|
| `fixer` | Diagnose and fix bugs, regressions, failures, and warnings. | There is broken behavior or failed validation. | Rewrite large areas without evidence. |
|
|
@@ -25,14 +25,23 @@ Turn vague client or user requests, screenshots, notes, and rough ideas into a c
|
|
|
25
25
|
- Surface risks, dependencies, and blocked decisions.
|
|
26
26
|
- Ask up to 5 discovery questions.
|
|
27
27
|
- Recommend the next workflow step.
|
|
28
|
+
- If the request includes implementation, file edits, execution flow, or specialist delegation, return `Blocked` and hand off to `orchestrator`.
|
|
28
29
|
|
|
29
30
|
## Constraints
|
|
30
31
|
|
|
31
32
|
- Do not estimate price directly.
|
|
32
33
|
- Do not implement.
|
|
34
|
+
- Do not edit files or perform write operations.
|
|
33
35
|
- Do not create a detailed technical plan before scope is clear.
|
|
34
36
|
- Do not ask more than 5 questions.
|
|
35
37
|
|
|
38
|
+
## Gate behavior (defensive)
|
|
39
|
+
|
|
40
|
+
- Discovery is a clarification step, not an execution owner.
|
|
41
|
+
- If a request requires implementation, review, validation, release actions, or multi-agent routing, output `Blocked` and route to `orchestrator`.
|
|
42
|
+
- Branch gate ownership is `orchestrator` (and step owners). Discovery must not bypass it.
|
|
43
|
+
- If Discovery is ever asked to perform a write operation, stop and return `Blocked` with this minimum safe instruction: run `git status -sb`; if branch is `main`, create/switch to a scoped branch before any edits.
|
|
44
|
+
|
|
36
45
|
## Expected output
|
|
37
46
|
|
|
38
47
|
- Objective
|
|
@@ -43,6 +52,8 @@ Turn vague client or user requests, screenshots, notes, and rough ideas into a c
|
|
|
43
52
|
- Dependencies
|
|
44
53
|
- Up to 5 discovery questions
|
|
45
54
|
- Recommended next step
|
|
55
|
+
- Gate result (`Pass` for discovery-only scope, `Blocked` when execution/delegation is requested)
|
|
56
|
+
- Next agent (`orchestrator`) when blocked
|
|
46
57
|
|
|
47
58
|
## Stop conditions
|
|
48
59
|
|
package/package.json
CHANGED
|
@@ -14,6 +14,12 @@ Delegate when at least one is true:
|
|
|
14
14
|
|
|
15
15
|
Do not delegate for trivial one-file edits that the active primary agent can complete safely.
|
|
16
16
|
|
|
17
|
+
## Discovery guard (mandatory)
|
|
18
|
+
|
|
19
|
+
- `discovery` is clarification-only and is not an execution owner.
|
|
20
|
+
- If a request during discovery requires implementation, file edits, validation execution, release actions, or specialist delegation, return `Blocked` and hand off to `orchestrator`.
|
|
21
|
+
- Branch gate ownership remains with `orchestrator` and step owners (`planner`, `implementer`, `fixer`, `reviewer`, `validator`, `release-manager`) before write operations.
|
|
22
|
+
|
|
17
23
|
## Delegation matrix
|
|
18
24
|
|
|
19
25
|
| Task type | Primary owner |
|