ai-engineering-loop 1.0.14 → 1.0.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (46) hide show
  1. package/.agents/workflows/ai-engineering-loop.md +2 -2
  2. package/.claude/commands/ai-engineering-loop.md +1 -1
  3. package/.claude/skills/ai-engineering-loop/SKILL.md +4 -3
  4. package/.gemini/skills/ai-engineering-loop/SKILL.md +4 -3
  5. package/.grok/commands/ai-engineering-loop.md +1 -1
  6. package/.grok/skills/ai-engineering-loop/SKILL.md +4 -4
  7. package/README.md +16 -10
  8. package/adapters/README.md +27 -0
  9. package/adapters/dot/README.md +8 -8
  10. package/adapters/dot/coreview.md +3 -2
  11. package/adapters/dot/gitlab.md +3 -3
  12. package/adapters/dot/mattermost.md +59 -71
  13. package/adapters/dot/multi-branch.md +3 -2
  14. package/adapters/dot/skills/dot-dev-workflow/SKILL.md +2 -2
  15. package/adapters/dot/skills/task-impact-inquiry/SKILL.md +155 -0
  16. package/adapters/generate-adapter/SKILL.md +123 -0
  17. package/adapters/github/README.md +28 -0
  18. package/adapters/github/pull-request.md +23 -0
  19. package/adapters/gitlab/README.md +28 -0
  20. package/adapters/gitlab/merge-request.md +26 -0
  21. package/adapters/standard/README.md +44 -0
  22. package/bin/ai-engineering-loop.js +31 -3
  23. package/core/grill-policy.md +14 -10
  24. package/core/repo-config-schema.md +1 -1
  25. package/examples/backend-api/payment-idempotency/README.md +3 -3
  26. package/examples/dot/status-display/README.md +23 -0
  27. package/examples/dot/status-display/delivery-report.md +41 -0
  28. package/examples/dot/status-display/goal-contract.md +46 -0
  29. package/examples/dot/status-display/judge-verdict.md +44 -0
  30. package/examples/dot/status-display/review-findings.md +63 -0
  31. package/examples/initialization/README.md +2 -2
  32. package/examples/initialization/discovery-trace.md +1 -1
  33. package/examples/mobile-app/offline-sync-queue/README.md +3 -3
  34. package/lib/generate-adapter.js +118 -0
  35. package/lib/sync-hosts.js +7 -1
  36. package/package.json +1 -1
  37. package/templates/repo-config/adapter.md +1 -1
  38. package/tests/generate-adapter.test.js +80 -0
  39. package/tests/no-company-leak.test.js +82 -0
  40. package/tests/skill-host-compat.test.js +45 -7
  41. package/tests/sync-hosts.test.js +33 -1
  42. package/examples/dot/attendance-confirmation/README.md +0 -22
  43. package/examples/dot/attendance-confirmation/delivery-report.md +0 -51
  44. package/examples/dot/attendance-confirmation/goal-contract.md +0 -39
  45. package/examples/dot/attendance-confirmation/judge-verdict.md +0 -43
  46. package/examples/dot/attendance-confirmation/review-findings.md +0 -57
@@ -5,7 +5,7 @@ description: Run the AI Engineering Loop on Antigravity (init, status, refresh,
5
5
 
6
6
  Follow `policies/review-budget.md`. Parent is Maker plus orchestrator. Do not use `browser_subagent`.
7
7
 
8
- Stage 1: if the user asks for ideas, list a short menu and wait; do not implement. Grill if the task is ambiguous (`core/grill-policy.md`), then freeze the Goal Contract file. Chat agreement is not freeze. 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. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only. Maker: TDD at those seams (`policies/tdd-policy.md`): one red test per AC row. Bugs: red repro first (`core/root-cause-analysis.md`). Mid-loop stop: `core/handoff-policy.md`.
8
+ Stage 1: if the user asks for ideas, list a short menu and wait; do not implement. Grill if the task is ambiguous (`core/grill-policy.md`), then freeze the Goal Contract file. Chat agreement is not freeze. On business-logic change, and always on `adapter_type: dot`, grill includes blast radius: lifecycle sketch, four pillars (state, sibling, approval, queues), ASCII picture. Load `task-impact-inquiry` if present. Do not run a second interview. Passing unit tests are not isolation proof. Use `.ai-engineering-loop/glossary.md`. Name test seams. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only. Maker: TDD at those seams (`policies/tdd-policy.md`): one red test per AC row. Bugs: red repro first (`core/root-cause-analysis.md`). Mid-loop stop: `core/handoff-policy.md`.
9
9
 
10
10
  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.
11
11
 
@@ -15,4 +15,4 @@ If `invoke_subagent` (or Task) exists, spawn `devil-advocate` then `judge` as si
15
15
 
16
16
  If no subagent tool exists, run the same budgets in this session as CONTEXT_ISOLATION_ONLY. Do not claim independent agent execution.
17
17
 
18
- 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.
18
+ Init/status/refresh/sync-hosts/generate-adapter: `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. Stage 8: load `adapters/<adapter_type>/`. If adapter.md is missing, run `generate-adapter` (grill). Do not invent a company pipeline.
@@ -8,4 +8,4 @@ Follow `.claude/skills/ai-engineering-loop/SKILL.md`.
8
8
 
9
9
  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.
10
10
 
11
- Arguments: init, status, refresh, sync-hosts, or a task description.
11
+ Arguments: init, status, refresh, sync-hosts, generate-adapter, or a task description.
@@ -24,7 +24,8 @@ Claude Code talks to strict proxies (including Kiro). Follow this exactly:
24
24
 
25
25
  ## Commands
26
26
 
27
- - `init` / `status` / `refresh` / `sync-hosts`: run `npx ai-engineering-loop <command>` in the repo. Do not commit unless asked.
27
+ - `init` / `status` / `refresh` / `sync-hosts` / `generate-adapter`: run `npx ai-engineering-loop <command>` in the repo. Do not commit unless asked.
28
+ - `generate-adapter`: load skill `generate-adapter` if present. Grill Q1-Q5. Then write `.ai-engineering-loop/adapter.md`. Do not start Maker.
28
29
  - Any other argument: full loop for that task.
29
30
 
30
31
  ## Loop
@@ -32,7 +33,7 @@ Claude Code talks to strict proxies (including Kiro). Follow this exactly:
32
33
  Parent session is Maker plus orchestrator. Spawn Devil's Advocate and Judge as **siblings**, not nested.
33
34
 
34
35
  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.
35
- 2. Stage 1: Goal Contract (`core/goal-contract.md`). If the user asks for ideas, list a short menu and wait; do not implement. 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. Chat agreement is not freeze: every user-visible decision must be a numbered AC in the Goal Contract file. Freeze before any production edit. Name test seams. Use glossary terms. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only.
36
+ 2. Stage 1: Goal Contract (`core/goal-contract.md`). If the user asks for ideas, list a short menu and wait; do not implement. 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 business-logic change, and always on `adapter_type: dot`, grill includes blast radius: lifecycle sketch, four pillars (state, sibling, approval, queues), ASCII picture. Load `task-impact-inquiry` if present. Do not run a second interview. Passing unit tests are not isolation proof. Chat agreement is not freeze: every user-visible decision must be a numbered AC in the Goal Contract file. Freeze before any production edit. Name test seams. Use glossary terms. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only.
36
37
  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`): one red test per AC row. Surgical diff.
