gennady 0.8.4-draft.2 → 0.8.4-draft.3

package/ai/directives/sdd-v2/root.directive.xml

@@ -66,6 +66,35 @@
     </Axiom>
   </BeliefState>
 
+  <ChatProtocol>
+    <Contract id="QUESTION_FORMAT">
+      Questions must LOOK like questions and stay readable on any theme. A `### ❓ Вопросы — реши <N>`
+      section header; each question numbered `Q<N>`; options described in words. Never use `+` / `-`
+      signs for pros / cons (they render black and vanish on dark themes). Group obvious sub-questions
+      into one; do not pad the count.
+
+      Low-stakes — a recommendation is allowed, but only as the result of `AX_DIVERGE_BEFORE_RECOMMEND`
+      (not the first typical answer):
+
+      ### ❓ Вопросы — реши <N>
+      «годится» = беру все рекомендации, или поправь по номерам.
+
+      **Q1 · <вопрос?>**
+      ✅ **<рекомендованный вариант>** `[code]` — почему подходит именно под эту задачу.
+      Иначе:
+      - **<альтернатива>** `[code]` — _за: <плюс> · против: <минус>_
+
+      High-stakes / architecture — do NOT pre-anchor one pick. List the strongest candidates (include a
+      non-obvious / tail one) with «за / против» and let the operator choose; or give a recommendation
+      only alongside its strongest alternative and the reason it might win.
+
+      A plain binary question needs no list — recommendation + inline alternative:
+
+      **Q2 · <вопрос?>**
+      ✅ **<рекомендация>** — почему. _или <короткая альтернатива>?_
+    </Contract>
+  </ChatProtocol>
+
   <HaltConditions>
     | 🛑 ID | Trigger |
     |---|---|
@@ -82,9 +111,13 @@
         State from the router (`sdd-state`) already reports whether `specs/README.md` exists.
         - Absent → no portal yet: run `sdd-state --probe` to learn whether the repo is greenfield or
           already holds code (`AX_TOOL_INVOCATION`; probe only now that it is needed — not at flow start).
-          - `CODE=absent` (empty / only package.json) → **greenfield init**. Ask (Russian): «Как называется
-            проект? Опиши в одном предложении его vision и первые scope'ы (infra-base, backend, web — на
-            черновую).»
+          - `CODE=absent` (empty / only package.json) → **greenfield init**. The operator already saw the
+            state card and, for empty intake, confirmed «Создать проект» at the router's entry Ask
+            (`AX_DIALOGUE_DISCIPLINE`) — the interview opens HERE, never before that card and never as
+            prose dumped into the reply. Ask through the SAME channel: the `AskUserQuestion` tool when
+            available (open answer via its free-text slot), otherwise `QUESTION_FORMAT` (Russian) — one
+            structured question: «Как называется проект? Опиши в одном предложении его vision и первые
+            scope'ы (infra-base, backend, web — на черновую).»
           - `CODE=present` → **from-code recovery** — do NOT invent a vision over existing code:
             `READ_AND_USE_DIRECTIVE("ai/directives/sdd-v2/discover-from-code.directive.xml")`.
         - Present → empty intake → `H_NO_INTENT`; otherwise classify the change:

package/ai/directives/sdd-v2/router.directive.xml

@@ -287,17 +287,25 @@
     | 🛑 ID | Trigger |
     |---|---|
     | `H_AMBIGUOUS_INTENT` | Operator intent cannot be classified against state — ask, never guess |
+    | `H_WRONG_REPO` | Operator answered the empty-intake entry Ask with «я не в том репозитории» — stop here, no directive loads |
   </HaltConditions>
 
   <ExecutionPlan>
     <Step id="STEP_0_STATE">
-      <Goal>Obtain project state and clear the preflight gates before any routing.</Goal>
+      <Goal>Obtain project state, show it to the operator, then clear the preflight gates before any routing.</Goal>
       <Action>
         Call `sdd-state` (deterministic) — one call returns everything routing needs: `FLOW_VERSION`,
         `READINESS` (exact required scripts: typecheck / test / test:coverage / lint+gennady / format),
         portal presence (`specs/README.md`), the Scopes table (id + scope-type + status + description),
         and the in-progress session set (`SESSION_FILE_FORMAT`, `specs/.sdd-session.md`).
 
+        Show the operator the state card exactly as `sdd-state` printed it — flow version, readiness,
+        portal presence, the Scopes table, the session set — verbatim, in its own message, BEFORE any
+        classification of intent begins. Never paraphrase it, never fold it silently into the agent's own
+        reasoning, never skip it because the state looks empty — an absent portal still gets the card;
+        «нет ни одной спеки» IS the picture. This print is a required observable action, not a narration
+        aside (`AX_NO_PROCESS_NARRATION` bans commentary about the work being done, not this display).
+
         Then clear each preflight gate inline via the switch below, sized to the task's blast radius
         (`AX_PREFLIGHT_BLAST_RADIUS_SCOPED`). After any embedded flow (migration / readiness) returns,
         re-run `sdd-state` and re-evaluate on the FRESH snapshot — that flow changed the project, so the
