@abelxiaoxing/cadence 2.0.21 → 2.0.23

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
@@ -45,11 +45,10 @@ Port und Token liegen in `~/.pi/agent/cadence/.env`; wer das Token hat, kann dei
45
45
  Dieses Gespräch bleibt im Cadence-Modus; kläre Anforderungen mit normalen Nachrichten.
46
46
  4. Prüfe den vollständigen Plan und klicke **Implement this plan**.
47
47
  Implementierung, Checks, begrenzte Reparaturen und die vereinbarte lokale Lieferung laufen automatisch.
48
- 5. Verfolge Fortschritt und Subagent-Protokolle im Gespräch.
48
+ 5. Verfolge den Fortschritt im Gespräch; die Protokolle der Subagenten öffnest du über das Dock **Subagents** unten links.
49
49
  Aktualisieren und Abschluss beenden den Modus nicht.
50
50
  **Exit Cadence** beendet nur den Modus; **Cancel workflow — request stop** fordert den Abbruch an.
51
51
 
52
- **Legacy task**: previous task/history workflow.
53
52
  No live Pi terminal is required for the browser conversation workflow.
54
53
 
55
54
  ### Im Terminal
@@ -64,7 +63,8 @@ Modellpräferenzen werden projektübergreifend in `~/.pi/agent/cadence/settings.
64
63
 
65
64
  Der lokale Owner startet bei Bedarf; ein Systemdienst ist nur für die optionale WebUI/Autostart-Nutzung nötig.
66
65
 
67
- `/cadence-inspect`: legacy task/history UI.
66
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
67
+ See [History and diagnostics](docs/history.md).
68
68
  [Conversation mode](docs/conversation-mode.md): native/browser approval, limits and worktree setup.
69
69
  Browser authentication is not execution consent.
70
70
 
@@ -80,14 +80,8 @@ Das Öffnen eines anderen Projekts stoppt nie die Arbeit im vorherigen.
80
80
 
81
81
  ### Checks
82
82
 
83
- Liste die Befehle, die dein Projekt verifizieren, in `.cadence/assistant/config.json` auf, und Aufgaben können sie vor der Prüfung als echte Checks ausführen:
84
-
85
- ```json
86
- {
87
- "schema": "cadence-assistant-checks/1",
88
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
89
- }
90
- ```
83
+ Prüfbefehle stehen im ausdrücklich genehmigten Plan, einschließlich Baseline- und Abnahmeprüfungen.
84
+ Ihre tatsächlichen Ergebnisse bleiben von der automatischen Agent-Prüfung getrennt.
91
85
 
92
86
  ## Dienst verwalten
93
87
 
package/README.es.md CHANGED
@@ -45,11 +45,10 @@ El puerto y el token están en `~/.pi/agent/cadence/.env`; cualquiera con el tok
45
45
  Esta conversación permanece en modo Cadence; aclara los requisitos con mensajes normales.
46
46
  4. Revisa el plan completo y pulsa **Implement this plan**.
47
47
  La implementación, comprobaciones, reparaciones limitadas y entrega local acordada son automáticas.
48
- 5. Sigue el progreso y los registros de subagentes en la conversación.
48
+ 5. Sigue el progreso en la conversación; abre los registros de los subagentes desde el panel **Subagents** abajo a la izquierda.
49
49
  Recargar o terminar un objetivo no desactiva el modo.
50
50
  **Exit Cadence** sale del modo; **Cancel workflow — request stop** solicita cancelar el trabajo.
51
51
 
52
- **Legacy task**: previous task/history workflow.
53
52
  No live Pi terminal is required for the browser conversation workflow.
54
53
 
55
54
  ### En el terminal
@@ -64,7 +63,8 @@ Las preferencias de modelo se guardan entre proyectos en `~/.pi/agent/cadence/se
64
63
 
65
64
  El propietario local se inicia bajo demanda; el servicio del sistema es opcional para WebUI/inicio automático.
66
65
 
67
- `/cadence-inspect`: legacy task/history UI.
66
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
67
+ See [History and diagnostics](docs/history.md).
68
68
  [Conversation mode](docs/conversation-mode.md): native/browser approval, limits and worktree setup.
69
69
  Browser authentication is not execution consent.
70
70
 
@@ -80,14 +80,8 @@ Abrir otro proyecto nunca detiene el trabajo del anterior.
80
80
 
81
81
  ### Comprobaciones
82
82
 
