axstack 0.50.0 → 0.50.2
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "axstack",
|
|
3
|
-
"version": "0.50.
|
|
3
|
+
"version": "0.50.2",
|
|
4
4
|
"description": "Axstack installer and setup CLI: installs owned chat skills and role data, configures supported harness settings, and checks T3 Code capabilities.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"claude-code",
|
|
@@ -387,7 +387,7 @@ Only prior passes that no guard keeps unsettled enter unresolved recovery.
|
|
|
387
387
|
A guard includes a hold or flag, an owned watch, unsettled descendants, a pending
|
|
388
388
|
receipt, a wedged pass or stalled owner, and every existing pass-start protection.
|
|
389
389
|
If a guard keeps a prior pass unsettled, drop it from the unresolved list and retain
|
|
390
|
-
|
|
390
|
+
any existing record, including non-terminal run evidence and user takeover.
|
|
391
391
|
Held or flagged prior passes never force a full pass or failure report by their unsettled state alone.
|
|
392
392
|
If the prior thread is unsettled and eligible, settle it under the existing pass-start guards
|
|
393
393
|
below and read back `settled: true`.
|
|
@@ -430,12 +430,14 @@ Retirement settles remaining predecessor, duplicate and failed-successor pass th
|
|
|
430
430
|
Unknown, active or user-taken-over threads,
|
|
431
431
|
ambiguous publication and failed salvage stay preserved.
|
|
432
432
|
|
|
433
|
-
A review-manager pass may retire a predecessor pass's local
|
|
434
|
-
|
|
433
|
+
A review-manager pass may retire a predecessor pass's local branch with exact
|
|
434
|
+
`git branch -D <branch>`; read its current branch name from the worktree before
|
|
435
|
+
removing it, regardless of branch name pattern; fetch origin before checking
|
|
436
|
+
ancestry; delete only when ALL hold: the predecessor pass is
|
|
435
437
|
settled and proven run/lane-owned by recorded identity, its descendants and
|
|
436
438
|
evidence are settled, no worktree has the branch checked out, no remote
|
|
437
439
|
counterpart exists, its tip equals the recorded tip, and its tip is an ancestor
|
|
438
|
-
of
|
|
440
|
+
of origin/main. Otherwise hold and record it in Open holds; all other `git branch -d`
|
|
439
441
|
rules remain unchanged.
|
|
440
442
|
|
|
441
443
|
Past the authorized storage limit (default 20 retained lane worktrees), disable the schedule
|
|
@@ -260,10 +260,10 @@ Before finishing PR work, including watch end or Close-out, the driver calls
|
|
|
260
260
|
Never link unrelated PRs.
|
|
261
261
|
|
|
262
262
|
Authors are never PR-linked: the driver alone links and watches the PR.
|
|
263
|
-
For delegated authors after accepted completion, in the same driver turn settle with
|
|
263
|
+
For delegated authors and launched fallback authors after accepted completion, in the same driver turn settle with
|
|
264
264
|
`t3_thread_organize` using `action: settle`, read back `settled: true` with `t3_thread_read`
|
|
265
265
|
and record `settle: manual` under the [Settlement](workspace-hygiene.md#settlement) guards.
|
|
266
|
-
For delegated authors, archive and guarded manual worktree removal wait for PR merge or close.
|
|
266
|
+
For delegated authors and launched fallback authors, archive and guarded manual worktree removal wait for PR merge or close.
|
|
267
267
|
Never rely on automatic child cleanup.
|
|
268
268
|
|
|
269
269
|
When the forge confirms a run PR merged or closed, in the same driver turn the
|
|
@@ -45,8 +45,8 @@ These metadata actions do not remove worktrees. Accept matching delegated task
|
|
|
45
45
|
or launched run completion under the runtime contract before settlement.
|
|
46
46
|
After the driver accepts a launched writer's (author or repair) or delegated task's completion from terminal run evidence plus a verified receipt or candidate check, in the same driver turn it settles the matching thread with `t3_thread_organize` using `action: settle` as metadata only.
|
|
47
47
|
The driver reads back `settled: true` with `t3_thread_read` on the writer thread for launched writers and on the `childThreadId` for delegated tasks.
|
|
48
|
-
For delegated authors after accepted completion, in the same driver turn settle with `t3_thread_organize` using `action: settle`, read back `settled: true` with `t3_thread_read` and record `settle: manual`.
|
|
49
|
-
For delegated authors, archive and guarded manual worktree removal wait for PR merge or close.
|
|
48
|
+
For delegated authors and launched fallback authors after accepted completion, in the same driver turn settle with `t3_thread_organize` using `action: settle`, read back `settled: true` with `t3_thread_read` and record `settle: manual`.
|
|
49
|
+
For delegated authors and launched fallback authors, archive and guarded manual worktree removal wait for PR merge or close.
|
|
50
50
|
Never rely on automatic child cleanup.
|
|
51
51
|
Delegated author threads stay hidden in the sidebar regardless of settlement; visibility statements below apply to launched writers.
|
|
52
52
|
This extends the existing same-turn settle rule: a pinned run-owned child is still settled.
|
|
@@ -46,7 +46,7 @@ rejected required seat holds Scout without substitution. The first dispatch
|
|
|
46
46
|
for each provider/model/effort must reach a running or completed run before
|
|
47
47
|
siblings launch, and its rejection stops siblings of that configuration.
|
|
48
48
|
|
|
49
|
-
|
|
49
|
+
Reconcile an uncertain dispatch natively before proceeding with Scout.
|
|
50
50
|
|
|
51
51
|
## 3. Pin evidence and report
|
|
52
52
|
|