gennady 0.8.4-next.3 → 0.8.4-next.6

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

@@ -87,10 +87,11 @@
     </Axiom>
 
     <Axiom id="AX_FINDINGS_AS_PROPOSALS">
-      Every finding contains a proposed remediation. Agent does not modify code. Three remediation types:
+      Every finding contains a proposed remediation. Agent does not modify code. Remediation types:
       - `code-fix` — concrete change in code (with location).
       - `spec-update` — concrete spec update (module or scope) with proposed diff.
       - `ticket-update` — ticket update (canonical case names, deferred scope, etc.).
+      - `rule-file-fix` — shared rule/directive/tooling artifact; outside any task, goes to its own ticket.
     </Axiom>
 
     <Axiom id="AX_FINDING_ROUTING">
@@ -108,6 +109,7 @@
       | `INSIGHT_BACKFLOW` | spec edit (scope or module spec) |
       | `STALE_AFTER_PIVOT` | reopen / refine the affected downstream artifact |
       | `TASK_ID_DRIFT` | code-fix via ticket reopen |
+      | `RULE_FILE_INCOMPLETE` | `rule-file-fix` — the rule file is shared project infrastructure, outside every phase's Target Files. Never `ticket-update` (the ticket cannot fix it, and the paper-fix loops forever), never `phases_to_fix`, never `FAIL` for this task |
       | operator-acknowledged risk | Decision Log entry in the scope spec |
 
       The audit agent proposes a concrete edit (diff or instruction). The operator decides and applies. The audit agent does not modify code autonomously (per `AX_NO_AUTO_FIX`).
@@ -458,7 +460,7 @@
     <Contract id="FINDING_FORMAT">
       ```markdown
       ### <🔴|🟠|🟡|🔵> F-NNN — <short title>
-      - **Type:** CLOSED_WORLD_DRIFT | COMPLETENESS_GAP | RUNTIME_BACKING_VIOLATION | RULES_COMPLIANCE_VIOLATION | RULES_CASCADE_MISMATCH | TASK_ID_DRIFT | BDD_COVERAGE_MISMATCH | EXECUTION_LOG_INCOMPLETE | STALE_AFTER_PIVOT | INSIGHT_BACKFLOW
+      - **Type:** CLOSED_WORLD_DRIFT | COMPLETENESS_GAP | RUNTIME_BACKING_VIOLATION | RULES_COMPLIANCE_VIOLATION | RULES_CASCADE_MISMATCH | TASK_ID_DRIFT | BDD_COVERAGE_MISMATCH | EXECUTION_LOG_INCOMPLETE | STALE_AFTER_PIVOT | INSIGHT_BACKFLOW | RULE_FILE_INCOMPLETE
       - **Severity:** 🔴 BLOCKER | 🟠 MAJOR | 🟡 MINOR | 🔵 INFO
       - **Confidence:** HIGH | MEDIUM | LOW
       - **Status:** 📂 open | ⚠️ operator-acknowledged | ✅ resolved
@@ -482,7 +484,7 @@
 
       ```
       @audit task=<Task-ID> round=<N> mode=<per-task|epic> status=<PASS|PASS_RISK|FAIL> counts=B<n>·M<n>·m<n>·I<n> phases_to_fix=[<P<N>>,...]