37
38
  4. Stage 5: run commands from `.ai-engineering-loop/verification.md`. Keep command, exit code, stdout, test counts. Vague "seems green" is invalid.
38
39
  5. Write artifacts, then spawn. Before Devil's Advocate:
@@ -43,7 +44,7 @@ Parent session is Maker plus orchestrator. Spawn Devil's Advocate and Judge as *
43
44
  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.
44
45
  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".
45
46
  8. ITERATE with iteration under 3: fix in the parent, re-verify, spawn a **new** Devil's Advocate (do not resume the previous child).
46
- 9. Stage 8: delivery from `.ai-engineering-loop/adapter.md`.
47
+ 9. Stage 8: delivery from `.ai-engineering-loop/adapter.md`. Load shipped spec `adapters/<adapter_type>/` (`standard`, `github`, `gitlab`, `dot`). If adapter.md is missing or the type is unknown, run `generate-adapter` (grill). Do not invent a company pipeline.
47
48
 
48
49
  ## Report header
49
50
 
@@ -19,13 +19,14 @@ Canonical mode ids: `TRUE_INDEPENDENT_AGENT`, `ISOLATED_AGENT_INSTANCE`, `FRESH_
19
19
 
20
20
  ## Commands
21
21
 
22
- - `init` / `status` / `refresh` / `sync-hosts`: run `npx ai-engineering-loop <command>` in the repo. Do not commit unless asked.
22
+ - `init` / `status` / `refresh` / `sync-hosts` / `generate-adapter`: run `npx ai-engineering-loop <command>` in the repo. Do not commit unless asked.
23
+ - `generate-adapter`: load skill `generate-adapter` if present. Grill Q1-Q5. Then write `.ai-engineering-loop/adapter.md`. Do not start Maker.
23
24
  - Any other argument: full loop for that task.
24
25
 
25
26
  ## Loop
26
27
 
27
28
  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.
28
- 2. Stage 1: Goal Contract (`core/goal-contract.md`). If the user asks for ideas, list a short menu and wait; do not implement. 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. Chat agreement is not freeze: every user-visible decision must be a numbered AC in the Goal Contract file. Freeze before any production edit. Name test seams. Use glossary terms. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only.
29
+ 2. Stage 1: Goal Contract (`core/goal-contract.md`). If the user asks for ideas, list a short menu and wait; do not implement. 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 business-logic change, and always on `adapter_type: dot`, grill includes blast radius: lifecycle sketch, four pillars (state, sibling, approval, queues), ASCII picture. Load `task-impact-inquiry` if present. Do not run a second interview. Passing unit tests are not isolation proof. Chat agreement is not freeze: every user-visible decision must be a numbered AC in the Goal Contract file. Freeze before any production edit. Name test seams. Use glossary terms. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only.
29
30
  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`): one red test per AC row. Surgical diff.
30
31
  4. Stage 5: run commands from `.ai-engineering-loop/verification.md`. Keep command, exit code, stdout, test counts. Vague "seems green" is invalid.
31
32
  5. Write artifacts, then spawn. Before Devil's Advocate:
