@eltonssouza/development-utility-kit 0.14.0 → 0.14.2

package/bin/cli.js

@@ -267,6 +267,31 @@ function harnessVersion() {
   }
 }
 
+// ─── spawn helpers (DEP0190-safe) ─────────────────────────────────────────────
+
+/**
+ * Whether a binary resolves on PATH — cross-platform, no shell (so no DEP0190).
+ * @param {string} bin
+ * @returns {boolean}
+ */
+function isOnPath(bin) {
+  const probe = process.platform === 'win32' ? 'where' : 'which';
+  const r = spawnSync(probe, [bin], { stdio: 'ignore' });
+  return r.status === 0;
+}
+
+/**
+ * Run a TRUSTED, static command line. A shell is needed on Windows to resolve
+ * `.cmd`/`.bat` shims (npm, git, rtk). Passing the command as a SINGLE string
+ * (not args[] + shell:true) avoids Node's DEP0190 warning. Never pass untrusted
+ * input — quote path arguments at the call site.
+ * @param {string} cmd
+ * @param {object} [opts]
+ */
+function runShell(cmd, opts = {}) {
+  return spawnSync(cmd, { shell: true, ...opts });
+}
+
 // ─── adoptProject (install / update) ──────────────────────────────────────────
 
 /**
@@ -432,17 +457,11 @@ function adoptProject(opts) {
   process.stdout.write('Written        : CLAUDE.md\n');
 
   // Auto-install duk globally when running via npx (duk not yet in PATH).
-  const dukCheck = spawnSync('duk', ['--version'], {
-    shell: process.platform === 'win32',
-    stdio: 'ignore',
-  });
-  if (dukCheck.error) {
+  if (!isOnPath('duk')) {
     process.stdout.write('\nInstalling duk CLI globally...\n');
-    const globalInstall = spawnSync(
-      'npm',
-      ['install', '-g', '@eltonssouza/development-utility-kit'],
-      { stdio: 'inherit', shell: process.platform === 'win32' }
-    );
+    const globalInstall = runShell('npm install -g @eltonssouza/development-utility-kit', {
+      stdio: 'inherit',
+    });
     if (globalInstall.status === 0) {
       process.stdout.write('duk installed globally. Run: duk help\n');
     } else {
@@ -530,10 +549,9 @@ function newProject(name, options) {
   fs.mkdirSync(target, { recursive: true });
 
   // 2. git init (non-fatal if git not installed; warn and continue)
-  const gitResult = spawnSync('git', ['init', '-q'], {
+  const gitResult = runShell('git init -q', {
     cwd: target,
     stdio: 'inherit',
-    shell: process.platform === 'win32',
   });
   if (gitResult.status !== 0) {
     process.stdout.write('Warning: "git init" failed or git is not in PATH. Continuing without git repo.\n');
@@ -707,9 +725,8 @@ function dashboard(passthroughArgs) {
 
   if (!fs.existsSync(nodeModulesDir)) {
     process.stdout.write('Installing dashboard dependencies (first run)...\n');
-    const result = spawnSync('npm', ['install', '--prefix', dashboardDir], {
+    const result = runShell(`npm install --prefix "${dashboardDir}"`, {
       stdio: 'inherit',
-      shell: process.platform === 'win32',
     });
     if (result.status !== 0) {
       process.stderr.write('Error: npm install failed for dashboard dependencies.\n');
@@ -718,8 +735,7 @@ function dashboard(passthroughArgs) {
   }
 
   // FR-008: print rtk gain output before starting the server
-  const rtkResult = spawnSync('rtk', ['gain'], {
-    shell: process.platform === 'win32',
+  const rtkResult = runShell('rtk gain', {
     stdio: ['ignore', 'pipe', 'ignore'],
   });
   if (rtkResult.status === 0 && rtkResult.stdout && rtkResult.stdout.length > 0) {

package/dashboard/public/content/docs/agents-reference.en.md

@@ -1,10 +1,10 @@
 # Agents reference
 
-This reference catalogs the 25 agents in the `development-utility-kit` harness. Each agent is a specialist declared in `.claude/agents/<name>.md` with a YAML frontmatter (`name`, `description`, `tools`, `model`). Skills invoke agents through the `Task` tool; agents can also invoke other agents (orchestration). Use this page as the operational index: which agent to open, with which model, at which point in the pipeline, and which downstream agents it dispatches.
+This reference catalogs the 21 agents in the `development-utility-kit` harness. Each agent is a specialist declared in `.claude/agents/<name>.md` with a YAML frontmatter (`name`, `description`, `tools`, `model`). Skills invoke agents through the `Task` tool; agents can also invoke other agents (orchestration). Use this page as the operational index: which agent to open, with which model, at which point in the pipeline, and which downstream agents it dispatches.
 
 Audience: developers on the team who open the local dashboard and need to decide, in seconds, which harness piece to move. Who decides what is consolidated in [autonomy-matrix](autonomy-matrix). Who enters each pipeline stage is in [pipeline](pipeline).
 
-## Master table — 25 agents
+## Master table — 21 agents
 
 | Agent | Model | Domain | Decides alone? | When to invoke |
 |---|---|---|---|---|
@@ -12,7 +12,6 @@ Audience: developers on the team who open the local dashboard and need to decide
 | `tech-lead` | opus 4.7 | Stack, pattern, refactor, final review | Yes (3 human-only exceptions) | Approve merge, decide pattern, resolve technical conflict |
 | `security-engineer` | opus 4.7 | OWASP, LGPD, hardening | Yes (technical veto HIGH/CRITICAL) | Security audit, vulnerability, headers, CORS |
 | `analyst` | sonnet 4.6 | Technical decomposition, goal-ready PLAN_*.md | Yes within scope | Break feature into FR/NFR/BR/IR and sprints with DoD |
-| `architect` | sonnet 4.6 | Macro architecture, ADR | Yes; cross-context escalates to tech-lead | Decide architectural pattern, propose ADR |
 | `backend-developer` | sonnet 4.6 | Java 25 + Spring Boot 4 | Yes within scope | Implement endpoint, service, DTO, repository |
 | `frontend-developer` | sonnet 4.6 | Angular 21 + Signals + ng-bootstrap | Yes within scope | Build component, screen, typed service |
 | `mobile-developer` | sonnet 4.6 | React Native 0.84 + Expo SDK 54 | Yes within scope | Mobile app from scratch, Angular→RN conversion, native integration |
@@ -22,16 +21,13 @@ Audience: developers on the team who open the local dashboard and need to decide
 | `ux-designer` | sonnet 4.6 | Wireframes, design system, a11y | Yes on "how it looks"; scope goes to PO | Wireframe, component spec, screen flow |
 | `qa-engineer` | sonnet 4.6 | Unit/integration/E2E/mutation tests | Yes within scope | Write JUnit, Jest, Playwright, PIT tests |
 | `gate-keeper` | sonnet 4.6 | Senior+ quality gate | Yes; blocks merge on red | Validate coverage, mutation, a11y, Lighthouse, pyramid |
-| `test-coverage-auditor` | sonnet 4.6 | Coverage + debt audit | Yes (gate inside prd-ready-check) | Map test debt, P0/P1 |
 | `code-reviewer` | sonnet 4.6 | Initial code review | Recommends; tech-lead merges | Review PR, findings by severity |
-| `prd-ready-check` | sonnet 4.6 | Final pre-production gate | Yes; GO/NO-GO | Final checklist before deploy |
-| `api-integration-test` | sonnet 4.6 | Real backend↔frontend smoke | Yes within scope | Boot stack and validate curl + clean console |
 | `sprint-runner` | sonnet 4.6 | TDD sprint orchestration | Yes; asks on plan ambiguity | Execute Sprint N of PLAN_*.md |
+| `stack-resolver` | haiku 4.5 | Stack pack resolution — reads Project Identity, returns STACK CONTEXT | Yes (mechanical) | Resolve the matching stack pack for the declared stack |
 | `scaffold` | haiku 4.5 | Java/Angular initial skeleton | Yes (mechanical, idempotent) | Create backend/, frontend/, or fullstack from scratch |
 | `update-template` | haiku 4.5 | Sync with development-utility-kit | Yes (with Y checkpoint) | Update `.claude/` + CLAUDE.md |
 | `migrator` | sonnet 4.6 | Legacy → target stack migration | Yes per phase; ADR per major cross | Java 8/11/17→25, Spring 2/3→4, Angular 14-20→21 |
 | `release-engineer` | sonnet 4.6 | SemVer bump + CHANGELOG | Yes through command output; human pushes | Cut release, generate tag, validate permissions |
-| `auditor` | sonnet 4.6 | Audit drift vs template | Reports only (read-only) | Compare project vs template, list divergent files |
 | `brain-keeper` | sonnet 4.6 | Obsidian vault under `docs/brain/` | Yes within scope | Record daily, feature, ADR, bug at end of PLAN |
 
 ---
@@ -48,7 +44,7 @@ PT triggers: `"decide produto"`, `"define escopo"`, `"regra de negócio"`, `"pri
 
 **Mission**: decide product and record an ADR. Never asks the human outside the 4 exceptions (deleting real customer data, relevant financial cost, breaking change on a published public contract, brand identity change approved by marketing).
 
-**Expected inputs**: raw user demand or hand-off from `analyst`/`architect`/developers with a product question.
+**Expected inputs**: raw user demand or hand-off from `analyst`/`tech-lead`/developers with a product question.
 
 **Outputs / artifacts**:
 - ADR at `docs/brain/decisions/ADR-NNN-<slug>.md`
@@ -79,7 +75,7 @@ PT triggers: `"decisão técnica"`, `"qual padrão"`, `"aprova merge"`, `"review
 
 **Mission**: orchestrate specialists, maintain technical consistency, block merge if the senior+ gate fails. Decides with a weighted framework (Impact 30 / Effort 25 / Risk 25 / Adherence 20).
 
-**Expected inputs**: technical demand, ADR proposed by `architect`, PR ready after `code-reviewer`.
+**Expected inputs**: technical demand, ADR to record, PR ready after `code-reviewer`.
 
 **Outputs**:
 - Technical decision ADR with score grid in `## Justification`
@@ -162,39 +158,12 @@ Autonomous path (`sprint-runner`, `release-engineer`): exempt via signal `caller
 - Never invent a requirement — ambiguities go in §7 "Pending decisions".
 - Filename always `PLAN_<NAME_KEBAB_CASE>.md`, no spaces or accents.
 
-**Escalation**: `architect` for new architectural decisions; `tech-lead` for ambiguity between stacks.
+**Escalation**: `tech-lead` for new architectural decisions and for ambiguity between stacks.
 
 **Tools**: Read, Write, Edit, Glob, Grep, Bash(cat/find/git log).
 
 **When NOT to use**: implementation (use `backend-developer`/`frontend-developer`). Trivial single-file edit. Bug with unknown root cause (use `pair-debug`).
 
-### architect
-
-**Model**: sonnet 4.6
-
-**When to invoke**: decide architectural pattern (DDD vs CRUD, modular monolith vs microservices, REST vs Event-Driven), model domain, record macro ADR.
-
-PT triggers: `"decide arquitetura"`, `"qual padrão usar"`, `"modela domínio"`, `"trade-off arquitetural"`, `"registra ADR"`.
-
-**Mission**: propose architecture with weighted framework (Impact 30 / Effort 25 / Risk 25 / Adherence 20). `tech-lead` approves cross-cutting decisions.
-
-**Expected inputs**: technical context (scale, team, domain complexity), constraints, existing code.
-
-**Outputs**: ADR saved at `docs/brain/decisions/ADR-NNN-<slug>.md` with Context, Decision, Consequences, Discarded alternatives and score grid.
-
-**Inviolable rules**:
-- No ADR, no architecture change.
-- Decision framework mandatory — score in the ADR.
-- Never introduce a dependency without justification.
-- Inspect code before proposing; never propose a rewrite of code you have not read.
-- No premature abstraction — only complicate with a concrete requirement.
-
-**Escalation**: `tech-lead` when decision spans > 1 bounded context, cost > R$ 200/month, or public external contract.
-
-**Tools**: Read, Write, Glob, Grep, Bash(git log/git diff/cat/find).
-
-**When NOT to use**: implementation (use a developer). Patch or lib bump (use `tech-lead`). Product decision (use `product-owner`).
-
 ---
 
 ## Implementation
@@ -465,32 +434,7 @@ PT triggers: `"roda os testes"`, `"gera os testes"`, `"garante que nada quebrou"
 
 **Tools**: Read, Write, Edit, MultiEdit, Glob, Grep, Bash(git/node/mvn/mvnw/gradle/gradlew/npm/npx/ng/cat/find/ls).
 
-**When NOT to use**: debt audit without running the suite (use `test-coverage-auditor`). Decision about what to test (use `qa-engineer`).
-
-### test-coverage-auditor
-
-**Model**: sonnet 4.6
-
-**When to invoke**: map untested code, identify recurring manual tests, prioritize debt (P0/P1/P2/P3). Acts as a gate inside `prd-ready-check`.
-
-PT triggers: `"audita os testes"`, `"tem débito de teste?"`, `"cobertura tá ok?"`, `"faz auditoria de cobertura"`.
-
-**Mission**: audit and report. Does not write tests (that's `qa-engineer`) nor run the suite (that's `gate-keeper`).
-
-**Expected inputs**: source tree (backend + frontend), JaCoCo + Jest reports, previous `tech-debt.md`.
-
-**Outputs**: count by severity, trend vs previous audit, verdict for the PRD gate, update to `tech-debt.md` with P0/P1.
-
-**Inviolable rules**:
-- Never lowers threshold without a formal ADR.
-- Never closes a P0 without a corresponding committed automated test.
-- Never confuses "passes CI" with "actually covered" — analyzes assertions.
-
-**Escalation**: open P0 → blocks `prd-ready-check`. Prioritization → `tech-lead`. Test generation → `gate-keeper`.
-
-**Tools**: Read, Write, Edit, Glob, Grep, Bash(git/mvn/mvnw/npm/npx/find/cat/ls).
-
-**When NOT to use**: generate the tests (use `qa-engineer`/`gate-keeper`). Formally accept the debt (use `tech-lead`).
+**When NOT to use**: debt audit without running the suite (use the `test-coverage-auditor` skill). Decision about what to test (use `qa-engineer`).
 
 ### code-reviewer
 
@@ -514,66 +458,12 @@ PT triggers: `"revisa o PR"`, `"code review"`, `"audita o código"`, `"revisa qu
 - Reviews the test diff with the same rigor as the production diff.
 - Does not merge — `tech-lead` merges.
 
-**Escalation**: security HIGH/CRITICAL → `security-engineer`. Conflict with active ADR → `tech-lead`. Architectural smell → `architect`. Test regression → `gate-keeper`.
+**Escalation**: security HIGH/CRITICAL → `security-engineer`. Conflict with active ADR → `tech-lead`. Architectural smell → `tech-lead`. Test regression → `gate-keeper`.
 
 **Tools**: Read, Glob, Grep, Bash(git diff/git log/git show).
 
 **When NOT to use**: formal merge approval (use `tech-lead`). Deep security audit (use `security-engineer`).
 
-### prd-ready-check
-
-**Model**: sonnet 4.6
-
-**When to invoke**: final gate before deploy. Runs the full checklist (tests, coverage, lint, production build, smoke E2E, security, observability, database) and returns GO or NO-GO.
-
-PT triggers: `"tá pronto pra PRD?"`, `"pode subir pra produção?"`, `"roda o checklist final"`, `"DoD"`, `"definição de pronto"`.
-
-**Mission**: confidently say whether the release goes to production. Never relaxes the gate — broken test = NO-GO; critical warning = NO-GO; console with error = NO-GO.
-
-**Expected inputs**: ready branch, viable local build, accessible smoke infrastructure.
-
-**Outputs**: report with each item OK/FAIL and evidence (HTTP status, console log, finding counts).
-
-**Inviolable rules**:
-- Any FAIL = NO-GO.
-- Never relaxes limits without a formal ADR.
-- Runs real commands — never assumes it passes because it passed yesterday.
-- Flaky: 1 failure in 3 = NO-GO + open a bug.
-- P0 from `test-coverage-auditor` = automatic NO-GO.
-- No recent GREEN from `gate-keeper` = NO-GO.
-
-**Escalation**: NO-GO returns to the specialist (backend/frontend/qa) with pending items.
-
-**Tools**: Read, Glob, Grep, Bash(mvn/mvnw/npm/npx/ng/docker/docker-compose/git/ls/cat/find).
-
-**When NOT to use**: task or sprint validation (use `gate-keeper`). Debt audit (use `test-coverage-auditor`).
-
-### api-integration-test
-
-**Model**: sonnet 4.6
-
-**When to invoke**: validate real backend↔frontend integration after the green gate, before the final gate. Boots the stack, hits curl, opens a browser via Chrome MCP and checks console + network.
-
-PT triggers: `"testa a integração"`, `"smoke test"`, `"sobe tudo e testa"`, `"verifica se a tela funciona"`, `"faz o E2E rápido"`.
-
-**Mission**: confirm backend and frontend talk in a live dev environment. Anything failing = integration NOT-OK.
-
-**Expected inputs**: built project, docker-compose or boot command, documented main endpoints.
-
-**Outputs**: report of each check with OK/FAIL and evidence. Process tear-down at the end (even on failure).
-
-**Inviolable rules**:
-- Never "proves OK" by reading code only — must boot and observe.
-- Zero console errors is a hard requirement.
-- Process tear-down on exit (uses trap).
-- Documents tested URLs, methods, and responses.
-
-**Escalation**: failure → returns to `backend-developer` or `frontend-developer`.
-
-**Tools**: Read, Glob, Grep, Bash(mvn/mvnw/npm/npx/ng/docker/docker-compose/curl/ss/netstat/cat/ls/sleep).
-
-**When NOT to use**: unit/integration suite (use `gate-keeper`). Final pre-production gate (use `prd-ready-check`).
-
 ---
 
 ## Orchestration
@@ -609,6 +499,34 @@ PT triggers: `"roda a sprint 1"`, `"executa a sprint"`, `"implementa as tarefas
 
 ## Project lifecycle
 
+### stack-resolver
+
+**Model**: haiku 4.5
+
+**When to invoke**: resolve the stack pack for the declared stack before specialists run. Reads `## Project Identity` from `CLAUDE.md`, locates the matching pack in `.claude/stacks/<lang>/<framework>-<major>.md`, and returns a rendered STACK CONTEXT block. Invoked programmatically by orchestrating skills at Step 0 (per ADR-026), not usually called by hand.
+
+PT triggers: `"resolve stack"`, `"carrega pack da stack"`.
+
+**Mission**: mechanical, read-only resolver. No decisions — just parse Project Identity, build the pack path, check `.claude/local/stacks/` first (override), read the pack, and format the STACK CONTEXT block. Hard-fails with `PACK_MISSING_ERROR` (plus nearest-pack suggestions) when no exact pack matches — never silently falls back to defaults.
+
+**Expected inputs**: project `CLAUDE.md` with a valid `## Project Identity` → `Primary stack` field (e.g., `Java 21 + Spring Boot 3.2`).
+
+**Outputs**: STACK CONTEXT block with the first-line tag `[STACK: <lang>/<framework>-<major> | PACK: loaded|none]`, the resolved language/framework/major, the pack path, and the full inline pack content. On miss, a `PACK_MISSING_ERROR` block the invoking skill must gate on.
+
+**Inviolable rules**:
+- Mechanical only — never makes a decision.
+- Local overrides win — `.claude/local/stacks/` checked before `.claude/stacks/`.
+- Always emits the `[STACK:` first-line tag for validation.
+- Never modifies any file — read-only.
+- No agent dispatch — it is a leaf; invokers dispatch specialists from its output.
+- Hard-fail on missing pack — no silent fallback; always suggests nearest packs.
+
+**Escalation**: pack missing → invoking skill dispatches the `create-stack-pack` skill or requires an explicit `[STACK_BYPASS: <reason>]` token before proceeding.
+
+**Tools**: Read, Glob, Grep.
+
+**When NOT to use**: create a missing pack (use the `create-stack-pack` skill). Migrate between stacks (use `migrator`). Any implementation work (use the specialists).
+
 ### scaffold
 
 **Model**: haiku 4.5
@@ -629,7 +547,7 @@ PT triggers: `"scaffolda o projeto"`, `"monta a estrutura"`, `"cria o esqueleto"
 - Versions pinned to `CLAUDE.md`; never silent fallback.
 - Smoke build mandatory (`./mvnw compile` or `npm run build` returns 0).
 
-**Escalation**: type missing → `tech-lead`. Stack version unavailable → `devops-engineer`. After scaffold, first feature → `analyst` → `architect` → `sprint-runner`.
+**Escalation**: type missing → `tech-lead`. Stack version unavailable → `devops-engineer`. After scaffold, first feature → `analyst` → `tech-lead` → `sprint-runner`.
 
 **Tools**: Read, Write, Edit, Glob, Grep, Bash(mvn/mvnw/npm/npx/ng/curl/cat/find/mkdir/unzip).
 
@@ -719,30 +637,6 @@ PT triggers: `"release"`, `"bump version"`, `"cria tag"`, `"novo release"`, `"pr
 
 **When NOT to use**: dependency update (use `tech-lead`). Revert release (use `tech-lead` + ADR — never undoes, bumps again). Intermediate QA tag (branch + manual tag, outside release flow).
 
-### auditor
-
-**Model**: sonnet 4.6
-
-**When to invoke**: compare a project's structure against the official template. Detects missing, divergent, and outdated files in `.claude/`, `CLAUDE.md`, `.claude/agents`, `.claude/commands`, `.claude/skills`, `.claude/settings.json`, `.claude-version.json`.
-
-PT triggers: `"audita estrutura claude"`, `"compara projetos com template"`, `"verifica desatualizado"`.
-
-**Mission**: read-only. Never copies, edits, deletes, or overwrites. Reports and recommends `/sync-all-projects` or `/update-template`.
-
-**Expected inputs**: project path, official template path.
-
-**Outputs**: per project — Path, Status, Missing files, Divergent files, Local version, Expected version, Risk, Recommendation.
-
-**Inviolable rules**:
-- Auditor only. NEVER copies/edits/deletes/overwrites.
-- When it finds an issue, recommends a command — does not fix.
-
-**Escalation**: corrective action → `update-template` (with human confirmation).
-
-**Tools**: Read, Glob, Bash.
-
-**When NOT to use**: apply correction (use `update-template`). Create project (use `scaffold`).
-
 ---
 
 ## History
@@ -757,7 +651,7 @@ PT triggers: `"registra no cérebro"`, `"atualiza brain"`, `"log do dia"`, `"sal
 
 **Mission**: WRITE mode in `docs/brain/`. Never deletes history — on conflict, new note prevails with `[[supersedes ADR-XXX]]` or a `## History` section.
 
-**Expected inputs**: plan path, output of `sprint-runner`, output of `gate-keeper`, output of `prd-ready-check`, git range (starting SHA → HEAD).
+**Expected inputs**: plan path, output of `sprint-runner`, output of `gate-keeper`, output of the `prd-ready-check` skill, git range (starting SHA → HEAD).
 
 **Outputs**:
 - `daily/YYYY-MM-DD.md` (always)
@@ -777,7 +671,7 @@ PT triggers: `"registra no cérebro"`, `"atualiza brain"`, `"log do dia"`, `"sal
 - Never logs PII/token/password.
 - Read-only outside `docs/brain/` (except marking PLAN as `status: completed`).
 
-**Escalation**: formal ADR comes from `architect`; this agent only records. Accepting debt is `tech-lead`'s call; this agent only persists into `tech-debt.md`.
+**Escalation**: formal ADR comes from `tech-lead`; this agent only records. Accepting debt is `tech-lead`'s call; this agent only persists into `tech-debt.md`.
 
 **Tools**: Read, Write, Edit, MultiEdit, Glob, Grep, Bash(git log/git diff/git show/find/cat/ls/mkdir/cp).
 
@@ -791,7 +685,7 @@ PT triggers: `"registra no cérebro"`, `"atualiza brain"`, `"log do dia"`, `"sal
 |---|---|---|
 | Scope, business rule, UX, API contract | `product-owner` | 4 situations: deleting real data, relevant financial cost, breaking change to public contract, identity change |
 | Stack, pattern, refactor, lib, final review | `tech-lead` | 3 situations: irreconcilable requirement conflict, public breaking change, infra cost > R$ 200/month |
-| Macro architecture | `architect` proposes → `tech-lead` decides | Never (escalates via `tech-lead`) |
+| Macro architecture, ADR | `tech-lead` | 3 situations (as above) |
 | Schema, index, DB perf | `database-engineer` | Cross-cutting → `tech-lead` |
 | Security HIGH/CRITICAL | `security-engineer` (technical veto) | 1 situation: irreversible action on real data |
 | Infra, cost, deploy | `devops-engineer` | Cost > R$ 200/month → human |
@@ -816,11 +710,11 @@ Full details in [autonomy-matrix](autonomy-matrix).
                             │ Task
               ┌─────────────┼─────────────────────────┐
               ▼             ▼                         ▼
-       product-owner   tech-lead                  scaffold / update-template / migrator
+       product-owner   tech-lead          stack-resolver / scaffold / update-template / migrator
               │             │
               │             │ delegates
               │             ▼
-              │       analyst ──► architect ──► (ADR)
+              │       analyst ──► tech-lead ──► (ADR)
               │             │
               │             │
               │             ▼
@@ -843,8 +737,9 @@ Full details in [autonomy-matrix](autonomy-matrix).
                                               │
                           ┌───────────────────┼───────────────────┐
                           ▼                   ▼                   ▼
-                api-integration-test   prd-ready-check     security-engineer
-                                              │             (veto at any point)
+              api-integration-test     prd-ready-check     security-engineer
+                  (skill)                 (skill)          (veto at any point)
+                                              │
                                               ▼
                                        release-engineer
                                               │
@@ -859,8 +754,8 @@ Reading the diagram:
 - `code-reviewer` recommends; only `tech-lead` merges.
 - `security-engineer` has lateral entry — can issue veto at any point in the flow.
 - `brain-keeper` is always the last step of the PLAN.
-- `test-coverage-auditor` is an internal gate inside `prd-ready-check`.
-- `auditor` operates outside the feature flow — it diagnoses against the template.
+- `stack-resolver` runs at Step 0 of orchestrating skills — it resolves the stack pack before any specialist is dispatched.
+- The `test-coverage-auditor` skill is an internal gate inside the `prd-ready-check` skill; both are skills, not agents.
 
 ---
 
@@ -884,9 +779,9 @@ model: opus | sonnet | haiku
 
 3. **Write the description in English** (the rest of the prompt too), but **include 2-5 PT triggers** at the end of the `description`, in quotes, in the format `PT triggers: '...', '...'`. The project-manager matcher keys on those triggers.
 
-4. **List required tools** with scoped Bash permissions (`Bash(mvn:*)`, not `Bash`). Avoid open `Bash` except when the agent must run arbitrary commands (case of `auditor`).
+4. **List required tools** with scoped Bash permissions (`Bash(mvn:*)`, not `Bash`). Avoid open `Bash` except when the agent must run arbitrary commands.
 
-5. **Write the agent body** following the pattern of the 25 existing ones: "You decide. You don't ask." block at the top, mission, flow, numbered inviolable rules, interface with other agents, examples when useful.
+5. **Write the agent body** following the pattern of the 21 existing ones: "You decide. You don't ask." block at the top, mission, flow, numbered inviolable rules, interface with other agents, examples when useful.
 
 6. **Register in `CLAUDE.md`** in the sections:
    - "Sub-Agent Routing" table

package/dashboard/public/content/docs/architecture-overview.en.md

@@ -115,8 +115,8 @@ The `model:` field is mandatory. The model-per-agent rule (defined in `CLAUDE.md
 | Model | When to use | Agents |
 |---|---|---|
 | **Opus 4.7** | Irreversible decision, macro technical veto | `product-owner`, `tech-lead`, `security-engineer` |
-| **Sonnet 4.6** | Implementation, decomposition, review, test, UI, recording | `architect`, `analyst`, `backend-developer`, `frontend-developer`, `mobile-developer`, `n8n-specialist`, `ux-designer`, `database-engineer`, `devops-engineer`, `qa-engineer`, `code-reviewer`, `gate-keeper`, `test-coverage-auditor`, `prd-ready-check`, `api-integration-test`, `sprint-runner`, `brain-keeper`, `auditor`, `release-engineer`, `migrator` |
-| **Haiku 4.5** | Scaffold, template, mechanical sync | `scaffold`, `update-template` |
+| **Sonnet 4.6** | Implementation, decomposition, review, test, UI, recording | `analyst`, `backend-developer`, `frontend-developer`, `mobile-developer`, `n8n-specialist`, `ux-designer`, `database-engineer`, `devops-engineer`, `qa-engineer`, `code-reviewer`, `gate-keeper`, `sprint-runner`, `brain-keeper`, `release-engineer`, `migrator` |
+| **Haiku 4.5** | Scaffold, template, mechanical sync, stack resolution | `scaffold`, `update-template`, `stack-resolver` |
 
 Invocation happens via the Task tool, inside a Skill:
 
@@ -258,7 +258,7 @@ Captured metrics: agent name, model used, tokens in/out, duration, success/failu
 
 ## Cross-references
 
-- [Agents reference](agents-reference) — full catalog of the 22 agents + responsibilities + model
+- [Agents reference](agents-reference) — full catalog of the 21 agents + responsibilities + model
 - [Skills reference](skills-reference) — catalog of skills + triggers + outputs
 - [Hooks reference](hooks-reference) — scripts in `scripts/hooks/` + matchers + behavior
 - [Autonomy matrix](autonomy-matrix) — who decides what, when to escalate

package/dashboard/public/content/docs/autonomy-matrix.en.md

@@ -41,13 +41,13 @@ Everything else fits below these two poles:
                     └──────┬──────┘         └──────┬──────┘
                            │                        │
               ┌────────────┴──────┐    ┌────────────┼─────────────┐
-              │                   │    │            │             │
-              ▼                   ▼    ▼            ▼             ▼
-        ux-designer        architect      database-       devops-      security-
-       (Sonnet)            (Sonnet)       engineer        engineer     engineer
-                                          (Sonnet)        (Sonnet)     (Opus, veto)
-              │                  │              │             │            │
-              └──────────┬───────┴──────────────┴─────────────┴────────────┘
+              │                        │            │             │
+              ▼                        ▼            ▼             ▼
+        ux-designer              database-       devops-      security-
+       (Sonnet)                  engineer        engineer     engineer
+                                 (Sonnet)        (Sonnet)     (Opus, veto)
+              │                        │             │            │
+              └──────────┬─────────────┴─────────────┴────────────┘
                          ▼
                   backend-developer / frontend-developer / mobile-developer
                                        (Sonnet)
@@ -80,7 +80,7 @@ For everything else (high/critical vuln, OWASP Top 10, missing security header,
 
 ### Specialists NEVER escalate to the human
 
-The 17 specialist agents (analyst, architect, backend-developer, frontend-developer, mobile-developer, database-engineer, devops-engineer, qa-engineer, code-reviewer, ux-designer, n8n-specialist, sprint-runner, scaffold, release-engineer, migrator, auditor, brain-keeper) **DO NOT escalate to human**.
+The 18 specialist agents (analyst, backend-developer, frontend-developer, mobile-developer, database-engineer, devops-engineer, qa-engineer, code-reviewer, gate-keeper, ux-designer, n8n-specialist, sprint-runner, scaffold, stack-resolver, release-engineer, migrator, update-template, brain-keeper) **DO NOT escalate to human**.
 
 The rule is:
 - **Product** doubt → escalate to `product-owner`.
@@ -180,7 +180,7 @@ If they cannot agree, **PO has final say on scope, TL has final say on technical
 
 ## Cross-references
 
-- [Agents reference](agents-reference) — full list of the 22 agents + model + responsibilities
+- [Agents reference](agents-reference) — full list of the 21 agents + model + responsibilities
 - [Pipeline](pipeline) — where and how each agent shows up in the end-to-end flow
 - [Quality gate](quality-gate) — thresholds that `gate-keeper` and `security-engineer` enforce without human
 - [Architecture overview](architecture-overview) — 2-layer macro model

package/dashboard/public/content/docs/pipeline.en.md

@@ -7,7 +7,7 @@ This document describes the full path. For trivial changes or hotfixes, shortcut
 ## Macro view
 
 ```
-discovery → specification → planning → architecture → execution → validation → recording
+discovery → specification → planning → architecture (tech-lead) → execution → validation → recording
                                                           │
                                                           ▼
                                                   gate-keeper blocks
@@ -17,12 +17,12 @@ discovery → specification → planning → architecture → execution → vali
 ## Full pipeline diagram
 
 ```
-┌──────────┐    ┌────────┐    ┌──────────┐    ┌─────────┐    ┌───────────┐    ┌──────────┐
-│ grill-me │ -> │ to-prd │ -> │to-issues │ -> │ analyst │ -> │ architect │ -> │tech-lead │
-│(skill)   │    │(skill) │    │ (skill)  │    │ (agent) │    │  (agent)  │    │ (approve)│
-└──────────┘    └────────┘    └──────────┘    └─────────┘    └───────────┘    └────┬─────┘
-                                                                                   │
-                                                                                   ▼
+┌──────────┐    ┌────────┐    ┌──────────┐    ┌─────────┐    ┌──────────────────────┐
+│ grill-me │ -> │ to-prd │ -> │to-issues │ -> │ analyst │ -> │ tech-lead            │
+│(skill)   │    │(skill) │    │ (skill)  │    │ (agent) │    │ (ADR + approve)      │
+└──────────┘    └────────┘    └──────────┘    └─────────┘    └────┬─────────────────┘
+                                                                  │
+                                                                  ▼
                               ┌────────────────────────────────────────────────────────┐
                               │ sprint-runner (skill+agent)                            │
                               │   ├─► qa-engineer (TDD: failing tests)                 │
@@ -131,17 +131,17 @@ Acceptance criteria:
 - Estimates (in "complexity", not hours)
 - Definition of Done per task
 
-**Next step**: `architect` (if there is a new macro decision) or directly to `tech-lead` (if it is only an established pattern).
+**Next step**: `tech-lead` — proposes an ADR if there is a new macro decision, or approves directly if it is only an established pattern.
 
 ⏸️ **Checkpoint**: human confirms the PLAN.
 
-### 5. Architecture (`architect`)
+### 5. Architecture + approval (`tech-lead`)
 
-**When it fires**: PLAN includes a new macro decision (new lib, new pattern, new bounded context, relevant tech choice).
+**When it fires**: PLAN includes a new macro decision (new lib, new pattern, new bounded context, relevant tech choice); or at the end of the PLAN when there are patterns to approve.
 
 **Input**: PLAN + project context + prior decisions in `docs/decisions/`.
 
-**Output**: `docs/decisions/ADR-NNN-<slug>.md` (proposed) following the MADR template:
+**How it works**: `tech-lead` owns both the architectural proposal and its approval. It writes the ADR following the MADR template:
 - Status: Proposed
 - Context
 - Decision drivers
@@ -149,13 +149,7 @@ Acceptance criteria:
 - Decision outcome
 - Consequences
 
-**Next step**: `tech-lead` reviews and approves (Status: Accepted) or requests revision (Status: Rejected → back).
-
-### 6. Approval (`tech-lead`)
-
-**When it fires**: after `architect` produces an ADR; or at the end of the PLAN when there are patterns to approve.
-
-**Input**: PLAN + proposed ADR(s).
+It then accepts (Status: Accepted) or rejects (Status: Rejected → re-propose) the decision.
 
 **Output**: ADR with Status: Accepted (or Rejected with reason). Updates `CLAUDE.md` if the decision changes a stack rule.
 
@@ -279,7 +273,7 @@ code-reviewer with bugs       → back to developer
 api-integration-test FAIL     → back to `qa-engineer` to debug
 prd-ready-check NO-GO         → back to `gate-keeper` or specific specialist
 tech-lead returns in review   → back to developer
-ADR rejected                  → back to architect to re-propose
+ADR rejected                  → back to tech-lead to re-propose
 ```
 
 ## Shortcuts
@@ -296,7 +290,7 @@ The full pipeline is for new features. Shortcuts exist for other cases:
 ### Hotfix in production
 
 ```
-hotfix request → architect (quick proposal) → sprint-runner (1 task) → gate-keeper → tech-lead → merge → brain-keeper (bug entry)
+hotfix request → tech-lead (quick proposal) → sprint-runner (1 task) → gate-keeper → tech-lead → merge → brain-keeper (bug entry)
 ```
 
 - Skip `grill-me`/`to-prd`/`to-issues`.
@@ -355,11 +349,9 @@ Out of scope: batch signup.
 - Sprint 1: backend (T1: migration, T2: service, T3: controller, T4: tests)
 - Sprint 2: frontend (T1: component, T2: Angular service, T3: E2E)
 
-**5. `architect`** — does not fire (patterns already established).
-
-**6. `tech-lead`** — approves PLAN.
+**5. `tech-lead`** — no new ADR needed (patterns already established); approves PLAN.
 
-**7. `sprint-runner` Sprint 1** — dispatches in parallel:
+**6. `sprint-runner` Sprint 1** — dispatches in parallel:
 - `qa-engineer` writes JUnit tests for Service + controller
 - `database-engineer` generates `V20260527_001__create_product.sql`
 - `backend-developer` implements Service + Controller + DTOs (record)
@@ -371,11 +363,11 @@ After 30 min, `gate-keeper` runs:
 - SpotBugs: 0 issues ✓
 - OWASP DC: 0 CVE ✓
 
-**8. `code-reviewer`** suggests extracting unique-name validation to a domain service. `backend-developer` applies.
+**7. `code-reviewer`** suggests extracting unique-name validation to a domain service. `backend-developer` applies.
 
-**9. `tech-lead`** approves Sprint 1.
+**8. `tech-lead`** approves Sprint 1.
 
-**10. `sprint-runner` Sprint 2** — dispatches:
+**9. `sprint-runner` Sprint 2** — dispatches:
 - `qa-engineer` writes Playwright E2E + jest-axe component test
 - `ux-designer` produces wireframe + tokens
 - `frontend-developer` implements component (3 files: `.ts`, `.html`, `.scss`)
@@ -389,13 +381,13 @@ After 30 min, `gate-keeper` runs:
 - LCP: 1820ms ✓, CLS: 0.04 ✓, TBT: 210ms ✓
 - E2E pyramid: 18% ✓
 
-**11. `api-integration-test`** boots local stack, validates POST + UI via Chrome MCP. Clean console.
+**10. `api-integration-test`** boots local stack, validates POST + UI via Chrome MCP. Clean console.
 
-**12. `prd-ready-check`** returns GO.
+**11. `prd-ready-check`** returns GO.
 
-**13. `tech-lead`** approves merge. Human triggers merge on GitHub.
+**12. `tech-lead`** approves merge. Human triggers merge on GitHub.
 
-**14. `brain-keeper`** updates `docs/brain/`:
+**13. `brain-keeper`** updates `docs/brain/`:
 - `features/product-signup.md` — feature summary
 - `daily/2026-05-27.md` — daily entry
 - `MOC.md` — link to `product-signup` under Catalog

package/dashboard/public/content/docs/plugins.en.md

@@ -46,7 +46,7 @@ Matt's original design surfaced hidden requirements that prompt-only conversatio
 Three pre-existing problems in our pipeline made grill-me an obvious fit:
 
 - **PRD authoring used to start from a single user paragraph.** Result: under-specified scope, edge cases discovered late, sprint rework. Grill-me forces the user to confront ambiguity *before* the PRD exists.
-- **Planning agents (`analyst`, `architect`) need a structured input.** Free-form prompts make them hallucinate constraints. Grill-me produces a structured `DISCOVERY_*.md` that `analyst` can consume deterministically.
+- **Planning agents (`analyst`, `tech-lead`) need a structured input.** Free-form prompts make them hallucinate constraints. Grill-me produces a structured `DISCOVERY_*.md` that `analyst` can consume deterministically.
 - **The interview pattern was already proven viral.** Reproducing it from scratch would have taken weeks, with no clear UX improvement.
 
 We did not modify the interview mechanic, the recommended-answer pattern, the rubber-duck framing, or the conversational tone. Those are Matt's design.

package/dashboard/public/content/docs/quality-gate.en.md

@@ -298,7 +298,7 @@ Summary of what `gate-keeper` enforces, in order:
 
 1. `product-owner` decides requirements.
 2. `analyst` produces PLAN_*.md with goal-ready DoD.
-3. `architect` proposes ADR when there is a macro decision; `tech-lead` approves.
+3. `tech-lead` proposes ADR when there is a macro decision and approves it.
 4. `sprint-runner` executes Sprint N delegating to `backend-developer` + `frontend-developer` + `database-engineer` in parallel; `qa-engineer` writes tests.
 5. `gate-keeper` generates missing tests + runs the full senior+ gate (coverage, mutation, a11y, Lighthouse, pyramid).
 6. `code-reviewer` does initial review.

package/dashboard/public/content/docs/skills-reference.en.md

@@ -41,7 +41,7 @@ This document covers the 18 official skills of the harness, grouped by purpose.
 
 **What it does**: reads the intent, decides one of three modes (per ADR-033), and dispatches accordingly:
 
-- **ROUTE** (single-domain task) → picks ONE specialist from the routing table (`analyst`, `architect`, `backend-developer`, `frontend-developer`, `code-reviewer`, `database-engineer`, `devops-engineer`, `mobile-developer`, `n8n-specialist`, `product-owner`, `qa-engineer`, `security-engineer`, `tech-lead`, `ux-designer`, `migrator`, `release-engineer`, `auditor`), announces the choice in one line, and dispatches via the `Task` tool.
+- **ROUTE** (single-domain task) → picks ONE specialist from the routing table (`analyst`, `backend-developer`, `frontend-developer`, `code-reviewer`, `database-engineer`, `devops-engineer`, `mobile-developer`, `n8n-specialist`, `product-owner`, `qa-engineer`, `security-engineer`, `tech-lead`, `ux-designer`, `migrator`, `release-engineer`), announces the choice in one line, and dispatches via the `Task` tool.
 - **ORCHESTRATE** (multi-domain ad-hoc task, ≤5 subtasks) → prints a mini-plan inline (table: Subtask | Agent | Mode `[PAR]`/`[SEQ]` | Touches | Depends on) and dispatches multiple `Task` calls in parallel. Each parallel subtask must touch disjoint paths and have no output dependency on a sibling; otherwise it gets marked `[SEQ]`. No `PLAN_*.md` is generated.
 - **ESCALATE** (>5 subtasks, formal `PLAN_*.md` needed, or any subtask requires further decomposition) → refuses inline, suggests `grill-me` → `analyst` → `sprint-runner` chain.
 
@@ -374,8 +374,7 @@ Standard feature flow, from zero to deploy:
                                   │
                                   ▼
 [auto]     project-manager →  analyst                  →  docs/plans/PLAN_<name>.md
-                              architect (if new ADR)   →  docs/decisions/ADR-NNN.md
-                              tech-lead (approves)
+                              tech-lead (ADR + approve) →  docs/decisions/ADR-NNN.md
                                   │
                                   ▼
 [manual]   run-sprint  → sprint-runner

package/dashboard/public/content/manual/backend.en.md

@@ -583,7 +583,7 @@ correctly in case of conflict.
 | `migrator` | Sonnet 4.6 | Java 8/11/17 → 25, Spring Boot 2/3 → 4 |
 | `sprint-runner` | Sonnet 4.6 | Orchestrates the sprint, delegates in parallel |
 | `brain-keeper` | Sonnet 4.6 | History in `docs/brain/` |
-| `auditor` | Sonnet 4.6 | Audits `.claude/` consistency |
+| `update-template` | Haiku 4.5 | Audits/syncs `.claude/` against the template |
 | `release-engineer` | Sonnet 4.6 | Version bump, CHANGELOG, tag |
 | `scaffold` | Haiku 4.5 | Initial scaffold pipeline |
 

package/dashboard/public/content/manual/existing-project.en.md

@@ -162,10 +162,11 @@ harness for offline reference.
 From here the chat has access to all agents/skills. Recommended first prompt:
 
 ```text
-auditor compares .claude structure with official template
+update the template
 ```
 
-Confirms the install came out clean.
+The `update-template` agent compares the `.claude/` structure against the
+template and confirms the install came out clean.
 
 ## 3. Onboarding — project ALREADY HAS `.claude/`
 
@@ -275,11 +276,11 @@ You just installed the harness. Before touching code, audit the state.
 
 ```text
 You:
-auditor compares .claude structure with official template
+update the template
 
-Claude (auditor):
+Claude (update-template):
 > Diff vs template development-utility-kit v5.18.0:
->   .claude/agents/: 25 agents, all up to date ✓
+>   .claude/agents/: 21 agents, all up to date ✓
 >   .claude/skills/: 18 skills, 1 outdated:
 >     - auto-test-guard V5.13 (current V5.18) — pyramid ratio gate missing
 >   CLAUDE.md: Project Identity OK ✓
@@ -347,7 +348,7 @@ Claude (brain-keeper):
 > docs/brain/ provisioned:
 >   ├── MOC.md (map of content)
 >   ├── architecture/
->   │   ├── tech-debt.md (auditor report)
+>   │   ├── tech-debt.md (test-coverage-auditor report)
 >   │   └── decisions.md (ADR index)
 >   ├── features/
 >   ├── daily/2026-05-27.md
@@ -442,7 +443,7 @@ Claude (grill-me):
 > Output: docs/discovery/DISCOVERY-csv-export-sales.md
 ```
 
-From here the flow is standard (analyst → architect → sprint-runner →
+From here the flow is standard (analyst → tech-lead → sprint-runner →
 gate-keeper → code-reviewer → tech-lead). See `pipeline.en.md` for details.
 
 ## 7. Workflow 3 — Stack migration (migrator)
@@ -600,7 +601,7 @@ All trigger the `update-template` agent (haiku). Result identical to CLI.
 - ALWAYS on a dedicated branch (`chore/update-harness-<date>`)
 - Review diff in `.claude/settings.json` (hooks can change behavior)
 - Confirm `## Project Identity` in `CLAUDE.md` is intact
-- Run `auditor` afterwards to validate
+- Run `duk lint` afterwards to validate the `.claude/` structure
 - Test 1-2 critical skills before merge (`audit the tests`, `run the tests`)
 - Keep `.claude.backup-*` backup for 7 days before removing
 
@@ -610,7 +611,7 @@ All trigger the `update-template` agent (haiku). Result identical to CLI.
 |---|---|
 | Adopt project without .claude/ | `duk install` (terminal) OR `update-template` (chat) |
 | Update template | `duk install` (terminal) OR `update the template` (chat) |
-| Compare with official template | `auditor compares .claude structure with official template` |
+| Compare with official template | `duk lint` (terminal) OR `update the template` (chat) |
 | Audit coverage | `audit the tests` |
 | Prioritize debt | `tech-lead prioritizes P0/P1` |
 | Generate missing tests | `gate-keeper generates tests for P0` |
@@ -744,8 +745,8 @@ conflict on the next merge.
 | `duk install` fails with "not a git repo" | Target directory isn't a git repo | `git init` or abort — installer requires git |
 | `duk install` fails with `git pull` error | Target directory has pending changes | `git commit` or `git stash` first |
 | Directory exists but isn't a git repo | Detected but invalid | Installer aborts with exit 1 — init git or remove directory |
-| `auditor` reports outdated agents | Template evolved | `duk install` re-injects |
-| `auditor` reports custom skills deleted | Overwritten by update | Restore from `.claude.backup-<date>/skills/` |
+| `update-template` reports outdated agents | Template evolved | `duk install` re-injects |
+| `update-template` reports custom skills deleted | Overwritten by update | Restore from `.claude.backup-<date>/skills/` |
 | `migrator` refuses to start | Gate baseline isn't GREEN | `run the tests`, pay debt, try again |
 | `test-coverage-auditor` returns P0 | Business rules without tests | DO NOT skip; generate tests (`gate-keeper generates...`) OR create a documented acceptance ADR |
 | `update-template` botched `CLAUDE.md` merge | Conflict in automatic merge | `cp CLAUDE.md.bak.<date> CLAUDE.md` + manual section merge |

package/dashboard/public/content/manual/frontend.en.md

@@ -821,7 +821,7 @@ Full details in `[Mobile](mobile)`.
 | Wireframe / screen flow | `wireframe for <screen>` |
 | Refactor component | `refactor <ComponentName>` |
 | Standalone a11y audit | `accessibility audit on <feature>` |
-| Macro ADR (signal vs RxJS, etc.) | `architect proposes ADR for <decision>` |
+| Macro ADR (signal vs RxJS, etc.) | `tech-lead proposes ADR for <decision>` |
 | Remember preference | `remember that <X>` |
 | Record history | `record in brain` |
 | Stop caveman | `stop caveman` |
@@ -1015,7 +1015,7 @@ Full reference: `[Hooks reference](../docs/hooks-reference)`.
 - `[Architecture](../docs/architecture-overview)` — harness macro view
 - `[Agents reference](../docs/agents-reference)` — full agent list
 - `[Skills reference](../docs/skills-reference)` — full skill list
-- `[Pipeline](../docs/pipeline)` — PO → analyst → architect → run-sprint → gate-keeper flow
+- `[Pipeline](../docs/pipeline)` — PO → analyst → tech-lead → run-sprint → gate-keeper flow
 - `[Quality gate](../docs/quality-gate)` — detailed senior+ thresholds
 - `[Stack rules](../docs/stack-rules)` — Angular/Spring/etc. conventions
 - `[Hooks reference](../docs/hooks-reference)` — active Git hooks

package/dashboard/public/content/manual/fullstack.en.md

@@ -18,7 +18,7 @@ a project with:
   `ng-bootstrap`).
 - **PostgreSQL 17** + **Redis 7** via `docker-compose`.
 - Shared types via `openapi-typescript` (generated from `/v3/api-docs`).
-- Workflow driven by Cowork / Claude Code agents (analyst, architect,
+- Workflow driven by Cowork / Claude Code agents (analyst,
   backend-developer, frontend-developer, qa-engineer, gate-keeper,
   tech-lead, etc.).
 
@@ -172,7 +172,7 @@ my-fullstack/
 │   ├── prd/                              ← PRD_*.md         (to-prd skill)
 │   ├── issues/                           ← ISSUES_*.md      (to-issues skill)
 │   ├── plans/                            ← PLAN_*.md        (analyst agent)
-│   ├── decisions/                        ← ADR-NNN-<slug>.md (architect/tech-lead)
+│   ├── decisions/                        ← ADR-NNN-<slug>.md (tech-lead)
 │   └── brain/                            ← Obsidian vault   (brain-keeper agent)
 │       ├── daily/
 │       ├── features/
@@ -180,7 +180,7 @@ my-fullstack/
 │       ├── decisions/
 │       └── architecture/tech-debt.md
 ├── .claude/                              ← harness config
-│   ├── agents/                           ← 25 agents
+│   ├── agents/                           ← 21 agents
 │   ├── skills/                           ← 18 skills
 │   ├── hooks/                            ← PreToolUse, PostToolUse, etc.
 │   └── settings.json
@@ -899,7 +899,7 @@ Edit `CLAUDE.md`:
 In chat:
 
 ```text
-> "auditor, compare structure with template"
+> "update the template"
 > "test-coverage-auditor, audit test debt"
 > "tech-lead, prioritize P0/P1"
 > "migrate to Spring Boot 4 + Angular 21"   (optional)
@@ -1152,13 +1152,13 @@ Big table, ordered by intent.
 | Intent | Example trigger | Skill / Agent |
 |---|---|---|
 | New monorepo from scratch | `scaffold the monorepo` | `bootstrap-fullstack` |
-| Adopt existing project | `duk install` (CLI) + `auditor, compare structure` | `update-template` + `auditor` |
+| Adopt existing project | `duk install` (CLI) + `update the template` | `update-template` agent |
 | Non-interactive adoption | `duk install` (per project) / `duk sync-all` (batch) | `duk` CLI |
 | Idea discovery | `grill me about <X>` | `grill-me` |
 | Generate PRD | `generate PRD` | `to-prd` |
 | PRD into issues | `break into issues` | `to-issues` |
 | Technical plan (Sprint) | `analyst, generate the plan` | `analyst` agent |
-| Decision ADR | `architect, propose an ADR for <X>` | `architect` agent |
+| Decision ADR | `tech-lead, propose an ADR for <X>` | `tech-lead` agent |
 | Implement Sprint N | `run sprint <N> of PLAN_<X>.md` | `run-sprint` |
 | Backend feature | `backend-developer, create endpoint <X>` | `backend-developer` agent |
 | Frontend feature | `frontend-developer, create screen <X>` | `frontend-developer` agent |

package/dashboard/public/content/manual/mobile.en.md

@@ -679,11 +679,10 @@ Tests missing?                  -> run tests
 |---|---|---|
 | `mobile-developer` | Sonnet 4.6 | React Native 0.84+, Expo SDK 54+, New Architecture, TS strict, Reanimated 4, FlashList 2 |
 | `ux-designer` | Sonnet 4.6 | Mobile-specific: touch targets (>= 44pt), safe area, dynamic type, dark mode |
-| `architect` | Sonnet 4.6 | State mgmt (Zustand vs TanStack vs Jotai), navigation pattern, OTA strategy |
 | `qa-engineer` | Sonnet 4.6 | Jest + RN Testing Library + Detox/Maestro |
 | `gate-keeper` | Sonnet 4.6 | Senior+ gate adapted for mobile (Detox flakiness tolerated) |
 | `devops-engineer` | Sonnet 4.6 | EAS Build, EAS Submit, EAS Update, fastlane (if bare workflow) |
-| `tech-lead` | Opus 4.7 | Mobile stack decision, OTA strategy, native breaking changes |
+| `tech-lead` | Opus 4.7 | Mobile stack decision, state mgmt (Zustand vs TanStack vs Jotai), navigation pattern, OTA strategy, native breaking changes |
 | `product-owner` | Opus 4.7 | Scope, MVP iOS-first vs Android-first, mobile persona |
 | `security-engineer` | Opus 4.7 | SecureStore, jailbreak/root detection, certificate pinning, OWASP MASVS |
 | `database-engineer` | Sonnet 4.6 | MMKV schema, AsyncStorage migration, encrypted local DB (SQLite + sqlcipher) |
@@ -823,7 +822,7 @@ Check:
 ## Cross references
 
 - [Architecture overview](../docs/architecture-overview) — 2-layer model (skill + agent)
-- [Agents reference](../docs/agents-reference) — all 25 agents
+- [Agents reference](../docs/agents-reference) — all 21 agents
 - [Skills reference](../docs/skills-reference) — all 18 skills
 - [Pipeline](../docs/pipeline) — end-to-end flow
 - [Quality gate](../docs/quality-gate) — senior+ thresholds

package/dashboard/public/content/manual/quickstart.en.md

@@ -151,7 +151,7 @@ You just installed the harness, scaffolded or adopted a project, ran your first
 |---|---|
 | "How do skills know when to fire?" | [architecture-overview](../docs/architecture-overview) — 3-layer model, keyword matching, agent dispatch |
 | "What skill should I use for X?" | [skills-reference](../docs/skills-reference) — full catalog, per-skill triggers, when NOT to use |
-| "Which agent does what?" | [agents-reference](../docs/agents-reference) — 25 agents grouped by domain authority |
+| "Which agent does what?" | [agents-reference](../docs/agents-reference) — 21 agents grouped by domain authority |
 | "What is the discovery → delivery pipeline?" | [pipeline](../docs/pipeline) — full canonical flow + shortcuts for small features |
 | "Who decides what, when do I get interrupted?" | [autonomy-matrix](../docs/autonomy-matrix) — the master rule |
 | "Why these external plugins?" | [plugins](../docs/plugins) — selection rationale for grill-me, caveman, impeccable, rtk |
@@ -184,7 +184,7 @@ For deeper problems: [troubleshooting](../docs/troubleshooting).
 
 ## What this guide skipped on purpose
 
-- The 8-stage canonical pipeline (`grill-me → to-prd → to-issues → analyst → architect → tech-lead → sprint-runner → gate-keeper → code-reviewer → tech-lead → brain-keeper`). For 99% of tasks you do not invoke it directly — `project-manager` handles routing. Read [pipeline](../docs/pipeline) when you need the formal flow.
+- The canonical pipeline (`grill-me → to-prd → to-issues → analyst → tech-lead → sprint-runner → gate-keeper → code-reviewer → tech-lead → brain-keeper`). For 99% of tasks you do not invoke it directly — `project-manager` handles routing. Read [pipeline](../docs/pipeline) when you need the formal flow.
 - 34 ADRs. They explain why each architectural choice was made. Read them when you are evaluating whether to adopt the harness for a serious project, or when you propose a change. Not required for daily use.
 - The senior+ quality gate thresholds (coverage ≥85%, mutation ≥70%, a11y, Lighthouse). They run when `gate-keeper` is invoked — you do not need to memorize them.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eltonssouza/development-utility-kit",
-  "version": "0.14.0",
+  "version": "0.14.2",
   "description": "npx installer for the development-utility-kit harness",
   "bin": {
     "duk": "bin/cli.js"