-      F-<NN> | sev=<B|M|m|I> | type=<TYPETOKEN> | conf=<H|M|L> | loc=<path:line|—> | phase=<P<N>|—> | src=<spec/ticket/rule anchor|—> | route=<spec-edit|ticket-reopen|ticket-update|decision-log|code-fix> | act=<one-line action, no newlines>
+      F-<NN> | sev=<B|M|m|I> | type=<TYPETOKEN> | conf=<H|M|L> | loc=<path:line|—> | phase=<P<N>|—> | src=<spec/ticket/rule anchor|—> | route=<spec-edit|ticket-reopen|ticket-update|decision-log|code-fix|rule-file-fix> | act=<one-line action, no newlines>
       F-<NN> | …
       ~applied | <target> | <one-line description of inline change>   (optional, repeat per applied change)
       ```
@@ -490,8 +492,8 @@
       Token vocabulary:
       - `sev`: `B`=BLOCKER, `M`=MAJOR, `m`=MINOR, `I`=INFO.
       - `conf`: `H`=HIGH, `M`=MEDIUM, `L`=LOW.
-      - `type`: one of `CLOSED_WORLD_DRIFT` | `COMPLETENESS_GAP` | `RUNTIME_BACKING_VIOLATION` | `RULES_COMPLIANCE_VIOLATION` | `RULES_CASCADE_MISMATCH` | `TASK_ID_DRIFT` | `BDD_COVERAGE_MISMATCH` | `EXECUTION_LOG_INCOMPLETE` | `STALE_AFTER_PIVOT` | `INSIGHT_BACKFLOW`.
-      - `route`: one of `spec-edit` | `ticket-reopen` | `ticket-update` | `decision-log` | `code-fix` (per `AX_FINDING_ROUTING`).
+      - `type`: one of `CLOSED_WORLD_DRIFT` | `COMPLETENESS_GAP` | `RUNTIME_BACKING_VIOLATION` | `RULES_COMPLIANCE_VIOLATION` | `RULES_CASCADE_MISMATCH` | `TASK_ID_DRIFT` | `BDD_COVERAGE_MISMATCH` | `EXECUTION_LOG_INCOMPLETE` | `STALE_AFTER_PIVOT` | `INSIGHT_BACKFLOW` | `RULE_FILE_INCOMPLETE`.
+      - `route`: one of `spec-edit` | `ticket-reopen` | `ticket-update` | `decision-log` | `code-fix` | `rule-file-fix` (per `AX_FINDING_ROUTING`).
       - `act` text: Russian operator-facing per `AX_OPERATOR_LANGUAGE` (this is operator-facing artifact text), single line, no pipe character.
       - `status` `PASS_RISK` = PASS_WITH_ACKNOWLEDGED_RISKS.
 

package/ai/directives/sdd/phase-execution-protocol.xml

@@ -28,6 +28,8 @@
   <BeliefState>
     <Axiom id="AX_PHASE_SCOPE_LOCK">
       Touch only this phase's `Target Files`. Reading other files (specs, sibling-phase code, rule files cited in this phase's Rules list) is allowed and expected. Writing anywhere outside this phase's Target Files → `H_OUT_OF_PHASE_WRITE`. Operator decides via re-planning or new task.
+
+      This bounds ownership of verification failures too. A repo-wide gate that fails inside ANOTHER phase's `Target Files` is that phase's work: do not write there, do not call it resolved, do not treat it as your blocker. Record it in Handoff `open:` and continue. Everywhere else the failure is yours — including a file you never opened whose build your diff broke. Nothing outside this ticket's phases is covered by either case: that is `AX_BLOCKER_ESCALATION`.
     </Axiom>
 
 
@@ -73,7 +75,7 @@
 
     <Axiom id="AX_PERMITTED_BASH_COMMANDS">
       Phase agent may ONLY run these bash commands:
-      - **Must run:** `<sdd-path> verify <target-files>` — MANDATORY. Auto-discovers and runs typecheck, gennady DBC lint, linter, tests, and format check for the project. Runs before §5 commands. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. Failing gate → fix and re-run before EMIT_HANDOFF. Log each passing gate on a separate `ver` line.
+      - **Must run:** `<sdd-path> verify <target-files>` — MANDATORY. Auto-discovers and runs typecheck, gennady DBC lint, linter, tests, and format check for the project. Runs before §5 commands. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. Failing gate → fix and re-run before EMIT_HANDOFF. ONE `ver` line per invocation (see `STEP_5_VERIFY`).
       - **Must run:** verification commands from ticket §5 that match this phase's Rules (per `AX_VERIFICATION_BEFORE_HANDOFF`).
       - **May run:** `ls <dir>` for targeted recon (NOT `-la` or recursive); `tsc --noEmit` after code changes; `node --test <specific test file>` for test-kind phases; `date -u +%Y-%m-%dT%H:%M:%SZ` for timestamps.
       - **May run:** `<sdd-path> extract <file> <NAME>` — extract anchored section from ticket/spec.
@@ -280,11 +282,9 @@
     <Step id="STEP_5_VERIFY">
       <Goal>Run MANDATORY sdd verify on target files, then ticket §5 commands. Log only final results.</Goal>
       <Action>
-         1. **MANDATORY — sdd verify gate:** Run `<sdd-path> verify <target-files>`. This auto-discovers and executes typecheck, gennady DBC lint, linter, tests, and format check from package.json scripts. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. If any gate fails → fix ALL failures and re-run the full `sdd verify` again. Do NOT proceed to EMIT_HANDOFF until all gates pass.
-
-            **⚠️ ERROR OWNERSHIP (MANDATORY):** Every error surfaced by `<sdd-path> verify` is an error of the current session. The agent is the sole actor in this repository during the session. No error may be dismissed as «not my file», «pre-existing», «someone else's problem», or «out of scope». If `<sdd-path> verify` reports a failure in ANY file — edited, created, never touched, outside Target Files, config, spec, task, generated — the agent owns it and MUST fix it. There is no «their error». There are only errors the agent has not yet fixed. Verification is holistic; so is ownership. Fix everything.
+         1. **MANDATORY — sdd verify gate:** Run `<sdd-path> verify <target-files>`. This auto-discovers and executes typecheck, gennady DBC lint, linter, tests, and format check from package.json scripts. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. Any failure is yours to fix unless `AX_PHASE_SCOPE_LOCK` puts the file in another phase's hands — «pre-existing» and «not my file» are not available for the rest. Fix, re-run the full `sdd verify`, and do not proceed to EMIT_HANDOFF while a gate you own is red.
 
-            Each passing gate gets its own `ver` line.
+            Log ONE `ver` line for this invocation, quoting the tool's own verdict — `sdd verify` names only the gates that FAILED, so a per-gate «pass» line reports a result it never printed. That is `fabricated-verification`, same BLOCKER class as logging a §5 command you did not run.
         2. Then run ticket §5 commands per existing logic below.
         2. **MANDATORY (PROTOCOL):** Execute EACH such §5 command **verbatim — the exact string from the ticket**. No substitutions, no "equivalents", no narrower variants. If §5 says `npm run check`, run `npm run check` (not `npx vitest`, not `tsc --noEmit`, not `<sdd-path> verify`). This is the Canonical Gate (per `AX_VERIFICATION_BEFORE_HANDOFF`); fabrication is a BLOCKER-class finding at audit.
         3. **Supplemental (OPTIONAL):** You MAY additionally run `<sdd-path> verify <Target Files>` or `tsc --noEmit` for narrower diagnostics — useful for fast feedback or DBC lint. These do NOT replace §5; they add to it. Each supplemental run is logged on its own `ver` line with its real command.

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

@@ -95,7 +95,6 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
 4.  **Close Round** — append to ticket section 7:
     ```
     #### Round close
-    - [x] `<ts>` sync <scope>+root
     - [x] `<ts>` DONE
     ```
     Set ticket Meta Status → `[x] DONE`.
@@ -131,7 +130,7 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
 6.  **Branch on audit status:**
     - `PASS` or `PASS_WITH_ACKNOWLEDGED_RISKS` → ticket verified; jump to step 9 (summary).
     - `FAIL` AND `audit_attempt = 1` → step 7 (resolve findings).
-    - `FAIL` AND `audit_attempt = 2` → STOP; jump to step 9 (summary with FAIL after 2 attempts).
+    - `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.
 
 7.  **Resolve audit findings (max one retry, total 2 audit attempts):**
 
@@ -197,7 +196,8 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
 - Writing code, audit reports, or phase blocks in Execution Log. (Subagents do.)
 - Skipping audit after all phases DONE. Audit dispatch is mandatory; this is the safety net.
 - Sharing context between phase subagents and audit subagent. Each gets a fresh prompt; orchestrator threads only typed Handoff payloads.
-- Audit retry beyond 2 total attempts. Hard cap.
+- Audit retry beyond 2 attempts per session. Hard cap. Only the operator's literal `--new-audit-session` arg resets it — never your reading of «доделай» / «продолжай» / «finish it», which does not distinguish «lift the cap» from «finish what is already unblocked». No token → print the command and wait.
+- Writing a `✅ RESOLVED` marker for a blocker that is not resolved. `check-blockers` counts markers, so one makes it dispatch — that is a bug you can trigger, not permission you can grant. The marker records a fact; fabricating it is the same class as a fabricated `ver` line.
 - Re-running phases not flagged in `phases_to_fix`. The map finding-location → phase is the contract; do not "just re-run everything".
 - Auto-reopening on phase BLOCKED/FAIL. Only on audit FAIL after all phases DONE the retry kicks in.
 - Parallel dispatch of phases of the SAME task. Phases are sequential by declared `Deps`. Cross-task parallelism is the job of `sdd-execute-batch`.

package/ai/skills/sdd-execute/scripts/__tests__/verify-delegation.test.ts

@@ -1,4 +1,5 @@
-// @file: Tests for verify.sh delegation probe and the legacy classifier's mutation screen.
+// @file: Tests for verify.sh delegation probe, the legacy classifier's mutation screen, and
+//        lint-artifacts.sh surviving sync-skills path normalization.
 // @consumers: CI
 // @tasks: TSK-96
 
@@ -9,10 +10,12 @@ import os from 'node:os';
 import path from 'node:path';
 import { execFileSync, spawnSync } from 'node:child_process';
 import { fileURLToPath } from 'node:url';
