@abelxiaoxing/cadence 2.0.31 → 2.0.33

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.de.md CHANGED
@@ -107,11 +107,12 @@ Cadence erzwingt keinen Pi-Versionsbereich; Entwicklungs-Pins und getestete Lauf
107
107
 
108
108
  ```sh
109
109
  bun install
110
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
110
+ bun run verify
111
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
111
112
  ```
112
113
 
113
114
  Engineering-Anleitungen sind unter [engineering/](engineering/) nach Bereich aufgeteilt; der Projektindex in [AGENTS.md](AGENTS.md) sagt, welche Datei welchen Code abdeckt.
114
- `verify` benötigt außerdem einen offiziellen Node-Build, ein privates temporäres Verzeichnis und ein vorhandenes Chromium; siehe [Verifikation](engineering/verification.md).
115
+ `verify` benötigt außerdem einen offiziellen Node-Build und ein privates temporäres Verzeichnis; `verify:full` ergänzt die langsamen Tests und Browserszenarien, die ein vorhandenes Chromium brauchen; siehe [Verifikation](engineering/verification.md).
115
116
 
116
117
  ## Lizenz
117
118
 
package/README.es.md CHANGED
@@ -107,11 +107,12 @@ Cadence no impone un rango de versiones de Pi; los pines de desarrollo y los tie
107
107
 
108
108
  ```sh
109
109
  bun install
110
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
110
+ bun run verify
111
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
111
112
  ```
112
113
 
113
114
  La guía de ingeniería se divide por área bajo [engineering/](engineering/); el índice del proyecto en [AGENTS.md](AGENTS.md) indica qué archivo cubre qué código.
114
- `verify` también necesita un build oficial de Node, un directorio temporal privado y un Chromium existente; ver [verificación](engineering/verification.md).
115
+ `verify` también necesita un build oficial de Node y un directorio temporal privado; `verify:full` añade las pruebas lentas y los escenarios de navegador, que necesitan un Chromium existente; ver [verificación](engineering/verification.md).
115
116
 
116
117
  ## Licencia
117
118
 
package/README.fr.md CHANGED
@@ -107,11 +107,12 @@ Cadence n'impose pas de plage de versions de Pi ; les versions figées de dével
107
107
 
108
108
  ```sh
109
109
  bun install
110
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
110
+ bun run verify
111
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
111
112
  ```
112
113
 
113
114
  Les conseils d'ingénierie sont répartis par domaine sous [engineering/](engineering/) ; l'index du projet dans [AGENTS.md](AGENTS.md) indique quel fichier couvre quel code.
114
- `verify` nécessite aussi un build Node officiel, un répertoire temporaire privé et un Chromium existant ; voir [vérification](engineering/verification.md).
115
+ `verify` nécessite aussi un build Node officiel et un répertoire temporaire privé ; `verify:full` ajoute les tests lents et les scénarios navigateur, qui nécessitent un Chromium existant ; voir [vérification](engineering/verification.md).
115
116
 
116
117
  ## Licence
117
118
 
package/README.ja.md CHANGED
@@ -126,12 +126,14 @@ Cadence は Pi のバージョン範囲を強制しない。
126
126
 
127
127
  ```sh
128
128
  bun install
129
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
129
+ bun run verify
130
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
130
131
  ```
131
132
 
132
133
  エンジニアリングのガイダンスは [engineering/](engineering/) 下に領域ごとに分割されている。
133
134
  [AGENTS.md](AGENTS.md) のプロジェクト索引がどのファイルがどのコードをカバーするかを示す。
134
- `verify` には公式 Node ビルド、プライベートな一時ディレクトリ、既存の Chromium も必要。
135
+ `verify` には公式 Node ビルドとプライベートな一時ディレクトリが必要。
136
+ 低速テストとブラウザシナリオを加える `verify:full` には既存の Chromium も必要。
135
137
  [検証](engineering/verification.md)を参照。
136
138
 
137
139
  ## ライセンス
package/README.ko.md CHANGED
@@ -123,12 +123,13 @@ Cadence는 Pi 버전 범위를 강제하지 않습니다.
123
123
 
124
124
  ```sh
125
125
  bun install
126
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
126
+ bun run verify
127
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
127
128
  ```
128
129
 
129
130
  엔지니어링 지침은 [engineering/](engineering/) 아래 영역별로 나뉘어 있습니다.
130
131
  [AGENTS.md](AGENTS.md)의 프로젝트 인덱스가 어느 파일이 어느 코드를 다루는지 설명합니다.
131
- `verify`에는 공식 Node 빌드, 개인 임시 디렉터리, 기존 Chromium도 필요합니다.
132
+ `verify`에는 공식 Node 빌드와 개인 임시 디렉터리가 필요하고, 느린 테스트와 브라우저 시나리오를 더하는 `verify:full`에는 기존 Chromium도 필요합니다.
132
133
  [검증](engineering/verification.md)을 참조하세요.
133
134
 
134
135
  ## 라이선스
package/README.md CHANGED
@@ -109,11 +109,12 @@ Cadence does not impose a Pi version range; development pins and tested runtimes
109
109
 