@@ -329,6 +337,19 @@
         inside the `root` branch, not this switch). A path-bearing request against an absent portal is
         still ambiguous between the two — ask the operator which they mean before routing.
 
+        WHEN `specs/README.md` is absent AND the operator's message carries no substantive project
+        content (bare `/sdd`, a greeting, no vision / scope-type stated) — empty intake against an empty
+        portal — do NOT silently classify `project-setup` by elimination; the operator just saw the state
+        card and is still «в непонятной ситуации» without a concrete next step. Run `sdd-state --probe`
+        (`CODE` presence only) and STOP: ask via the `AskUserQuestion` tool when available, otherwise
+        `QUESTION_FORMAT` (message in Russian) — «Создать проект» (рекомендую) · «Воссоздать спеки из
+        существующего кода» (offered ONLY when `CODE=present`) · «Я не в том репозитории» → halt
+        (`H_WRONG_REPO`), no directive loads. Either non-halt answer locks `intent: project-setup` for
+        STEP_2_ROUTE's existing case below — this is a confirmation of intent, not a new route. WHEN the
+        message already carries substantive project content (e.g. «новый проект X про Y») this Ask is
+        skipped entirely — classify `project-setup` directly and fold its confirmation into the ordinary
+        SCALE exchange below; one stop, not two.
+
         Alongside intent, assess SCALE ∈ {product, library, module, function, fix} from context:
         the intent itself, the portal state (an empty portal leans product; a mature scope leans
         module / function), and the size of the request. Per `AX_SCALE_PROPORTIONAL_DEPTH` the

package/ai/kit/templates/sdd-v2/root.directive.hbs

@@ -33,6 +33,10 @@
     {{> "axiom/process/ax-close-with-integrity-check"}}
   </BeliefState>
 
+  <ChatProtocol>
+    {{> "contract/process/question-format"}}
+  </ChatProtocol>
+
   <HaltConditions>
     | 🛑 ID | Trigger |
     |---|---|
@@ -49,9 +53,13 @@
         State from the router (`sdd-state`) already reports whether `specs/README.md` exists.
         - Absent → no portal yet: run `sdd-state --probe` to learn whether the repo is greenfield or
           already holds code (`AX_TOOL_INVOCATION`; probe only now that it is needed — not at flow start).
-          - `CODE=absent` (empty / only package.json) → **greenfield init**. Ask (Russian): «Как называется
-            проект? Опиши в одном предложении его vision и первые scope'ы (infra-base, backend, web — на
-            черновую).»
+          - `CODE=absent` (empty / only package.json) → **greenfield init**. The operator already saw the
+            state card and, for empty intake, confirmed «Создать проект» at the router's entry Ask
+            (`AX_DIALOGUE_DISCIPLINE`) — the interview opens HERE, never before that card and never as
+            prose dumped into the reply. Ask through the SAME channel: the `AskUserQuestion` tool when
+            available (open answer via its free-text slot), otherwise `QUESTION_FORMAT` (Russian) — one
+            structured question: «Как называется проект? Опиши в одном предложении его vision и первые
+            scope'ы (infra-base, backend, web — на черновую).»
           - `CODE=present` → **from-code recovery** — do NOT invent a vision over existing code:
             `READ_AND_USE_DIRECTIVE("ai/directives/sdd-v2/discover-from-code.directive.xml")`.
         - Present → empty intake → `H_NO_INTENT`; otherwise classify the change:

package/ai/kit/templates/sdd-v2/router.directive.hbs

@@ -82,17 +82,25 @@
     | 🛑 ID | Trigger |
     |---|---|
     | `H_AMBIGUOUS_INTENT` | Operator intent cannot be classified against state — ask, never guess |
+    | `H_WRONG_REPO` | Operator answered the empty-intake entry Ask with «я не в том репозитории» — stop here, no directive loads |
   </HaltConditions>
 
   <ExecutionPlan>
     <Step id="STEP_0_STATE">
-      <Goal>Obtain project state and clear the preflight gates before any routing.</Goal>
+      <Goal>Obtain project state, show it to the operator, then clear the preflight gates before any routing.</Goal>
       <Action>
         Call `sdd-state` (deterministic) — one call returns everything routing needs: `FLOW_VERSION`,
         `READINESS` (exact required scripts: typecheck / test / test:coverage / lint+gennady / format),
         portal presence (`specs/README.md`), the Scopes table (id + scope-type + status + description),
         and the in-progress session set (`SESSION_FILE_FORMAT`, `specs/.sdd-session.md`).
 