+import { normalize, SYNC_SKILLS_PATH_RULES } from '../../../../../shared/common/sync/path-normalizer.ts';
 
 const SCRIPTS_DIR = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..');
 const VERIFY_SH = path.join(SCRIPTS_DIR, 'verify.sh');
 const CLASSIFIER = path.join(SCRIPTS_DIR, 'classify-scripts.js');
+const LINT_ARTIFACTS_SH = path.join(SCRIPTS_DIR, 'lint-artifacts.sh');
 
 /** @purpose Create a temp fixture with files, run fn, clean up. */
 function withFixture<T>(files: Record<string, string>, fn: (dir: string) => T): T {
@@ -85,6 +88,74 @@ describe('verify.sh capability probe', () => {
   });
 });
 
+/**
+ * @purpose Write the sync-skills-normalized copy of lint-artifacts.sh into dir and run it.
+ * @param dir Temp directory acting as the deployed project root.
+ * @param fakeGennady Shim body to expose as `gennady` on PATH; empty string exposes none.
+ * @returns Exit status and merged stdout/stderr of the deployed copy.
+ */
+function runDeployedLint(
+  dir: string,
+  fakeGennady: string
+): { status: number | null; out: string } {
+  const deployed = path.join(dir, 'lint-artifacts.sh');
+  fs.writeFileSync(
+    deployed,
+    normalize(fs.readFileSync(LINT_ARTIFACTS_SH, 'utf-8'), SYNC_SKILLS_PATH_RULES)
+  );
+  fs.chmodSync(deployed, 0o755);
+
+  const bin = path.join(dir, '_bin');
+  fs.mkdirSync(bin, { recursive: true });
+  if (fakeGennady !== '') {
+    const fake = path.join(bin, 'gennady');
+    fs.writeFileSync(fake, fakeGennady);
+    fs.chmodSync(fake, 0o755);
+  }
+
+  // GENNADY_HOME points at an empty dir so only PATH resolution can succeed.
+  const proc = spawnSync('bash', [deployed, 'target.ts'], {
+    cwd: dir,
+    encoding: 'utf-8',
+    env: { ...process.env, PATH: `${bin}:${process.env.PATH}`, GENNADY_HOME: bin },
+  });
+  return { status: proc.status, out: `${proc.stdout}${proc.stderr}` };
+}
+
+describe('lint-artifacts.sh after sync-skills normalization', () => {
+  // Regression: the CLI path used to live in `GENNADY_CLI=~/Developer/gennady/cli/gennady.ts`.
+  // PathNormalizer rewrote it to `GENNADY_CLI=npx gennady` — an assignment-prefixed command, not an
+  // assignment — so the variable stayed unset and `set -u` killed every deployed copy on first use.
+  it('resolves gennady from PATH instead of a normalization-mangled path literal', () => {
+    withFixture({ 'target.ts': 'export const x = 1;\n' }, (dir) => {
+      const { status, out } = runDeployedLint(
+        dir,
+        '#!/usr/bin/env bash\necho "[linting → clean] no errors"\nexit 0\n'
+      );
+
+      assert.equal(status, 0, out);
+      assert.match(out, /LINT_PASS/);
+      assert.ok(!out.includes('unbound variable'), `must not die on set -u: ${out}`);
+    });
+  });
+
+  it('reports an actionable miss — never an unbound variable — when gennady is unreachable', () => {
+    withFixture({ 'target.ts': 'export const x = 1;\n' }, (dir) => {
+      const { status, out } = runDeployedLint(dir, '');
+
+      assert.equal(status, 1, out);
+      assert.match(out, /GENNADY_CLI_NOT_FOUND/);
+      assert.ok(!out.includes('unbound variable'), `must not die on set -u: ${out}`);
+    });
+  });
+
+  it('carries no foreign absolute path into the deployed copy', () => {
+    const deployed = normalize(fs.readFileSync(LINT_ARTIFACTS_SH, 'utf-8'), SYNC_SKILLS_PATH_RULES);
+
+    assert.ok(!/\/Users\//.test(deployed), 'deployed skill must not reference a developer home');
+  });
+});
+
 describe('classify-scripts.js mutation screen', () => {
   it('classifies --fix/--autofix/--write bodies as mutating and never selects them', () => {
     withFixture(

package/ai/skills/sdd-execute/scripts/lint-artifacts.sh

@@ -4,7 +4,10 @@
 # @contract: AX_BASH_NO_SILENT_EMPTY — never produces empty stdout. On miss → actionable instruction.
 #
 # Why this wrapper exists:
-#   - gennady CLI lives outside the project (canonical: ~/Developer/gennady/cli/gennady.ts).
+#   - gennady CLI may live outside the project; resolution is done at RUNTIME (see resolve_gennady).
+#     It MUST NOT be a bare dev-path literal assigned to a variable: `sync-skills` rewrites dev paths
+#     through PathNormalizer, which turned that assignment into an unquoted two-word command, leaving
+#     the variable unset — every deployed copy then died on `set -u`. Keep this file path-literal-free.
 #   - gennady requires `node --experimental-strip-types` (Node 22+) — the bare `node` invocation is non-obvious.
 #   - gennady returns exit code 0 even when lint reports errors (the failure signal is the literal token
 #     "[linting → failed]" in stdout). We must parse output, not trust exit code.
@@ -23,7 +26,29 @@
 set -uo pipefail
 
 PROG="lint-artifacts"
-GENNADY_CLI=~/Developer/gennady/cli/gennady.ts
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# Repo root of a gennady checkout: scripts → sdd-execute → skills → ai → root.
+GENNADY_HOME="${GENNADY_HOME:-$SCRIPT_DIR/../../../..}"
+
+# Runtime resolution — deliberately contains no dev-path literal, so PathNormalizer has
+# nothing to rewrite and the deployed copy behaves identically to the checkout copy.
+GENNADY_ARGV=()
+resolve_gennady() {
+    if command -v gennady &>/dev/null; then
+        GENNADY_ARGV=(gennady)
+        return 0
+    fi
+    if [[ -x "$GENNADY_HOME/node_modules/.bin/tsx" && -f "$GENNADY_HOME/cli/gennady.ts" ]]; then
+        GENNADY_ARGV=("$GENNADY_HOME/node_modules/.bin/tsx" "$GENNADY_HOME/cli/gennady.ts")
+        return 0
+    fi
+    if [[ -x "./node_modules/.bin/gennady" ]]; then
+        GENNADY_ARGV=(./node_modules/.bin/gennady)
+        return 0
+    fi
+    return 1
+}
 
 if [[ $# -lt 1 ]]; then
     cat <<EOF
@@ -38,16 +63,18 @@ EOF
     exit 4
 fi
 
-if [[ ! -f "$GENNADY_CLI" ]]; then
+if ! resolve_gennady; then
     cat <<EOF
 [$PROG] GENNADY_CLI_NOT_FOUND
-  expected at: $GENNADY_CLI
+  tried: gennady on PATH
+         \$GENNADY_HOME/cli/gennady.ts via checkout tsx (GENNADY_HOME=$GENNADY_HOME)
+         ./node_modules/.bin/gennady
 
 Diagnosis: the gennady AST DbC linter is unreachable from this environment.
 
 Required action (ORCHESTRATOR):
-  1. Verify the gennady project is checked out at ~/Developer/gennady.
-  2. If gennady moved → update GENNADY_CLI variable in this script.
+  1. Install it in the project (\`npm i -D gennady\`) or put it on PATH.
+  2. Working from a gennady checkout → export GENNADY_HOME=<checkout-root>.
   3. If on a CI/sandbox without gennady → this is a HARD blocker; phase cannot verify.
      Report to operator: cannot complete phase without DBC contract verification.
 
@@ -65,7 +92,7 @@ tmp_out=$(mktemp -t lint-artifacts.XXXXXX)
 trap 'rm -f "$tmp_out"' EXIT
 
 # Run gennady. We intentionally ignore its exit code (unreliable per contract above).
-npx tsx "$GENNADY_CLI" lint "$@" > "$tmp_out" 2>&1 || true
+"${GENNADY_ARGV[@]}" lint "$@" > "$tmp_out" 2>&1 || true
 
 has_clean=$(grep -c '\[linting → clean\]' "$tmp_out" 2>/dev/null || echo 0)
 has_failed=$(grep -c '\[linting → failed\]' "$tmp_out" 2>/dev/null || echo 0)
@@ -108,7 +135,7 @@ Required action (PHASE AGENT, before EMIT_HANDOFF):
   5. Do NOT EMIT_HANDOFF with lint failures present — that is fabricated DONE.
 
 References:
-  /Users/k.lebedev/Developer/vkt/ai/directives/coding/typescript-rules.xml
+  ai/directives/coding/typescript-rules.xml
   — AX_TAG_USAGE_MATRIX, AX_BASE_CONTRACT_SHAPE, AX_FLAT_JSDOC_FOR_PROPERTIES
 EOF
     exit 2
@@ -135,7 +162,7 @@ Captured output:
 $(cat "$tmp_out" | head -50)
 
 Required action (ORCHESTRATOR):
-  1. Re-read gennady source: ~/Developer/gennady/cli/gennady.ts
+  1. Re-read the gennady LintCommand source in the checkout you resolved above.
   2. Check command output tokens in the LintCommand implementation.
   3. Update this script's parsing to match new tokens.
   4. Until resolved → treat as a HARD blocker; DO NOT assume PASS.

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

@@ -174,7 +174,7 @@ run_cmd() {
 while IFS=: read cls name; do
   case "$cls" in
     typecheck) run_cmd "typecheck" "npm run $name" npm run "$name" || true ;;
-    gennady)   run_cmd "gennady DBC lint" "gennady lint ${#FILES[@]} files" npx tsx ~/Developer/gennady/cli/gennady.ts lint "${FILES[@]}" || true ;;
+    gennady)   run_cmd "gennady DBC lint" "gennady lint ${#FILES[@]} files" "$SCRIPT_DIR/lint-artifacts.sh" "${FILES[@]}" || true ;;
     lint)      run_cmd "lint" "npm run $name" npm run "$name" || true ;;
     test)      run_cmd "test" "npm run $name" npm run "$name" || true ;;
     format)    run_cmd "format check" "npm run $name" npm run "$name" || true ;;

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

@@ -125,12 +125,13 @@ Per-task phase tokens:
                 ```
 
             b. Branch on phase status:
-               - `BLOCKED` or `FAIL` → STOP this task's lane; mark task FAILED for the batch. Other parallel tasks in same sub-batch continue.
+               - `BLOCKED` on a repo-wide gate failing in files this ticket does not own → PARK the lane, do not fail it. Parallel lanes share one working tree, so that is usually a sibling lane mid-flight. Resume each parked lane once after the sub-batch drains; still blocked → `✋ AWAITING UNBLOCK`, not `❌ FAILED`.
+               - `BLOCKED` or `FAIL` otherwise → STOP this task's lane; mark task FAILED for the batch. Other parallel tasks in same sub-batch continue.
                - `DONE` → record Handoff (artifacts, decisions, open). Continue to next phase.
 
             c. Thread next phase's Inputs from this phase's Handoff (verbatim).
 
-          After all phases DONE: close Round (append `#### Round close` block: sync + DONE). Sync trackers. Ticket Status → `[x] DONE`.
+          After all phases DONE: close Round (append `#### Round close` block per `ROUND_CLOSE_FORMAT`: a single `DONE` line). Sync trackers. Ticket Status → `[x] DONE`.
 
            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):
               ```
@@ -161,7 +162,7 @@ Per-task phase tokens:
                  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.
-                 FAIL (audit_attempt = 2) → STOP lane; mark task FAILED.
+                 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.
          — Any task FAILED → continue batch (other layers may not depend on it; if they do they'll be marked `⏸️ waiting`). Operator gets failure list in final summary.
@@ -202,7 +203,8 @@ Per-task phase tokens:
 - Writing code or phase blocks in Execution Log. (Phase subagents do.)
 - Sharing context between phase subagents of different tasks. Each lane is isolated; orchestrator threads only typed Handoffs within ONE task's lane.
 - Skipping audit after Round close in default (per-task) mode. Audit dispatch is mandatory.
-- Audit retry beyond 2 total attempts per task. Hard cap.
+- Audit retry beyond 2 attempts per task per session. Hard cap; only the operator's literal `--new-audit-session` arg resets it, and only via the sibling `sdd-execute` skill.
+- Writing a `✅ RESOLVED` marker for a blocker that is not resolved, to get past the `check-blockers` preflight. The marker records a fact, not permission.
 - Re-running phases not flagged in `phases_to_fix`. The map finding-location → phase is the contract.
 - Parallel dispatch ACROSS layers. Layers run sequentially.
 - Parallel dispatch ACROSS sub-batches in same layer. Sub-batches exist exactly because of file conflicts.

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

@@ -87,10 +87,11 @@
     </Axiom>
 
     <Axiom id="AX_FINDINGS_AS_PROPOSALS">
-      Every finding contains a proposed remediation. Agent does not modify code. Three remediation types:
+      Every finding contains a proposed remediation. Agent does not modify code. Remediation types:
       - `code-fix` — concrete change in code (with location).
       - `spec-update` — concrete spec update (module or scope) with proposed diff.
       - `ticket-update` — ticket update (canonical case names, deferred scope, etc.).
+      - `rule-file-fix` — shared rule/directive/tooling artifact; outside any task, goes to its own ticket.
     </Axiom>
 
     <Axiom id="AX_FINDING_ROUTING">
@@ -108,6 +109,7 @@
       | `INSIGHT_BACKFLOW` | spec edit (scope or module spec) |
       | `STALE_AFTER_PIVOT` | reopen / refine the affected downstream artifact |
       | `TASK_ID_DRIFT` | code-fix via ticket reopen |
+      | `RULE_FILE_INCOMPLETE` | `rule-file-fix` — the rule file is shared project infrastructure, outside every phase's Target Files. Never `ticket-update` (the ticket cannot fix it, and the paper-fix loops forever), never `phases_to_fix`, never `FAIL` for this task |
       | operator-acknowledged risk | Decision Log entry in the scope spec |
 
       The audit agent proposes a concrete edit (diff or instruction). The operator decides and applies. The audit agent does not modify code autonomously (per `AX_NO_AUTO_FIX`).
@@ -458,7 +460,7 @@
     <Contract id="FINDING_FORMAT">
       ```markdown
       ### <🔴|🟠|🟡|🔵> F-NNN — <short title>
-      - **Type:** CLOSED_WORLD_DRIFT | COMPLETENESS_GAP | RUNTIME_BACKING_VIOLATION | RULES_COMPLIANCE_VIOLATION | RULES_CASCADE_MISMATCH | TASK_ID_DRIFT | BDD_COVERAGE_MISMATCH | EXECUTION_LOG_INCOMPLETE | STALE_AFTER_PIVOT | INSIGHT_BACKFLOW
+      - **Type:** CLOSED_WORLD_DRIFT | COMPLETENESS_GAP | RUNTIME_BACKING_VIOLATION | RULES_COMPLIANCE_VIOLATION | RULES_CASCADE_MISMATCH | TASK_ID_DRIFT | BDD_COVERAGE_MISMATCH | EXECUTION_LOG_INCOMPLETE | STALE_AFTER_PIVOT | INSIGHT_BACKFLOW | RULE_FILE_INCOMPLETE
       - **Severity:** 🔴 BLOCKER | 🟠 MAJOR | 🟡 MINOR | 🔵 INFO
       - **Confidence:** HIGH | MEDIUM | LOW
       - **Status:** 📂 open | ⚠️ operator-acknowledged | ✅ resolved
@@ -482,7 +484,7 @@
 
       ```
       @audit task=<Task-ID> round=<N> mode=<per-task|epic> status=<PASS|PASS_RISK|FAIL> counts=B<n>·M<n>·m<n>·I<n> phases_to_fix=[<P<N>>,...]
-      F-<NN> | sev=<B|M|m|I> | type=<TYPETOKEN> | conf=<H|M|L> | loc=<path:line|—> | phase=<P<N>|—> | src=<spec/ticket/rule anchor|—> | route=<spec-edit|ticket-reopen|ticket-update|decision-log|code-fix> | act=<one-line action, no newlines>
+      F-<NN> | sev=<B|M|m|I> | type=<TYPETOKEN> | conf=<H|M|L> | loc=<path:line|—> | phase=<P<N>|—> | src=<spec/ticket/rule anchor|—> | route=<spec-edit|ticket-reopen|ticket-update|decision-log|code-fix|rule-file-fix> | act=<one-line action, no newlines>
       F-<NN> | …
       ~applied | <target> | <one-line description of inline change>   (optional, repeat per applied change)
       ```
@@ -490,8 +492,8 @@
       Token vocabulary:
       - `sev`: `B`=BLOCKER, `M`=MAJOR, `m`=MINOR, `I`=INFO.
       - `conf`: `H`=HIGH, `M`=MEDIUM, `L`=LOW.
-      - `type`: one of `CLOSED_WORLD_DRIFT` | `COMPLETENESS_GAP` | `RUNTIME_BACKING_VIOLATION` | `RULES_COMPLIANCE_VIOLATION` | `RULES_CASCADE_MISMATCH` | `TASK_ID_DRIFT` | `BDD_COVERAGE_MISMATCH` | `EXECUTION_LOG_INCOMPLETE` | `STALE_AFTER_PIVOT` | `INSIGHT_BACKFLOW`.
-      - `route`: one of `spec-edit` | `ticket-reopen` | `ticket-update` | `decision-log` | `code-fix` (per `AX_FINDING_ROUTING`).
+      - `type`: one of `CLOSED_WORLD_DRIFT` | `COMPLETENESS_GAP` | `RUNTIME_BACKING_VIOLATION` | `RULES_COMPLIANCE_VIOLATION` | `RULES_CASCADE_MISMATCH` | `TASK_ID_DRIFT` | `BDD_COVERAGE_MISMATCH` | `EXECUTION_LOG_INCOMPLETE` | `STALE_AFTER_PIVOT` | `INSIGHT_BACKFLOW` | `RULE_FILE_INCOMPLETE`.
+      - `route`: one of `spec-edit` | `ticket-reopen` | `ticket-update` | `decision-log` | `code-fix` | `rule-file-fix` (per `AX_FINDING_ROUTING`).
       - `act` text: Russian operator-facing per `AX_OPERATOR_LANGUAGE` (this is operator-facing artifact text), single line, no pipe character.
       - `status` `PASS_RISK` = PASS_WITH_ACKNOWLEDGED_RISKS.
 

package/dist/ai/directives/sdd/phase-execution-protocol.xml

@@ -28,6 +28,8 @@
   <BeliefState>
     <Axiom id="AX_PHASE_SCOPE_LOCK">
       Touch only this phase's `Target Files`. Reading other files (specs, sibling-phase code, rule files cited in this phase's Rules list) is allowed and expected. Writing anywhere outside this phase's Target Files → `H_OUT_OF_PHASE_WRITE`. Operator decides via re-planning or new task.
+
+      This bounds ownership of verification failures too. A repo-wide gate that fails inside ANOTHER phase's `Target Files` is that phase's work: do not write there, do not call it resolved, do not treat it as your blocker. Record it in Handoff `open:` and continue. Everywhere else the failure is yours — including a file you never opened whose build your diff broke. Nothing outside this ticket's phases is covered by either case: that is `AX_BLOCKER_ESCALATION`.
     </Axiom>
 
 
@@ -73,7 +75,7 @@
 
     <Axiom id="AX_PERMITTED_BASH_COMMANDS">
       Phase agent may ONLY run these bash commands:
-      - **Must run:** `<sdd-path> verify <target-files>` — MANDATORY. Auto-discovers and runs typecheck, gennady DBC lint, linter, tests, and format check for the project. Runs before §5 commands. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. Failing gate → fix and re-run before EMIT_HANDOFF. Log each passing gate on a separate `ver` line.
+      - **Must run:** `<sdd-path> verify <target-files>` — MANDATORY. Auto-discovers and runs typecheck, gennady DBC lint, linter, tests, and format check for the project. Runs before §5 commands. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. Failing gate → fix and re-run before EMIT_HANDOFF. ONE `ver` line per invocation (see `STEP_5_VERIFY`).
       - **Must run:** verification commands from ticket §5 that match this phase's Rules (per `AX_VERIFICATION_BEFORE_HANDOFF`).
       - **May run:** `ls <dir>` for targeted recon (NOT `-la` or recursive); `tsc --noEmit` after code changes; `node --test <specific test file>` for test-kind phases; `date -u +%Y-%m-%dT%H:%M:%SZ` for timestamps.
       - **May run:** `<sdd-path> extract <file> <NAME>` — extract anchored section from ticket/spec.
@@ -280,11 +282,9 @@
     <Step id="STEP_5_VERIFY">
       <Goal>Run MANDATORY sdd verify on target files, then ticket §5 commands. Log only final results.</Goal>
       <Action>
-         1. **MANDATORY — sdd verify gate:** Run `<sdd-path> verify <target-files>`. This auto-discovers and executes typecheck, gennady DBC lint, linter, tests, and format check from package.json scripts. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. If any gate fails → fix ALL failures and re-run the full `sdd verify` again. Do NOT proceed to EMIT_HANDOFF until all gates pass.
-
-            **⚠️ ERROR OWNERSHIP (MANDATORY):** Every error surfaced by `<sdd-path> verify` is an error of the current session. The agent is the sole actor in this repository during the session. No error may be dismissed as «not my file», «pre-existing», «someone else's problem», or «out of scope». If `<sdd-path> verify` reports a failure in ANY file — edited, created, never touched, outside Target Files, config, spec, task, generated — the agent owns it and MUST fix it. There is no «their error». There are only errors the agent has not yet fixed. Verification is holistic; so is ownership. Fix everything.
+         1. **MANDATORY — sdd verify gate:** Run `<sdd-path> verify <target-files>`. This auto-discovers and executes typecheck, gennady DBC lint, linter, tests, and format check from package.json scripts. **RUN-ALL**: every gate executes regardless of previous failures; failures accumulate. **SUPPRESS-ON-SUCCESS**: passing gates produce zero output; only failed gates dump their command, exit code, and captured output. On all-pass: single summary line. Any failure is yours to fix unless `AX_PHASE_SCOPE_LOCK` puts the file in another phase's hands — «pre-existing» and «not my file» are not available for the rest. Fix, re-run the full `sdd verify`, and do not proceed to EMIT_HANDOFF while a gate you own is red.
 
-            Each passing gate gets its own `ver` line.
+            Log ONE `ver` line for this invocation, quoting the tool's own verdict — `sdd verify` names only the gates that FAILED, so a per-gate «pass» line reports a result it never printed. That is `fabricated-verification`, same BLOCKER class as logging a §5 command you did not run.
         2. Then run ticket §5 commands per existing logic below.
         2. **MANDATORY (PROTOCOL):** Execute EACH such §5 command **verbatim — the exact string from the ticket**. No substitutions, no "equivalents", no narrower variants. If §5 says `npm run check`, run `npm run check` (not `npx vitest`, not `tsc --noEmit`, not `<sdd-path> verify`). This is the Canonical Gate (per `AX_VERIFICATION_BEFORE_HANDOFF`); fabrication is a BLOCKER-class finding at audit.
         3. **Supplemental (OPTIONAL):** You MAY additionally run `<sdd-path> verify <Target Files>` or `tsc --noEmit` for narrower diagnostics — useful for fast feedback or DBC lint. These do NOT replace §5; they add to it. Each supplemental run is logged on its own `ver` line with its real command.

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

@@ -95,7 +95,6 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
 4.  **Close Round** — append to ticket section 7:
     ```
     #### Round close
-    - [x] `<ts>` sync <scope>+root
     - [x] `<ts>` DONE
     ```
     Set ticket Meta Status → `[x] DONE`.
@@ -131,7 +130,7 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
 6.  **Branch on audit status:**
     - `PASS` or `PASS_WITH_ACKNOWLEDGED_RISKS` → ticket verified; jump to step 9 (summary).
     - `FAIL` AND `audit_attempt = 1` → step 7 (resolve findings).
-    - `FAIL` AND `audit_attempt = 2` → STOP; jump to step 9 (summary with FAIL after 2 attempts).
+    - `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.
 
 7.  **Resolve audit findings (max one retry, total 2 audit attempts):**
 
@@ -197,7 +196,8 @@ Pause path (distinguish from failure — skill is awaiting operator, not broken)
 - Writing code, audit reports, or phase blocks in Execution Log. (Subagents do.)
 - Skipping audit after all phases DONE. Audit dispatch is mandatory; this is the safety net.
 - Sharing context between phase subagents and audit subagent. Each gets a fresh prompt; orchestrator threads only typed Handoff payloads.
-- Audit retry beyond 2 total attempts. Hard cap.
+- Audit retry beyond 2 attempts per session. Hard cap. Only the operator's literal `--new-audit-session` arg resets it — never your reading of «доделай» / «продолжай» / «finish it», which does not distinguish «lift the cap» from «finish what is already unblocked». No token → print the command and wait.
+- Writing a `✅ RESOLVED` marker for a blocker that is not resolved. `check-blockers` counts markers, so one makes it dispatch — that is a bug you can trigger, not permission you can grant. The marker records a fact; fabricating it is the same class as a fabricated `ver` line.
 - Re-running phases not flagged in `phases_to_fix`. The map finding-location → phase is the contract; do not "just re-run everything".
 - Auto-reopening on phase BLOCKED/FAIL. Only on audit FAIL after all phases DONE the retry kicks in.
 - Parallel dispatch of phases of the SAME task. Phases are sequential by declared `Deps`. Cross-task parallelism is the job of `sdd-execute-batch`.

package/dist/ai/skills/sdd-execute/scripts/__tests__/verify-delegation.test.ts

@@ -1,4 +1,5 @@
-// @file: Tests for verify.sh delegation probe and the legacy classifier's mutation screen.
+// @file: Tests for verify.sh delegation probe, the legacy classifier's mutation screen, and
+//        lint-artifacts.sh surviving sync-skills path normalization.
 // @consumers: CI
 // @tasks: TSK-96
 
@@ -9,10 +10,12 @@ import os from 'node:os';
 import path from 'node:path';
 import { execFileSync, spawnSync } from 'node:child_process';
 import { fileURLToPath } from 'node:url';
+import { normalize, SYNC_SKILLS_PATH_RULES } from '../../../../../shared/common/sync/path-normalizer.ts';
 
 const SCRIPTS_DIR = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..');
 const VERIFY_SH = path.join(SCRIPTS_DIR, 'verify.sh');
 const CLASSIFIER = path.join(SCRIPTS_DIR, 'classify-scripts.js');
+const LINT_ARTIFACTS_SH = path.join(SCRIPTS_DIR, 'lint-artifacts.sh');
 
 /** @purpose Create a temp fixture with files, run fn, clean up. */
 function withFixture<T>(files: Record<string, string>, fn: (dir: string) => T): T {
@@ -85,6 +88,74 @@ describe('verify.sh capability probe', () => {
   });
 });
 
+/**
+ * @purpose Write the sync-skills-normalized copy of lint-artifacts.sh into dir and run it.
+ * @param dir Temp directory acting as the deployed project root.
+ * @param fakeGennady Shim body to expose as `gennady` on PATH; empty string exposes none.
+ * @returns Exit status and merged stdout/stderr of the deployed copy.
+ */
+function runDeployedLint(
+  dir: string,
+  fakeGennady: string
+): { status: number | null; out: string } {
+  const deployed = path.join(dir, 'lint-artifacts.sh');
+  fs.writeFileSync(
+    deployed,
+    normalize(fs.readFileSync(LINT_ARTIFACTS_SH, 'utf-8'), SYNC_SKILLS_PATH_RULES)
+  );
+  fs.chmodSync(deployed, 0o755);
+
+  const bin = path.join(dir, '_bin');
+  fs.mkdirSync(bin, { recursive: true });
+  if (fakeGennady !== '') {
+    const fake = path.join(bin, 'gennady');
+    fs.writeFileSync(fake, fakeGennady);
+    fs.chmodSync(fake, 0o755);
+  }
+
+  // GENNADY_HOME points at an empty dir so only PATH resolution can succeed.
+  const proc = spawnSync('bash', [deployed, 'target.ts'], {
+    cwd: dir,
+    encoding: 'utf-8',
+    env: { ...process.env, PATH: `${bin}:${process.env.PATH}`, GENNADY_HOME: bin },
+  });
+  return { status: proc.status, out: `${proc.stdout}${proc.stderr}` };
+}
+
+describe('lint-artifacts.sh after sync-skills normalization', () => {
+  // Regression: the CLI path used to live in `GENNADY_CLI=~/Developer/gennady/cli/gennady.ts`.
+  // PathNormalizer rewrote it to `GENNADY_CLI=npx gennady` — an assignment-prefixed command, not an
+  // assignment — so the variable stayed unset and `set -u` killed every deployed copy on first use.
+  it('resolves gennady from PATH instead of a normalization-mangled path literal', () => {
+    withFixture({ 'target.ts': 'export const x = 1;\n' }, (dir) => {
+      const { status, out } = runDeployedLint(
+        dir,
+        '#!/usr/bin/env bash\necho "[linting → clean] no errors"\nexit 0\n'
+      );
+
+      assert.equal(status, 0, out);
+      assert.match(out, /LINT_PASS/);
+      assert.ok(!out.includes('unbound variable'), `must not die on set -u: ${out}`);
+    });
+  });
+
+  it('reports an actionable miss — never an unbound variable — when gennady is unreachable', () => {
+    withFixture({ 'target.ts': 'export const x = 1;\n' }, (dir) => {
+      const { status, out } = runDeployedLint(dir, '');
+
+      assert.equal(status, 1, out);
+      assert.match(out, /GENNADY_CLI_NOT_FOUND/);
+      assert.ok(!out.includes('unbound variable'), `must not die on set -u: ${out}`);
+    });
+  });
+
+  it('carries no foreign absolute path into the deployed copy', () => {
+    const deployed = normalize(fs.readFileSync(LINT_ARTIFACTS_SH, 'utf-8'), SYNC_SKILLS_PATH_RULES);
+
+    assert.ok(!/\/Users\//.test(deployed), 'deployed skill must not reference a developer home');
+  });
+});
+
 describe('classify-scripts.js mutation screen', () => {
   it('classifies --fix/--autofix/--write bodies as mutating and never selects them', () => {
     withFixture(

package/dist/ai/skills/sdd-execute/scripts/lint-artifacts.sh

@@ -4,7 +4,10 @@
 # @contract: AX_BASH_NO_SILENT_EMPTY — never produces empty stdout. On miss → actionable instruction.
 #
 # Why this wrapper exists:
-#   - gennady CLI lives outside the project (canonical: ~/Developer/gennady/cli/gennady.ts).
+#   - gennady CLI may live outside the project; resolution is done at RUNTIME (see resolve_gennady).
+#     It MUST NOT be a bare dev-path literal assigned to a variable: `sync-skills` rewrites dev paths
+#     through PathNormalizer, which turned that assignment into an unquoted two-word command, leaving
+#     the variable unset — every deployed copy then died on `set -u`. Keep this file path-literal-free.
 #   - gennady requires `node --experimental-strip-types` (Node 22+) — the bare `node` invocation is non-obvious.
 #   - gennady returns exit code 0 even when lint reports errors (the failure signal is the literal token
 #     "[linting → failed]" in stdout). We must parse output, not trust exit code.
@@ -23,7 +26,29 @@
 set -uo pipefail
 
 PROG="lint-artifacts"
-GENNADY_CLI=~/Developer/gennady/cli/gennady.ts
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# Repo root of a gennady checkout: scripts → sdd-execute → skills → ai → root.
+GENNADY_HOME="${GENNADY_HOME:-$SCRIPT_DIR/../../../..}"
+
+# Runtime resolution — deliberately contains no dev-path literal, so PathNormalizer has
+# nothing to rewrite and the deployed copy behaves identically to the checkout copy.
+GENNADY_ARGV=()
+resolve_gennady() {
+    if command -v gennady &>/dev/null; then
+        GENNADY_ARGV=(gennady)
+        return 0
+    fi
+    if [[ -x "$GENNADY_HOME/node_modules/.bin/tsx" && -f "$GENNADY_HOME/cli/gennady.ts" ]]; then
+        GENNADY_ARGV=("$GENNADY_HOME/node_modules/.bin/tsx" "$GENNADY_HOME/cli/gennady.ts")
+        return 0
+    fi
+    if [[ -x "./node_modules/.bin/gennady" ]]; then
+        GENNADY_ARGV=(./node_modules/.bin/gennady)
+        return 0
+    fi
+    return 1
+}
 
 if [[ $# -lt 1 ]]; then
     cat <<EOF
@@ -38,16 +63,18 @@ EOF
     exit 4
 fi
 
-if [[ ! -f "$GENNADY_CLI" ]]; then
+if ! resolve_gennady; then
     cat <<EOF
 [$PROG] GENNADY_CLI_NOT_FOUND
-  expected at: $GENNADY_CLI
+  tried: gennady on PATH
+         \$GENNADY_HOME/cli/gennady.ts via checkout tsx (GENNADY_HOME=$GENNADY_HOME)
+         ./node_modules/.bin/gennady
 
 Diagnosis: the gennady AST DbC linter is unreachable from this environment.
 
 Required action (ORCHESTRATOR):
-  1. Verify the gennady project is checked out at ~/Developer/gennady.
-  2. If gennady moved → update GENNADY_CLI variable in this script.
+  1. Install it in the project (\`npm i -D gennady\`) or put it on PATH.
+  2. Working from a gennady checkout → export GENNADY_HOME=<checkout-root>.
   3. If on a CI/sandbox without gennady → this is a HARD blocker; phase cannot verify.
      Report to operator: cannot complete phase without DBC contract verification.
 
@@ -65,7 +92,7 @@ tmp_out=$(mktemp -t lint-artifacts.XXXXXX)
 trap 'rm -f "$tmp_out"' EXIT
 
 # Run gennady. We intentionally ignore its exit code (unreliable per contract above).
-npx tsx "$GENNADY_CLI" lint "$@" > "$tmp_out" 2>&1 || true
+"${GENNADY_ARGV[@]}" lint "$@" > "$tmp_out" 2>&1 || true
 
 has_clean=$(grep -c '\[linting → clean\]' "$tmp_out" 2>/dev/null || echo 0)
 has_failed=$(grep -c '\[linting → failed\]' "$tmp_out" 2>/dev/null || echo 0)
@@ -108,7 +135,7 @@ Required action (PHASE AGENT, before EMIT_HANDOFF):
   5. Do NOT EMIT_HANDOFF with lint failures present — that is fabricated DONE.
 
 References:
-  /Users/k.lebedev/Developer/vkt/ai/directives/coding/typescript-rules.xml
+  ai/directives/coding/typescript-rules.xml
   — AX_TAG_USAGE_MATRIX, AX_BASE_CONTRACT_SHAPE, AX_FLAT_JSDOC_FOR_PROPERTIES
 EOF
     exit 2
@@ -135,7 +162,7 @@ Captured output:
 $(cat "$tmp_out" | head -50)
 
 Required action (ORCHESTRATOR):
-  1. Re-read gennady source: ~/Developer/gennady/cli/gennady.ts
+  1. Re-read the gennady LintCommand source in the checkout you resolved above.
   2. Check command output tokens in the LintCommand implementation.
   3. Update this script's parsing to match new tokens.
   4. Until resolved → treat as a HARD blocker; DO NOT assume PASS.

package/dist/ai/skills/sdd-execute/scripts/verify.sh

@@ -174,7 +174,7 @@ run_cmd() {
 while IFS=: read cls name; do
   case "$cls" in
     typecheck) run_cmd "typecheck" "npm run $name" npm run "$name" || true ;;
-    gennady)   run_cmd "gennady DBC lint" "gennady lint ${#FILES[@]} files" npx tsx ~/Developer/gennady/cli/gennady.ts lint "${FILES[@]}" || true ;;
+    gennady)   run_cmd "gennady DBC lint" "gennady lint ${#FILES[@]} files" "$SCRIPT_DIR/lint-artifacts.sh" "${FILES[@]}" || true ;;
     lint)      run_cmd "lint" "npm run $name" npm run "$name" || true ;;
     test)      run_cmd "test" "npm run $name" npm run "$name" || true ;;
     format)    run_cmd "format check" "npm run $name" npm run "$name" || true ;;

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

@@ -125,12 +125,13 @@ Per-task phase tokens:
                 ```
 
             b. Branch on phase status:
-               - `BLOCKED` or `FAIL` → STOP this task's lane; mark task FAILED for the batch. Other parallel tasks in same sub-batch continue.
+               - `BLOCKED` on a repo-wide gate failing in files this ticket does not own → PARK the lane, do not fail it. Parallel lanes share one working tree, so that is usually a sibling lane mid-flight. Resume each parked lane once after the sub-batch drains; still blocked → `✋ AWAITING UNBLOCK`, not `❌ FAILED`.
+               - `BLOCKED` or `FAIL` otherwise → STOP this task's lane; mark task FAILED for the batch. Other parallel tasks in same sub-batch continue.
                - `DONE` → record Handoff (artifacts, decisions, open). Continue to next phase.
 
             c. Thread next phase's Inputs from this phase's Handoff (verbatim).
 
-          After all phases DONE: close Round (append `#### Round close` block: sync + DONE). Sync trackers. Ticket Status → `[x] DONE`.
+          After all phases DONE: close Round (append `#### Round close` block per `ROUND_CLOSE_FORMAT`: a single `DONE` line). Sync trackers. Ticket Status → `[x] DONE`.
 
            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):
               ```
@@ -161,7 +162,7 @@ Per-task phase tokens:
                  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.
-                 FAIL (audit_attempt = 2) → STOP lane; mark task FAILED.
+                 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.
          — Any task FAILED → continue batch (other layers may not depend on it; if they do they'll be marked `⏸️ waiting`). Operator gets failure list in final summary.
@@ -202,7 +203,8 @@ Per-task phase tokens:
 - Writing code or phase blocks in Execution Log. (Phase subagents do.)
 - Sharing context between phase subagents of different tasks. Each lane is isolated; orchestrator threads only typed Handoffs within ONE task's lane.
 - Skipping audit after Round close in default (per-task) mode. Audit dispatch is mandatory.
-- Audit retry beyond 2 total attempts per task. Hard cap.
+- Audit retry beyond 2 attempts per task per session. Hard cap; only the operator's literal `--new-audit-session` arg resets it, and only via the sibling `sdd-execute` skill.
+- Writing a `✅ RESOLVED` marker for a blocker that is not resolved, to get past the `check-blockers` preflight. The marker records a fact, not permission.
 - Re-running phases not flagged in `phases_to_fix`. The map finding-location → phase is the contract.
 - Parallel dispatch ACROSS layers. Layers run sequentially.
 - Parallel dispatch ACROSS sub-batches in same layer. Sub-batches exist exactly because of file conflicts.

package/dist/gennady.js

@@ -3,7 +3,7 @@ import { c as s } from "./chunks/shared-DbIfVgIg.js";
 import "node:fs";
 import "node:path";
 import "node:url";
-const r = "0.8.4-next.3", i = /* @__PURE__ */ new Set(["help", "--help", "-h"]), p = /* @__PURE__ */ new Set(["--version", "-v"]), t = process.argv[2];
+const r = "0.8.4-next.6", i = /* @__PURE__ */ new Set(["help", "--help", "-h"]), p = /* @__PURE__ */ new Set(["--version", "-v"]), t = process.argv[2];
 p.has(t) && (console.log(r), process.exit(0));
 (!t || i.has(t)) && (await import("./chunks/help.cmd-Bz1YqU2V.js"), process.exit(0));
 s({ name: "gennady", version: r });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gennady",
-  "version": "0.8.4-next.3",
+  "version": "0.8.4-next.6",
   "author": "Konstantin Lebedev <ibnrubaxa@gmail.com>",
   "description": "Gennady — General Extensible Neural Network Adaptive Data Yntelligence",
   "keywords": [