gennady 0.8.4-next.6 → 0.8.4-next.8

package/ai/directives/sdd/audit.directive.xml

@@ -49,7 +49,7 @@
       Deterministic mechanical checks — file-header presence, Task-ID collision, tracker-sync — are NOT hand-coded here. They live in one tool, `sdd check`, which sdd-check (whole tree) and this directive (scoped) both consume. Single source of mechanical truth → no drift between the two SDD reviewers.
 
       - `sdd check --files <git-diff in-scope files>` → [HEADERS] (`@file`/`@consumers`/`@tasks` presence).
-      - `sdd check --task <Task-ID>` → [TASKID] (collision for that id) + [TRACKER_SYNC] (Meta.Status vs tracker row).
+      - `sdd check --task <Task-ID>` → [TASKID] (collision for that id) + [TRACKER_SYNC] (Meta.Status vs tracker row) + [RULES] (four-section presence in the rules this ticket cites; `rule_findings` is counted apart from `findings` because a shared rule file is not this task's defect).
       - `sdd check <root>` (no flag) → tree-wide [TASKID] orphan refs (epic mode).
 
       Audit still owns everything the tool cannot decide mechanically: semantic `@consumers` resolvability, current-Task-ID identity, append-only `@tasks` regression vs git, section-anchor coverage, and all code-reading checks (closed-world, completeness, rules-compliance, runtime-backing, backflow).
@@ -67,7 +67,7 @@
       | `RULES_CASCADE_MISMATCH` | a phase's `Rules:` list ≠ what scaffolder would derive now from cascade × that phase's `Target Files` + kind |
       | `TASK_ID_DRIFT` | `@tasks` field references non-existent ticket ID (orphan); OR Task-ID duplicated across ticket files (collision); OR `@tasks` field lost prior IDs (regression of append-only) |
       | `BDD_COVERAGE_MISMATCH` | canonical case names in ticket Test Scenario Coverage ≠ real test cases |
-      | `EXECUTION_LOG_INCOMPLETE` | mandatory closing lines missing (`ver` / `DONE` per phase, `DONE` at Round close); OR `intro` line absent for an entity that appears in code but not in module Inventory; OR a previous round was edited (round log is append-only); OR `[x]` line with unreplaced `<…>` placeholder (fabricated done) |
+      | `EXECUTION_LOG_INCOMPLETE` | mandatory closing lines missing (`ver` / `DONE` per phase, `DONE` at Round close); OR `intro` line absent for an entity that appears in code but not in module Inventory; OR a previous round was edited (round log is append-only); OR `[x]` line with unreplaced `<…>` placeholder (fabricated done). Token vocabulary and Round-close shape are decided by `sdd check` [LOG], not by eye: `unknown-token` / `unclosed-round` are findings, `retired-token` / `round-close-no-timestamp` are not (append-only history) |
       | `INSIGHT_BACKFLOW` | Phase agent discovered something that changes contract / requirement understanding; should flow back into spec |
       | `STALE_AFTER_PIVOT` | scope spec was reworked in `pivot` mode (Pivot Invalidation List exists) but downstream artifacts named in the list have not been refined / reopened / updated |
       | `RULE_FILE_INCOMPLETE` | activated rule file lacks one of the universal checkable sections (`<BeliefState>` / `<AntiPatterns>` / `<VerificationHooks>` / `<RewardCriteria>`) per `AX_RULES_COMPLIANCE_AGAINST_ACTIVATED_RULES`; audit can partially proceed but the gap blocks full coverage |
@@ -172,7 +172,7 @@
       - `<VerificationHooks>` → executable check commands
       - `<RewardCriteria>` → ✅ invariants / ❌ forbidden states
 
-      Required sections: `<BeliefState>` / `<AntiPatterns>` / `<VerificationHooks>` / `<RewardCriteria>`. Optional: `<DependsOn>` (only when the rule extends another). Required section missing → `RULE_FILE_INCOMPLETE` (`MAJOR`); audit proceeds with available sections.
+      Section presence is NOT judged by eye — `sdd check --task <Task-ID>` emits `[RULES]` for exactly this ticket's cited rules (per `AX_MECHANICAL_VIA_SDD_CHECK`). Each `INCOMPLETE` row → one `RULE_FILE_INCOMPLETE`, its `missing` column copied verbatim. Audit proceeds with the sections that exist. `<DependsOn>` is optional and unchecked.
 
       **Per (artifact ∈ Round diff, rule ∈ union of all phases' Rules):**
       1. Apply rule's `<Triggers>` / `<ActivationHint>` from `knowledge.xml` to decide if the rule governs this artifact. No match → skip pair.

package/ai/directives/sdd/scaffold.directive.xml

@@ -229,7 +229,9 @@
     </Axiom>
 
     <Axiom id="AX_AUDIT_HOOK">
-      Round is complete only after `audit` returns PASS. `sdd-execute` orchestrator dispatches audit-subagent automatically after the last phase of a Round closes — operator does not invoke audit manually. `[x] DONE` on the ticket is mechanical close, not verification. Until audit PASS, dependents are blocked.
+      Round is complete only after `audit` returns PASS. `sdd-execute` orchestrator dispatches audit-subagent automatically after the last phase of a Round closes — operator does not invoke audit manually.
+
+      Closing the Round does NOT set `[x] DONE`. The ticket stays `[~] IN_PROGRESS` from Round close until audit PASS, and only then becomes `[x] DONE`. So `[x] DONE` means verified — one meaning, and the one dependents rely on: pickability reads that status, and a task whose audit has not run (or has failed) must not read as pickable.
     </Axiom>
 
     <Axiom id="AX_PHASES_DECLARED_IN_HEADER">
@@ -714,7 +716,7 @@
       ⛔ `[x]` line with any unreplaced `<…>` literal = fabricated done → `EXECUTION_LOG_INCOMPLETE` (BLOCKER).
 
       ### Post-task Hook
-      Per `AX_AUDIT_HOOK`. After last phase of a Round closes, the orchestrator dispatches `sdd-audit`. Until audit returns PASS, Round is closed-but-unverified and dependents are blocked.
+      Per `AX_AUDIT_HOOK`. After last phase of a Round closes, the orchestrator dispatches `sdd-audit`. Round close leaves the ticket `[~] IN_PROGRESS`; audit PASS is what sets `[x] DONE`. Until then dependents are blocked, and the status says so.
 
       ## High-Level DAG
       Cross-scope edges + integration tickets only. Intra-scope DAGs live in per-scope READMEs.

package/ai/skills/sdd-check/SKILL.md

@@ -81,10 +81,16 @@ Parse `Dependencies:` from each task ticket planning surface. Topological sort.
 
 From scan [TASKS] output: check `placeholders` column for any task with >0. Flag tasks where placeholders > 0 even if status DONE. Also inspect `warnings` column for `no-execlog-section` or `anchors-mismatch`.
 
+Token vocabulary and Round-close shape come from `sdd check` [LOG] — do not re-read logs by hand. `unknown-token` (outside the scaffold table) and `unclosed-round` (a Round close with no ticked DONE) → FAIL. `retired-token` (valid before the vocabulary was consolidated) and `round-close-no-timestamp` → INFO: rounds are append-only, so history cannot be rewritten to satisfy a later rule.
+
 ### Check 5b — Task-ID Integrity (from `sdd check` [TASKID])
 
 Read the [TASKID] section of `sdd check`. `collision` (one Task-ID on ≥2 ticket files) → FAIL (BLOCKER). `orphan` (a code `@tasks: TSK-NN` with no ticket file) → FAIL. Empty section → PASS. Same tool sdd-audit STEP_2_5 uses.
 
+### Check 5c — Rule File Schema (from `sdd check` [RULES])
+
+Read the [RULES] section. Each `verdict=INCOMPLETE` row is a rule file missing one of the four checkable sections; the `missing` column names them. Report as INFO with the file list, **not** as a tree FAIL: these are shared project artifacts, tracked by `rule_findings` separately from `findings` for exactly that reason. Fixing them is its own ticket, never a task reopen.
+
 ### Check 6 — File Headers (from `sdd check --files`)
 
 Pass recently modified source files to the shared checker instead of sampling by hand:
@@ -134,8 +140,9 @@ First: Self-Reflection. Then: Mechanical Checks. Use compact single-line-per-che
 
 Rules for VERDICT line:
 
-- All 8 checks PASS AND 0 protocol violations → `✅ CLEAN — artifact tree is consistent, next pickable: TSK-NN`
-- All 8 checks PASS AND 0 violations but some tasks deferred/TODO → `✅ CLEAN — <N> tasks remaining in queue`
+- All checks PASS AND 0 protocol violations → `✅ CLEAN — artifact tree is consistent, next pickable: TSK-NN`
+- All checks PASS AND 0 violations but some tasks deferred/TODO → `✅ CLEAN — <N> tasks remaining in queue`
+- Check 5c findings are INFO — they never move the verdict off `✅ CLEAN`; append `· <N> rule file(s) incomplete` to the line instead
 - Any FAIL check OR protocol violations → `❌ NOT READY — <N> issue(s) require attention`
 - Checks skipped (marked `—`) → treat as PASS for verdict unless evidence of gap exists
   </Output>

package/ai/skills/sdd-execute/SKILL.md

@@ -97,13 +97,14 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
     #### Round close
     - [x] `<ts>` DONE
     ```
-    Set ticket Meta Status → `[x] DONE`.
+    Set ticket Meta Status → `[~] IN_PROGRESS`. **Not `[x] DONE` — the round is closed, not verified.** `DONE` is set in step 6, and only on audit PASS. Dependents pick on `DONE`, so setting it here advertises a task the audit has not seen yet.
 
 4a. **Sync Trackers** (MANDATORY, cannot skip):
 
-- Read `tasks/<scope>/README.md`. Find the Tracker row for this Task-ID. Set its Status → `[x] DONE`. Write back.
-- Read `tasks/README.md` Tracker Index. Update the scope's aggregate counts (done/total). Write back.
+- Read `tasks/<scope>/README.md`. Find the Tracker row for this Task-ID. Set its Status to the ticket's current Meta Status. Write back.
+- Read `tasks/README.md` Tracker Index. Update the scope's aggregate counts (done/total) — a task counts as done only at `[x] DONE`. Write back.
 - Verify: re-read both files, confirm the changes took effect. If not → retry once.
+- Run this step again after step 6 sets the final status.
 
 5.  **Dispatch AUDIT** (MANDATORY, always runs). Dispatch ONE subagent (`subagent_type: general-purpose`, **`model: "haiku"`** — audit is mechanical verification + fact-checking against artifacts; sonnet capability is overkill, haiku is faster and cheaper for this read-heavy task). Include in prompt the SDD tooling location: `~/Developer/gennady/ai/skills/sdd-execute/scripts/sdd` (audit may use `lint`, `verify`, `check-blockers` subcommands). With this prompt:
 
@@ -128,7 +129,7 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
     Wait for return. If dispatch fails → retry once. If fails again → mark task FAILED.
 
 6.  **Branch on audit status:**
-    - `PASS` or `PASS_WITH_ACKNOWLEDGED_RISKS` → ticket verified; jump to step 9 (summary).
+    - `PASS` or `PASS_WITH_ACKNOWLEDGED_RISKS` → ticket verified. **Only now** set Meta Status → `[x] DONE` and re-run step 4a so the trackers and the aggregate counts follow. Jump to step 9 (summary).
     - `FAIL` AND `audit_attempt = 1` → step 7 (resolve findings).
     - `FAIL` AND `audit_attempt = 2` → cap exhausted. Set Meta Status `[!] BLOCKED`, log `🛑 BLOCKED: audit-cap-exhausted` whose `💬 unblock:` line is the literal command `/sdd-execute <TSK-NN> --new-audit-session`, sync trackers, jump to step 9.
 

package/ai/skills/sdd-execute/scripts/check.sh

@@ -5,19 +5,37 @@
 #            header presence, Task-ID integrity, or tracker sync. Pure function of files on disk.
 #
 # Three modes:
-#   check.sh [project-root]          — whole tree: TASKID + TRACKER_SYNC (all tickets) + HEADERS (all marker-bearing src)
-#   check.sh --task <TSK-NN> [root]  — one ticket: TASKID (collision/orphan-for-its-refs) + TRACKER_SYNC for that id
+#   check.sh [project-root]          — whole tree: TASKID + TRACKER_SYNC (all tickets) + RULES (all rule files)
+#   check.sh --task <TSK-NN> [root]  — one ticket: TASKID + TRACKER_SYNC for that id + RULES for its cited rules
 #   check.sh --files <f1> [f2 ...]   — header-trio presence for an explicit file list (audit passes its git-diff scope)
 #
 # Output sections (TSV, machine-readable, stable):
 #   [HEADERS]      — file \t has_file \t has_consumers \t has_tasks \t verdict(OK|PARTIAL|NONE)
 #   [TASKID]       — kind(orphan|collision) \t id \t detail
 #   [TRACKER_SYNC] — task_id \t ticket_status \t tracker_status \t match(YES|NO|NO_ROW)
+#   [RULES]        — file \t belief \t anti \t hooks \t reward \t verdict(OK|INCOMPLETE) \t missing
+#   [LOG]          — ticket \t round \t line \t kind \t token \t detail
+#                    kinds: unknown-token | unclosed-round        (counted as findings)
+#                           retired-token | round-close-no-timestamp (informational: append-only
+#                           history and cosmetics never fail a tree)
 #   [SUMMARY]      — key=value totals + findings count
 #
+# [RULES] implements the mechanical half of AX_RULES_COMPLIANCE_AGAINST_ACTIVATED_RULES: a rule file
+# must expose <BeliefState> / <AntiPatterns> / <VerificationHooks> / <RewardCriteria>. Detection is a
+# tolerant opening-tag scan, NOT an XML parse — these files are HTML-like by design and carry prose
+# such as `<Target Files>` and `Meta<typeof Button>` that no XML parser accepts.
+#
+# Rule files are the non-`*.directive.xml` entries of the cascade categories (coding / testing / infra),
+# in the project and in plugin directive trees. `*.directive.xml` are protocols, not rules, and are
+# exempt. Tree mode scans every rule file; task mode scans only the ones that ticket's phases cite —
+# the "activated" set the axiom is written against.
+#
+# Rule findings are counted SEPARATELY from task findings (`rule_findings=`): a shared rule file is
+# project infrastructure that no single task owns or may edit, so it must not decide a task's verdict.
+#
 # Exit codes:
 #   0 — all checks clean (zero findings)
-#   3 — one or more findings (desync / orphan / collision / partial-or-missing header)
+#   3 — one or more findings (desync / orphan / collision / partial-or-missing header / incomplete rule)
 #   2 — structural failure (bad root / not an SDD project)
 #   4 — bad invocation
 
@@ -82,6 +100,7 @@ EOF
 esac
 
 FINDINGS=0
+RULE_FINDINGS=0
 
 # ---------------------------------------------------------------------------
 # Mode: --files  → HEADERS only
@@ -227,6 +246,148 @@ done <<< "$TASK_FILES"
 # is a policy (task-generated vs hand-authored), not a mechanical fact. Header presence
 # is meaningful only against a known in-scope file set — provided by audit via --files.
 
+# ---------------------------------------------------------------------------
+# [RULES] — activated rule files expose the four checkable sections
+# ---------------------------------------------------------------------------
+
+printf '\n[RULES]\n# file\tbelief\tanti\thooks\treward\tverdict\tmissing\n'
+
+# Cascade categories only; `*.directive.xml` are protocols, not rules.
+rule_files_in_tree() {
+    find -L "$ROOT_ABS/ai/directives" "$ROOT_ABS"/plugins/*/directives \
+        -type d -name node_modules -prune -o \
+        -type f -name '*.xml' ! -name '*.directive.xml' -print 2>/dev/null \
+        | grep -E '/(coding|testing|infra)/[^/]+\.xml$' | sort -u || true
+}
+
+# Task mode: the rules this ticket's phases actually cite (the "activated" set).
+rule_files_for_task() {
+    local ticket
+    ticket=$(grep -l "^- \*\*Task-ID:\*\* $TASK_ID\$" $TASK_FILES 2>/dev/null | head -1)
+    [[ -z "$ticket" ]] && return
+    grep -ohE '(ai/directives|plugins/[a-z0-9-]+/directives)/[a-z0-9-]+/[a-z0-9._-]+\.xml' "$ticket" \
+        | grep -vE '\.directive\.xml$' | sort -u \
+        | while IFS= read -r rel; do
+            [[ -f "$ROOT_ABS/$rel" ]] && printf '%s\n' "$ROOT_ABS/$rel"
+          done
+}
+
+if [[ "$MODE" == "task" ]]; then
+    RULE_FILES=$(rule_files_for_task)
+else
+    RULE_FILES=$(rule_files_in_tree)
+fi
+
+if [[ -z "$RULE_FILES" ]]; then
+    printf '# none%s\n' "$([[ "$MODE" == task ]] && echo " — ticket cites no rule files")"
+else
+    while IFS= read -r rf; do
+        [[ -z "$rf" ]] && continue
+        b=0; a=0; h=0; r=0; missing=""
+        grep -q '<BeliefState' "$rf" && b=1 || missing="${missing}BeliefState,"
+        grep -q '<AntiPatterns' "$rf" && a=1 || missing="${missing}AntiPatterns,"
+        grep -q '<VerificationHooks' "$rf" && h=1 || missing="${missing}VerificationHooks,"
+        grep -q '<RewardCriteria' "$rf" && r=1 || missing="${missing}RewardCriteria,"
+        if [[ -z "$missing" ]]; then
+            printf '%s\t1\t1\t1\t1\tOK\t-\n' "${rf#$ROOT_ABS/}"
+        else
+            printf '%s\t%d\t%d\t%d\t%d\tINCOMPLETE\t%s\n' "${rf#$ROOT_ABS/}" "$b" "$a" "$h" "$r" "${missing%,}"
+            RULE_FINDINGS=$((RULE_FINDINGS+1))
+        fi
+    done <<< "$RULE_FILES"
+fi
+
+# ---------------------------------------------------------------------------
+# [LOG] — Execution Log token vocabulary + Round-close shape
+# ---------------------------------------------------------------------------
+
+printf '\n[LOG]\n# ticket\tround\tline\tkind\ttoken\tdetail\n'
+
+# `retired` tokens were valid before the vocabulary was consolidated. Rounds are append-only, so
+# their presence in an old round is history, not a defect — they are reported and NOT counted.
+# Anything outside both sets is `unknown-token` and IS counted.
+LOG_TMP="$(mktemp -t sdd-check-log.XXXXXX)"
+trap 'rm -f "$COLLISION_TMP" "$LOG_TMP"' EXIT
+
+while IFS= read -r f; do
+    [[ -z "$f" ]] && continue
+    if [[ "$MODE" == "task" ]]; then
+        [[ "$(sdd_lib_task_id "$f")" == "$TASK_ID" ]] || continue
+    fi
+    awk -v ticket="${f#$ROOT_ABS/}" '
+        BEGIN {
+            split("intro decision tried discovery insight verified ver BLOCKED DONE", v, " ")
+            for (i in v) valid[v[i]] = 1
+            # Retired when the vocabulary was consolidated (scaffold.directive names exactly these).
+            split("sync file test cov rules recon", r, " ")
+            for (i in r) retired[r[i]] = 1
+            # Blocker lifecycle markers are their own shape, not action tokens.
+            valid["🛑"] = 1; valid["✅"] = 1
+            round = "-"; inlog = 0; inclose = 0; closelines = 0; closebad = 0
+        }
+        /^## 7\. Execution Log/ { inlog = 1; next }
+        /^## [0-9]+\./       { if (inlog) inlog = 0 }
+        inlog == 0           { next }
+        /^### Round /        {
+            if (inclose && closelines != 1 && closebad == 0)
+                printf "%s\t%s\t%d\tbad-round-close\t-\texpected exactly one DONE line, found %d\n", ticket, round, closeline, closelines
+            round = $3; inclose = 0; closelines = 0; closebad = 0; next
+        }
+        /^#### Round close/  { inclose = 1; closelines = 0; closebad = 0; closeline = NR; next }
+        /^#### /             {
+            if (inclose && closelines != 1 && closebad == 0)
+                printf "%s\t%s\t%d\tbad-round-close\t-\texpected exactly one DONE line, found %d\n", ticket, round, closeline, closelines
+            inclose = 0; closebad = 0; next
+        }
+        # Token lines: "- [x] `<ts>` <token> ..."  (blocker lines use 🛑 and are matched separately)
+        /^- \[[ x~!]\] `[^`]*` / {
+            rest = $0; sub(/^- \[[ x~!]\] `[^`]*` +/, "", rest)
+            split(rest, w, " "); tok = w[1]
+            sub(/:$/, "", tok)   # a trailing colon is cosmetic, not a different token
+            if (inclose) { if (tok == "DONE") closelines++ }
+            if (tok in valid) next
+            # Every real token is lowercase except BLOCKED / DONE. A capitalised first word is a
+            # sentence from the pre-consolidation prose plan ("Implementation file:", "Tracker
+            # synced:"), which the same consolidation retired.
+            if (tok ~ /^[A-Z]/) {
+                printf "%s\t%s\t%d\tretired-token\t%s\tprose line from the pre-consolidation plan template\n", ticket, round, NR, tok
+                next
+            }
+            if (tok in retired) {
+                printf "%s\t%s\t%d\tretired-token\t%s\tvalid before the vocabulary was consolidated; round is append-only\n", ticket, round, NR, tok
+            } else {
+                printf "%s\t%s\t%d\tunknown-token\t%s\tnot in the scaffold.directive token table\n", ticket, round, NR, tok
+            }
+            next
+        }
+        # A checkbox line inside Round close that carries no timestamped token at all.
+        # Close-block lines that carry no timestamped token. A ticked DONE without a timestamp is
+        # cosmetic drift; an unticked box means the round was never actually closed.
+        inclose == 1 && /^- / {
+            if ($0 ~ /\[x\]/ && $0 ~ /DONE/) {
+                printf "%s\t%s\t%d\tround-close-no-timestamp\tDONE\tclosed, but the `<ts>` is missing\n", ticket, round, NR
+                closelines++
+            } else {
+                printf "%s\t%s\t%d\tunclosed-round\t-\tRound close carries no ticked DONE: %s\n", ticket, round, NR, substr($0, 1, 40)
+                closebad = 1
+            }
+        }
+        END {
+            if (inclose && closelines != 1 && closebad == 0)
+                printf "%s\t%s\t%d\tbad-round-close\t-\texpected exactly one DONE line, found %d\n", ticket, round, closeline, closelines
+        }
+    ' "$f" >> "$LOG_TMP"
+done <<< "$TASK_FILES"
+
+if [[ -s "$LOG_TMP" ]]; then
+    cat "$LOG_TMP"
+    # Informational kinds record history or cosmetics; they must not fail the tree.
+    LOG_FINDINGS=$(awk -F'\t' '$4 != "retired-token" && $4 != "round-close-no-timestamp"' "$LOG_TMP" | grep -c '' || true)
+    FINDINGS=$((FINDINGS + LOG_FINDINGS))
+else
+    printf '# none\n'
+fi
+
 # ---------------------------------------------------------------------------
 # [SUMMARY]
 # ---------------------------------------------------------------------------
@@ -234,5 +395,6 @@ done <<< "$TASK_FILES"
 printf '\n[SUMMARY]\nmode=%s\n' "$MODE"
 [[ "$MODE" == "task" ]] && printf 'task=%s\n' "$TASK_ID"
 printf 'findings=%d\n' "$FINDINGS"
+printf 'rule_findings=%d\n' "$RULE_FINDINGS"
 
-[[ "$FINDINGS" -gt 0 ]] && exit 3 || exit 0
+[[ $((FINDINGS + RULE_FINDINGS)) -gt 0 ]] && exit 3 || exit 0

package/ai/skills/sdd-execute-batch/SKILL.md

@@ -131,7 +131,7 @@ Per-task phase tokens:
 
             c. Thread next phase's Inputs from this phase's Handoff (verbatim).
 
-          After all phases DONE: close Round (append `#### Round close` block per `ROUND_CLOSE_FORMAT`: a single `DONE` line). Sync trackers. Ticket Status → `[x] DONE`.
+          After all phases DONE: close Round (append `#### Round close` block per `ROUND_CLOSE_FORMAT`: a single `DONE` line). Ticket Status → `[~] IN_PROGRESS` — closed, not verified. Sync trackers to that status. `[x] DONE` is set in step e, on audit PASS only: dependents pick on `DONE`, and a later layer must not start against a task the audit has not seen.
 
            d. Dispatch AUDIT subagent (`subagent_type: general-purpose`, **`model: "haiku"`** — audit is mechanical verification + fact-checking, haiku sufficient and cheaper). MANDATORY, always runs. Include in prompt the SDD tooling location: `~/Developer/gennady/ai/skills/sdd-execute/scripts/sdd` (audit may use `lint`, `verify`, `check-blockers` subcommands):
               ```
@@ -154,14 +154,14 @@ Per-task phase tokens:
               Wait for return. If dispatch fails → retry once. If fails again → mark task FAILED.
 
           e. Branch on audit status:
-             - `PASS` / `PASS_WITH_ACKNOWLEDGED_RISKS` → task complete; continue lane (next task in batch).
+             - `PASS` / `PASS_WITH_ACKNOWLEDGED_RISKS` → task verified. Only now set Ticket Status → `[x] DONE` and re-sync trackers. Continue lane (next task in batch).
              - `FAIL` AND `audit_attempt = 1` → trigger selective phase re-run.
                Open new Round with reason `audit-driven fix: F-NNN, F-MMM`.
                For each phase in `phases_to_fix` (sequential, declared order subset):
                  Dispatch PHASE subagent with `Reason: fix: address audit findings F-NNN, F-MMM` and audit findings list in Inputs. Wait.
                  On BLOCKED/FAIL → STOP this task's lane; mark task FAILED.
                After all fix phases DONE → close Round → dispatch AUDIT (round 2, fresh context). Branch again:
-                 PASS → task complete.
+                 PASS → task verified: Ticket Status → `[x] DONE`, re-sync trackers.
                  FAIL (audit_attempt = 2) → STOP lane; cap exhausted. Meta Status `[!] BLOCKED`, `🛑 BLOCKED: audit-cap-exhausted` with `💬 unblock: /sdd-execute <TSK-NN> --new-audit-session`. Report as `🛑 cap-exhausted`, distinct from `❌ FAILED`. The batch never lifts the cap itself.
 
          — Wait for all parallel task lanes in sub-batch to finish.

package/dist/ai/directives/sdd/audit.directive.xml

@@ -49,7 +49,7 @@
       Deterministic mechanical checks — file-header presence, Task-ID collision, tracker-sync — are NOT hand-coded here. They live in one tool, `sdd check`, which sdd-check (whole tree) and this directive (scoped) both consume. Single source of mechanical truth → no drift between the two SDD reviewers.
 
       - `sdd check --files <git-diff in-scope files>` → [HEADERS] (`@file`/`@consumers`/`@tasks` presence).
-      - `sdd check --task <Task-ID>` → [TASKID] (collision for that id) + [TRACKER_SYNC] (Meta.Status vs tracker row).
+      - `sdd check --task <Task-ID>` → [TASKID] (collision for that id) + [TRACKER_SYNC] (Meta.Status vs tracker row) + [RULES] (four-section presence in the rules this ticket cites; `rule_findings` is counted apart from `findings` because a shared rule file is not this task's defect).
       - `sdd check <root>` (no flag) → tree-wide [TASKID] orphan refs (epic mode).
 
       Audit still owns everything the tool cannot decide mechanically: semantic `@consumers` resolvability, current-Task-ID identity, append-only `@tasks` regression vs git, section-anchor coverage, and all code-reading checks (closed-world, completeness, rules-compliance, runtime-backing, backflow).
@@ -67,7 +67,7 @@
       | `RULES_CASCADE_MISMATCH` | a phase's `Rules:` list ≠ what scaffolder would derive now from cascade × that phase's `Target Files` + kind |
       | `TASK_ID_DRIFT` | `@tasks` field references non-existent ticket ID (orphan); OR Task-ID duplicated across ticket files (collision); OR `@tasks` field lost prior IDs (regression of append-only) |
       | `BDD_COVERAGE_MISMATCH` | canonical case names in ticket Test Scenario Coverage ≠ real test cases |
-      | `EXECUTION_LOG_INCOMPLETE` | mandatory closing lines missing (`ver` / `DONE` per phase, `DONE` at Round close); OR `intro` line absent for an entity that appears in code but not in module Inventory; OR a previous round was edited (round log is append-only); OR `[x]` line with unreplaced `<…>` placeholder (fabricated done) |
+      | `EXECUTION_LOG_INCOMPLETE` | mandatory closing lines missing (`ver` / `DONE` per phase, `DONE` at Round close); OR `intro` line absent for an entity that appears in code but not in module Inventory; OR a previous round was edited (round log is append-only); OR `[x]` line with unreplaced `<…>` placeholder (fabricated done). Token vocabulary and Round-close shape are decided by `sdd check` [LOG], not by eye: `unknown-token` / `unclosed-round` are findings, `retired-token` / `round-close-no-timestamp` are not (append-only history) |
       | `INSIGHT_BACKFLOW` | Phase agent discovered something that changes contract / requirement understanding; should flow back into spec |
       | `STALE_AFTER_PIVOT` | scope spec was reworked in `pivot` mode (Pivot Invalidation List exists) but downstream artifacts named in the list have not been refined / reopened / updated |
       | `RULE_FILE_INCOMPLETE` | activated rule file lacks one of the universal checkable sections (`<BeliefState>` / `<AntiPatterns>` / `<VerificationHooks>` / `<RewardCriteria>`) per `AX_RULES_COMPLIANCE_AGAINST_ACTIVATED_RULES`; audit can partially proceed but the gap blocks full coverage |
@@ -172,7 +172,7 @@
       - `<VerificationHooks>` → executable check commands
       - `<RewardCriteria>` → ✅ invariants / ❌ forbidden states
 
-      Required sections: `<BeliefState>` / `<AntiPatterns>` / `<VerificationHooks>` / `<RewardCriteria>`. Optional: `<DependsOn>` (only when the rule extends another). Required section missing → `RULE_FILE_INCOMPLETE` (`MAJOR`); audit proceeds with available sections.
+      Section presence is NOT judged by eye — `sdd check --task <Task-ID>` emits `[RULES]` for exactly this ticket's cited rules (per `AX_MECHANICAL_VIA_SDD_CHECK`). Each `INCOMPLETE` row → one `RULE_FILE_INCOMPLETE`, its `missing` column copied verbatim. Audit proceeds with the sections that exist. `<DependsOn>` is optional and unchecked.
 
       **Per (artifact ∈ Round diff, rule ∈ union of all phases' Rules):**
       1. Apply rule's `<Triggers>` / `<ActivationHint>` from `knowledge.xml` to decide if the rule governs this artifact. No match → skip pair.

package/dist/ai/directives/sdd/scaffold.directive.xml

@@ -229,7 +229,9 @@
     </Axiom>
 
     <Axiom id="AX_AUDIT_HOOK">
-      Round is complete only after `audit` returns PASS. `sdd-execute` orchestrator dispatches audit-subagent automatically after the last phase of a Round closes — operator does not invoke audit manually. `[x] DONE` on the ticket is mechanical close, not verification. Until audit PASS, dependents are blocked.
+      Round is complete only after `audit` returns PASS. `sdd-execute` orchestrator dispatches audit-subagent automatically after the last phase of a Round closes — operator does not invoke audit manually.
+
+      Closing the Round does NOT set `[x] DONE`. The ticket stays `[~] IN_PROGRESS` from Round close until audit PASS, and only then becomes `[x] DONE`. So `[x] DONE` means verified — one meaning, and the one dependents rely on: pickability reads that status, and a task whose audit has not run (or has failed) must not read as pickable.
     </Axiom>
 
     <Axiom id="AX_PHASES_DECLARED_IN_HEADER">
@@ -714,7 +716,7 @@
       ⛔ `[x]` line with any unreplaced `<…>` literal = fabricated done → `EXECUTION_LOG_INCOMPLETE` (BLOCKER).
 
       ### Post-task Hook
-      Per `AX_AUDIT_HOOK`. After last phase of a Round closes, the orchestrator dispatches `sdd-audit`. Until audit returns PASS, Round is closed-but-unverified and dependents are blocked.
+      Per `AX_AUDIT_HOOK`. After last phase of a Round closes, the orchestrator dispatches `sdd-audit`. Round close leaves the ticket `[~] IN_PROGRESS`; audit PASS is what sets `[x] DONE`. Until then dependents are blocked, and the status says so.
 
       ## High-Level DAG
       Cross-scope edges + integration tickets only. Intra-scope DAGs live in per-scope READMEs.

package/dist/ai/skills/sdd-check/SKILL.md

@@ -81,10 +81,16 @@ Parse `Dependencies:` from each task ticket planning surface. Topological sort.
 
 From scan [TASKS] output: check `placeholders` column for any task with >0. Flag tasks where placeholders > 0 even if status DONE. Also inspect `warnings` column for `no-execlog-section` or `anchors-mismatch`.
 
+Token vocabulary and Round-close shape come from `sdd check` [LOG] — do not re-read logs by hand. `unknown-token` (outside the scaffold table) and `unclosed-round` (a Round close with no ticked DONE) → FAIL. `retired-token` (valid before the vocabulary was consolidated) and `round-close-no-timestamp` → INFO: rounds are append-only, so history cannot be rewritten to satisfy a later rule.
+
 ### Check 5b — Task-ID Integrity (from `sdd check` [TASKID])
 
 Read the [TASKID] section of `sdd check`. `collision` (one Task-ID on ≥2 ticket files) → FAIL (BLOCKER). `orphan` (a code `@tasks: TSK-NN` with no ticket file) → FAIL. Empty section → PASS. Same tool sdd-audit STEP_2_5 uses.
 
+### Check 5c — Rule File Schema (from `sdd check` [RULES])
+
+Read the [RULES] section. Each `verdict=INCOMPLETE` row is a rule file missing one of the four checkable sections; the `missing` column names them. Report as INFO with the file list, **not** as a tree FAIL: these are shared project artifacts, tracked by `rule_findings` separately from `findings` for exactly that reason. Fixing them is its own ticket, never a task reopen.
+
 ### Check 6 — File Headers (from `sdd check --files`)
 
 Pass recently modified source files to the shared checker instead of sampling by hand:
@@ -134,8 +140,9 @@ First: Self-Reflection. Then: Mechanical Checks. Use compact single-line-per-che
 
 Rules for VERDICT line:
 
-- All 8 checks PASS AND 0 protocol violations → `✅ CLEAN — artifact tree is consistent, next pickable: TSK-NN`
-- All 8 checks PASS AND 0 violations but some tasks deferred/TODO → `✅ CLEAN — <N> tasks remaining in queue`
+- All checks PASS AND 0 protocol violations → `✅ CLEAN — artifact tree is consistent, next pickable: TSK-NN`
+- All checks PASS AND 0 violations but some tasks deferred/TODO → `✅ CLEAN — <N> tasks remaining in queue`
+- Check 5c findings are INFO — they never move the verdict off `✅ CLEAN`; append `· <N> rule file(s) incomplete` to the line instead
 - Any FAIL check OR protocol violations → `❌ NOT READY — <N> issue(s) require attention`
 - Checks skipped (marked `—`) → treat as PASS for verdict unless evidence of gap exists
   </Output>

package/dist/ai/skills/sdd-execute/SKILL.md

@@ -97,13 +97,14 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
     #### Round close
     - [x] `<ts>` DONE
     ```
-    Set ticket Meta Status → `[x] DONE`.
+    Set ticket Meta Status → `[~] IN_PROGRESS`. **Not `[x] DONE` — the round is closed, not verified.** `DONE` is set in step 6, and only on audit PASS. Dependents pick on `DONE`, so setting it here advertises a task the audit has not seen yet.
 
 4a. **Sync Trackers** (MANDATORY, cannot skip):
 
-- Read `tasks/<scope>/README.md`. Find the Tracker row for this Task-ID. Set its Status → `[x] DONE`. Write back.
-- Read `tasks/README.md` Tracker Index. Update the scope's aggregate counts (done/total). Write back.
+- Read `tasks/<scope>/README.md`. Find the Tracker row for this Task-ID. Set its Status to the ticket's current Meta Status. Write back.
+- Read `tasks/README.md` Tracker Index. Update the scope's aggregate counts (done/total) — a task counts as done only at `[x] DONE`. Write back.
 - Verify: re-read both files, confirm the changes took effect. If not → retry once.
+- Run this step again after step 6 sets the final status.
 
 5.  **Dispatch AUDIT** (MANDATORY, always runs). Dispatch ONE subagent (`subagent_type: general-purpose`, **`model: "haiku"`** — audit is mechanical verification + fact-checking against artifacts; sonnet capability is overkill, haiku is faster and cheaper for this read-heavy task). Include in prompt the SDD tooling location: `~/Developer/gennady/ai/skills/sdd-execute/scripts/sdd` (audit may use `lint`, `verify`, `check-blockers` subcommands). With this prompt:
 
@@ -128,7 +129,7 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
     Wait for return. If dispatch fails → retry once. If fails again → mark task FAILED.
 
 6.  **Branch on audit status:**
-    - `PASS` or `PASS_WITH_ACKNOWLEDGED_RISKS` → ticket verified; jump to step 9 (summary).
+    - `PASS` or `PASS_WITH_ACKNOWLEDGED_RISKS` → ticket verified. **Only now** set Meta Status → `[x] DONE` and re-run step 4a so the trackers and the aggregate counts follow. Jump to step 9 (summary).
     - `FAIL` AND `audit_attempt = 1` → step 7 (resolve findings).
     - `FAIL` AND `audit_attempt = 2` → cap exhausted. Set Meta Status `[!] BLOCKED`, log `🛑 BLOCKED: audit-cap-exhausted` whose `💬 unblock:` line is the literal command `/sdd-execute <TSK-NN> --new-audit-session`, sync trackers, jump to step 9.