83
- Lista los comandos que verifican tu proyecto en `.cadence/assistant/config.json`, y las tareas pueden ejecutarlos como comprobaciones reales antes de la revisión:
84
-
85
- ```json
86
- {
87
- "schema": "cadence-assistant-checks/1",
88
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
89
- }
90
- ```
83
+ Los comandos de verificación se declaran en el plan aprobado, incluidas las comprobaciones iniciales y de aceptación.
84
+ Sus resultados reales se mantienen separados de la revisión automática del agente.
91
85
 
92
86
  ## Gestionar el servicio
93
87
 
package/README.fr.md CHANGED
@@ -45,11 +45,10 @@ Le port et le jeton se trouvent dans `~/.pi/agent/cadence/.env` ; quiconque poss
45
45
  Cette conversation reste en mode Cadence ; précisez les besoins par des messages ordinaires.
46
46
  4. Lisez le plan complet et cliquez sur **Implement this plan**.
47
47
  L’implémentation, les vérifications, les réparations bornées et la livraison locale convenue sont automatiques.
48
- 5. Suivez la progression et les traces des sous-agents dans la conversation.
48
+ 5. Suivez la progression dans la conversation ; ouvrez les traces des sous-agents depuis le panneau **Subagents** en bas à gauche.
49
49
  Actualiser ou terminer un objectif ne quitte pas le mode.
50
50
  **Exit Cadence** quitte le mode ; **Cancel workflow — request stop** demande l’annulation.
51
51
 
52
- **Legacy task**: previous task/history workflow.
53
52
  No live Pi terminal is required for the browser conversation workflow.
54
53
 
55
54
  ### Dans le terminal
