opencode-codeops 2.3.0 → 2.4.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/CHANGELOG.md CHANGED
@@ -2,6 +2,12 @@
2
2
 
3
3
  All notable changes to CodeOps are recorded here.
4
4
 
5
+ ## 2.4.0 — 2026-10-29
6
+
7
+ ### Features
8
+
9
+ - setup-codeops: enable Discovery by default for new projects
10
+
5
11
  ## 2.3.0 — 2026-10-29
6
12
 
7
13
  ### Fixes
@@ -20,6 +26,7 @@ All notable changes to CodeOps are recorded here.
20
26
 
21
27
  ### Features
22
28
 
29
+ - discovery: redesign the plan workspace with group navigation, a decision summary, honest save feedback, and System/Light/Dark themes
23
30
  - discovery: complete the Fluent UI workspace
24
31
  - discovery: add guarded editing and the workspace shell
25
32
  - discovery: add workspace destinations and theme preference
package/README.md CHANGED
@@ -164,7 +164,7 @@ execution.
164
164
 
165
165
  ## Discovery
166
166
 
167
- Discovery is an opt-in local web page where the agent publishes a CodeOps question round
167
+ Discovery is a local web page where the agent publishes a CodeOps question round
168
168
  instead of asking every question in chat. Questions, options, recommendations, and dependency
169
169
  rules render in the browser; answers are saved there, and Submit wakes the OpenCode session that
170
170
  published them so it can continue.
@@ -191,8 +191,8 @@ The shared header carries a real breadcrumb and a **System / Light / Dark** them
191
191
  follows the operating-system setting; an explicit choice is remembered in the browser. If storage
192
192
  is unavailable, the choice still applies for the current tab.
193
193
 
194
- Enable it for a project with `analyze-project --with-discovery`, or add the setting to
195
- `codeops/codeops.json`:
194
+ New projects created with `setup-codeops` start with Discovery enabled. For an existing project,
195
+ run `analyze-project --with-discovery`, or add the setting to `codeops/codeops.json`:
196
196
 
197
197
  ```json
198
198
  {
@@ -3,9 +3,9 @@
3
3
  > **CodeOps Artifact Schema**: 1
4
4
 
5
5
  Discovery moves large question rounds out of the chat scroll and into a local
6
- browser page. It is opt-in per project and never replaces the Ambiguity
7
- Register. Use it only when this file's conditions hold; otherwise ask in chat
8
- exactly as before.
6
+ browser page. New projects created with `setup-codeops` enable it by default;
7
+ existing projects opt in. It never replaces the Ambiguity Register. Use it only
8
+ when this file's conditions hold; otherwise ask in chat exactly as before.
9
9
 
10
10
  ## When it applies
11
11
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-codeops",
3
- "version": "2.3.0",
3
+ "version": "2.4.0",
4
4
  "description": "Specification-first engineering for complex systems — CodeOps plugin for OpenCode",
5
5
  "type": "module",
6
6
  "engines": {
@@ -20,6 +20,9 @@ it is the single source of truth for the layout. Do not re-encode paths here.
20
20
  - **Per-repo only.** One git repo at a time; no cross-repo or portfolio-of-projects work.
21
21
  - This skill sets up the *structure*. It never authors requirements, plans, or roadmaps — that is
22
22
  `make-requirements` / `make-plan` / `roadmap`, which then resolve paths via the convention doc.
23
+ - A fresh scaffold enables Discovery by default (`discovery.enabled: true`,
24
+ `chatMaxQuestions: 3`). Existing projects keep their current setting; enable it with
25
+ `analyze-project --with-discovery` or by adding the setting manually.
23
26
 
24
27
  ## Dispatch — detect repo state, then branch
25
28
 
@@ -23,7 +23,7 @@ front. Those appear lazily when the first RD, plan, or task is authored (AR #5).
23
23
  1. Confirm the repo is a git repo (suggest `git init` if not).
24
24
  2. Create `codeops/features/` (the empty features dir).
25
25
  3. Write `codeops/.codeops.yml` (the marker — `setup-codeops` is its sole writer).
26
- 4. Write `codeops/codeops.json` with the strict defaults below.
26
+ 4. Write `codeops/codeops.json` with the strict defaults below, including Discovery enabled by default.
27
27
  5. Write `codeops/00-roadmap.md` (empty portfolio — see the portfolio template in the `roadmap`
28
28
  skill; seed it with zero features and an empty Archived section).
29
29
  6. Confirm the marker, policy, portfolio, and empty feature directory exist; report setup state
@@ -38,6 +38,7 @@ front. Those appear lazily when the first RD, plan, or task is authored (AR #5).
38
38
  "schema": 1,
39
39
  "mode": "strict",
40
40
  "artifacts": {"layout": "nested", "root": "codeops"},
41
+ "discovery": {"enabled": true, "chatMaxQuestions": 3},
41
42
  "quality": {
42
43
  "independentReview": true,
43
44
  "minimumReviewers": 1,