+        Show the operator the state card exactly as `sdd-state` printed it — flow version, readiness,
+        portal presence, the Scopes table, the session set — verbatim, in its own message, BEFORE any
+        classification of intent begins. Never paraphrase it, never fold it silently into the agent's own
+        reasoning, never skip it because the state looks empty — an absent portal still gets the card;
+        «нет ни одной спеки» IS the picture. This print is a required observable action, not a narration
+        aside (`AX_NO_PROCESS_NARRATION` bans commentary about the work being done, not this display).
+
         Then clear each preflight gate inline via the switch below, sized to the task's blast radius
         (`AX_PREFLIGHT_BLAST_RADIUS_SCOPED`). After any embedded flow (migration / readiness) returns,
         re-run `sdd-state` and re-evaluate on the FRESH snapshot — that flow changed the project, so the
@@ -124,6 +132,19 @@
         inside the `root` branch, not this switch). A path-bearing request against an absent portal is
         still ambiguous between the two — ask the operator which they mean before routing.
 
+        WHEN `specs/README.md` is absent AND the operator's message carries no substantive project
+        content (bare `/sdd`, a greeting, no vision / scope-type stated) — empty intake against an empty
+        portal — do NOT silently classify `project-setup` by elimination; the operator just saw the state
+        card and is still «в непонятной ситуации» without a concrete next step. Run `sdd-state --probe`
+        (`CODE` presence only) and STOP: ask via the `AskUserQuestion` tool when available, otherwise
+        `QUESTION_FORMAT` (message in Russian) — «Создать проект» (рекомендую) · «Воссоздать спеки из
+        существующего кода» (offered ONLY when `CODE=present`) · «Я не в том репозитории» → halt
+        (`H_WRONG_REPO`), no directive loads. Either non-halt answer locks `intent: project-setup` for
+        STEP_2_ROUTE's existing case below — this is a confirmation of intent, not a new route. WHEN the
+        message already carries substantive project content (e.g. «новый проект X про Y») this Ask is
+        skipped entirely — classify `project-setup` directly and fold its confirmation into the ordinary
+        SCALE exchange below; one stop, not two.
+
         Alongside intent, assess SCALE ∈ {product, library, module, function, fix} from context:
         the intent itself, the portal state (an empty portal leans product; a mature scope leans
         module / function), and the size of the request. Per `AX_SCALE_PROPORTIONAL_DEPTH` the

package/ai/skills/agent-inbox/SKILL.md

@@ -31,7 +31,7 @@ compatibility: opencode
       single-MR review pipeline, and finalization. You EMBODY this directive.
     </Step>
     <Step id="PREFLIGHT">
-      Run `npx tsx ~/Developer/gennady/cli/gennady.ts inbox --json`. Response has
+      Run `npx gennady inbox --json`. Response has
       `"configured": false` → do NOT exit: run the setup flow from inbox-flow (two `AskUserQuestion`
       — `reposBase`, then `vcsHost` → `inbox config --set` → retry). `"configured": true` → EMBODY.
       Not inside a repo → pass `--vcs-host=<host>` on every call. Token: `GITLAB_PERSONAL_TOKEN` or

package/ai/skills/sdd/SKILL.md

@@ -16,10 +16,12 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
       — one call returns portal presence, the Scopes table (id / type / status), declared gate scripts,