@@ -36,7 +37,7 @@ Canonical mode ids: `TRUE_INDEPENDENT_AGENT`, `ISOLATED_AGENT_INSTANCE`, `FRESH_
36
37
  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.
37
38
  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".
38
39
  8. ITERATE with iteration under 3: fix in the parent, re-verify, spawn a **new** Devil's Advocate.
39
- 9. Stage 8: delivery from `.ai-engineering-loop/adapter.md`.
40
+ 9. Stage 8: delivery from `.ai-engineering-loop/adapter.md`. Load shipped spec `adapters/<adapter_type>/` (`standard`, `github`, `gitlab`, `dot`). If adapter.md is missing or the type is unknown, run `generate-adapter` (grill). Do not invent a company pipeline.
40
41
 
41
42
  ## Report header
42
43
 
@@ -7,5 +7,5 @@ Follow `.grok/skills/ai-engineering-loop/SKILL.md`.
7
7
 
8
8
  Arguments:
9
9
 
10
- - `init` / `status` / `refresh` / `sync-hosts` → run `npx ai-engineering-loop <arg>`
10
+ - `init` / `status` / `refresh` / `sync-hosts` / `generate-adapter` → run `npx ai-engineering-loop <arg>`
11
11
  - anything else → full 8-stage loop for that task, spawning `devil-advocate` then `judge` via `spawn_subagent`
@@ -38,14 +38,14 @@ Optional fallback if `devil-advocate` / `judge` types are not registered: `subag
38
38
 
39
39
  ## Commands
40
40
 
41
- ### `/ai-engineering-loop init|status|refresh|sync-hosts`
41
+ ### `/ai-engineering-loop init|status|refresh|sync-hosts|generate-adapter`
42
42
 
43
- 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.
43
+ 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. `generate-adapter`: load skill `generate-adapter` if present. Grill Q1-Q5. Then write `.ai-engineering-loop/adapter.md`. Do not start Maker.
44
44
 
45
45
  ### `/ai-engineering-loop [task]`
46
46
 
47
47
  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.
48
- 2. Stage 1: Goal Contract (`core/goal-contract.md`). If the user asks for ideas, list a short menu and wait; do not implement. 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. Chat agreement is not freeze: every user-visible decision must be a numbered AC in the Goal Contract file. Freeze before any production edit. Name test seams. Use glossary terms. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only.
48
+ 2. Stage 1: Goal Contract (`core/goal-contract.md`). If the user asks for ideas, list a short menu and wait; do not implement. 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 business-logic change, and always on `adapter_type: dot`, grill includes blast radius: lifecycle sketch, four pillars (state, sibling, approval, queues), ASCII picture. Load `task-impact-inquiry` if present. Do not run a second interview. Passing unit tests are not isolation proof. Chat agreement is not freeze: every user-visible decision must be a numbered AC in the Goal Contract file. Freeze before any production edit. Name test seams. Use glossary terms. AC is a failure table (happy, empty/omit, boundary, sibling, error). One red test per AC row. Do not freeze sunny-path-only.
49
49
  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`): one red test per AC row. 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.
50
50
  4. Stage 5: run verification from `.ai-engineering-loop/verification.md`. Keep command, exit code, stdout, test counts. Vague "seems green" is invalid.
51
51
  5. Write artifacts to disk so children do not need parent chat:
@@ -56,7 +56,7 @@ Run `npx ai-engineering-loop <command>` in the target repo. Do not commit unless
56
56
  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.
57
57
  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".
58
58
  8. If Judge says `ITERATE` and iteration < 3, Maker fixes in the parent, re-verify, spawn a **fresh** DA (new spawn, no resume).
59
- 9. Stage 8: delivery adapter from `.ai-engineering-loop/adapter.md`.
59
+ 9. Stage 8: delivery from `.ai-engineering-loop/adapter.md`. Load shipped spec `adapters/<adapter_type>/` (`standard`, `github`, `gitlab`, `dot`). If adapter.md is missing or the type is unknown, run `generate-adapter` (grill). Do not invent a company pipeline.
60
60
 
61
61
  After a proven Grok DA spawn, the report header must be:
62
62
 
package/README.md CHANGED
@@ -6,7 +6,7 @@
6
6
  [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
7
7
  [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/egagofur/ai-engineering-loop/pulls)
8
8
  [![AI Engineering](https://img.shields.io/badge/AI-Engineering%20Loop-orange.svg)](https://github.com/egagofur/ai-engineering-loop)
9
- [![Release](https://img.shields.io/badge/release-v1.0.14-purple.svg)](https://github.com/egagofur/ai-engineering-loop/releases)
9
+ [![Release](https://img.shields.io/badge/release-v1.0.16-purple.svg)](https://github.com/egagofur/ai-engineering-loop/releases)
10
10
 
11
11
  **A Reusable, Framework-Agnostic AI Engineering Operating System for Autonomous Coding Agents**
12
12
 
@@ -64,7 +64,7 @@ The 8-stage loop stays one OS. These techniques sit **inside** existing stages (
64
64
 
65
65
  | Stage | Technique | Spec |
66
66
  |---|---|---|
67
- | 1 | Grill until the design-tree frontier is empty, then freeze the Goal Contract. Idea requests: menu, wait, then grill the pick. Chat `setuju` is not freeze; user-visible decisions must be numbered AC in the contract file. AC is a **failure table** (happy, empty/omit, boundary, sibling, error), not sunny path only. | `core/grill-policy.md` |
67
+ | 1 | Grill until the design-tree frontier is empty, then freeze the Goal Contract. Idea requests: menu, wait, then grill the pick. Chat `setuju` is not freeze; user-visible decisions must be numbered AC in the contract file. AC is a **failure table** (happy, empty/omit, boundary, sibling, error), not sunny path only. Business-logic change: **blast radius** (lifecycle sketch, four pillars, ASCII picture) via `task-impact-inquiry` inside grill — not a second loop. Passing unit tests are not isolation proof. | `core/grill-policy.md` |
68
68
  | 1 | Ubiquitous language in `.ai-engineering-loop/glossary.md`; load-bearing choices in `.ai-engineering-loop/adrs/` | `core/repo-config-schema.md` |
69
69
  | 2 | Bugs: red repro → minimise → hypothesise → instrument → fix | `core/root-cause-analysis.md` |
70
70
  | 4–5 | Red-green at named **seams**; failure table (not happy path only); coverage is a map; no grep/tautology | `policies/tdd-policy.md` |
@@ -180,9 +180,15 @@ npx ai-engineering-loop run
180
180
 
181
181
  # Copy package skills/agents/commands into ~/.claude ~/.grok ~/.gemini ~/.agents
182
182
  npx ai-engineering-loop sync-hosts
183
+
184
+ # Grill (or --type) a Stage 8 delivery adapter for this repo
185
+ npx ai-engineering-loop generate-adapter
186
+ npx ai-engineering-loop generate-adapter --type github
183
187
  ```