@@ -64,7 +63,8 @@ Les préférences de modèle sont conservées entre projets dans `~/.pi/agent/ca
64
63
 
65
64
  Le propriétaire local démarre à la demande ; le service système est facultatif pour la WebUI et le démarrage automatique.
66
65
 
67
- `/cadence-inspect`: legacy task/history UI.
66
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
67
+ See [History and diagnostics](docs/history.md).
68
68
  [Conversation mode](docs/conversation-mode.md): native/browser approval, limits and worktree setup.
69
69
  Browser authentication is not execution consent.
70
70
 
@@ -80,14 +80,8 @@ Ouvrir un autre projet n'arrête jamais le travail du précédent.
80
80
 
81
81
  ### Vérifications
82
82
 
83
- Listez les commandes qui vérifient votre projet dans `.cadence/assistant/config.json`, et les tâches peuvent les exécuter comme de véritables vérifications avant l'examen :
84
-
85
- ```json
86
- {
87
- "schema": "cadence-assistant-checks/1",
88
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
89
- }
90
- ```
83
+ Les commandes de vérification figurent dans le plan explicitement approuvé, avec les vérifications initiales et d’acceptation.
84
+ Leurs résultats restent distincts de la revue automatique par un Agent.
91
85
 
92
86
  ## Gérer le service
93
87
 
package/README.ja.md CHANGED
@@ -56,11 +56,10 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
56
56
  この会話は Cadence モードを維持し、その後は通常のメッセージで要件を明確にできます。
57
57
  4. 完全な計画を確認し、**Implement this plan** を押します。
58
58
  実装、検証、回数制限付きの修正、合意したローカル納品が自動で進みます。
59
- 5. 同じ会話で進捗とサブエージェントの記録を確認できます。
59
+ 5. 同じ会話で進捗を確認し、サブエージェントの記録は左下の **Subagents** パネルから開きます。
60
60
  再読み込みや目標完了でもモードは維持されます。
61
61
  **Exit Cadence** はモード終了のみ、**Cancel workflow — request stop** は作業のキャンセル要求です。
62
62
 
63
- **Legacy task**: previous task/history workflow.
64
63
  No live Pi terminal is required for the browser conversation workflow.
65
64
 
66
65
  ### ターミナルで
@@ -77,7 +76,8 @@ Cadence がプロジェクトを調査し、必要な判断を確認して計画
77
76
  ローカル owner は必要時に起動します。
78
77
  システムサービスのインストールは WebUI・自動起動を使う場合のみ必要です。
79
78
 
80
- `/cadence-inspect`: legacy task/history UI.
79
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
80
+ See [History and diagnostics](docs/history.md).
81
81
  [Conversation mode](docs/conversation-mode.md): native/browser approval, limits and worktree setup.
82
82
  Browser authentication is not execution consent.
83
83
 
@@ -94,14 +94,8 @@ WebUI のフォルダピッカーも同じ方法でプロジェクトを開く
94
94
 
95
95
  ### チェック
96
96
 
97
- `.cadence/assistant/config.json` にプロジェクトを検証するコマンドを列挙すると、タスクはレビュー前にそれを実際のチェックとして実行できる:
98
-
99
- ```json
100
- {
101
- "schema": "cadence-assistant-checks/1",
102
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
103
- }
104
- ```
97
+ チェックコマンドは、明示的に承認する計画に記載します。
98
+ 開始前のチェックと受け入れチェックの実際の結果は、自動 Agent レビューとは別に記録されます。
105
99
 
106
100
  ## サービスの管理
107
101
 
package/README.ko.md CHANGED
@@ -54,11 +54,10 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
54
54
  이 대화는 Cadence 모드를 유지하며 이후에는 일반 메시지로 요구사항을 구체화합니다.
55
55
  4. 전체 계획을 확인하고 **Implement this plan**을 누르세요.
56
56
  구현, 검사, 제한된 수정 및 합의한 로컬 전달을 자동으로 진행합니다.
57
- 5. 같은 대화에서 진행 상황과 서브에이전트 기록을 확인하세요.
57
+ 5. 같은 대화에서 진행 상황을 확인하고, 서브에이전트 기록은 왼쪽 아래 **Subagents** 패널에서 여세요.
58
58
  새로고침이나 목표 완료로 모드가 꺼지지 않습니다.
59
59
  **Exit Cadence**는 모드만 종료하고, **Cancel workflow — request stop**은 작업 취소를 요청합니다.
60
60
 
61
- **Legacy task**: previous task/history workflow.
62
61
  No live Pi terminal is required for the browser conversation workflow.
63
62
 
64
63
  ### 터미널에서
@@ -74,7 +73,8 @@ Cadence가 프로젝트를 조사하고 결정 사항을 확인한 뒤 계획을
74
73
  로컬 owner는 필요할 때 시작됩니다.
75
74
  시스템 서비스는 선택적인 WebUI 및 자동 시작용입니다.
76
75
 
77
- `/cadence-inspect`: legacy task/history UI.
76
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
77
+ See [History and diagnostics](docs/history.md).
78
78
  [Conversation mode](docs/conversation-mode.md): native/browser approval, limits and worktree setup.
79
79
  Browser authentication is not execution consent.
80
80
 
@@ -91,14 +91,8 @@ WebUI 폴더 선택기도 같은 방법으로 프로젝트를 엽니다.
91
91
 
92
92
  ### 체크
93
93
 
94
- `.cadence/assistant/config.json`에 프로젝트를 검증하는 명령을 나열하면, 작업은 검토 전에 그것들을 실제 체크로 실행할 수 있습니다:
95
-
96
- ```json
97
- {
98
- "schema": "cadence-assistant-checks/1",
99
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
100
- }
101
- ```
94
+ 기준 검사와 인수 검사의 명령은 명시적으로 승인하는 계획에 포함됩니다.
95
+ 실제 검사 결과는 자동 Agent 검토와 별도로 기록됩니다.
102
96
 
103
97
  ## 서비스 관리
104
98
 
package/README.md CHANGED
@@ -4,7 +4,7 @@
4
4
 
5
5
  Cadence turns [Pi](https://www.npmjs.com/package/@earendil-works/pi-coding-agent) into a conversation-driven engineering workflow.
6
6
  Enter `/cadence [goal]`, align the plan through conversation, then let the persistent owner implement and verify it.
7
- The optional WebUI supports the same persistent conversation workflow without a live Pi terminal, alongside ordinary chat and explicitly labelled legacy tasks.
7
+ The optional WebUI supports the same persistent conversation workflow without a live Pi terminal, alongside ordinary chat and readonly retained history.
8
8
 
9
9
  ## Why Cadence
10
10
 
@@ -46,11 +46,9 @@ The port and token live in `~/.pi/agent/cadence/.env`; anyone with the token can
46
46
  3. Send `/cadence [goal]` once to enter Cadence in this conversation; continue with normal messages to investigate and clarify requirements.
47
47
  4. Review the complete inline plan and click **Implement this plan** (or send `按计划实施`).
48
48
  The owner implements, verifies, repairs within budget and delivers as approved.
49
- 5. Follow actual progress, subagent transcripts and local merge results in the conversation.
49
+ 5. Follow actual progress and local merge results in the conversation; open any subagent's full context from the lower-left **Subagents** dock.
50
50
  Refresh and completion keep Cadence on; **Exit Cadence** only exits the mode, while **Cancel workflow — request stop** requests cancellation.
51
51
 
52
- **Legacy task** retains the old create/plan/Save/Start/check/human-Review route explicitly.
53
-
54
52
  ### In the terminal
55
53
 
56
54
  Enter `/cadence <goal>` once in any trusted project's Pi conversation.
@@ -65,7 +63,8 @@ Native use starts/reuses a local project owner on demand, without installing a s
65
63
  Model preferences are remembered in `~/.pi/agent/cadence/settings.json`; authentication stays with Pi.
66
64
 
67
65
  See [Conversation mode](docs/conversation-mode.md) for exact approval, worktree prerequisites and cancellation.
68
- `/cadence-inspect` retains the advanced legacy task/history UI, including separate checks and human review; it is not the daily entrypoint.
66
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
67
+ See [History and diagnostics](docs/history.md).
69
68
  Browser approval is separately bound to the displayed plan and conversation; authentication alone never authorizes execution.
70
69
 
71
70
  ### More projects
@@ -80,15 +79,8 @@ Opening another project never stops work in the previous one.
80
79
 
81
80
  ### Checks
82
81
 
83
- New workflows declare their checks in the approved plan.
84
- For legacy tasks, list configured checks in `.cadence/assistant/config.json`:
85
-
86
- ```json
87
- {
88
- "schema": "cadence-assistant-checks/1",
89
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
90
- }
91
- ```
82
+ Checks are declared in the exact plan you approve, including baseline and acceptance commands.
83
+ Their actual outcomes remain separate from automatic Agent review.
92
84
 
93
85
  ## Manage the service
94
86
 
package/README.pt-BR.md CHANGED
@@ -45,11 +45,10 @@ A porta e o token ficam em `~/.pi/agent/cadence/.env`; qualquer pessoa com o tok
45
45
  Esta conversa permanece no modo Cadence; esclareça os requisitos com mensagens normais.
46
46
  4. Revise o plano completo e clique em **Implement this plan**.
47
47
  Implementação, verificações, reparos limitados e entrega local acordada são automáticos.
48
- 5. Acompanhe o progresso e os registros dos subagentes na conversa.
48
+ 5. Acompanhe o progresso na conversa; abra os registros dos subagentes no painel **Subagents**, no canto inferior esquerdo.
49
49
  Atualizar a página ou concluir um objetivo não desativa o modo.
50
50
  **Exit Cadence** sai do modo; **Cancel workflow — request stop** solicita o cancelamento.
51
51
 
52
- **Legacy task**: previous task/history workflow.
53
52
  No live Pi terminal is required for the browser conversation workflow.
54
53
 
55
54
  ### No terminal
@@ -64,7 +63,8 @@ As preferências de modelo são mantidas entre projetos em `~/.pi/agent/cadence/
64
63
 