-      and the in-progress session set — AND read in full
-      `~/Developer/gennady/ai/directives/sdd-v2/router.directive.xml`.
+      and the in-progress session set — AND read in full `ai/directives/sdd-v2/router.directive.xml`.
+      Resolve deterministically, project root first: `ai/directives/sdd-v2/router.directive.xml`; if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/router.directive.xml`; if neither exists,
+      stop and tell the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="EMBODY">You ARE the router directive now. Intent — from the operator message; state — from sdd-state.</Step>
     <Step id="ROUTE">

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

@@ -6,8 +6,11 @@ compatibility: opencode
 
 1. **Extract intent.** Operator wants audit of {TSK-NN | full tree | current changes}. If ambiguous — ask.
 
-2. **Load & activate directive.** Read in full: `~/Developer/gennady/ai/directives/sdd-v2/audit.directive.xml`
+2. **Load & activate directive.** Read in full `ai/directives/sdd-v2/audit.directive.xml`. Resolve
+   deterministically, project root first: `ai/directives/sdd-v2/audit.directive.xml`; if missing,
+   `node_modules/gennady/ai/directives/sdd-v2/audit.directive.xml`; if neither exists, stop and tell
+   the operator to run `npx gennady sync` — never search for it.
    Announce: `🔒 DIRECTIVE ACTIVATED: SddAudit`
    You ARE this directive now.
 
-3. **Apply directive to intent.** Mode auto-detected per `AX_AUDIT_MODES` (per-task | epic-level). Per `STEP_1_MECHANICAL`, first run the mechanical tool — `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-check --task <ticket-path>` (or `--all` for an epic) — and take its findings as given. Then re-derive the gate independently: `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-verify --profile full`, `npx tsx ~/Developer/gennady/cli/gennady.ts lint --spec=<module-spec>` on changed files, and `npx tsx ~/Developer/gennady/cli/gennady.ts testcov --run --min=80`. Feed all output into the directive's finding pipeline. Then follow Execution_Plan end-to-end (STEP_2_SEMANTIC, STEP_3_ROUTE). Do not deviate.
+3. **Apply directive to intent.** Mode auto-detected per `AX_AUDIT_MODES` (per-task | epic-level). Per `STEP_1_MECHANICAL`, first run the mechanical tool — `npx gennady sdd-check --task <ticket-path>` (or `--all` for an epic) — and take its findings as given. Then re-derive the gate independently: `npx gennady sdd-verify --profile full`, `npx gennady lint --spec=<module-spec>` on changed files, and `npx gennady testcov --run --min=80`. Feed all output into the directive's finding pipeline. Then follow Execution_Plan end-to-end (STEP_2_SEMANTIC, STEP_3_ROUTE). Do not deviate.

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

@@ -14,8 +14,8 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="RUN">
-      If the operator named a Task-ID / ticket path → `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-check --task <path>`.
-      Otherwise (whole project) → `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-check --all`.
+      If the operator named a Task-ID / ticket path → `npx gennady sdd-check --task <path>`.
+      Otherwise (whole project) → `npx gennady sdd-check --all`.
     </Step>
     <Step id="REPORT">
       Relay the findings verbatim grouped by file (`file: severity: code  message`) plus the one-line summary,

package/ai/skills/sdd-code-review/SKILL.md

@@ -16,7 +16,10 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      Read in full `~/Developer/gennady/ai/directives/sdd-v2/code-review.directive.xml`.
+      Read in full `ai/directives/sdd-v2/code-review.directive.xml`. Resolve deterministically,
+      project root first: `ai/directives/sdd-v2/code-review.directive.xml`; if missing,
+      `node_modules/gennady/ai/directives/sdd-v2/code-review.directive.xml`; if neither exists,
+      stop and tell the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="EMBODY">
       You ARE the code-review now. Input — a Task-ID (or the dispatch payload from the execute orchestrator):

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

@@ -16,8 +16,11 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
-      AND read in full `~/Developer/gennady/ai/directives/sdd-v2/critic.directive.xml`.
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
+      AND read in full `ai/directives/sdd-v2/critic.directive.xml`.
+      Resolve every `ai/directives/sdd-v2/<file>` below deterministically, project root first: if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/<file>`; if neither exists, stop and tell
+      the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="PREFLIGHT">
       Size the gate to this request's blast radius first: when the critique target stays inside its own scope (a single spec / task) and never touches `tasks/` layout or a missing gate script, record `FLOW_VERSION` / `READINESS` in one line and proceed straight to EMBODY — offer migration / readiness setup to the operator as a separate next step, not inside this run.

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

@@ -16,9 +16,12 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
       (flow version · readiness · scopes) AND read in full
-      `~/Developer/gennady/ai/directives/sdd-v2/execute.directive.xml`.
+      `ai/directives/sdd-v2/execute.directive.xml`.
+      Resolve every `ai/directives/sdd-v2/<file>` below deterministically, project root first: if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/<file>`; if neither exists, stop and tell
+      the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="PREFLIGHT">
       Size the gate to this request's blast radius first: when the requested execution stays inside a single task's own scope and never touches `tasks/` layout or a missing gate script, record `FLOW_VERSION` / `READINESS` in one line and proceed straight to EMBODY — offer migration / readiness setup to the operator as a separate next step, not inside this run.

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

@@ -16,8 +16,11 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
-      AND read in full `~/Developer/gennady/ai/directives/sdd-v2/reconcile.directive.xml`.
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
+      AND read in full `ai/directives/sdd-v2/reconcile.directive.xml`.
+      Resolve every `ai/directives/sdd-v2/<file>` below deterministically, project root first: if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/<file>`; if neither exists, stop and tell
+      the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="PREFLIGHT">
       Size the gate to this request's blast radius first: when the reconcile stays inside its own scope (a single finding, a single ticket) and never touches `tasks/` layout or a missing gate script, record `FLOW_VERSION` / `READINESS` in one line and proceed straight to EMBODY — offer migration / readiness setup to the operator as a separate next step, not inside this run.

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

@@ -16,9 +16,12 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
       (flow version · readiness · portal · scopes) AND read in full