110
110
  ```sh
111
111
  bun install
112
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
112
+ bun run verify
113
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
113
114
  ```
114
115
 
115
116
  Engineering guidance is split by area under [engineering/](engineering/); the project index in [AGENTS.md](AGENTS.md) says which file covers which code.
116
- `verify` also needs an official Node build, a private temporary directory and an existing Chromium; see [verification](engineering/verification.md).
117
+ `verify` also needs an official Node build and a private temporary directory; `verify:full` adds the slow tests and browser scenarios, which need an existing Chromium; see [verification](engineering/verification.md).
117
118
 
118
119
  ## License
119
120
 
package/README.pt-BR.md CHANGED
@@ -107,11 +107,12 @@ O Cadence não impõe uma faixa de versões do Pi; fixações de desenvolvimento
107
107
 
108
108
  ```sh
109
109
  bun install
110
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
110
+ bun run verify
111
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
111
112
  ```
112
113
 
113
114
  As orientações de engenharia são divididas por área sob [engineering/](engineering/); o índice do projeto em [AGENTS.md](AGENTS.md) diz qual arquivo cobre qual código.
114
- `verify` também precisa de um build oficial do Node, um diretório temporário privado e um Chromium existente; veja [verificação](engineering/verification.md).
115
+ `verify` também precisa de um build oficial do Node e de um diretório temporário privado; `verify:full` acrescenta os testes lentos e os cenários de navegador, que precisam de um Chromium existente; veja [verificação](engineering/verification.md).
115
116
 
116
117
  ## Licença
117
118
 
package/README.ru.md CHANGED
@@ -107,12 +107,13 @@ Cadence не налагает диапазон версий Pi; фиксиров
107
107
 
108
108
  ```sh
109
109
  bun install
110
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
110
+ bun run verify
111
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
111
112
  ```
112
113
 
113
114
  Инженерные указания разделены по областям в [engineering/](engineering/).
114
115
  Индекс проекта в [AGENTS.md](AGENTS.md) указывает, какой файл покрывает какой код.
115
- `verify` также требует официального сборки Node, приватного временного каталога и существующего Chromium, подробности — в [верификация](engineering/verification.md).
116
+ `verify` также требует официальной сборки Node и приватного временного каталога; `verify:full` добавляет медленные тесты и браузерные сценарии, которым нужен существующий Chromium, подробности — в [верификация](engineering/verification.md).
116
117
 
117
118
  ## Лицензия
118
119
 
package/README.zh-CN.md CHANGED
@@ -107,11 +107,12 @@ Cadence 不指定 Pi 版本范围;开发用的固定版本和已测试运行
107
107
 
108
108
  ```sh
109
109
  bun install
110
- CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify
110
+ bun run verify
111
+ CADENCE_BROWSER_PATH=/absolute/existing/chromium bun run verify:full
111
112
  ```
112
113
 
113
114
  工程指导按领域拆分在 [engineering/](engineering/) 下;[AGENTS.md](AGENTS.md) 中的项目索引说明了哪个文件覆盖哪部分代码。
114
- `verify` 还需要官方 Node 构建、私有临时目录和已有的 Chromium;见[验证](engineering/verification.md)。
115
+ `verify` 还需要官方 Node 构建和私有临时目录;`verify:full` 另外运行慢速测试和浏览器场景,需要已有的 Chromium;见[验证](engineering/verification.md)。
115
116
 
116
117
  ## 许可证
117
118
 
@@ -24,7 +24,7 @@ Browser conversation mode is retained by the project owner, not by a browser-onl
24
24
 
25
25
  Native mode is branch-aware; browser mode follows its server-owned conversation identity.
26
26
  The browser and the terminal share the conversation itself (it is the same Pi session), but each keeps its own Cadence mode and plan approval: entering Cadence in one does not enter it in the other.
27
- A workflow started in either place appears as a card in that conversation in the browser.
27
+ A workflow started in either place appears in that conversation in the browser as one line after the turn it started in.
28
28
  A saved native mode is active only in a trusted interactive terminal; print/RPC sessions keep ordinary tools and can still exit with `/cadence exit`.
29
29
  In Pi, the agent panel lists workflow subagents and opens their transcripts; `cadence_status` can read one step's transcript.
30
30
  Resume and compaction retain the mode/context, not execution grants.
@@ -105,7 +105,8 @@ System-service installation and remote access remain separate explicit operation
105
105
 
106
106
  `/cadence-history [run-id]` provides readonly diagnostics without model calls or service startup; see [History and diagnostics](history.md).
107
107
  The WebUI uses the same execution engine with a separate, context-bound browser confirmation path.
108
- Its main composer stays in the same conversation; the plan card, workflow progress and actual merge outcomes appear inline.
108
+ Its main composer stays in the same conversation; the plan card appears inline, and each workflow is one line after the turn it started in, showing what it is doing (with **Stop**) or how it ended: its merge commit, or the reason it did not complete.
109
+ Select the line to open the workflow's steps, checks, delivery and diagnostics in the main area; while it runs, the conversation's status names its phase.
109
110
  Research, implementation and review subagents are listed in the lower-left **Subagents** dock, together with legacy task children; selecting one (or **Open subagent context** on a step) opens its full transcript and retained result in the main area, and **Back to conversation** returns.