65
64
  O proprietário local inicia sob demanda; o serviço do sistema é opcional para WebUI/inicialização automática.
66
65
 
67
- `/cadence-inspect`: legacy task/history UI.
66
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
67
+ See [History and diagnostics](docs/history.md).
68
68
  [Conversation mode](docs/conversation-mode.md): native/browser approval, limits and worktree setup.
69
69
  Browser authentication is not execution consent.
70
70
 
@@ -80,14 +80,8 @@ Abrir outro projeto nunca interrompe o trabalho no anterior.
80
80
 
81
81
  ### Verificações
82
82
 
83
- Liste os comandos que verificam seu projeto em `.cadence/assistant/config.json`, e as tarefas podem executá-los como verificações reais antes da revisão:
84
-
85
- ```json
86
- {
87
- "schema": "cadence-assistant-checks/1",
88
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
89
- }
90
- ```
83
+ Os comandos de verificação constam do plano aprovado, incluindo verificações iniciais e de aceitação.
84
+ Os resultados reais permanecem separados da revisão automática do agente.
91
85
 
92
86
  ## Gerenciar o serviço
93
87
 
package/README.ru.md CHANGED
@@ -45,11 +45,10 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
45
45
  Разговор остаётся в режиме Cadence; уточняйте требования обычными сообщениями.
46
46
  4. Проверьте полный план и нажмите **Implement this plan**.
47
47
  Реализация, проверки, ограниченные исправления и согласованная локальная интеграция выполняются автоматически.
