axstack 0.25.2 → 0.25.3

package/docs/workflows.md

@@ -265,9 +265,13 @@ one theme and a measured size under the shared
 For own PRs, automatic merge is the default under the
 [watch predicate](../skills/axstack-watch/SKILL.md#5-state-readiness-precisely).
 Review approval alone never grants merge authority.
-For the rationale band, the autonomous driver records a cohesion rationale. The exception band
-requires a reasonable split attempt and full exception record. These are
-autonomous driver choices; size alone never requires user approval.
+Treat size flags as informational only.
+Size alone must never block review, reject a PR, require split attempts or
+cohesion/exception rationale, or hold approval.
+Review the actual footprint, complexity, and required context, incrementally when needed.
+Approval requires sufficient review coverage.
+Report INCOMPLETE when required coverage is missing.
+Shape choices remain autonomous driver decisions; size alone never requires user approval.
 
 ## Explicit handoff
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.25.2",
+  "version": "0.25.3",
   "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/pr-shape.md

@@ -12,16 +12,15 @@ Total additions + deletions over all files. Disclose moves detected by `-M`;
 report binaries by count and purpose, never estimated lines. Disclose generated,
 lockfile, and formatter-only bulk buckets alongside the total.
 
-The full total controls the level: ≤2000 is the target. The 2001–2500 rationale
-band requires only a recorded cohesion rationale, with no split-attempt record.
-The >2500 exception band requires the full exception record below. Bulk may
-support either rationale only with a reproducible recorded command. Never
-automatically subtract bulk or shift bands; silent exclusion is forbidden; no file-count hard metric.
+Flag totals above 2500 changed lines as informational only.
+Never automatically subtract bulk from the full total; silent exclusion is forbidden; no file-count hard metric.
+Disclose each bulk bucket with a reproducible recorded command.
+There is no universal safe LOC limit or fixed token percentage.
 
 ## Theme
 One behavior or component may include the callers, tests, types, docs, and
 migrations that must change together to stay green and reviewable.
-This is not a folder restriction. Unrelated themes split even under the target.
+This is not a folder restriction. Unrelated themes split regardless of size.
 Smaller cohesive PRs are encouraged; no padding.
 
 ## PR body
@@ -29,16 +28,13 @@ Smaller cohesive PRs are encouraged; no padding.
 Every own PR description must contain exactly one `Revert` line.
 Follow [Revert line](candidate-publication.md#revert-line) for its format and classification.
 
-## Exception band
-The driver attempts a reasonable split first. If each tried split materially
-compromises atomicity, green state, or independent reviewability, or inseparable
-reproducible bulk dominates, record and proceed autonomously within the approved
-spec. The mandatory record includes the full total, bulk buckets with their
-reproducible command, measured head and base, split attempts tried, and why each
-fails on atomicity, green state, or reviewability. “Already written,” deadlines,
-and rebase pain are not reasons.
-Size alone never requires user approval. Review verifies the measurement and
-whether the stated split failure is real under angle 6, not the number itself.
-Missing rationale blocks approval; weak rationale returns to the author through
-the normal split/rework loop, never to the user. Escalate only for an existing
-material-scope, security, downtime, data-loss, major-design-risk, or unavailable-model hold.
+## Review and decisions
+Size alone must never block review, reject a PR, require split attempts or
+cohesion/exception rationale, or hold approval.
+Review the actual footprint, complexity, and required context, incrementally when needed.
+Approval requires sufficient review coverage.
+Report INCOMPLETE when required coverage is missing.
+Routine shape decisions remain autonomous driver decisions within approved scope;
+size alone never requires user approval.
+Escalate only for an existing material-scope, security, downtime, data-loss,
+major-design-risk, or unavailable-model hold.

package/skills/axstack-audit/SKILL.md

@@ -117,10 +117,10 @@ counts with denominators plus the evidence behind the count:
 - Rework cycles with causes.
 - Avoidable user interventions where records support the call, and no call where they do not.
 - Parallelizable tasks identified versus dispatched, judged with dependency and writer isolation.
-- PRs within band / total PRs using the actual denominator. Apply the level
-  matching the measured total. For the rationale band, record cohesion
-  rationale presence; for the exception band, record the full driver exception
-  record. Record `UNKNOWN` when a receipt lacks the measurement.
+- PRs with an informational size flag / total PRs using the actual denominator.
+  Record full totals, bulk buckets with reproducible commands, and measured head/base.
+  Treat size flags as informational only.
+  Record `UNKNOWN` when a receipt lacks the measurement.
   This is evidence, not a score to game. Audit treats routine shape choices as
   autonomous driver decisions; size alone never requires user approval.
 - API-dollar cost by model when provider receipts are available, UNKNOWN otherwise.

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

@@ -17,7 +17,7 @@ Review: <exact-rev independent review status + unresolved findings>
 Rework: <cycles + causes>
 Interventions: <avoidable user interventions, or unsupported by records>
 Parallelism: <identified vs dispatched + dependency/writer isolation>
-Shape: <PRs within band / total PRs + rationale-band cohesion rationale + exception-band full driver exception record; missing measurement: UNKNOWN>
+Shape: <PRs with an informational size flag / total PRs; full totals + bulk buckets with reproducible commands + measured head/base; UNKNOWN when measurement is missing>
 Cost: <API dollars by model when measured, or UNKNOWN with reason>
 Judgment: <execution outcome vs procedural adherence vs measurement coverage>
 Proposals: <bounded hypothesized changes with regression-first plan, or none>
@@ -25,6 +25,8 @@ Learning candidates: <each candidate's statement + scope + evidence/revision poi
 Privacy: <local/private default; sanitized summary only when authorized>
 ```
 
+Treat size flags as informational only.
+
 The record is complete when its counts reconcile, its judgments remain
 separate, every proposal has a regression-first validation path, every learning
 candidate is bounded to accepted audited evidence, and all unknowns and

package/skills/axstack-review/SKILL.md

@@ -293,17 +293,15 @@ This section applies to peer and authored PR modes.
    Rate a wrong or missing `Revert` line at least `medium` under [Finding severity](#finding-severity).
 
    Under angle 6, verify the recorded shape against the pinned head and base.
-   A mismatch between the recorded and measured total is a finding. Apply the
-   level matching the measured total. The rationale band requires only its
-   recorded cohesion rationale, not a split-attempt record. For the exception
-   band, verify the full exception record: total, bulk buckets with their
-   reproducible command, measured head/base, split attempts tried, and why each
-   fails on atomicity, green state, or reviewability. Missing rationale is a
-   validated angle 6 finding that blocks approval like any other. Reviewer
-   judgment is bounded to verifying the measurement and whether the stated split
-   failure is real, not the number itself. A weak rationale returns to the
-   author as a split or rework request through the normal fix loop, never to the
-   user. Routine shape decisions remain autonomous driver decisions; size alone
+   A mismatch between the recorded and measured total is a finding.
+   Verify full totals and bulk buckets with their reproducible command.
+   Treat size flags as informational only.
+   Size alone must never block review, reject a PR, require split attempts or
+   cohesion/exception rationale, or hold approval.
+   Review the actual footprint, complexity, and required context, incrementally when needed.
+   Approval requires sufficient review coverage.
+   Report INCOMPLETE when required coverage is missing.
+   Routine shape decisions remain autonomous driver decisions; size alone
    never requires user approval. Escalate only when that work exposes an
    existing material-scope, security, downtime,
    data-loss, major-design-risk, or unavailable-model hold.

package/skills/axstack-tickets/SKILL.md

@@ -50,11 +50,12 @@ no dispatch preflight.
    sketch boundary as a split signal. Identify internal tasks, dependencies,
    PR ownership, and worktrees. For each task the driver records
    one theme and a coarse size estimate from the ownership, interface, and
-   dependency map. A task estimated in the exception band is assessed for a
-   split at mapping time and split where a green, atomic, reviewable split
-   exists. If the driver judges it inseparable, record the coarse planning
-   rationale with the task; actual measurement and exception evidence follow in
-   the implement receipt. Mapping time requires no actual SHAs or line counts.
+   dependency map. Plan coherent, independently reviewable tasks around those
+   boundaries. Treat size flags as informational only.
+   Size alone must never block review, reject a PR, require split attempts or
+   cohesion/exception rationale, or hold approval.
+   Actual measurement and bulk disclosure follow in the implement receipt.
+   Mapping time requires no actual SHAs or line counts.
    Every capability ends with the fields below and an explicit dependency list.
    Before accepting the map, dispatch `axstack-diligence` under
    [Diligence](../axstack/references/diligence.md) to confirm every spec
@@ -72,7 +73,7 @@ Spec: <approved revision>
 Capability: <Markdown ref, GitHub issue URL, or Linear issue URL> <title>
 Internal task: <task> -> <PR owner> -> <worktree>
 Theme: <one behavior or component>
-Size est: <coarse band estimate>
+Size est: <coarse size estimate>
 Acceptance: <checks from approved spec rev>
 Depends: <task IDs or none>
 ```