ai-engineering-loop 1.0.11 → 1.0.12

package/.agents/devil-advocate.md

@@ -17,15 +17,24 @@ Use only:
 1. The diff file path in the spawn prompt. Read that file first. Do not run git diff if a diff path was given.
 2. Goal Contract path (if given).
 3. Verification log path (if given).
-4. At most 8 source files that appear as paths in the diff.
+4. conventions.md path (if given). At most one extra read.
+5. At most 8 source files that appear as paths in the diff.
 
 Skip: `*.css`, files named like `*-css.ts` or `report-css.ts`, generated/vendor dirs, and any file where the diff hunk already contains enough evidence. Prefer quoting the hunk over opening the whole file.
 
 Do not ask for Maker rationale.
 
-## What to find
+## Two axes (do not merge)
 
-Priority: correctness, error handling, security, concurrency, tests that fail to prove an acceptance criterion. Skip style nits unless they hide a defect.
+Report Spec and Standards as separate findings. Do not rerank one axis with the other. A change can pass Spec and fail Standards, or the reverse. Do not spawn children to split axes.
+
+**Spec** (`axis: "spec"`): Goal Contract acceptance criteria, correctness, error handling, security, concurrency, tests that fail to prove an AC. BLOCKER or HIGH only for a real AC breach or runtime defect.
+
+**Standards** (`axis: "standards"`): `.ai-engineering-loop/conventions.md` plus the smell baseline below. Judgement calls: severity MEDIUM or LOW. Set `hardConvention: true` only when conventions.md states a hard rule that this hunk violates. A smell that hides an AC defect is Spec, not Standards.
+
+Skip style nits unless they hide a defect.
+
+Smell baseline (judgement only; skip if tooling already enforces; repo conventions override): Mysterious Name; Duplicated Code; Feature Envy; Data Clumps; Primitive Obsession; Repeated Switches; Shotgun Surgery; Divergent Change; Speculative Generality; Message Chains; Middle Man; Refused Bequest.
 
 ## Output
 