48
- 5. Следите за ходом работы и записями субагентов в разговоре.
48
+ 5. Следите за ходом работы в разговоре; записи субагентов открываются из панели **Subagents** слева внизу.
49
49
  Обновление страницы и завершение цели не выключают режим.
50
50
  **Exit Cadence** выходит из режима; **Cancel workflow — request stop** запрашивает отмену работы.
51
51
 
52
- **Legacy task**: previous task/history workflow.
53
52
  No live Pi terminal is required for the browser conversation workflow.
54
53
 
55
54
  ### В терминале
@@ -64,7 +63,8 @@ Cadence исследует проект, уточняет решения и со
64
63
 
65
64
  Локальный владелец запускается по требованию; системная служба нужна только для дополнительного WebUI и автозапуска.
66
65
 
67
- `/cadence-inspect`: legacy task/history UI.
66
+ `/cadence-history [run-id]`: readonly run details and retained history; no service startup or task execution.
67
+ See [History and diagnostics](docs/history.md).
68
68
  [Conversation mode](docs/conversation-mode.md): native/browser approval, limits and worktree setup.
69
69
  Browser authentication is not execution consent.
70
70
 
@@ -80,14 +80,8 @@ cadence project open /absolute/new-project --create
80
80
 
81
81
  ### Проверки
82
82
 
83
- Перечислите команды, которые проверяют ваш проект, в `.cadence/assistant/config.json`, и задачи могут выполнять их как реальные проверки перед обзором:
84
-
85
- ```json
86
- {
87
- "schema": "cadence-assistant-checks/1",
88
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
89
- }
90
- ```
83
+ Команды исходных и приёмочных проверок указываются в явно одобренном плане.
84
+ Их фактические результаты отделены от автоматической проверки агентом.
91
85
 
92
86
  ## Управление службой
93
87
 
package/README.zh-CN.md CHANGED
@@ -44,11 +44,9 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
44
44
  3. 输入一次 `/cadence [目标]`,当前对话进入持续 Cadence 模式;之后正常对话,调查项目并反复澄清需求。
45
45
  4. 查看完整计划,点击**按此计划实施**或发送 `按计划实施`。
46
46
  后台自动实施、检查、有限修复,并按计划完成本地交付。
47
- 5. 在同一对话查看真实进度、子代理记录和合并结果。
47
+ 5. 在同一对话查看真实进度和合并结果;子代理的完整上下文从左下角**子代理**面板打开。
48
48
  刷新、完成目标后仍保持 Cadence;**退出 Cadence**不取消后台工作,**取消工作流 — 请求停止**才请求取消。
49
49
 
50
- “旧版任务”入口明确保留原有创建任务、Save/Start、独立检查和人工 Review 路径。
51
-
52
50
  ### 在终端中:一次进入,持续对话
53
51
 
54
52
  在任意已信任项目的 Pi 对话里输入一次 `/cadence <目标>`,之后正常对话即可。
@@ -66,7 +64,8 @@ Cadence 自动调查仓库、汇总需要你决定的问题,并与你反复对
66
64
  项目知识维护在 `.cadence/project.md`;隔离 worktree 不会自动复制依赖或凭据,必要的准备命令会列入计划确认。
67
65
 
68
66
  详细边界见 [对话模式](docs/conversation-mode.md)。
69
- 旧高级检查入口保留为 `/cadence-inspect`,不再作为日常流程。
67
+ `/cadence-history [运行 ID]` 提供只读诊断、运行详情和已有任务历史,不创建或执行任务,也不启动服务。
68
+ 见[历史与诊断](docs/history.md)。
70
69
  浏览器批准与所展示的计划、会话和访问身份绑定;登录本身不是执行授权。
71
70
 
72
71
  ### 更多项目
@@ -81,15 +80,8 @@ cadence project open /absolute/new-project --create
81
80
 
82
81
  ### 检查
83
82
 
84
- 新工作流的检查命令在批准的计划中明确列出。
85
- 旧版任务可以在 `.cadence/assistant/config.json` 中配置检查:
86
-
87
- ```json
88
- {
89
- "schema": "cadence-assistant-checks/1",
90
- "checks": [{ "name": "Tests", "command": "bun run test", "timeoutMs": 120000 }]
91
- }
92
- ```
83
+ 检查命令在你批准的具体计划中列出,包括基线检查和验收检查。
84
+ 真实检查结果与自动 Agent 审查保持独立。
93
85
 