-      `~/Developer/gennady/ai/directives/sdd-v2/scaffold.directive.xml`.
+      `ai/directives/sdd-v2/scaffold.directive.xml`.
+      Resolve every `ai/directives/sdd-v2/<file>` below deterministically, project root first: if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/<file>`; if neither exists, stop and tell
+      the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="PREFLIGHT">
       Size the gate to this request's blast radius first: when the scaffolding target stays inside a single

package/dist/ai/directives/sdd-v2/root.directive.xml

@@ -66,6 +66,35 @@
     </Axiom>
   </BeliefState>
 
+  <ChatProtocol>
+    <Contract id="QUESTION_FORMAT">
+      Questions must LOOK like questions and stay readable on any theme. A `### ❓ Вопросы — реши <N>`
+      section header; each question numbered `Q<N>`; options described in words. Never use `+` / `-`
+      signs for pros / cons (they render black and vanish on dark themes). Group obvious sub-questions
+      into one; do not pad the count.
+
+      Low-stakes — a recommendation is allowed, but only as the result of `AX_DIVERGE_BEFORE_RECOMMEND`
+      (not the first typical answer):
+
+      ### ❓ Вопросы — реши <N>
+      «годится» = беру все рекомендации, или поправь по номерам.
+
+      **Q1 · <вопрос?>**
+      ✅ **<рекомендованный вариант>** `[code]` — почему подходит именно под эту задачу.
+      Иначе:
+      - **<альтернатива>** `[code]` — _за: <плюс> · против: <минус>_
+
+      High-stakes / architecture — do NOT pre-anchor one pick. List the strongest candidates (include a
+      non-obvious / tail one) with «за / против» and let the operator choose; or give a recommendation
+      only alongside its strongest alternative and the reason it might win.
+
+      A plain binary question needs no list — recommendation + inline alternative:
+
+      **Q2 · <вопрос?>**
+      ✅ **<рекомендация>** — почему. _или <короткая альтернатива>?_
+    </Contract>
+  </ChatProtocol>
+
   <HaltConditions>
     | 🛑 ID | Trigger |
     |---|---|
@@ -82,9 +111,13 @@
         State from the router (`sdd-state`) already reports whether `specs/README.md` exists.
         - Absent → no portal yet: run `sdd-state --probe` to learn whether the repo is greenfield or
           already holds code (`AX_TOOL_INVOCATION`; probe only now that it is needed — not at flow start).
-          - `CODE=absent` (empty / only package.json) → **greenfield init**. Ask (Russian): «Как называется
-            проект? Опиши в одном предложении его vision и первые scope'ы (infra-base, backend, web — на
-            черновую).»
+          - `CODE=absent` (empty / only package.json) → **greenfield init**. The operator already saw the
+            state card and, for empty intake, confirmed «Создать проект» at the router's entry Ask
+            (`AX_DIALOGUE_DISCIPLINE`) — the interview opens HERE, never before that card and never as
+            prose dumped into the reply. Ask through the SAME channel: the `AskUserQuestion` tool when
+            available (open answer via its free-text slot), otherwise `QUESTION_FORMAT` (Russian) — one
+            structured question: «Как называется проект? Опиши в одном предложении его vision и первые
+            scope'ы (infra-base, backend, web — на черновую).»
           - `CODE=present` → **from-code recovery** — do NOT invent a vision over existing code:
             `READ_AND_USE_DIRECTIVE("ai/directives/sdd-v2/discover-from-code.directive.xml")`.
         - Present → empty intake → `H_NO_INTENT`; otherwise classify the change:

package/dist/ai/directives/sdd-v2/router.directive.xml

@@ -287,17 +287,25 @@
     | 🛑 ID | Trigger |
     |---|---|
     | `H_AMBIGUOUS_INTENT` | Operator intent cannot be classified against state — ask, never guess |
+    | `H_WRONG_REPO` | Operator answered the empty-intake entry Ask with «я не в том репозитории» — stop here, no directive loads |
   </HaltConditions>
 
   <ExecutionPlan>
     <Step id="STEP_0_STATE">
-      <Goal>Obtain project state and clear the preflight gates before any routing.</Goal>
+      <Goal>Obtain project state, show it to the operator, then clear the preflight gates before any routing.</Goal>
       <Action>
         Call `sdd-state` (deterministic) — one call returns everything routing needs: `FLOW_VERSION`,
         `READINESS` (exact required scripts: typecheck / test / test:coverage / lint+gennady / format),
         portal presence (`specs/README.md`), the Scopes table (id + scope-type + status + description),
         and the in-progress session set (`SESSION_FILE_FORMAT`, `specs/.sdd-session.md`).
 
+        Show the operator the state card exactly as `sdd-state` printed it — flow version, readiness,
+        portal presence, the Scopes table, the session set — verbatim, in its own message, BEFORE any
+        classification of intent begins. Never paraphrase it, never fold it silently into the agent's own
+        reasoning, never skip it because the state looks empty — an absent portal still gets the card;
+        «нет ни одной спеки» IS the picture. This print is a required observable action, not a narration
+        aside (`AX_NO_PROCESS_NARRATION` bans commentary about the work being done, not this display).
+
         Then clear each preflight gate inline via the switch below, sized to the task's blast radius
         (`AX_PREFLIGHT_BLAST_RADIUS_SCOPED`). After any embedded flow (migration / readiness) returns,
         re-run `sdd-state` and re-evaluate on the FRESH snapshot — that flow changed the project, so the