@@ -38,6 +47,8 @@ Return a Finding Ledger as a fenced JSON block and stop:
   "findings": [
     {
       "id": "DA-01",
+      "axis": "spec",
+      "hardConvention": false,
       "topic": "correctness",
       "validity": "VALID",
       "severity": "BLOCKER",
@@ -53,4 +64,4 @@ Return a Finding Ledger as a fenced JSON block and stop:
 }
 ```
 
-Rules: validity VALID or INVALID; severity BLOCKER, HIGH, MEDIUM, or LOW; disposition STRONG, ACCEPTABLE, or WEAK. VALID BLOCKER or HIGH must include concreteAlternativeDiff. Empty findings is allowed.
+Rules: axis is spec or standards (default spec). hardConvention is boolean, default false. validity VALID or INVALID; severity BLOCKER, HIGH, MEDIUM, or LOW; disposition STRONG, ACCEPTABLE, or WEAK. VALID BLOCKER or HIGH must include concreteAlternativeDiff. Empty findings is allowed.

package/.agents/judge.md

@@ -14,12 +14,16 @@ Finish in at most 4 tool calls, then emit the verdict. Read the Finding Ledger a
 
 Use only paths in the spawn prompt: Goal Contract, verification evidence, Finding Ledger. Ignore Maker optimism and reviewer tone. Disposition never overrides Validity plus Severity.
 
-## Decision matrix
+## Axes
 
-- Verification missing, vague, or non-zero exit: ITERATE
-- Any VALID BLOCKER or HIGH still open: ITERATE (ESCALATE if iteration is 3 or more)
+Do not merge Spec and Standards into one ranking.
+
+- Spec VALID BLOCKER or HIGH (or missing axis, treated as spec): ITERATE (ESCALATE if iteration is 3 or more)
+- Standards VALID BLOCKER or HIGH: ITERATE only when hardConvention is true
+- Other Standards findings: ACCEPT as tradeoff; may still PASS
 - INVALID findings: DISMISS, cannot block delivery
 - VALID MEDIUM or LOW: ACCEPT as tradeoff; may still PASS
+- Verification missing, vague, or non-zero exit: ITERATE
 - All acceptance criteria proven, verification green, zero open blockers: PASS
 
 ## Output

package/.agents/workflows/ai-engineering-loop.md

@@ -5,12 +5,14 @@ description: Run the AI Engineering Loop on Antigravity (init, status, refresh,
 
 Follow `policies/review-budget.md`. Parent is Maker plus orchestrator. Do not use `browser_subagent`.
 
+Stage 1: grill if the task is ambiguous (`core/grill-policy.md`), then freeze the Goal Contract. On `adapter_type: dot`, that grill includes `task-impact-inquiry` (Antigravity skill under `~/.gemini/config/skills/`); do not run a second interview. Use `.ai-engineering-loop/glossary.md`. Name test seams. Maker: TDD at those seams (`policies/tdd-policy.md`). Bugs: red repro first (`core/root-cause-analysis.md`). Mid-loop stop: `core/handoff-policy.md`.
+
 If `invoke_subagent` (or Task) exists, spawn `devil-advocate` then `judge` as siblings. Wait for each child. Do not run them in the background. Use `general-purpose` only if the named type is rejected.
 
 5. Before Devil's Advocate: write `git diff` to `.ai-engineering-loop/tasks/current.diff` and put `git diff --name-only` in the child prompt. Do not paste Maker rationale.
-6. Devil's Advocate prompt: diff file path, name-only list, Goal Contract path, verification log path, and "at most 8 tool calls; read the diff file; skip css and generated files".
+6. Devil's Advocate prompt: diff file path, name-only list, Goal Contract path, verification log path, conventions.md path, and "at most 8 tool calls; read the diff file; skip css and generated files". Report Spec and Standards axes separately.
 7. Judge prompt: Goal Contract path, verification evidence path, Finding Ledger, and "at most 4 tool calls; ledger and contract only; skip css; do not re-review the whole diff".
 
 If no subagent tool exists, run the same budgets in this session as CONTEXT_ISOLATION_ONLY. Do not claim independent agent execution.
 
-Init/status/refresh: `npx ai-engineering-loop <command>`.
+Init/status/refresh/sync-hosts: `npx ai-engineering-loop <command>`. Stage 0: `npx ai-engineering-loop sync-hosts` then `npx ai-engineering-loop status`. If sync-hosts copied files, tell the user a new session is needed for updated skill text; keep going with this session.

package/.claude/agents/devil-advocate.md

@@ -18,15 +18,24 @@ Use only:
 1. The diff file path in the spawn prompt. Read that file first. Do not run git diff if a diff path was given.
 2. Goal Contract path (if given).
 3. Verification log path (if given).
-4. At most 8 source files that appear as paths in the diff.
+4. conventions.md path (if given). At most one extra read.
+5. At most 8 source files that appear as paths in the diff.
 
 Skip: `*.css`, files named like `*-css.ts` or `report-css.ts`, generated/vendor dirs, and any file where the diff hunk already contains enough evidence. Prefer quoting the hunk over opening the whole file.
 
 Do not ask for Maker rationale.
 
-## What to find
+## Two axes (do not merge)
 
-Priority: correctness, error handling, security, concurrency, tests that fail to prove an acceptance criterion. Skip style nits unless they hide a defect.
+Report Spec and Standards as separate findings. Do not rerank one axis with the other. A change can pass Spec and fail Standards, or the reverse. Do not spawn children to split axes.
+
+**Spec** (`axis: "spec"`): Goal Contract acceptance criteria, correctness, error handling, security, concurrency, tests that fail to prove an AC. BLOCKER or HIGH only for a real AC breach or runtime defect.
+
+**Standards** (`axis: "standards"`): `.ai-engineering-loop/conventions.md` plus the smell baseline below. Judgement calls: severity MEDIUM or LOW. Set `hardConvention: true` only when conventions.md states a hard rule that this hunk violates. A smell that hides an AC defect is Spec, not Standards.
+
+Skip style nits unless they hide a defect.
+
+Smell baseline (judgement only; skip if tooling already enforces; repo conventions override): Mysterious Name; Duplicated Code; Feature Envy; Data Clumps; Primitive Obsession; Repeated Switches; Shotgun Surgery; Divergent Change; Speculative Generality; Message Chains; Middle Man; Refused Bequest.
 
 ## Output
 
@@ -39,6 +48,8 @@ Return a Finding Ledger as a fenced JSON block and stop:
   "findings": [
     {
       "id": "DA-01",
+      "axis": "spec",
+      "hardConvention": false,
       "topic": "correctness",
       "validity": "VALID",
       "severity": "BLOCKER",
@@ -54,4 +65,4 @@ Return a Finding Ledger as a fenced JSON block and stop:
 }
 ```
 
-Rules: validity VALID or INVALID; severity BLOCKER, HIGH, MEDIUM, or LOW; disposition STRONG, ACCEPTABLE, or WEAK. VALID BLOCKER or HIGH must include concreteAlternativeDiff. Empty findings is allowed.
+Rules: axis is spec or standards (default spec). hardConvention is boolean, default false. validity VALID or INVALID; severity BLOCKER, HIGH, MEDIUM, or LOW; disposition STRONG, ACCEPTABLE, or WEAK. VALID BLOCKER or HIGH must include concreteAlternativeDiff. Empty findings is allowed.

package/.claude/agents/judge.md

@@ -15,12 +15,16 @@ Finish in at most 4 tool calls, then emit the verdict. Read the Finding Ledger a
 
 Use only paths in the spawn prompt: Goal Contract, verification evidence, Finding Ledger. Ignore Maker optimism and reviewer tone. Disposition never overrides Validity plus Severity.
 
-## Decision matrix
+## Axes
 
-- Verification missing, vague, or non-zero exit: ITERATE
-- Any VALID BLOCKER or HIGH still open: ITERATE (ESCALATE if iteration is 3 or more)
+Do not merge Spec and Standards into one ranking.
+
+- Spec VALID BLOCKER or HIGH (or missing axis, treated as spec): ITERATE (ESCALATE if iteration is 3 or more)
+- Standards VALID BLOCKER or HIGH: ITERATE only when hardConvention is true
+- Other Standards findings: ACCEPT as tradeoff; may still PASS
 - INVALID findings: DISMISS, cannot block delivery
 - VALID MEDIUM or LOW: ACCEPT as tradeoff; may still PASS
+- Verification missing, vague, or non-zero exit: ITERATE
 - All acceptance criteria proven, verification green, zero open blockers: PASS
 
 ## Output

package/.claude/commands/ai-engineering-loop.md

@@ -8,4 +8,4 @@ Follow `.claude/skills/ai-engineering-loop/SKILL.md`.
 
 Use the Task tool for Devil's Advocate and Judge. Pass subagent_type, description, and prompt. If the schema includes run_in_background, set it false. Wait for each Task to finish. Write the git diff to a file and pass that path. DA: 8 tool calls. Judge: 4 tool calls, ledger and contract only. Do not let either roam the repo.
 
-Arguments: init, status, refresh, or a task description.
+Arguments: init, status, refresh, sync-hosts, or a task description.

package/.claude/skills/ai-engineering-loop/SKILL.md

@@ -24,22 +24,23 @@ Claude Code talks to strict proxies (including Kiro). Follow this exactly:
 
 ## Commands
 
-- `init` / `status` / `refresh`: run `npx ai-engineering-loop <command>` in the repo. Do not commit unless asked.
+- `init` / `status` / `refresh` / `sync-hosts`: run `npx ai-engineering-loop <command>` in the repo. Do not commit unless asked.
 - Any other argument: full loop for that task.
 
 ## Loop
 
 Parent session is Maker plus orchestrator. Spawn Devil's Advocate and Judge as **siblings**, not nested.
 
-1. Stage 0: `npx ai-engineering-loop status` (init or refresh if missing or stale).
-2. Stage 1: write a Goal Contract. Schema: `core/goal-contract.md`.
-3. Stages 2-4: Maker work in the parent. Surgical diff plus tests.
+1. Stage 0: `npx ai-engineering-loop sync-hosts` then `npx ai-engineering-loop status` (init or refresh if missing or stale). Read `.ai-engineering-loop/glossary.md`. If sync-hosts copied files, tell the user a new session is needed for updated skill text; keep going with this session.
+2. Stage 1: Goal Contract (`core/goal-contract.md`). If the task is ambiguous and the user can answer, grill first (`core/grill-policy.md`): design tree, recommended answers, do not ask look-up facts. Skip grill if the contract is already frozen or the user waived it. On `adapter_type: dot`, that grill includes the four-pillar blast radius (state, sibling, approval, queues). Do not run a second interview. Freeze before any production edit. Name test seams. Use glossary terms.
+3. Stages 2-4: Maker in the parent. Bugs: red repro first (`core/root-cause-analysis.md`). Features: TDD at named seams (`policies/tdd-policy.md`). Surgical diff.
 4. Stage 5: run commands from `.ai-engineering-loop/verification.md`. Keep command, exit code, stdout, test counts. Vague "seems green" is invalid.
 5. Write artifacts, then spawn. Before Devil's Advocate:
    - Write `git diff` to a file (for example `.ai-engineering-loop/tasks/current.diff`).
    - Write changed paths (`git diff --name-only`) into the Task prompt as a short list.
    - Put those paths in the child prompt. Do not paste Maker rationale.
-6. Stage 6: Task `subagent_type: devil-advocate`. Use `general-purpose` only if that type is rejected. If the Task schema includes `run_in_background`, set it false. Then wait for Task to return. Do not start Judge or more Maker work until the Finding Ledger is back. Prompt: diff file path, name-only list, Goal Contract path, verification log path, and "at most 8 tool calls; read the diff file; skip css and generated files".
+   - If stopping mid-loop, write `.ai-engineering-loop/tasks/handoff.md` (`core/handoff-policy.md`).
+6. Stage 6: Task `subagent_type: devil-advocate`. Use `general-purpose` only if that type is rejected. If the Task schema includes `run_in_background`, set it false. Then wait for Task to return. Do not start Judge or more Maker work until the Finding Ledger is back. Prompt: diff file path, name-only list, Goal Contract path, verification log path, conventions.md path, and "at most 8 tool calls; read the diff file; skip css and generated files". Report Spec and Standards axes separately.
 7. Stage 7: Task `subagent_type: judge` the same way (wait, no background). Use `general-purpose` only if `judge` is rejected. Prompt: Goal Contract path, verification evidence path, Finding Ledger, and "at most 4 tool calls; ledger and contract only; skip css; do not re-review the whole diff".
 8. ITERATE with iteration under 3: fix in the parent, re-verify, spawn a **new** Devil's Advocate (do not resume the previous child).
 9. Stage 8: delivery from `.ai-engineering-loop/adapter.md`.

package/.gemini/skills/ai-engineering-loop/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: ai-engineering-loop
+description: Use when the user runs /ai-engineering-loop, asks to init or refresh living project context, or wants the Maker / Devil's Advocate / Judge engineering loop on Antigravity.
+---
+
+# AI Engineering Loop (Antigravity)
+
+Canonical specs: if this workspace has `core/`, `agents/`, `policies/`, read those files. Otherwise run `npx ai-engineering-loop` and follow the published specs.
+
+Follow `policies/review-budget.md` when that file exists. Parent is Maker plus orchestrator. Do not use `browser_subagent`.
+
+## Host rule
+
+If `invoke_subagent` (or Task) exists, spawn `devil-advocate` then `judge` as siblings. Wait for each child. Do not run them in the background. Use `general-purpose` only if the named type is rejected.
+
+If no subagent tool exists, run the same budgets in this session as CONTEXT_ISOLATION_ONLY. Do not claim independent agent execution.
+
+Canonical mode ids: `TRUE_INDEPENDENT_AGENT`, `ISOLATED_AGENT_INSTANCE`, `FRESH_PROCESS_AGENT`, `CONTEXT_ISOLATION_ONLY`, `UNAVAILABLE`.
+
+## Commands
+
+- `init` / `status` / `refresh` / `sync-hosts`: run `npx ai-engineering-loop <command>` in the repo. Do not commit unless asked.
+- Any other argument: full loop for that task.
+
+## Loop
+
+1. Stage 0: `npx ai-engineering-loop sync-hosts` then `npx ai-engineering-loop status` (init or refresh if missing or stale). Read `.ai-engineering-loop/glossary.md`. If sync-hosts copied files, tell the user a new session is needed for updated skill text; keep going with this session.
+2. Stage 1: Goal Contract (`core/goal-contract.md`). If the task is ambiguous and the user can answer, grill first (`core/grill-policy.md`): design tree, recommended answers, do not ask look-up facts. Skip grill if the contract is already frozen or the user waived it. On `adapter_type: dot`, that grill includes `task-impact-inquiry` (this host: `~/.gemini/config/skills/task-impact-inquiry`); do not run a second interview. Freeze before any production edit. Name test seams. Use glossary terms.
+3. Stages 2-4: Maker in the parent. Bugs: red repro first (`core/root-cause-analysis.md`). Features: TDD at named seams (`policies/tdd-policy.md`). Surgical diff.
+4. Stage 5: run commands from `.ai-engineering-loop/verification.md`. Keep command, exit code, stdout, test counts. Vague "seems green" is invalid.
+5. Write artifacts, then spawn. Before Devil's Advocate:
+   - Write `git diff` to a file (for example `.ai-engineering-loop/tasks/current.diff`).
+   - Write changed paths (`git diff --name-only`) into the child prompt as a short list.
+   - Put those paths in the child prompt. Do not paste Maker rationale.
+   - If stopping mid-loop, write `.ai-engineering-loop/tasks/handoff.md` (`core/handoff-policy.md`).
+6. Stage 6: spawn `devil-advocate`. Wait. Prompt: diff file path, name-only list, Goal Contract path, verification log path, conventions.md path, and "at most 8 tool calls; read the diff file; skip css and generated files". Report Spec and Standards axes separately.
+7. Stage 7: spawn `judge` the same way (wait, no background). Prompt: Goal Contract path, verification evidence path, Finding Ledger, and "at most 4 tool calls; ledger and contract only; skip css; do not re-review the whole diff".
+8. ITERATE with iteration under 3: fix in the parent, re-verify, spawn a **new** Devil's Advocate.
+9. Stage 8: delivery from `.ai-engineering-loop/adapter.md`.
+
+## Report header
+
+When a child actually returned a result:
+
+```
+Execution Mode: TRUE_INDEPENDENT_AGENT
+Independent LLM Execution: PROVEN
+Native Subagent Invocation: AVAILABLE
+Review Method: True Independent Agent
+```
+
+When no subagent tool exists:
+
+```
+Execution Mode: CONTEXT_ISOLATION_ONLY
+Independent LLM Execution: NOT PROVEN
+Native Subagent Invocation: UNAVAILABLE
+Review Method: Clean-Slate Artifact Isolation Barrier
+```

package/.grok/agents/devil-advocate.md

@@ -19,15 +19,24 @@ Use only:
 1. The diff file path in the spawn prompt. Read that file first. Do not run git diff if a diff path was given.
 2. Goal Contract path (if given).
 3. Verification log path (if given).
-4. At most 8 source files that appear as paths in the diff.
+4. conventions.md path (if given). At most one extra read.
+5. At most 8 source files that appear as paths in the diff.
 
 Skip: `*.css`, files named like `*-css.ts` or `report-css.ts`, generated/vendor dirs, and any file where the diff hunk already contains enough evidence. Prefer quoting the hunk over opening the whole file.
 
 Do not ask for Maker rationale.
 
-## What to find
+## Two axes (do not merge)
 
-Priority: correctness, error handling, security, concurrency, tests that fail to prove an acceptance criterion. Skip style nits unless they hide a defect.
+Report Spec and Standards as separate findings. Do not rerank one axis with the other. A change can pass Spec and fail Standards, or the reverse. Do not spawn children to split axes.
+
+**Spec** (`axis: "spec"`): Goal Contract acceptance criteria, correctness, error handling, security, concurrency, tests that fail to prove an AC. BLOCKER or HIGH only for a real AC breach or runtime defect.
+
+**Standards** (`axis: "standards"`): `.ai-engineering-loop/conventions.md` plus the smell baseline below. Judgement calls: severity MEDIUM or LOW. Set `hardConvention: true` only when conventions.md states a hard rule that this hunk violates. A smell that hides an AC defect is Spec, not Standards.
+
+Skip style nits unless they hide a defect.
+
+Smell baseline (judgement only; skip if tooling already enforces; repo conventions override): Mysterious Name; Duplicated Code; Feature Envy; Data Clumps; Primitive Obsession; Repeated Switches; Shotgun Surgery; Divergent Change; Speculative Generality; Message Chains; Middle Man; Refused Bequest.
 
 ## Output
 
@@ -40,6 +49,8 @@ Return a Finding Ledger as a fenced JSON block and stop:
   "findings": [
     {
       "id": "DA-01",
+      "axis": "spec",
+      "hardConvention": false,
       "topic": "correctness",
       "validity": "VALID",
       "severity": "BLOCKER",
@@ -55,4 +66,4 @@ Return a Finding Ledger as a fenced JSON block and stop:
 }
 ```
 
-Rules: validity VALID or INVALID; severity BLOCKER, HIGH, MEDIUM, or LOW; disposition STRONG, ACCEPTABLE, or WEAK. VALID BLOCKER or HIGH must include concreteAlternativeDiff. Empty findings is allowed.
+Rules: axis is spec or standards (default spec). hardConvention is boolean, default false. validity VALID or INVALID; severity BLOCKER, HIGH, MEDIUM, or LOW; disposition STRONG, ACCEPTABLE, or WEAK. VALID BLOCKER or HIGH must include concreteAlternativeDiff. Empty findings is allowed.

package/.grok/agents/judge.md

@@ -16,12 +16,16 @@ Finish in at most 4 tool calls, then emit the verdict. Read the Finding Ledger a
 
 Use only paths in the spawn prompt: Goal Contract, verification evidence, Finding Ledger. Ignore Maker optimism and reviewer tone. Disposition never overrides Validity plus Severity.
 
-## Decision matrix
+## Axes
 
-- Verification missing, vague, or non-zero exit: ITERATE
-- Any VALID BLOCKER or HIGH still open: ITERATE (ESCALATE if iteration is 3 or more)
+Do not merge Spec and Standards into one ranking.
+
+- Spec VALID BLOCKER or HIGH (or missing axis, treated as spec): ITERATE (ESCALATE if iteration is 3 or more)
+- Standards VALID BLOCKER or HIGH: ITERATE only when hardConvention is true
+- Other Standards findings: ACCEPT as tradeoff; may still PASS
 - INVALID findings: DISMISS, cannot block delivery
 - VALID MEDIUM or LOW: ACCEPT as tradeoff; may still PASS
+- Verification missing, vague, or non-zero exit: ITERATE
 - All acceptance criteria proven, verification green, zero open blockers: PASS
 
 ## Output

package/.grok/commands/ai-engineering-loop.md

@@ -7,5 +7,5 @@ Follow `.grok/skills/ai-engineering-loop/SKILL.md`.
 
 Arguments:
 
-- `init` / `status` / `refresh` → run `npx ai-engineering-loop <arg>`
+- `init` / `status` / `refresh` / `sync-hosts` → run `npx ai-engineering-loop <arg>`
 - anything else → full 8-stage loop for that task, spawning `devil-advocate` then `judge` via `spawn_subagent`

package/.grok/skills/ai-engineering-loop/SKILL.md

@@ -5,6 +5,7 @@ description: >
   with native spawn_subagent for Devil's Advocate and Judge (TRUE_INDEPENDENT_AGENT).
   Also handles init/status/refresh of .ai-engineering-loop/ living context.
   Triggers: /ai-engineering-loop, "run the engineering loop", "devil's advocate review".
+user-invocable: true
 ---
 
 # AI Engineering Loop — Grok CLI Runtime
@@ -37,21 +38,22 @@ Optional fallback if `devil-advocate` / `judge` types are not registered: `subag
 
 ## Commands
 
-### `/ai-engineering-loop init|status|refresh`
+### `/ai-engineering-loop init|status|refresh|sync-hosts`
 
-Run `npx ai-engineering-loop <command>` in the target repo. Do not commit unless the user asks.
+Run `npx ai-engineering-loop <command>` in the target repo. Do not commit unless the user asks. `sync-hosts` copies this package's skills/agents/commands into `~/.claude`, `~/.grok`, `~/.gemini`, and `~/.agents` for hosts that already exist.
 
 ### `/ai-engineering-loop [task]`
 
-1. Stage 0: `npx ai-engineering-loop status` (init/refresh if missing or stale).
-2. Stage 1: write a Goal Contract (`core/goal-contract.md`).
-3. Stages 2–4: Maker work in the **parent**. Surgical diff + tests. Parent may be the Maker; do not spawn Maker as a child if you still need to spawn DA/Judge afterward from the same parent.
+1. Stage 0: `npx ai-engineering-loop sync-hosts` then `npx ai-engineering-loop status` (init/refresh if missing or stale). Read `.ai-engineering-loop/glossary.md`. If sync-hosts copied files, tell the user a new session is needed for updated skill text; keep going with this session.
+2. Stage 1: Goal Contract (`core/goal-contract.md`). If the task is ambiguous and the user can answer, grill first (`core/grill-policy.md`): design tree, recommended answers, do not ask look-up facts. Skip grill if the contract is already frozen or the user waived it. On `adapter_type: dot`, that grill includes the four-pillar blast radius (state, sibling, approval, queues). Do not run a second interview. Freeze before any production edit. Name test seams. Use glossary terms.
+3. Stages 2–4: Maker work in the **parent**. Bugs: red repro first (`core/root-cause-analysis.md`). Features: TDD at named seams (`policies/tdd-policy.md`). Surgical diff. Parent may be the Maker; do not spawn Maker as a child if you still need to spawn DA/Judge afterward from the same parent.
 4. Stage 5: run verification from `.ai-engineering-loop/verification.md`. Keep command, exit code, stdout, test counts. Vague "seems green" is invalid.
 5. Write artifacts to disk so children do not need parent chat:
    - Goal Contract path
    - `git diff` written to `.ai-engineering-loop/tasks/current.diff`
    - verification log (file)
-6. Stage 6: `spawn_subagent` Devil's Advocate. `background: false`. `capability_mode: "execute"`. Do **not** pass `resume_from`. Wait for the child. Prompt: diff file path, name-only file list, Goal Contract path, verification log path, plus "at most 8 tool calls; read the diff file; skip css and generated files".
+   - If stopping mid-loop, `.ai-engineering-loop/tasks/handoff.md` (`core/handoff-policy.md`)
+6. Stage 6: `spawn_subagent` Devil's Advocate. `background: false`. `capability_mode: "execute"`. Do **not** pass `resume_from`. Wait for the child. Prompt: diff file path, name-only file list, Goal Contract path, verification log path, conventions.md path, plus "at most 8 tool calls; read the diff file; skip css and generated files". Report Spec and Standards axes separately.
 7. Stage 7: `spawn_subagent` Judge the same way (`background: false`, wait). Use `general-purpose` only if `judge` is rejected. Prompt: Goal Contract path, verification evidence path, Finding Ledger, and "at most 4 tool calls; ledger and contract only; skip css; do not re-review the whole diff".
 8. If Judge says `ITERATE` and iteration < 3, Maker fixes in the parent, re-verify, spawn a **fresh** DA (new spawn, no resume).
 9. Stage 8: delivery adapter from `.ai-engineering-loop/adapter.md`.

package/README.md

@@ -6,13 +6,13 @@
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/egagofur/ai-engineering-loop/pulls)
 [![AI Engineering](https://img.shields.io/badge/AI-Engineering%20Loop-orange.svg)](https://github.com/egagofur/ai-engineering-loop)
-[![Release](https://img.shields.io/badge/release-v1.0.11-purple.svg)](https://github.com/egagofur/ai-engineering-loop/releases)
+[![Release](https://img.shields.io/badge/release-v1.0.12-purple.svg)](https://github.com/egagofur/ai-engineering-loop/releases)
 
 **A Reusable, Framework-Agnostic AI Engineering Operating System for Autonomous Coding Agents**
 
 *Featuring living project context, strict verification evidence contracts, 3-stage capability lifecycle registry, and dual-axis Judge evaluation.*
 
-[Overview](#overview--philosophy) • [Runtime Capability Registry](#runtime-capability-registry--execution-modes) • [Verification Evidence](#verification-evidence-contract) • [CLI Commands](#cli-interface--commands) • [Grok CLI](#grok-cli-integration) • [Claude Code](#claude-code-integration) • [Antigravity](#antigravity-agent-integration) • [Lifecycle](#lifecycle-stages) • [Architecture](#architecture--5-layer-configuration) • [Project Profiles](#project-profiles) • [Repository Structure](#repository-structure) • [Reference Examples](#reference-examples) • [Contributing](#contributing)
+[Overview](#overview--philosophy) • [Stage techniques](#stage-techniques) • [Runtime Capability Registry](#runtime-capability-registry--execution-modes) • [Verification Evidence](#verification-evidence-contract) • [CLI Commands](#cli-interface--commands) • [Grok CLI](#grok-cli-integration) • [Claude Code](#claude-code-integration) • [Antigravity](#antigravity-agent-integration) • [Lifecycle](#lifecycle-stages) • [Architecture](#architecture--5-layer-configuration) • [Project Profiles](#project-profiles) • [Repository Structure](#repository-structure) • [Reference Examples](#reference-examples) • [Contributing](#contributing)
 
 </div>
 
@@ -58,6 +58,23 @@ flowchart TD
 
 ---
 
+## Stage techniques
+
+The 8-stage loop stays one OS. These techniques sit **inside** existing stages (they are not optional slash-command products):
+
+| Stage | Technique | Spec |
+|---|---|---|
+| 1 | Grill until the design-tree frontier is empty, then freeze the Goal Contract. Skip if already frozen, waived, or headless with testable AC. | `core/grill-policy.md` |
+| 1 | Ubiquitous language in `.ai-engineering-loop/glossary.md`; load-bearing choices in `.ai-engineering-loop/adrs/` | `core/repo-config-schema.md` |
+| 2 | Bugs: red repro → minimise → hypothesise → instrument → fix | `core/root-cause-analysis.md` |
+| 4–5 | Red-green at named **seams**; no implementation-coupled or tautological tests | `policies/tdd-policy.md` |
+| 6–7 | Spec vs Standards reported separately. Standards BLOCKER/HIGH iterate only when `hardConvention` is true | `policies/finding-policy.md` |
+| any | Mid-loop stop writes `.ai-engineering-loop/tasks/handoff.md` | `core/handoff-policy.md` |
+
+`init` now requires `glossary.md` and `adrs/README.md`. Repair fills missing files only; a filled glossary is never overwritten.
+
+---
+
 ## Runtime Capability Registry & Execution Modes
 
 The system maintains a strict distinction between **Configuration Support**, **Invocation Availability**, and **Execution Proof**:
@@ -160,8 +177,13 @@ npx ai-engineering-loop refresh
 
 # Verify context readiness and begin engineering loop
 npx ai-engineering-loop run
+
+# Copy package skills/agents/commands into ~/.claude ~/.grok ~/.gemini ~/.agents
+npx ai-engineering-loop sync-hosts
 ```
 
+`sync-hosts` updates only hosts that already exist on the machine. DOT skills (`dot-dev-skill-router`, `dot-dev-workflow`) are updated only if they are already installed. It does not install `task-impact-inquiry`. After a copy, start a new session so the host reloads skill text. `/ai-engineering-loop` Stage 0 and `run` call `sync-hosts` so a published package bump reaches global host files without a manual copy.
+
 ---
 
 ## Grok CLI Integration
@@ -243,7 +265,7 @@ ai-engineering-loop/
 ├── package.json                        # CLI package manifest
 │
 ├── bin/                                # CLI execution entrypoints
-│   └── ai-engineering-loop.js          # npx executable CLI (init, status, refresh, run)
+│   └── ai-engineering-loop.js          # npx executable CLI (init, status, refresh, run, sync-hosts)
 │
 ├── lib/                                # Core orchestration & decision engine
 │   └── orchestration.js                # 3-stage capability registry, barrier builder, Judge engine
@@ -276,6 +298,9 @@ ai-engineering-loop/
 │   ├── context-refresh-policy.md       # Progressive drift hierarchy & living baseline
 │   ├── context-impact-assessment.md    # Post-task impact assessment (NONE, TARGETED, MAJOR)
 │   ├── goal-contract.md                # Task contract schema & acceptance criteria
+│   ├── grill-policy.md                 # Stage 1 human alignment (design tree)
+│   ├── root-cause-analysis.md          # Stage 2 diagnosis gates
+│   ├── handoff-policy.md               # Mid-loop session handoff artifact
 │   ├── verification-loop.md            # Dual-layer verification & Evidence Contract
 │   ├── definition-of-done.md           # 5 pillars of Done & rejection triggers
 │   ├── iteration-policy.md             # Bounded autonomous loop (MAX_ITERATIONS = 3)
@@ -300,6 +325,7 @@ ai-engineering-loop/
 ├── policies/                           # Operational schemas & algorithms
 │   ├── discovery-safety-policy.md      # Secret protection & non-destructive discovery rules
 │   ├── finding-policy.md               # Dual-axis finding schema & severity matrix
+│   ├── tdd-policy.md                   # Red-green at named seams
 │   ├── evidence-policy.md              # 5-level evidence hierarchy & Verification Evidence Contract
 │   └── no-progress-policy.md           # Finding signature hashing & stagnation detection
 │
@@ -315,6 +341,8 @@ ai-engineering-loop/
     └── repo-config/                    # Ready-to-copy .ai-engineering-loop/ files
         ├── config.md                   # Project identity & profile binding
         ├── architecture.md             # Layers & boundary invariants
+        ├── glossary.md                 # Ubiquitous language
+        ├── adr-readme.md               # ADR folder template
         ├── conventions.md              # Code standards & forbidden patterns
         ├── verification.md             # CLI test/lint/build commands
         └── adapter.md                  # Configured release pipeline

package/README.npm.md

@@ -26,14 +26,17 @@ npx ai-engineering-loop refresh
 
 # 4. Verify context readiness and begin engineering loop
 npx ai-engineering-loop run
+
+# 5. Copy package host skills into ~/.claude ~/.grok ~/.gemini ~/.agents
+npx ai-engineering-loop sync-hosts
 ```
 
 ---
 
 ## What It Does
 
-1. **Zero-Config Discovery (`init`)**: Analyzes repository topology (monorepo vs single app), package manifests (`package.json`, `go.mod`, `Cargo.toml`, etc.), frameworks, and test scripts to generate `.ai-engineering-loop/`.
-2. **Living Project Context**: Tracks repository revisions and manifest checksums in `metadata.json` for instant drift detection.
+1. **Zero-Config Discovery (`init`)**: Analyzes repository topology (monorepo vs single app), package manifests (`package.json`, `go.mod`, `Cargo.toml`, etc.), frameworks, and test scripts to generate `.ai-engineering-loop/` including `glossary.md` and `adrs/`.
+2. **Living Project Context**: Tracks repository revisions and manifest checksums in `metadata.json` for instant drift detection. Stage 1 grill freezes a Goal Contract; Maker uses TDD at named seams; DA reports Spec vs Standards without merging them.
 3. **Multi-Agent Triad**: Coordinates **Maker** (surgical diffs & tests), **Devil's Advocate** (independent adversarial review), and **Judge** (impartial evaluation & PASS certification).
 4. **Context Impact Assessment**: Evaluates completed tasks (`NONE`, `TARGETED`, `MAJOR`) to keep project context fresh without expensive whole-repo re-analysis.
 5. **Grok CLI host**: Native `spawn_subagent` for Devil's Advocate and Judge (`TRUE_INDEPENDENT_AGENT`). Disabled by `GROK_SUBAGENTS=0`.

package/adapters/dot/README.md

@@ -36,15 +36,39 @@ The DOT adapter is organized into four dedicated specification modules:
    - Clean cherry-picking workflow and target-specific test verification.
 3. **[Coreview External Reviewer Triage (`coreview.md`)](file:///Users/egagofur/Development/work/ai-engineering-loop/adapters/dot/coreview.md)**:
    - Ingestion of `@coreview-bot` automated PR comments.
-   - Rigorous evaluation of bot suggestions into `VALID` (fix & propagate) vs `HALU` (false positive pushback).
+   - Mandatory Phase 8 Triage reporting gate before Mattermost dispatch.
+   - Rigorous evaluation of bot suggestions into `VALID` (fix & propagate) vs `HALU` (false positive pushback) using principles from `gitlab-mr-feedback` and `receiving-code-review`.
 4. **[Mattermost Notifications (`mattermost.md`)](file:///Users/egagofur/Development/work/ai-engineering-loop/adapters/dot/mattermost.md)**:
    - Repository-to-channel resolution using persistent configuration.
    - MCP `mattermost_send_message` dispatch with mandatory `from: "AI Agent"` attribution.
-   - Environment-tagged Markdown blocks (`[MR DEV]`, `[MR STAGING]`, `[MR MAIN]`).
+   - Environment-tagged Markdown blocks (`[MR DEV]`, `[MR STAGING]`, `[MR MAIN]`) formatted with strict **`no-ai-slop`** human-written standards.
 
 ---
 
-## 3. Separation of Concerns
+## 3. Official DOT Engineering Skills Integration
+
+This adapter composes the DOT skill suite that Antigravity loads from `~/.gemini/config/skills/` (not from `~/.claude/skills/` and not from this npm package). Claude Code and Grok do not get these skills unless the same files are installed on those hosts.
+
+On a DOT repo (`adapter_type: dot`), **run `ai-engineering-loop`**, not the old 9-phase `dot-dev-workflow`, as the engineering OS. Stage 1 grill **includes** `task-impact-inquiry`. Do not run a second interview. After Judge `PASS`, Stage 8 is `dot-dev-workflow` delivery (GitLab, cherry-pick, Coreview, Mattermost). Canonical copies: `adapters/dot/skills/`. See `core/grill-policy.md`.
+
+| Skill | Primary Role & Governance |
+| :--- | :--- |
+| **`ai-engineering-loop`** | Engineering OS (Stages 0-7). Use this for DOT bugfix/feature/refactor. |
+| **`dot-dev-workflow`** | Stage 8 delivery only after Judge PASS. Not a parallel engineering loop. |
+| **`dot-dev-skill-router`** | Routes commit-bound DOT work to `ai-engineering-loop`, then Stage 8. |
+| **`task-impact-inquiry`** | Antigravity skill at `~/.gemini/config/skills/task-impact-inquiry/`. Four-pillar blast radius (state, sibling, approval, downstream queues). Fills Stage 1 grill on DOT; then freeze the Goal Contract. |
+| **`backend-development`** | Framework-agnostic backend guidelines (clean naming, database queries, security, error handling). |
+| **`backend-safety-guardrails`** | 6 architectural backend safety invariants (queue bypass, BigInt, status recalculation loops). |
+| **`devils-advocate`** | Legacy DOT pre-commit skill. On AEL, Stages 6-7 are package Devil's Advocate + Judge. Do not re-run this skill after Judge PASS. |
+| **`requesting-code-review`** | Optional peer-review dispatch. AEL Judge is the pre-commit gate. |
+| **`receiving-code-review`** | Technical rigor in evaluating review feedback without blind compliance. |
+| **`gitlab-mr-feedback`** | GitLab API patterns and thread resolution on MR discussions. |
+| **`auto-mr-issue`** | Automated issue, MR creation, and Mattermost Markdown formatting. |
+| **`no-ai-slop`** | Human-written, crisp, active-voice release notes without AI puffery. |
+
+---
+
+## 4. Separation of Concerns
 
 | Generic Core Responsibility | DOT Adapter Responsibility |
 |---|---|

package/adapters/dot/coreview.md

@@ -5,21 +5,34 @@
 In the DOT ecosystem, `@coreview-bot` operates as an external, company-level automated code reviewer attached to GitLab Merge Requests (specifically MRs targeting `develop`).
 
 > [!IMPORTANT]
-> **We do not have access to `@coreview-bot`'s internal rules or heuristics.**
-> - Do not attempt to reverse-engineer or invent Coreview behavior.
-> - Treat Coreview strictly as an external reviewer providing asynchronous critique on GitLab MRs.
-> - Evaluate its comments objectively through the lens of the repository's ground truth.
+> **GATE sebelum Phase 9 (Mattermost Dispatch)**:
+> Dilarang mengirim Mattermost sebelum hasil `glab mr view --comments` **tercetak di pesan ke user**.
+> Jika `comments: 0`, triage kosong tetap wajib dilaporkan sebagai bukti bahwa pengecekan bot telah dilakukan secara riil.
+> 
+> Selalu cetak laporan triage dengan format:
+> ```text
+> Phase 8 Triage
+> MR: !<id>
+> Command: glab mr view <id> --comments
+> Comments: <n>
+> Valid: <list atau none>
+> Halu: <list atau none>
+> Action: <none | fix | reply>
+> ```
 
 ---
 
 ## 2. Coreview Triage Workflow
 
+Mengikuti panduan dari skill `gitlab-mr-feedback` dan `receiving-code-review` (verifikasi teknis menyeluruh sebelum implementasi, tanpa *performative agreement*).
+
 ```mermaid
 flowchart TD
     MRDev[MR Targeting develop Created] --> FetchBot[Fetch Comments via glab mr view --comments]
-    FetchBot --> CheckComments{Bot Comments Found?}
+    FetchBot --> PrintTriage[Print Phase 8 Triage Report to User]
+    PrintTriage --> CheckComments{Bot Comments Found?}
     
-    CheckComments -->|No| Done([Complete Triage])
+    CheckComments -->|No: comments: 0| Done([Complete Triage -> Gate Passed])
     CheckComments -->|Yes| Evaluate{Evaluate Each Comment}
     
     Evaluate -->|VALID: Real Defect| Fix[1. Surgical Code Fix<br>2. Run Tests & Linter<br>3. Commit & Cherry-pick to all branches<br>4. Reply with commit hash]
@@ -63,12 +76,15 @@ Every Coreview comment must be categorized into one of two paths:
      git push origin <branch-name>
      ```
   4. Cherry-pick the new fix commit to all other active environment branches (`main`, `staging`).
-  5. Post a resolution note on GitLab citing the commit hash:
+  5. Post a resolution reply directly **inside the bot's discussion thread**:
      ```bash
-     glab mr note <mr-id> --repo <repo> -m "Fixed in commit <commit-hash>: <technical explanation of the resolution>"
+     # Get discussion_id: glab api "projects/:fullpath/merge_requests/<mr-id>/discussions"
+     glab api "projects/:fullpath/merge_requests/<mr-id>/discussions/<discussion_id>/notes" \
+       -X POST \
+       -F "body=Fixed in commit <commit-hash>: <technical explanation of the resolution>"
      ```
 
-### Case B: Feedback is HALU (False Positive / Hallucinated)
+### Case B: Feedback is HALU (False Positive / Intended Architecture)
 - **Criteria**:
   - The bot suggests calling an API, library method, or hook that does not exist in the codebase or standard library.
   - The bot flags intentional architecture or established framework patterns as "errors".
@@ -76,9 +92,12 @@ Every Coreview comment must be categorized into one of two paths:
   - The bot misinterprets domain-specific business logic already agreed in the Goal Contract.
 - **Action Plan**:
   1. **DO NOT modify any code.**
-  2. Post a polite, evidence-backed technical rebuttal on the GitLab note explaining why the suggestion is invalid:
+  2. Post a polite, evidence-backed technical rebuttal directly **inside the bot's discussion thread**:
      ```bash
-     glab mr note <mr-id> --repo <repo> -m "Feedback is invalid / false positive: <detailed technical explanation with file citations>."
+     # Get discussion_id: glab api "projects/:fullpath/merge_requests/<mr-id>/discussions"
+     glab api "projects/:fullpath/merge_requests/<mr-id>/discussions/<discussion_id>/notes" \
+       -X POST \
+       -F "body=Terima kasih atas masukannya @coreview-bot. <detailed technical explanation with file citations>."
      ```
 
 ---