184
188
 
185
- `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.
189
+ Shipped adapters (Stage 8 only, after Judge PASS): `standard`, `github`, `gitlab`, `dot`. Catalog: `adapters/README.md`. Each team generates its own; do not copy a neighbour's pipeline.
190
+
191
+ `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. `task-impact-inquiry` and `generate-adapter` are upserted onto Claude, Grok, and Gemini. 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.
186
192
 
187
193
  ---
188
194
 
@@ -329,13 +335,13 @@ ai-engineering-loop/
329
335
  │ ├── evidence-policy.md # 5-level evidence hierarchy & Verification Evidence Contract
330
336
  │ └── no-progress-policy.md # Finding signature hashing & stagnation detection
331
337
  │
332
- ├── adapters/ # Pluggable delivery pipelines
333
- │ └── dot/ # DOT Indonesia delivery adapter
334
- │ ├── README.md # DOT adapter overview
335
- │ ├── gitlab.md # glab CLI, issue cards, & MR generation
336
- │ ├── multi-branch.md # main / staging / develop cherry-pick propagation
337
- │ ├── coreview.md # @coreview-bot external review triage (Valid vs Halu)
338
- │ └── mattermost.md # Channel mapping & MCP dispatch (from: "AI Agent")
338
+ ├── adapters/ # Pluggable Stage 8 delivery (not a second OS)
339
+ │ ├── README.md # Catalog: standard, github, gitlab, dot
340
+ │ ├── generate-adapter/SKILL.md # Grill Q1-Q5, then write adapter.md
341
+ │ ├── standard/ # Generic git delivery (any forge)
342
+ │ ├── github/ # gh pr / GitHub Issues
343
+ │ ├── gitlab/ # glab mr (not the DOT pipeline)
344
+ │ └── dot/ # DOT-specific GitLab + multi-branch + chat
339
345
  │
340
346
  └── templates/ # Starter templates for target repositories
341
347
  └── repo-config/ # Ready-to-copy .ai-engineering-loop/ files
@@ -0,0 +1,27 @@
1
+ # Delivery adapters
2
+
3
+ Stages 0–7 are the same on every host. **Stage 8 is the only place that knows your forge.**
4
+
5
+ An adapter is not a second engineering OS. It runs **after Judge `PASS`**. It must not start Maker, amend the Goal Contract, or skip Devil's Advocate.
6
+
7
+ ## Shipped types
8
+
9
+ | Type | Use when | Spec |
10
+ |---|---|---|
11
+ | **`standard`** | Default. Any git repo. No company tools assumed. | [`standard/`](standard/) |
12
+ | **`github`** | `github.com` remote, `gh` CLI | [`github/`](github/) |
13
+ | **`gitlab`** | GitLab.com or self-hosted GitLab (not DOT) | [`gitlab/`](gitlab/) |
14
+ | **`dot`** | DOT delivery (GitLab + multi-branch + Coreview + Mattermost) | [`dot/`](dot/) |
15
+
16
+ Pick one with `npx ai-engineering-loop generate-adapter`. The agent **asks** (grill). Do not copy a neighbour's adapter.
17
+
18
+ Custom tools (Linear, Slack, Bitbucket): still start from `standard`, then name those tools in `.ai-engineering-loop/adapter.md`. Do not put secrets in the file.
19
+
20
+ ## Generate
21
+
22
+ ```bash
23
+ npx ai-engineering-loop generate-adapter
24
+ npx ai-engineering-loop generate-adapter --type github
25
+ ```
26
+
27
+ Interactive path: load skill `generate-adapter`, answer Q1–Q5, then the agent writes `.ai-engineering-loop/adapter.md`.
@@ -2,7 +2,7 @@
2
2
 
3
3
  ## 1. Overview & Architecture
4
4
 