@@ -329,6 +337,19 @@
         inside the `root` branch, not this switch). A path-bearing request against an absent portal is
         still ambiguous between the two — ask the operator which they mean before routing.
 
+        WHEN `specs/README.md` is absent AND the operator's message carries no substantive project
+        content (bare `/sdd`, a greeting, no vision / scope-type stated) — empty intake against an empty
+        portal — do NOT silently classify `project-setup` by elimination; the operator just saw the state
+        card and is still «в непонятной ситуации» without a concrete next step. Run `sdd-state --probe`
+        (`CODE` presence only) and STOP: ask via the `AskUserQuestion` tool when available, otherwise
+        `QUESTION_FORMAT` (message in Russian) — «Создать проект» (рекомендую) · «Воссоздать спеки из
+        существующего кода» (offered ONLY when `CODE=present`) · «Я не в том репозитории» → halt
+        (`H_WRONG_REPO`), no directive loads. Either non-halt answer locks `intent: project-setup` for
+        STEP_2_ROUTE's existing case below — this is a confirmation of intent, not a new route. WHEN the
+        message already carries substantive project content (e.g. «новый проект X про Y») this Ask is
+        skipped entirely — classify `project-setup` directly and fold its confirmation into the ordinary
+        SCALE exchange below; one stop, not two.
+
         Alongside intent, assess SCALE ∈ {product, library, module, function, fix} from context:
         the intent itself, the portal state (an empty portal leans product; a mature scope leans
         module / function), and the size of the request. Per `AX_SCALE_PROPORTIONAL_DEPTH` the

package/dist/ai/kit/templates/sdd-v2/root.directive.hbs

@@ -33,6 +33,10 @@
     {{> "axiom/process/ax-close-with-integrity-check"}}
   </BeliefState>
 
+  <ChatProtocol>
+    {{> "contract/process/question-format"}}
+  </ChatProtocol>
+
   <HaltConditions>
     | 🛑 ID | Trigger |
     |---|---|
@@ -49,9 +53,13 @@
         State from the router (`sdd-state`) already reports whether `specs/README.md` exists.
         - Absent → no portal yet: run `sdd-state --probe` to learn whether the repo is greenfield or
           already holds code (`AX_TOOL_INVOCATION`; probe only now that it is needed — not at flow start).
-          - `CODE=absent` (empty / only package.json) → **greenfield init**. Ask (Russian): «Как называется
-            проект? Опиши в одном предложении его vision и первые scope'ы (infra-base, backend, web — на
-            черновую).»
+          - `CODE=absent` (empty / only package.json) → **greenfield init**. The operator already saw the
+            state card and, for empty intake, confirmed «Создать проект» at the router's entry Ask
+            (`AX_DIALOGUE_DISCIPLINE`) — the interview opens HERE, never before that card and never as
+            prose dumped into the reply. Ask through the SAME channel: the `AskUserQuestion` tool when
+            available (open answer via its free-text slot), otherwise `QUESTION_FORMAT` (Russian) — one
+            structured question: «Как называется проект? Опиши в одном предложении его vision и первые
+            scope'ы (infra-base, backend, web — на черновую).»
           - `CODE=present` → **from-code recovery** — do NOT invent a vision over existing code:
             `READ_AND_USE_DIRECTIVE("ai/directives/sdd-v2/discover-from-code.directive.xml")`.
         - Present → empty intake → `H_NO_INTENT`; otherwise classify the change:

package/dist/ai/kit/templates/sdd-v2/router.directive.hbs

@@ -82,17 +82,25 @@
     | 🛑 ID | Trigger |
     |---|---|
     | `H_AMBIGUOUS_INTENT` | Operator intent cannot be classified against state — ask, never guess |
+    | `H_WRONG_REPO` | Operator answered the empty-intake entry Ask with «я не в том репозитории» — stop here, no directive loads |
   </HaltConditions>
 
   <ExecutionPlan>
     <Step id="STEP_0_STATE">
-      <Goal>Obtain project state and clear the preflight gates before any routing.</Goal>
+      <Goal>Obtain project state, show it to the operator, then clear the preflight gates before any routing.</Goal>
       <Action>
         Call `sdd-state` (deterministic) — one call returns everything routing needs: `FLOW_VERSION`,
         `READINESS` (exact required scripts: typecheck / test / test:coverage / lint+gennady / format),
         portal presence (`specs/README.md`), the Scopes table (id + scope-type + status + description),
         and the in-progress session set (`SESSION_FILE_FORMAT`, `specs/.sdd-session.md`).
 
