axstack 0.49.0 → 0.49.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.49.0",
+  "version": "0.49.1",
   "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/contracts.md

@@ -121,6 +121,7 @@ Never advise spec approval, npm stage approval or collaborator approval.
 Never advise access or credentials.
 Never advise forge merges by the user.
 Never advise `Auto-merge: off`.
+Never advise risky-path holds.
 Never advise work-promotion, deploying-base or unknown-base report cards.
 Never advise the report-only comment-rating card.
 Never advise model unavailability or substitution.

package/skills/axstack-watch/references/escalation.md

@@ -8,7 +8,8 @@ and a counted collaborator approval exists, on an `integration` base.
 Work promotion PRs and `deploying` or unknown bases are merged by the user on
 the forge. The existing serious-risk hold applies at once to both personal and
 work PRs.
-Personal and work PRs remain eligible whatever files they change, including
+Personal and work PRs remain eligible whatever files they change, subject to the
+[risky-path hold](readiness.md#5-state-readiness-precisely), including
 `.github/`, workflow-invoked files, package.json, lockfiles, test-runner config,
 branch-protection or ruleset config, `CODEOWNERS`, `AGENTS.md`, and non-clean
 revert lines such as `Revert: steps`.
@@ -30,15 +31,18 @@ at line start in the PR description.
 A quoted format inside a bullet never counts as the declaration.
 `--admin` and rule bypass are never used.
 `Auto-merge: off` for a run or PR makes the merge card wait, and it waits for the user.
+A risky-path hold blocks automatic merge.
 
-Post a merge card for every nonqualifying approval, base, verification, or off case.
+Post a merge card for every nonqualifying approval, base, verification, off,
+or risky-path case.
 Follow [Advised holds](../../axstack/references/contracts.md#advised-holds) for eligible merge-card causes.
 Bind it to the PR head and base SHA; list CI, authored review and diligence at
 those SHAs, counted collaborator approvals and bot votes with each vote's SHA
 and stale flag, and the causes holding this merge.
-A card that needs the user's decision (work promotion or work deploying/unknown base,
-`Auto-merge: off`, provenance, or an unclosable verification gap) is a decision
-hold raised in the T3 driver thread; the driver ends its turn parked on the decision.
+A card that needs the user's decision (work promotion or work deploying/unknown
+base, `Auto-merge: off`, risky-path, provenance, or an unclosable verification gap)
+is a decision hold raised in the T3 driver thread, and the driver ends its turn
+parked on the decision.
 Revalidate the current head and base; the reply clears only its bound cause.
 Person-wait cards follow the clock below.
 A changed head or base requires a refreshed card.
@@ -46,6 +50,9 @@ For an own PR on an `integration` base, the user's reply to the card authorizes
 the merge actor to merge under the guarded path, subject to the exceptions below.
 In `solo` mode the user's merge-card reply authorizes the guarded merge of
 user-written PRs or PRs with unknown or mixed provenance.
+Only an explicit user "merge this" for this PR at the exact head and base SHA
+clears the risky-path hold and authorizes the merge actor under the guarded path.
+A new head or base re-applies the hold.
 In `team` mode a reply never replaces counted collaborator approval.
 A reply can clear auto-merge turned off; verification acceptance follows the
 head-and-base-bound rule above. It never clears an ineligible work base or a

package/skills/axstack-watch/references/readiness.md

@@ -47,8 +47,14 @@ For each current head and base SHA, every merge-ready term must hold:
   Reviews carrying an Axstack automation marker never count.
   A later `CHANGES_REQUESTED` blocks until resolved; a stale or dismissed
   approval does not count.
-  A collaborator approval carries over only across a rebase, base-update merge or base-only retarget with unchanged
-  patch-id recorded for both heads while the forge still counts it.
+  A collaborator approval carries over only across a rebase, base-update merge or
+  base-only retarget with unchanged patch-id recorded for both heads, or to a new
+  head made by repairs addressing review feedback (that reviewer's comments,
+  other review threads, authored-review or diligence findings, or CI fixes),
+  while the forge still counts it.
+  Carryover requires an undismissed approval, no later `CHANGES_REQUESTED` from
+  that reviewer, and repository rules that require neither last-push approval
+  nor stale-review dismissal.
   Require fresh authored review, diligence, and CI on every new head.
   Refresh authored review, diligence and CI evidence at the current head and base after every head or base change; base updates return to the same author under the existing repair route.
   Text carrying a visible machine marker never counts as a user reply:
@@ -77,6 +83,11 @@ For each current head and base SHA, every merge-ready term must hold:
   evidence instead.
 - Proven verification: apply every receipt and acceptance term below, or its
   head-and-base-bound user acceptance, while every other gate still holds.
+- Risky paths: `merge-base..head` touches none of database migrations,
+  auth/authentication code, secrets or credential config, money/funds-moving
+  paths, or production deploy config, or a head-and-base-bound user clearance
+  under [Escalation](escalation.md) applies.
+  An uncertain risky-path classification holds automatic merge.
 - Veto: no `do-not-merge` label and no chat `hold` applies.
 
 Only comments and threads whose IDs are recorded in an agent receipt count as agent-authored.