5
- The **DOT Delivery Adapter** connects the generic [AI Engineering Loop](file:///Users/egagofur/Development/work/ai-engineering-loop/README.md) to the specific development infrastructure of **DOT Indonesia**.
5
+ The **DOT Delivery Adapter** connects the generic [AI Engineering Loop](../../README.md) to DOT's delivery tools (GitLab, multi-branch, Coreview, Mattermost).
6
6
 
7
7
  The generic engineering loop guarantees that code is correct, verified, and adversarially tested. The DOT adapter is responsible for downstream release engineering, collaboration tools, issue tracking, and multi-environment synchronization.
8
8
 
@@ -27,18 +27,18 @@ flowchart TD
27
27
 
28
28
  The DOT adapter is organized into four dedicated specification modules:
29
29
 
30
- 1. **[GitLab Integration (`gitlab.md`)](file:///Users/egagofur/Development/work/ai-engineering-loop/adapters/dot/gitlab.md)**:
30
+ 1. **[GitLab Integration (`gitlab.md`)](gitlab.md)**:
31
31
  - CLI automation with `glab`.
32
32
  - Standardized issue card templates with actual vs expected tables and QA testing steps.
33
33
  - Standardized MR descriptions linking issue IDs and change summaries.
34
- 2. **[Multi-Branch Propagation (`multi-branch.md`)](file:///Users/egagofur/Development/work/ai-engineering-loop/adapters/dot/multi-branch.md)**:
34
+ 2. **[Multi-Branch Propagation (`multi-branch.md`)](multi-branch.md)**:
35
35
  - Multi-environment branching model across `main`, `staging`, and `develop`.
36
36
  - Clean cherry-picking workflow and target-specific test verification.
37
- 3. **[Coreview External Reviewer Triage (`coreview.md`)](file:///Users/egagofur/Development/work/ai-engineering-loop/adapters/dot/coreview.md)**:
37
+ 3. **[Coreview External Reviewer Triage (`coreview.md`)](coreview.md)**:
38
38
  - Ingestion of `@coreview-bot` automated PR comments.
39
39
  - Mandatory Phase 8 Triage reporting gate before Mattermost dispatch.
40
40
  - Rigorous evaluation of bot suggestions into `VALID` (fix & propagate) vs `HALU` (false positive pushback) using principles from `gitlab-mr-feedback` and `receiving-code-review`.
41
- 4. **[Mattermost Notifications (`mattermost.md`)](file:///Users/egagofur/Development/work/ai-engineering-loop/adapters/dot/mattermost.md)**:
41
+ 4. **[Mattermost Notifications (`mattermost.md`)](mattermost.md)**:
42
42
  - Repository-to-channel resolution using persistent configuration.
43
43
  - MCP `mattermost_send_message` dispatch with mandatory `from: "AI Agent"` attribution.
44
44
  - Environment-tagged Markdown blocks (`[MR DEV]`, `[MR STAGING]`, `[MR MAIN]`) formatted with strict **`no-ai-slop`** human-written standards.
@@ -47,7 +47,7 @@ The DOT adapter is organized into four dedicated specification modules:
47
47
 
48
48
  ## 3. Official DOT Engineering Skills Integration
49
49
 
50
- 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.
50
+ This adapter composes the DOT skill suite. `task-impact-inquiry` ships in this package (`adapters/dot/skills/task-impact-inquiry/`) and `sync-hosts` upserts it to Claude, Grok, and Gemini. Other DOT skills (router, workflow) still update-if-exists only.
51
51
 
52
52
  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`.
53
53
 
@@ -56,7 +56,7 @@ On a DOT repo (`adapter_type: dot`), **run `ai-engineering-loop`**, not the old
56
56
  | **`ai-engineering-loop`** | Engineering OS (Stages 0-7). Use this for DOT bugfix/feature/refactor. |
57
57
  | **`dot-dev-workflow`** | Stage 8 delivery only after Judge PASS. Not a parallel engineering loop. |
58
58
  | **`dot-dev-skill-router`** | Routes commit-bound DOT work to `ai-engineering-loop`, then Stage 8. |
59
- | **`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. |
59
+ | **`task-impact-inquiry`** | Business blast radius (lifecycle sketch, four pillars, ASCII picture). Canonical: `adapters/dot/skills/task-impact-inquiry/`. Host copies: `~/.claude/skills/`, `~/.grok/skills/`, `~/.gemini/config/skills/`. Fills Stage 1 grill; impact-only stops after the matrix. Not a parallel OS. |
60
60
  | **`backend-development`** | Framework-agnostic backend guidelines (clean naming, database queries, security, error handling). |
61
61
  | **`backend-safety-guardrails`** | 6 architectural backend safety invariants (queue bypass, BigInt, status recalculation loops). |
62
62
  | **`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. |
@@ -73,7 +73,7 @@ On a DOT repo (`adapter_type: dot`), **run `ai-engineering-loop`**, not the old
73
73
  | Generic Core Responsibility | DOT Adapter Responsibility |
74
74
  |---|---|
75
75
  | Goal Contract & Acceptance Criteria | GitLab Issue Card drafting |
76
- | Unit testing, typecheck, lint, build | Running DOT-specific scripts (`npx jest --testPathIgnorePatterns="dotify-api"`) |
76
+ | Unit testing, typecheck, lint, build | Commands from `.ai-engineering-loop/verification.md` |
77
77
  | Internal Devil's Advocate Review | External `@coreview-bot` triage on GitLab MRs |
78
78
  | Judge verdict & completion certificate | Multi-environment cherry-picking & branch synchronization |
79
79
  | Evidence collection & finding logs | Mattermost channel notifications & MR link delivery |
@@ -67,7 +67,8 @@ Every Coreview comment must be categorized into one of two paths:
67
67
  1. Apply the fix surgically to the local working branch.
68
68
  2. Re-run all unit tests and static analysis:
69
69
  ```bash
70
- npx jest --testPathIgnorePatterns="dotify-api"
70
+ # commands from .ai-engineering-loop/verification.md
71
+ npx jest
71
72
  npx tsc --noEmit
72
73
  ```
73
74
  3. Commit and push the fix to the branch:
@@ -104,4 +105,4 @@ Every Coreview comment must be categorized into one of two paths:
104
105
 
105
106
  ## 5. Anti-Pattern: Blind Compliance
106
107
 
107
- Agents must **never** rewrite working, verified code solely because an automated review bot posted a comment. If the bot's suggestion violates the [Goal Contract](file:///Users/egagofur/Development/work/ai-engineering-loop/core/goal-contract.md) or introduces broken dependencies, it MUST be triaged as `HALU` with evidence.
108
+ Agents must **never** rewrite working, verified code solely because an automated review bot posted a comment. If the bot's suggestion violates the [Goal Contract](../../core/goal-contract.md) or introduces broken dependencies, it MUST be triaged as `HALU` with evidence.
@@ -2,7 +2,7 @@
2
2
 
3
3
  ## 1. Purpose & Scope
4
4
 
5
- This module encapsulates all GitLab operations within the DOT ecosystem. Once a code change has successfully passed the [Generic AI Engineering Loop](file:///Users/egagofur/Development/work/ai-engineering-loop/README.md), this adapter automates issue tracking and Merge Request (MR) generation via the `glab` CLI.
5
+ This module encapsulates GitLab operations for the DOT adapter. Once a change has passed the [generic AI Engineering Loop](../../README.md), this adapter automates issue tracking and Merge Request (MR) generation via the `glab` CLI.
6
6
 
7
7
  ---
8
8
 
@@ -54,7 +54,7 @@ flowchart TD
54
54
  ```
55
55
 
56
56
  ### B. Create Standardized Issue Card
57
- If no issue exists, create one in the designated tracker (e.g. `dot-system/dotify-new` for central Dotify tracker, or the target repository):
57
+ If no issue exists, create one in the current repository (or the tracker named in `.ai-engineering-loop/adapter.md`):
58
58
 
59
59
  ```bash
60
60
  glab issue create \
@@ -79,7 +79,7 @@ glab issue create \
79
79
  ## Testing Steps
80
80
  1. Login as [User Role / Email].
81
81
  2. Navigate to [Target Menu / URL].
82
- 3. Perform [Action e.g. submit attendance, clock-in, approve overtime].
82
+ 3. Perform [Action e.g. submit the form, approve the request].
83
83
  4. Verify [Expected Result].
84
84
 
85
85
  ## Expectation
@@ -2,74 +2,70 @@
2
2
 
3
3
  ## 1. Overview & Objectives
4
4
 
5
- The **Mattermost Notification Module** formats final release notes and automatically delivers them to designated team channels via the Mattermost MCP server or CLI.
5
+ The **Mattermost Notification Module** formats final release notes and delivers them to team channels via the Mattermost MCP server or CLI.
6
6
 
7
- This provides seamless visibility to QA engineers, product managers, and reviewers upon successful completion of the delivery pipeline.
7
+ This gives QA, product, and reviewers visibility when the delivery pipeline finishes.
8
8
 
9
9
  ---
10
10
 
11
11
  ## 2. Channel Resolution & Dispatch Flow
12
12
 
13
- ```mermaid
14
- flowchart TD
15
- Complete[MRs Created Across Environments] --> CheckMap[Check /Users/egagofur/.gemini/config/mattermost-channel-mapping.json]
16
-
17
- CheckMap --> Found{Channel Found for Repo?}
18
-
19
- Found -->|Yes| Dispatch[Dispatch via MCP mattermost_send_message]
20
- Found -->|No| PromptUser[Ask User for Target Channel]
21
-
22
- PromptUser --> SaveMap[Save New Channel to mattermost-channel-mapping.json]
23
- SaveMap --> Dispatch
24
-
25
- Dispatch --> CheckMCP{MCP Success?}
26
- CheckMCP -->|Yes| Done([Notification Complete])
27
- CheckMCP -->|No / Failed| FallbackCLI[Fallback to Mattermost Agent CLI]
28
- FallbackCLI --> Done
13
+ ```text
14
+ MRs created
15
+ -> read ~/.gemini/config/mattermost-channel-mapping.json
16
+ -> channel found -> MCP mattermost_send_message
17
+ -> channel missing -> ask user, save mapping, then send
18
+ -> if MCP fails -> Mattermost agent CLI once
29
19
  ```
30
20
 
21
+ Do not hard-code a machine path. The mapping file lives under the user's home directory.
22
+
31
23
  ---
32
24
 
33
25
  ## 3. Mandatory Attribution Rule
34
26
 
35
- > [!IMPORTANT]
36
- > When sending messages or replying to threads on Mattermost (via MCP tools or CLI):
37
- > - **Always** include the sender attribution parameter (`from: "AI Agent"`) in MCP calls:
38
- > ```json
39
- > {
40
- > "channel": "internal-dotify",
41
- > "message": "...",
42
- > "from": "AI Agent"
43
- > }
44
- > ```
45
- > - **Always** include the CLI flag (`--from "AI Agent"`) in CLI calls:
46
- > ```bash
47
- > node /Users/egagofur/Development/work/kontribusi/mattermost-agent/dist/cli/index.js send <channel> "<message>" --from "AI Agent"
48
- > ```
49
- > - Do not omit or suppress sender attribution.
27
+ When sending messages or replying to threads (MCP or CLI):
28
+
29
+ - Always set sender attribution (`from: "AI Agent"`) in MCP calls:
30
+
31
+ ```json
32
+ {
33
+ "channel": "<team-channel>",
34
+ "message": "...",
35
+ "from": "AI Agent"
36
+ }
37
+ ```
38
+
39
+ - Always pass `--from "AI Agent"` on the CLI:
40
+
41
+ ```bash
42
+ <mattermost-cli> send <channel> "<message>" --from "AI Agent"
43
+ ```
44
+
45
+ Resolve the CLI from PATH or the command the user already uses. Do not embed another developer's local checkout.
50
46
 
51
47
  ---
52
48
 
53
49
  ## 4. Channel Resolution Logic
54
50
 
55
- 1. **Inspect Mapping File**:
56
- Read `/Users/egagofur/.gemini/config/mattermost-channel-mapping.json` using the current repository name or project slug (e.g. `dotify-new`, `dotify-api`, `dot-system/dotify-new`).
57
- 2. **Channel Found**:
58
- Dispatch message to the mapped channel name (e.g. `"internal-dotify"`).
59
- 3. **Channel Unknown**:
60
- - **DO NOT GUESS** or broadcast to arbitrary channels.
61
- - Ask the user to specify the target channel for this repository.
62
- - Immediately persist the user's answer into `/Users/egagofur/.gemini/config/mattermost-channel-mapping.json` for future automated runs.
51
+ 1. **Inspect mapping file**:
52
+ Read `~/.gemini/config/mattermost-channel-mapping.json` using the current repository name or `git` remote slug (`<group>/<repo>`).
53
+ 2. **Channel found**:
54
+ Dispatch to that channel name.
55
+ 3. **Channel unknown**:
56
+ - Do not guess or broadcast.
57
+ - Ask the user for the channel for this repository.
58
+ - Persist the answer in `~/.gemini/config/mattermost-channel-mapping.json`.
63
59
 
64
60
  ---
65
61
 
66
62
  ## 5. Standardized Mattermost Markdown Report Format (No AI Slop + Human-Written + PIC at End)
67
63
 
68
- Render separate, ready-to-copy Markdown blocks for every generated Merge Request using a simple, clean, and punchy format:
64
+ Render a ready-to-copy block per Merge Request:
69
65
 
70
66
  ```text
71
67
  [MR <ENV_TAG>] <MR_URL>
72
- Changes log
68
+ Changes log
73
69
  - <Poin 1: Apa yang diperbaiki / fitur apa yang aktif>
74
70
  - <Poin 2: Perubahan mekanisme/perilaku sistem secara gamblang>
75
71
  - <Poin 3: Proteksi regresi atau pengujian yang ditambahkan>
@@ -78,37 +74,29 @@ cc: <PIC>
78
74
  ```
79
75
 
80
76
  ### Formatting & Writing Rules (Prinsip `no-ai-slop`):
81
- - **DILARANG MENGGUNAKAN HEADING MARKDOWN (`#`, `##`, `###`, `####`)**: Gunakan teks polos agar font di Mattermost tidak membesar secara berlebihan.
82
- - **Format Sederhana Tanpa Metadata Bertele-tele**: Jangan menyertakan tabel metadata yang panjang (seperti Branch, Repo, Status Verifikasi). Cukup link MR dan list `Changes log`.
83
- - **Sertakan PIC di Akhir Pesan**: Ambil PIC dari file konfigurasi `mattermost-channel-mapping.json`. Jika belum ada, tanyakan kepada user dan simpan ke file mapping. Tambahkan `cc: <PIC>` di baris paling bawah.
84
- - **Gunakan Bahasa Manusia yang Lugas & Konkret**:
85
- - ✅ **Awali dengan kata kerja aktif**: *"Memperbaiki..."*, *"Memigrasikan..."*, *"Menjaga..."*, *"Menambahkan..."*, *"Mengubah..."*.
86
- - ❌ **Dilarang kata-kata AI Slop / Puffery**: `secara komprehensif`, `memastikan keakuratan`, `memfasilitasi`, `menyelaraskan alur`, `mengoptimalkan proses`, `solusi yang kokoh/robust`, `meningkatkan efisiensi`, `telah berhasil diimplementasikan`.
87
- - ❌ **Dilarang raw code / AST leakage**: Jangan menyebut nama variabel internal atau query mentah (misal `user.type.hasNormalHours`, `attendanceConfirmationPagination Prisma query`). Jelaskan dampak fungsionalnya.
77
+
78
+ - **No markdown headings** (`#`, `##`, `###`): plain text so Mattermost does not enlarge fonts.
79
+ - **No long metadata tables** (branch, repo, verification). MR link + Changes log only.
80
+ - **PIC on the last line**: from the mapping file. If missing, ask and save. `cc: <PIC>`.
81
+ - **Concrete human language**:
82
+ - Start with an active verb: *"Memperbaiki..."*, *"Memigrasikan..."*, *"Menjaga..."*, *"Menambahkan..."*, *"Mengubah..."*.
83
+ - No puffery: `secara komprehensif`, `memastikan keakuratan`, `memfasilitasi`, `menyelaraskan alur`, `mengoptimalkan proses`, `solusi yang kokoh/robust`, `meningkatkan efisiensi`, `telah berhasil diimplementasikan`.
84
+ - No raw code / AST: do not name internal fields, queries, or ORM calls. Describe the user-visible change.
88
85
 
89
86
  ### Environment Tags:
90
- - `[MR DEV]`: Merge Request targeting `develop`.
91
- - `[MR STAGING]`: Merge Request targeting `staging`.
92
- - `[MR MAIN]` (or `[MR PROD]`): Merge Request targeting `main` / `master`.
93
87
 
94
- ### Contoh Penerapan Nyata:
88
+ - `[MR DEV]`: `develop`
89
+ - `[MR STAGING]`: `staging`
90
+ - `[MR MAIN]` (or `[MR PROD]`): `main` / `master`
91
+
92
+ ### Fictional sample (do not replace with a real ticket):
95
93
 
96
94
  ```text
97
- [MR DEV] https://gitlab.dot.co.id/playground/bikin-rindu-tools-v2/-/merge_requests/108
98
- Changes log
99
- - Memperbaiki crash halaman dashboard di Safari setelah login akibat QuotaExceededError pada localStorage.
100
- - Memigrasikan penyimpanan cache browser ke IndexedDB (idb-keyval) sehingga kapasitas penyimpanan leluasa dan tidak memblokir main thread.
101
- - Menjaga synchronous script di head untuk preferensi tema agar tidak terjadi kedipan tampilan (FOUC).
102
- - Menambahkan auto-migration otomatis untuk memindahkan data lama dari localStorage ke IndexedDB sekaligus membebaskan kuota browser.
103
-
104
- cc: @hanaaaca
105
-
106
- [MR DEV] https://gitlab.dot.co.id/dot-system/dotify-new/-/merge_requests/963
107
- Changes log
108
- - Mengubah status entitas yang tadinya APPROVED menjadi NEED APPROVAL otomatis saat project atau jam kerjanya diedit.
109
- - Memperbaiki sinkronisasi worker agar periode absensi berjalan (UNCONFIRMED) tetap diproses saat admin mengedit data.
110
- - Menjaga entitas lain yang sudah disetujui PM di periode yang sama agar status approval-nya tidak ter-reset.
111
- - Menambahkan unit test untuk skenario lembur multi-entry harian.
112
-
113
- cc: @ulfa.mufida
95
+ [MR DEV] https://gitlab.example.com/example-org/work-portal/-/merge_requests/12
96
+ Changes log
97
+ - Memperbaiki status kartu di daftar request yang masih PENDING padahal semua baris sudah disetujui.
98
+ - Menjaga request lain di periode yang sama agar approval-nya tidak ter-reset.
99
+ - Menambahkan unit test untuk hari libur, jendela non-standar, dan koleksi baris yang kosong.
100
+
101
+ cc: @owner
114
102
  ```
@@ -53,7 +53,8 @@ git checkout -b <branch-name>-<target-env> origin/<target-env>
53
53
  git cherry-pick <commit-hash>
54
54
 
55
55
  # 4. Resolve any target-specific differences and verify tests pass
56
- npx jest --testPathIgnorePatterns="dotify-api"
56
+ # commands from .ai-engineering-loop/verification.md
57
+ npx jest
57
58
  npx tsc --noEmit
58
59
 
59
60
  # 5. Push the branch to remote
@@ -75,7 +76,7 @@ glab mr create \
75
76
  ## 3. Conflict & Environment Discrepancy Handling
76
77
 
77
78
  1. **Clean Cherry-Picks**:
78
- Because the [Generic AI Engineering Loop](file:///Users/egagofur/Development/work/ai-engineering-loop/README.md) enforces surgical, minimal diffs, cherry-picking should be clean in >95% of cases.
79
+ Because the [generic AI Engineering Loop](../../README.md) enforces surgical, minimal diffs, cherry-picking should be clean in >95% of cases.
79
80
  2. **Merge Conflicts**:
80
81
  If a merge conflict occurs due to divergent code between `main` and `develop`:
81
82
  - Resolve the conflict surgically preserving the fix semantics.
@@ -32,7 +32,7 @@ While AEL Maker runs, still enforce:
32
32
 
33
33
  - `backend-development` for naming, queries, layering.
34
34
  - `backend-safety-guardrails` on mutations, jobs, recalculation: never bypass BullMQ; scope by entity id not coarse date strings; never overwrite `APPROVED`/`REJECTED` without explicit force; BigInt as string across boundaries; container moves sync old and new parents.
35
- - Tests: `npx jest --testPathIgnorePatterns="dotify-api"` unless `.ai-engineering-loop/verification.md` says otherwise.
35
+ - Tests: commands in `.ai-engineering-loop/verification.md` (fallback `npx jest && npx tsc --noEmit`).
36
36
  - Branch from a clean target (`main`, `staging`, or `develop`), then `git checkout -b <type>/<descriptive-name>`.
37
37
 
38
38
  Print these six invariants before commit (N/A allowed only with one sentence citing the diff):
@@ -97,7 +97,7 @@ glab api "projects/:fullpath/merge_requests/<mr-id>/discussions/<discussion_id>/
97
97
 
98
98
  Follow `adapters/dot/mattermost.md` when present.
99
99
 
100
- 1. Resolve channel and PIC from `/Users/egagofur/.gemini/config/mattermost-channel-mapping.json`. If PIC is missing, ask the user and save it.
100
+ 1. Resolve channel and PIC from `~/.gemini/config/mattermost-channel-mapping.json`. If PIC is missing, ask the user and save it.
101
101
  2. Send via MCP `mattermost_send_message` with `from: "AI Agent"`. Use the Mattermost CLI only if MCP fails. Do not send twice.
102
102
  3. Put `cc: <PIC>` on the last line.
103
103