110
111
  Active workflows are listed under **Running conversations** with **Cancel workflow — request stop**; this includes native-started workflows, and an unavailable observation is not proof of no work.
111
112
  The old task creation/Save/Start/check/human-Review controls are retired on both clients and refused by the service.
@@ -115,7 +116,7 @@ Approval grants are neither stored in the browser nor restored after restart.
115
116
  Losing a response only observes its original command/run identity; it never retries execution.
116
117
  Exit does not stop accepted work, and **Cancel workflow — request stop** remains independent of conversation mode.
117
118
  There is no generic browser shell/PTY, service management/recovery or checkpoint pause/resume feature.
118
- Conversation response completion is distinct from workflow completion; read the workflow card for actual delivery/check outcomes.
119
+ Conversation response completion is distinct from workflow completion; read the workflow's line and view for actual delivery/check outcomes.
119
120
 
120
121
  ### Research scope, timing and retained results
121
122
 
package/docs/history.md CHANGED
@@ -5,9 +5,9 @@ History is evidence, not a second task manager or renewed execution consent.
5
5
 
6
6
  ## Current workflows
7
7
 
8
- - In the conversation, open a workflow's steps to see actual checks, Agent review, delivery and failures.
8
+ - In the conversation, select a workflow's line to open its steps: actual checks, Agent review, delivery and failures.
9
9
  **Open subagent context** shows the retained transcript; **Read retained step result** reads the retained result rather than its clipped status preview.
10
- - A workflow belongs to the conversation that started it, in the browser or in the terminal, and its card stays there.
10
+ - A workflow belongs to the conversation that started it, in the browser or in the terminal, and its line stays after the turn it started in.
11
11
  An active workflow is also listed under **Running conversations** in the browser sidebar.
12
12
  - In a trusted Pi terminal, `/cadence-history` lists workflows without asking a model.
13
13
  The listing is paged in ID order, not chronological order; larger histories show scan progress first, and **Continue scanning** resumes it.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@abelxiaoxing/cadence",
3
- "version": "2.0.31",
3
+ "version": "2.0.33",
4
4
  "description": "Conversation-driven Pi workspace: persistent native and WebUI workflows, explicit plan approval, checks and local delivery.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -93,17 +93,20 @@
93
93
  "scripts": {
94
94
  "pack:check": "node scripts/pack-check.mjs",
95
95
  "traceability:check": "node scripts/traceability-check.mjs",
96
- "verify": "bun run check && bun run check:web && bun run build:web:check && bun run lint && bun run check:agents && bun run test && bun run test:web && bun run test:browser && bun run pack:check",
97
- "check": "node scripts/check-syntax.mjs && bun scripts/build-operator.mjs --check && bun scripts/build-service.mjs --check && tsc --noEmit",
96
+ "verify": "node scripts/verify.mjs",
97
+ "verify:full": "node scripts/verify.mjs --full",
98
+ "check": "node scripts/check-syntax.mjs && bun scripts/build-operator.mjs --check && bun scripts/build-service.mjs --check && tsc --noEmit --incremental --tsBuildInfoFile .cache/tsc/root.tsbuildinfo",
98
99
  "lint": "biome check . && rumdl check .",
99
100
  "test": "vitest run",
101
+ "test:unit": "vitest run --tags-filter=!slow",
102
+ "test:slow": "vitest run --tags-filter=slow",
100
103
  "test:target": "vitest run",
101
104
  "check:agents": "node scripts/check-agents.mjs",
102
105
  "doctor": "node src/operator-cli.mjs doctor",
103
106
  "runs": "node src/operator-cli.mjs runs",
104
107
  "build:operator": "bun scripts/build-operator.mjs",
105
108
  "build:service": "bun scripts/build-service.mjs",
106
- "check:web": "tsc -p web/tsconfig.json && tsc -p web/tsconfig.config.json",
109
+ "check:web": "tsc -p web/tsconfig.json --incremental --tsBuildInfoFile .cache/tsc/web.tsbuildinfo && tsc -p web/tsconfig.config.json --incremental --tsBuildInfoFile .cache/tsc/web-config.tsbuildinfo",
107
110
  "test:web": "vitest run --config web/vitest.config.ts",
108
111
  "build:web": "node scripts/build-web.mjs",
109
112
  "build:web:check": "node scripts/build-web.mjs --check",
@@ -28150,7 +28150,7 @@ class WorkflowHistoryScanner {
28150
28150
 
28151
28151
  // src/service/workflows.ts
28152
28152
  var OWNER_RUNTIME = Object.freeze({
28153
- version: "2.0.31",
28153
+ version: "2.0.33",
28154
28154
  build: "b2e9f553ead7bbf1508624a3e834a8654557687cf2a3a26f2aa1161843abe5eb",
28155
28155
  entry: fileURLToPath6(import.meta.url),
28156
28156
  pid: process.pid,