@abelxiaoxing/cadence 2.2.6 → 2.2.7

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.
@@ -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` (in Pi also `/cadence exit`) to leave the mode explicitly; in the browser the composer's **Cadence mode** switch enters it on the next Send and leaves it when on.
6
+ Type `退出 Cadence` or `exit cadence` (in Pi also `/cadence exit`) to leave the mode explicitly; in the browser the mode switch beside **Send** enters it on the next Send and leaves it when on.
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
 
@@ -13,12 +13,19 @@ Browser conversation mode is retained by the project owner, not by a browser-onl
13
13
  2. Discuss requirements and decisions until nothing that changes the result is left open.
14
14
  This is the last time you are asked: what Cadence decides on your behalf is listed in the agreement as its assumptions.
15
15
  3. Cadence presents one readable delivery agreement: expected result, acceptance, decisions, assumptions, the initial route and write scope, setup/check commands, documents to update and delivery policy.
16
+ In the browser, use **View current plan** beside the conversation title.
17
+ The proposal stays in this conversation; you can keep discussing it and reopen it there, including after refresh.
18
+ Open **Technical details** for paths, commands, the exact binding and agreement.
19
+ Opening or closing the proposal does not validate or approve it.
16
20
  The technical route is an initial suggestion.
17
21
  After approval the service finishes on its own: it repairs and re-plans, may bring further files of the repository into the write scope (never credentials, keys, `.env`, `.git` or anything outside the repository), and installs dependencies only if the agreement says revisions may.
18
22
  If an acceptance item proves impossible it delivers the closest achievable result and records the deviation: what could not be met, why, what was delivered instead and any declared check set aside because of it.
19
23
  The automatic review must confirm each deviation, and a run that deviated says so first when it completes; the task branch is kept, so the merge can be undone.
20
24
  4. Type `按计划实施` after the plan to authorize those exact bytes.
21
- In the browser, click **Implement this plan** or send that exact approval phrase for the currently displayed plan.
25
+ In the browser, review the proposal from the conversation title, then click **Implement this plan** or enter and send the exact approval phrase.
26
+ The phrase belongs to the proposal and context you reviewed.
27
+ If either changes, or a reload restores only the text, the old phrase stays in the editor: it neither approves nor sends a message.
28
+ Opening the new proposal does not transfer that approval; use its button or enter the phrase anew.
22
29
  If execution is stopped or its plan binding is outdated, this first restores and validates the plan instead; review the updated context and choose **Confirm implementation** afterward (see below).
23
30
  In Pi, the Start tool can alternatively present one native confirmation of the complete plan.
24
31
  Native confirmation retains its raw-terminal guard.
@@ -47,6 +54,7 @@ When an observation reply is lost, ask for status; do not infer that the action
47
54
  ## Restore a saved plan without sending a message
48
55
 
49
56
  A stopped or restarted execution service does not require another discussion or a model-generated replacement plan.
57
+ **View current plan** shows the conversation's current proposal even when you are reading an older branch; return to the latest branch to validate or approve it.
50
58
  Use **Restore execution and validate plan** on the plan card; if the service is already running, **Validate plan again** refreshes its execution context.
51
59
  The exact `按计划实施` input follows the same validation path when the service or model binding is not current.
52
60
 
@@ -54,7 +62,7 @@ Validation may start or reuse the selected project's owner and applies the model
54
62
  It keeps the plan content, records a fresh execution binding and leaves the original snapshot intact.
55
63
  It sends no chat message, calls no model, creates no task branch/worktree and approves no implementation.
56
64
  Review the displayed model, runtime and target branch/base; changed environment evidence is labelled, and this tab also shows the previous context for comparison.
57
- Then click **Confirm implementation** or send the approval phrase again to approve that fresh snapshot.
65
+ Then click **Confirm implementation** or enter a fresh approval phrase for the revalidated proposal.
58
66
  A current plan remains directly approvable; validation is not an extra step for every ordinary approval.
59
67
 
60
68
  An unknown turn outcome, unreadable plan, changed conversation or unavailable selected model still blocks safely.
@@ -310,7 +318,9 @@ A revision may also change the assignments that have not started yet (drop, rewr
310
318
  The unified WebUI sidebar automatically lists active work in this account and state home, including projects you have never selected.
311
319
  An interactive terminal must load the Cadence extension: a real model/tool round appears even without `/cadence`, but an idle terminal or idle owner does not.
312
320
  Terminal rounds are observe-only; owner turns and workflows show their actual phases (including ordinary turn startup and workflow queueing) and existing authorized controls.
313
- Separate terminal instances and owner work keep their own rows; work already shown under **Running work** is not repeated.
321
+ In the selected project, a conversation with a live reply or linked workflow stays at the front of history.
322
+ Its workflow disclosure names each run; work without a reliable conversation link has a separate details entry.
323
+ Readonly discovery still distinguishes separate terminal instances and does not repeat owner work already represented here.
314
324
 
315
325
  Click an activity to remember its directory and read the shared Pi session at the observed branch.
316
326
  This does not start or associate an owner, grant execution consent or expand workbench Stop.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@abelxiaoxing/cadence",
3
- "version": "2.2.6",
3
+ "version": "2.2.7",
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",
@@ -36181,7 +36181,7 @@ function workflowResultDetail(value, secrets) {
36181
36181
  var runtimeSummary = (runtime) => `${describeWorkerRuntime(runtime)}
36182
36182
  ${RUN_ENVIRONMENT_POLICY}`;
36183
36183
  var OWNER_RUNTIME = Object.freeze({
36184
- version: "2.2.6",
36184
+ version: "2.2.7",
36185
36185
  build: "eb12cb5795f0345121f4d0e51627a15027dc2ba685fe5b8f6eb942f3c68c62d9",
36186
36186
  entry: fileURLToPath7(import.meta.url),
36187
36187
  pid: process.pid,