axstack 0.27.3 → 0.27.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.27.3",
+  "version": "0.27.4",
   "description": "Axstack installer and setup CLI: installs owned chat skills and role data, configures supported harness settings, and checks T3 Code capabilities.",
   "keywords": [
     "claude-code",

package/skills/axstack/references/run-record.md

@@ -43,8 +43,9 @@ or a receipt pointer containing both; a role label alone is insufficient.
 The recorded owning watch thread merges under the
 [watch predicate](../../axstack-watch/SKILL.md#5-state-readiness-precisely).
 
-Read the [T3 runtime boundary](t3-runtime.md) for native identity and receipt checks.
+Read the [T3 runtime boundary](t3-runtime.md) for native identity, reference freshness and receipt checks.
 Record driver threadId, projectId, host, T3 version, installed Axstack SHA,
+installed Axstack version and last reference read time,
 capabilities JSON path and scheduledTaskIds for every watch and manager schedule.
 Per dispatch record key, mechanism, requested target and read-back,
 taskId/childThreadId/childRunId or threadId/runId/worktree/branch/base SHA,
@@ -190,7 +191,7 @@ PR digest watermarks: <repo -> absolute path of its per-repository JSON file ins
 Release: <AGENTS.md file:line + tag-triggered workflow path + named install hosts> | not applicable (<reason>)
 Source base: <exact revision or source identity>
 IDs: <projectId + driver threadId/runId + dispatch identity receipt pointers>
-Runtime: <host + T3 version + installed Axstack SHA + capabilities JSON path>
+Runtime: <host + T3 version + installed Axstack SHA + installed Axstack version/check time + last reference read time + capabilities JSON path>
 Schedules: <scheduledTaskIds of every watch and manager schedule>
 Watch: <member publication/adoption receipts + cadence + last PR event + native lifetime + update/re-arm/stop receipts>
 Worktrees in other repositories: <per-run repository and worktree IDs or none>

package/skills/axstack/references/t3-runtime.md

@@ -6,6 +6,18 @@ delegated tasks, messaging and native schedules.
 
 ## Preflight and binding
 
+At every run start, resume and run-watch wake, the driver must run
+`axstack --version` and record the installed Axstack version and check time
+in the run record.
+When this run lacks a reference read or the installed version differs from
+the version recorded at the last reference read, the driver must re-read
+the installed phase SKILL.md and every shared reference it will use before any
+dispatch, receipt consumption, settlement or merge.
+After re-reading, the driver must record the installed version and reference
+read time in the run record.
+The driver must never rely on an in-context copy from an earlier run or an
+older installed version.
+
 The driver must be a T3 thread, save `orchestrator_capabilities` JSON under
 the run record, and follow the advertised tool schema; discovery alone proves
 neither provider readiness nor successful execution. Missing capability holds

package/skills/axstack/references/workspace-hygiene.md

@@ -35,7 +35,9 @@ Cleanup order is: settled descendants -> evidence readback -> salvage dirty or i
 Require terminal run evidence before `t3_thread_organize` settle or archive.
 These metadata actions do not remove worktrees. Accept matching delegated task
 or launched run completion under the runtime contract before settlement.
-After the driver accepts a launched writer's or delegated task's completion from terminal run evidence plus a verified receipt or candidate check, it settles the matching thread with `t3_thread_organize` as metadata only.
+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.
+The driver reads back `settled: true` with `t3_thread_read` on the writer thread for launched writers and on the `childThreadId` for delegated tasks.
+A missing or failed settle readback never triggers author repair: it holds only that dispatch's next advancement (publication, review routing, merge-ready) until resolved.
 Settling never removes, archives or abandons the thread or worktree.
 Retain the author worktree and thread unarchived until the PR merges or closes, with repairs returning to the same author.
 On forge-confirmed merge or closure, follow [Native PR links and watches](t3-runtime.md#native-pr-links-and-watches)