94
86
  ## 管理服务
95
87
 
@@ -3,7 +3,7 @@
3
3
  In a trusted Pi terminal or a WebUI conversation in an explicitly selected project, enter `/cadence <goal>` once (or `/cadence` to discuss the goal).
4
4
  Cadence stays enabled for the entire conversation, including after a goal finishes.
5
5
  Continue using normal messages; do not repeat the command for clarification or another goal.
6
- Type `退出 Cadence` or `exit cadence` to leave the mode explicitly.
6
+ Type `退出 Cadence` or `exit cadence` (in Pi also `/cadence exit`) to leave the mode explicitly.
7
7
  Leaving, closing Pi/browser and switching conversations detach; they do not cancel accepted work.
8
8
  Browser conversation mode is retained by the project owner, not by a browser-only toggle, and works without a live Pi terminal.
9
9
 
@@ -23,6 +23,8 @@ Browser conversation mode is retained by the project owner, not by a browser-onl
23
23
  Ask for status, more detail, cancellation, or the next goal normally.
24
24
 
25
25
  Native mode is branch-aware; browser mode follows its server-owned conversation identity.
26
+ 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`.
27
+ In Pi, the agent panel lists workflow subagents and opens their transcripts; `cadence_status` can read one step's transcript.
26
28
  Resume and compaction retain the mode/context, not execution grants.
27
29
  Opening a different conversation does not enable Cadence there.
28
30
  Restore never replays a command or automatically resumes an interrupted queue.
@@ -34,7 +36,7 @@ The first native use defaults to the current Pi provider/model/API/thinking sele
34
36
  The selected preference is remembered in `<agent-dir>/cadence/settings.json` (normally `~/.pi/agent/cadence/settings.json`) and reused across projects.
35
37
  Ask Cadence to change its model in Pi, or use **Model** in the browser.
36
38
  The browser restores an available saved preference on explicit Send; reads/login do not install a choice.
37
- If no usable preference exists, choose once.
39
+ If no usable preference exists, choose once; an unreadable preference file falls back to the current Pi model, and choosing a model rewrites it.
38
40
  An accepted run keeps its original exact model.
39
41
  An unavailable remembered model is not silently substituted.
40
42
  Pi's original model and authentication sources remain authoritative; Cadence does not copy credentials.
@@ -63,11 +65,17 @@ The plan chooses one delivery policy:
63
65
  Failed or canceled work leaves actual edits in place; this is not transactional application or a sandbox.
64
66
 
65
67
  A local-merge plan does not adopt existing dirty inputs into its committed baseline.
66
- Dirty declared targets refuse before implementation; unrelated user changes are preserved and rechecked before integration.
68
+ Dirty declared targets refuse before implementation; unrelated user changes made during a run are preserved and do not block integration (Git refuses a genuine overlap).
69
+ A write path naming a directory covers the files below it; in Git, working-copy edits outside the declared writes fail the run (the edits stay).
67
70
  Unresolved conflicts or a changed target stop integration.
68
71
  Cadence never resets, stashes, force-pushes or silently cleans uncertain worktrees.
69
72
  Ignored generated Markdown remains ignored and is published without forcing it into Git.
70
- Worktrees and all results are retained; there is no automatic eviction/cleanup.
73
+ Clean worktrees are removed after a successful merge (plain `git worktree remove`, which also deletes their ignored setup output such as `node_modules`); dirty or moved ones and all results are retained.
74
+ Only one approved implementation runs at a time; approving a second while one is active is refused with `conflict`.
75
+ The 90-minute budget starts when the run acquires the checkout; Cancel/Stop never interrupt the final fast-forward (a hung `git merge` therefore delays Stop until Git exits).
76
+ Local-merge plans cannot declare files that Git ignores; use working-copy delivery for those.
77
+ After an owner restart, an unfinished run is shown as `unknown` with its retained worktrees; it is never resumed.
78
+ Credential-looking text in plans and research questions is shown and approved redacted.
71
79
 
72
80
  An isolated worktree does **not** inherit ignored `node_modules`, build output, credentials or profiles.
73
81
  Investigate prerequisites during planning.
@@ -80,7 +88,7 @@ Final candidate checks must pass before merge.
80
88
  Post-merge failures remain failures and report the actual merge commit; no rollback is fabricated.
81
89
  Automatic review is never recorded as human review.
82
90
 
83
- Ask to cancel to request orderly closure.
91
+ To request orderly closure, ask Cadence to cancel in Pi, or use **Cancel workflow — request stop** in the browser (the browser coordinator cannot cancel).
84
92
  A pending or unknown cancellation is not reported as stopped.
85
93
  Failures, timeouts and unknown process/auth/storage outcomes remain distinct; unknown resources retain fences for explicit informed recovery.
86
94
 
@@ -88,14 +96,17 @@ Failures, timeouts and unknown process/auth/storage outcomes remain distinct; un
88
96
 
89
97
  An explicit native mode entry/current user Send may start or reuse its local project owner on demand.
90
98
  It does not install a system service, enable boot startup, select another account's credentials or expose a public listener.
99
+ Pi says once which command stops an owner it started; when Pi runs on Bun, Node must be on `PATH`.
91
100
  An existing owner/configuration is reused, not silently replaced after a connection failure.
92
101
  System-service installation and remote access remain separate explicit operations described in [Service management](service-management.md) and [Remote access](remote-access.md).
93
102
 
94
- `/cadence-inspect` retains the previous advanced task/history UI for diagnostics and legacy workflows; it is not needed for conversation mode.
103
+ `/cadence-history [run-id]` provides readonly diagnostics without model calls or service startup; see [History and diagnostics](history.md).
95
104
  The WebUI uses the same execution engine with a separate, context-bound browser confirmation path.
96
- Its main composer stays in the same conversation; plan, workflow progress, retained step results and actual merge outcomes appear inline.
97
- The background-workflow observer includes native-started workflows; an unavailable observation is not proof of no work.
98
- **Legacy task** retains the old create/plan/Save/Start/check/human-Review route explicitly, rather than making `/cadence` create a legacy task.
105
+ Its main composer stays in the same conversation; the plan card, workflow progress and actual merge outcomes appear inline.
106
+ 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.
107
+ 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.
108
+ The old task creation/Save/Start/check/human-Review controls are retired on both clients and refused by the service.
109
+ Existing task records remain readonly; they are not converted into workflows.
99
110
  Existing browser conversations enter the new mode only on explicit Send/activation; old tasks and Pi transcripts are not converted or imported.
100
111
  Approval grants are neither stored in the browser nor restored after restart.
101
112
  Losing a response only observes its original command/run identity; it never retries execution.
@@ -0,0 +1,50 @@
1
+ # History and diagnostics
2
+
3
+ Cadence has one engineering execution path: enter `/cadence`, discuss a goal and approve the exact plan.
4
+ History is evidence, not a second task manager or renewed execution consent.
5
+
6
+ ## Current workflows
7
+
8
+ - In the conversation, open a workflow's steps to see actual checks, Agent review, delivery and failures.
9
+ **Open subagent context** shows the retained transcript; **Read retained step result** reads the retained result rather than its clipped status preview.
10
+ - In the browser sidebar, expand **Workflow history** to find retained runs, including completed native-started work.
11
+ The listing is paged in ID order, not chronological order.
12
+ Larger histories show scan progress before a complete page; use **Continue reading history** in the browser or **Continue scanning** in Pi.
13
+ An expired scan requires a fresh observation; it never deletes history or resumes execution.
14
+ A new run may appear before a page you already read; return to the first page and refresh to observe it.
15
+ An unreadable record stays visibly unavailable rather than disappearing or being repaired.
16
+ - In a trusted Pi terminal, `/cadence-history` lists workflows without asking a model.
17
+ `/cadence-history <run-id>` opens one exact run directly.
18
+ Use **Full result** or **Subagent transcript** for step evidence, and the arrow/page/Home/End keys to read long text.
19
+
20
+ The native history command only attaches to an already-running project owner; it never starts a service, selects a model, approves work, executes tools or cancels a run.
21
+ It remains usable without a selected model.
22
+ If no owner is available, use the explicit service commands in [Service management](service-management.md).
23
+ Known omitted or truncated source content is still omitted or truncated; viewing a full retained result cannot recreate unrecorded data.
24
+ Automatic Agent review is never human review, and a check's actual exit is independent of model prose.
25
+
26
+ ## Existing task archives
27
+
28
+ The old `/cadence-inspect` interface and browser **Legacy task** creation route are removed.
29
+ Old create, Save, Generate, Start, check and human-Review requests are refused by the service, including from stale clients.
30
+ There is no feature flag to re-enable them.
31
+
32
+ Existing task summaries, private history and task-to-conversation links are preserved without migration, reset or cleanup.
33
+ Use **Retained task history** in `/cadence-history`, or select a retained task in the browser:
34
+
35
+ - Read recorded plans, runs, children, checks, changes and human Review evidence.
36
+ - Search the selected task/run/child scope with exact, case-sensitive literal search.
37
+ - Export that scope as Markdown or NDJSON.
38
+ Native export requires an explicitly confirmed new destination and verifies the complete stream, digest, trailer and EOF.
39
+ A browser download request alone is not proof that the download completed.
40
+
41
+ These task search/export formats do not apply to the separate workflow store; current workflows provide retained run/step results and transcripts instead.
42
+ A historical record cannot restart work or confer approval.
43
+
44
+ ## Cancellation and uncertain outcomes
45
+
46
+ Leaving history, switching conversations/projects or closing a client only detaches.
47
+ For current work, use the conversation's explicit Cancel workflow action or ask Cadence to cancel in Pi.
48
+ Archived task IDs are not current process handles and cannot be canceled through the retired task API.
49
+ Orderly Stop of the exact running owner remains available separately; an older running owner must be stopped before switching implementations.
50
+ No history read clears locks, repairs uncertain state, retries execution or infers that missing observations mean work has stopped.
@@ -113,7 +113,7 @@ For an explicit single-project definition, the older guards remain: no SDK means
113
113
 
114
114
  While no service is registered, Pi's session-start card shows a separate warning naming `cadence server install` for an installed package copy (`node <copy>/src/service-cli.mjs server install` for Pi's managed copy, which puts no bin on `PATH`); a checkout loaded with `pi -e` stays quiet.
115
115
  It is a warning rather than part of the info card because Pi's TUI replaces one info status with the next.
116
- The legacy `/cadence-inspect` client names the same management command when no owner exists; daily `/cadence` instead uses explicit on-demand project startup, without requiring a boot service.
116
+ The readonly `/cadence-history` client names the same management command when no owner exists; daily `/cadence` instead uses explicit on-demand project startup, without requiring a boot service.
117
117
  A machine without a supported user service manager and `CADENCE_AUTOSTART=0` keep both quiet; with `CADENCE_LINGER=0` they suggest `--no-linger`.
118
118
 
119
119
  ### One copy for Pi and the service
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@abelxiaoxing/cadence",
3
- "version": "2.0.21",
3
+ "version": "2.0.23",
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",
@@ -27,7 +27,6 @@
27
27
  "src/native-export.ts",
28
28
  "src/native-history.ts",
29
29
  "src/operator-cli.mjs",
30
- "src/plan-proposal.ts",
31
30
  "src/sdk-worker.mjs",
32
31
  "src/service-cli.mjs",
33
32
  "src/service-client.ts",
@@ -47,9 +46,8 @@
47
46
  "src/service/coordination.ts",
48
47
  "src/service/private-files.ts",
49
48
  "src/startup-card.ts",
50
- "src/task-shell.ts",
51
- "src/task-store.ts",
52
- "src/task-types.ts",
49
+ "src/history-shell.ts",
50
+ "src/native-workflow-history.ts",
53
51
  "src/verification-diagnostics.ts",
54
52
  "src/worker-capture.mjs",
55
53
  "src/worker-public.mjs",
@@ -76,7 +74,10 @@
76
74
  "src/cadence-preferences.ts",
77
75
  "src/service/contracts/workflow.ts",
78
76
  "src/cadence-instructions.ts",
79
- "src/coordinator-tools.mjs"
77
+ "src/coordinator-tools.mjs",
78
+ "src/workspace.ts",
79
+ "src/data-shapes.ts",
80
+ "src/service/checkout-lock.ts"
80
81
  ],
81
82
  "pi": {
82
83
  "extensions": [
@@ -100,7 +101,7 @@
100
101
  "build:operator": "bun scripts/build-operator.mjs",
101
102
  "build:service": "bun scripts/build-service.mjs",
102
103
  "check:web": "tsc -p web/tsconfig.json && tsc -p web/tsconfig.config.json",
103
- "test:web": "node --test test/web/task-entry.node.mjs && vitest run --config web/vitest.config.ts",
104
+ "test:web": "vitest run --config web/vitest.config.ts",
104
105
  "build:web": "node scripts/build-web.mjs",
105
106
  "build:web:check": "node scripts/build-web.mjs --check",
106
107
  "test:web:assets-browser": "bun run test:browser",