+        Show the operator the state card exactly as `sdd-state` printed it — flow version, readiness,
+        portal presence, the Scopes table, the session set — verbatim, in its own message, BEFORE any
+        classification of intent begins. Never paraphrase it, never fold it silently into the agent's own
+        reasoning, never skip it because the state looks empty — an absent portal still gets the card;
+        «нет ни одной спеки» IS the picture. This print is a required observable action, not a narration
+        aside (`AX_NO_PROCESS_NARRATION` bans commentary about the work being done, not this display).
+
         Then clear each preflight gate inline via the switch below, sized to the task's blast radius
         (`AX_PREFLIGHT_BLAST_RADIUS_SCOPED`). After any embedded flow (migration / readiness) returns,
         re-run `sdd-state` and re-evaluate on the FRESH snapshot — that flow changed the project, so the
@@ -124,6 +132,19 @@
         inside the `root` branch, not this switch). A path-bearing request against an absent portal is
         still ambiguous between the two — ask the operator which they mean before routing.
 
+        WHEN `specs/README.md` is absent AND the operator's message carries no substantive project
+        content (bare `/sdd`, a greeting, no vision / scope-type stated) — empty intake against an empty
+        portal — do NOT silently classify `project-setup` by elimination; the operator just saw the state
+        card and is still «в непонятной ситуации» without a concrete next step. Run `sdd-state --probe`
+        (`CODE` presence only) and STOP: ask via the `AskUserQuestion` tool when available, otherwise
+        `QUESTION_FORMAT` (message in Russian) — «Создать проект» (рекомендую) · «Воссоздать спеки из
+        существующего кода» (offered ONLY when `CODE=present`) · «Я не в том репозитории» → halt
+        (`H_WRONG_REPO`), no directive loads. Either non-halt answer locks `intent: project-setup` for
+        STEP_2_ROUTE's existing case below — this is a confirmation of intent, not a new route. WHEN the
+        message already carries substantive project content (e.g. «новый проект X про Y») this Ask is
+        skipped entirely — classify `project-setup` directly and fold its confirmation into the ordinary
+        SCALE exchange below; one stop, not two.
+
         Alongside intent, assess SCALE ∈ {product, library, module, function, fix} from context:
         the intent itself, the portal state (an empty portal leans product; a mature scope leans
         module / function), and the size of the request. Per `AX_SCALE_PROPORTIONAL_DEPTH` the

package/dist/ai/skills/agent-inbox/SKILL.md

@@ -31,7 +31,7 @@ compatibility: opencode
       single-MR review pipeline, and finalization. You EMBODY this directive.
     </Step>
     <Step id="PREFLIGHT">
-      Run `npx tsx ~/Developer/gennady/cli/gennady.ts inbox --json`. Response has
+      Run `npx gennady inbox --json`. Response has
       `"configured": false` → do NOT exit: run the setup flow from inbox-flow (two `AskUserQuestion`
       — `reposBase`, then `vcsHost` → `inbox config --set` → retry). `"configured": true` → EMBODY.
       Not inside a repo → pass `--vcs-host=<host>` on every call. Token: `GITLAB_PERSONAL_TOKEN` or

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

@@ -16,10 +16,12 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
       — one call returns portal presence, the Scopes table (id / type / status), declared gate scripts,
-      and the in-progress session set — AND read in full
-      `~/Developer/gennady/ai/directives/sdd-v2/router.directive.xml`.
+      and the in-progress session set — AND read in full `ai/directives/sdd-v2/router.directive.xml`.
+      Resolve deterministically, project root first: `ai/directives/sdd-v2/router.directive.xml`; if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/router.directive.xml`; if neither exists,
+      stop and tell the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="EMBODY">You ARE the router directive now. Intent — from the operator message; state — from sdd-state.</Step>
     <Step id="ROUTE">

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

@@ -6,8 +6,11 @@ compatibility: opencode
 
 1. **Extract intent.** Operator wants audit of {TSK-NN | full tree | current changes}. If ambiguous — ask.
 
-2. **Load & activate directive.** Read in full: `~/Developer/gennady/ai/directives/sdd-v2/audit.directive.xml`
+2. **Load & activate directive.** Read in full `ai/directives/sdd-v2/audit.directive.xml`. Resolve
+   deterministically, project root first: `ai/directives/sdd-v2/audit.directive.xml`; if missing,
+   `node_modules/gennady/ai/directives/sdd-v2/audit.directive.xml`; if neither exists, stop and tell
+   the operator to run `npx gennady sync` — never search for it.
    Announce: `🔒 DIRECTIVE ACTIVATED: SddAudit`
    You ARE this directive now.
 
-3. **Apply directive to intent.** Mode auto-detected per `AX_AUDIT_MODES` (per-task | epic-level). Per `STEP_1_MECHANICAL`, first run the mechanical tool — `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-check --task <ticket-path>` (or `--all` for an epic) — and take its findings as given. Then re-derive the gate independently: `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-verify --profile full`, `npx tsx ~/Developer/gennady/cli/gennady.ts lint --spec=<module-spec>` on changed files, and `npx tsx ~/Developer/gennady/cli/gennady.ts testcov --run --min=80`. Feed all output into the directive's finding pipeline. Then follow Execution_Plan end-to-end (STEP_2_SEMANTIC, STEP_3_ROUTE). Do not deviate.
+3. **Apply directive to intent.** Mode auto-detected per `AX_AUDIT_MODES` (per-task | epic-level). Per `STEP_1_MECHANICAL`, first run the mechanical tool — `npx gennady sdd-check --task <ticket-path>` (or `--all` for an epic) — and take its findings as given. Then re-derive the gate independently: `npx gennady sdd-verify --profile full`, `npx gennady lint --spec=<module-spec>` on changed files, and `npx gennady testcov --run --min=80`. Feed all output into the directive's finding pipeline. Then follow Execution_Plan end-to-end (STEP_2_SEMANTIC, STEP_3_ROUTE). Do not deviate.

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

@@ -14,8 +14,8 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="RUN">
-      If the operator named a Task-ID / ticket path → `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-check --task <path>`.
-      Otherwise (whole project) → `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-check --all`.
+      If the operator named a Task-ID / ticket path → `npx gennady sdd-check --task <path>`.
+      Otherwise (whole project) → `npx gennady sdd-check --all`.
     </Step>
     <Step id="REPORT">
       Relay the findings verbatim grouped by file (`file: severity: code  message`) plus the one-line summary,

package/dist/ai/skills/sdd-code-review/SKILL.md

@@ -16,7 +16,10 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      Read in full `~/Developer/gennady/ai/directives/sdd-v2/code-review.directive.xml`.
+      Read in full `ai/directives/sdd-v2/code-review.directive.xml`. Resolve deterministically,
+      project root first: `ai/directives/sdd-v2/code-review.directive.xml`; if missing,
+      `node_modules/gennady/ai/directives/sdd-v2/code-review.directive.xml`; if neither exists,
+      stop and tell the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="EMBODY">
       You ARE the code-review now. Input — a Task-ID (or the dispatch payload from the execute orchestrator):

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

@@ -16,8 +16,11 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
-      AND read in full `~/Developer/gennady/ai/directives/sdd-v2/critic.directive.xml`.
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
+      AND read in full `ai/directives/sdd-v2/critic.directive.xml`.
+      Resolve every `ai/directives/sdd-v2/<file>` below deterministically, project root first: if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/<file>`; if neither exists, stop and tell
+      the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="PREFLIGHT">
       Size the gate to this request's blast radius first: when the critique target stays inside its own scope (a single spec / task) and never touches `tasks/` layout or a missing gate script, record `FLOW_VERSION` / `READINESS` in one line and proceed straight to EMBODY — offer migration / readiness setup to the operator as a separate next step, not inside this run.

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

@@ -16,9 +16,12 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
       (flow version · readiness · scopes) AND read in full
-      `~/Developer/gennady/ai/directives/sdd-v2/execute.directive.xml`.
+      `ai/directives/sdd-v2/execute.directive.xml`.
+      Resolve every `ai/directives/sdd-v2/<file>` below deterministically, project root first: if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/<file>`; if neither exists, stop and tell
+      the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="PREFLIGHT">
       Size the gate to this request's blast radius first: when the requested execution stays inside a single task's own scope and never touches `tasks/` layout or a missing gate script, record `FLOW_VERSION` / `READINESS` in one line and proceed straight to EMBODY — offer migration / readiness setup to the operator as a separate next step, not inside this run.

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

@@ -16,8 +16,11 @@ compatibility: opencode
 
   <ExecutionPlan>
     <Step id="GATHER">
-      One parallel batch (do NOT serialize): run `npx tsx ~/Developer/gennady/cli/gennady.ts sdd-state`
-      AND read in full `~/Developer/gennady/ai/directives/sdd-v2/reconcile.directive.xml`.
+      One parallel batch (do NOT serialize): run `npx gennady sdd-state`
+      AND read in full `ai/directives/sdd-v2/reconcile.directive.xml`.
+      Resolve every `ai/directives/sdd-v2/<file>` below deterministically, project root first: if
+      missing, `node_modules/gennady/ai/directives/sdd-v2/<file>`; if neither exists, stop and tell
+      the operator to run `npx gennady sync` — never search for it.
     </Step>
     <Step id="PREFLIGHT">
       Size the gate to this request's blast radius first: when the reconcile stays inside its own scope (a single finding, a single ticket) and never touches `tasks/` layout or a missing gate script, record `FLOW_VERSION` / `READINESS` in one line and proceed straight to EMBODY — offer migration / readiness setup to the operator as a separate next step, not inside this run.