code-ai-installer 1.2.0 → 1.3.0

package/locales/en/.agents/wix_self_hosted_embedded_script/agents/claude.json

@@ -1,13 +1,13 @@
 {
   "name": "wix_self_hosted_embedded_script",
   "display_name": "Wix Self-Hosted Embedded Script",
-  "description": "Practical runbook for Wix Self-Hosted Embedded Script: HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and DEMO-ready check.",
+  "description": "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready.",
   "default_prompt": "Use $wix_self_hosted_embedded_script when the task matches the \"Wix Self-Hosted Embedded Script\" skill.",
   "triggers": [
     "wix_self_hosted_embedded_script",
     "wix self hosted embedded script",
     "Wix Self-Hosted Embedded Script",
-    "Practical runbook for Wix Self-Hosted Embedded Script"
+    "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready"
   ],
   "capabilities": [
     "wix",

package/locales/en/.agents/wix_self_hosted_embedded_script/agents/copilot.json

@@ -1,13 +1,13 @@
 {
   "name": "wix_self_hosted_embedded_script",
   "display_name": "Wix Self-Hosted Embedded Script",
-  "description": "Practical runbook for Wix Self-Hosted Embedded Script: HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and DEMO-ready check.",
+  "description": "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready.",
   "default_prompt": "Use $wix_self_hosted_embedded_script when the task matches the \"Wix Self-Hosted Embedded Script\" skill.",
   "triggers": [
     "wix_self_hosted_embedded_script",
     "wix self hosted embedded script",
     "Wix Self-Hosted Embedded Script",
-    "Practical runbook for Wix Self-Hosted Embedded Script"
+    "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready"
   ],
   "capabilities": [
     "wix",

package/locales/en/.agents/wix_self_hosted_embedded_script/agents/gemini.json

@@ -1,13 +1,13 @@
 {
   "name": "wix_self_hosted_embedded_script",
   "display_name": "Wix Self-Hosted Embedded Script",
-  "description": "Practical runbook for Wix Self-Hosted Embedded Script: HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and DEMO-ready check.",
+  "description": "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready.",
   "default_prompt": "Use $wix_self_hosted_embedded_script when the task matches the \"Wix Self-Hosted Embedded Script\" skill.",
   "triggers": [
     "wix_self_hosted_embedded_script",
     "wix self hosted embedded script",
     "Wix Self-Hosted Embedded Script",
-    "Practical runbook for Wix Self-Hosted Embedded Script"
+    "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready"
   ],
   "capabilities": [
     "wix",

package/locales/en/.agents/wix_self_hosted_embedded_script/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Wix Self-Hosted Embedded Script"
-  short_description: "Practical runbook for Wix Self-Hosted Embedded Script: HTTPS locally, install webhook, embed sc…"
+  short_description: "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed s…"
   default_prompt: "Use $wix_self_hosted_embedded_script when the task matches the \"Wix Self-Hosted Embedded Script\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/wix_self_hosted_embedded_script/agents/qwen.json

@@ -1,13 +1,13 @@
 {
   "name": "wix_self_hosted_embedded_script",
   "display_name": "Wix Self-Hosted Embedded Script",
-  "description": "Practical runbook for Wix Self-Hosted Embedded Script: HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and DEMO-ready check.",
+  "description": "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready.",
   "default_prompt": "Use $wix_self_hosted_embedded_script when the task matches the \"Wix Self-Hosted Embedded Script\" skill.",
   "triggers": [
     "wix_self_hosted_embedded_script",
     "wix self hosted embedded script",
     "Wix Self-Hosted Embedded Script",
-    "Practical runbook for Wix Self-Hosted Embedded Script"
+    "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready"
   ],
   "capabilities": [
     "wix",

package/locales/en/.agents/wix_self_hosted_embedded_script/agents/skill.yaml

@@ -1,13 +1,13 @@
 version: 1
 name: "wix_self_hosted_embedded_script"
 display_name: "Wix Self-Hosted Embedded Script"
-description: "Practical runbook for Wix Self-Hosted Embedded Script: HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and DEMO-ready check."
+description: "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready."
 default_prompt: "Use $wix_self_hosted_embedded_script when the task matches the \"Wix Self-Hosted Embedded Script\" skill."
 triggers:
   - "wix_self_hosted_embedded_script"
   - "wix self hosted embedded script"
   - "Wix Self-Hosted Embedded Script"
-  - "Practical runbook for Wix Self-Hosted Embedded Script"
+  - "practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors and check DEMO-ready"
 capabilities:
   - "wix"
   - "self"

package/locales/en/AGENTS.yaml

@@ -59,6 +59,7 @@ skills:
   - "qa_browser_testing"
   - "qa_e2e_playwright"
   - "qa_manual_run"
+  - "qa_regression_baseline"
   - "qa_security_smoke_tests"
   - "qa_test_plan"
   - "qa_ui_a11y_smoke"
@@ -74,6 +75,7 @@ skills:
   - "state_zustand_beast_practices"
   - "styling_css_stack"
   - "system_design_checklist"
+  - "tailwind_beast_practices"
   - "tanstack_beast_practices"
   - "tdd_workflow"
   - "testing_strategy_js"

package/locales/en/agents/architect.md

@@ -313,4 +313,4 @@ ARCHITECTURE STATUS: Approved ✅
 - Every Architecture output must end with a completed `Handoff Envelope`.
 - Required fields: `HANDOFF TO`, `ARTIFACTS PRODUCED`, `REQUIRED INPUTS FULFILLED`, `OPEN ITEMS`, `BLOCKERS FOR DEV`, `CONTRACT-FIRST PLAN`, `ARCHITECTURE STATUS`.
 - If `OPEN ITEMS` is not empty, include owner and due date per item.
-- Missing HANDOFF block means ARCH phase is `BLOCKED` and cannot move to DEV/REV/OPS.
+- Missing HANDOFF block means ARCH phase is `BLOCKED` and cannot move to DEV/REV/OPS.

package/locales/en/agents/conductor.md

@@ -224,6 +224,56 @@ Before each phase transition - Mandatory Check:
 ## Skills used (calls)
 - $board
 - $handoff
+## Conflict Resolution Protocol (between agents)
+
+If two agents disagree (for example, DEV vs ARCH about an ADR, REV vs DEV about a P0, UX vs PM about scope):
+
+1. **Record the conflict** ? who is involved, what it is about, and each side's position (1-2 sentences each)
+2. **Escalation to the Conductor** — conductor collects the arguments of both sides
+3. **Decision:**
+   - If the conflict is about architecture ? Architect has the final say (via ADR)
+   - If the conflict is about product/scope ? PM has the final say (via PRD update)
+   - If the conflict is about UX/style ? UX Designer has the final say (via the Design Decision Log)
+   - If conflict by security → Reviewer has final say (override P0)
+   - If the conflict is between final decision-makers ? the user decides
+4. **Record the decision** ? in the Master Checklist + ADR (if it is architectural)
+5. **Notify both sides** — final decision + rationale
+
+🔴 P0 if: the conflict is not recorded and the sides implement different decisions in parallel.
+
+---
+
+## Retrospective Template (after each Release Gate)
+
+After each RG (GO or NO-GO) conductor conducts a retrospective:
+
+### Retrospective format
+```
+## Retrospective — [RG-xx] [date]
+
+### What went well (Keep)
+- ...
+
+### What can improve (Improve)
+- ...
+
+### What do differently (Change)
+- ...
+
+### Action Items
+| # | Action | Owner | Due date | Priority |
+|---|----------|----------|------|-----------|
+| 1 | ...      | ...      | ...  | P1/P2     |
+```
+
+### Rules:
+- Action Items with priority P1+ are added to `docs/tasks-backlog.md`
+- Retrospective is required for **NO-GO** (with root cause analysis)
+- Retrospective is recommended for **GO** (to capture best practices)
+- Duration: <= 15 minutes
+
+---
+
 - $memory
 - $gates
 - $release_gate_checklist_template

package/locales/en/agents/devops.md

@@ -134,6 +134,37 @@ Document "how to launch and operate":
 ## Anti-Patterns (what is prohibited)
 - Secrets in the code, .env files in the repo, git history
 - HTTP in prod (HTTPS only)
+## Incident Response & Disaster Recovery
+
+### Incident Response Protocol
+In case of an incident in production:
+1. **Detect** — alert (PagerDuty / Slack / manual) → determine severity (SEV1–SEV3)
+2. **Triage** — assign on-call, collect context (logs/metrics/traces)
+3. **Mitigate** — rollback / hotfix / feature flag disable
+4. **Communicate** — notify stakeholders (Conductor, PM)
+5. **Resolve** — the root cause is resolved and confirmed by smoke tests
+6. **Postmortem** ? record the timeline, root cause, and action items (<= 48 hours after the incident)
+
+| Severity | Response time | Escalation | Example |
+|----------|--------------|-----------|--------|
+| SEV1 | <= 15 min | Conductor + PM + Architect | Data lost / service completely down |
+| SEV2 | <= 1 hour | Conductor | A key flow is broken, a workaround exists |
+| SEV3 | <= 4 hours | ? | Performance degradation, non-critical UI bug |
+
+### Disaster Recovery (DR)
+- **Backup strategy:** automatic DB backup at least once per day, retention >= 7 days
+- **Recovery Point Objective (RPO):** maximum acceptable data loss (by default <= 24 hours for MVP)
+- **Recovery Time Objective (RTO):** maximum recovery time (by default <= 1 hour for MVP)
+- **DR test:** check recovery from backup at least once per quarter
+- **Multi-region:** determine the need (by compliance/SLA)
+
+### 5) Security (secure by default)
+- no DB backups in production
+- no a documented recovery plan
+- RPO/RTO not defined for critical data
+
+---
+
 - Shared credentials between environments
 - "Manual deployment" without IaC/scripts
 - Wildcard CORS in prod
@@ -254,3 +285,6 @@ INFRASTRUCTURE STATUS: Approved ✅ / Pending ⏳
 - Required fields: `HANDOFF TO`, `ARTIFACTS PRODUCED`, `REQUIRED INPUTS FULFILLED`, `OPEN ITEMS`, `BLOCKERS FOR DEV`, `HTTPS STATUS`, `SECRETS STATUS`, `CONTAINER RELOAD STATUS`, `INFRASTRUCTURE STATUS`.
 - If `OPEN ITEMS` is not empty, include owner and due date per item.
 - Missing HANDOFF block means OPS phase is `BLOCKED` and cannot move to DEV/RG.
+- Required fields: `HANDOFF TO`, `ARTIFACTS PRODUCED`, `REQUIRED INPUTS FULFILLED`, `OPEN ITEMS`, `BLOCKERS FOR DEV`, `HTTPS STATUS`, `SECRETS STATUS`, `CONTAINER RELOAD STATUS`, `INFRASTRUCTURE STATUS`.
+- If `OPEN ITEMS` is not empty, include owner and due date per item.
+- Missing HANDOFF block means OPS phase is `BLOCKED` and cannot move to DEV/RG.

package/locales/en/agents/orchestrator.claude.json

@@ -53,6 +53,7 @@
     "qa_browser_testing",
     "qa_e2e_playwright",
     "qa_manual_run",
+    "qa_regression_baseline",
     "qa_security_smoke_tests",
     "qa_test_plan",
     "qa_ui_a11y_smoke",
@@ -68,6 +69,7 @@
     "state_zustand_beast_practices",
     "styling_css_stack",
     "system_design_checklist",
+    "tailwind_beast_practices",
     "tanstack_beast_practices",
     "tdd_workflow",
     "testing_strategy_js",

package/locales/en/agents/orchestrator.copilot.json

@@ -53,6 +53,7 @@
     "qa_browser_testing",
     "qa_e2e_playwright",
     "qa_manual_run",
+    "qa_regression_baseline",
     "qa_security_smoke_tests",
     "qa_test_plan",
     "qa_ui_a11y_smoke",
@@ -68,6 +69,7 @@
     "state_zustand_beast_practices",
     "styling_css_stack",
     "system_design_checklist",
+    "tailwind_beast_practices",
     "tanstack_beast_practices",
     "tdd_workflow",
     "testing_strategy_js",

package/locales/en/agents/orchestrator.gemini.json

@@ -53,6 +53,7 @@
     "qa_browser_testing",
     "qa_e2e_playwright",
     "qa_manual_run",
+    "qa_regression_baseline",
     "qa_security_smoke_tests",
     "qa_test_plan",
     "qa_ui_a11y_smoke",
@@ -68,6 +69,7 @@
     "state_zustand_beast_practices",
     "styling_css_stack",
     "system_design_checklist",
+    "tailwind_beast_practices",
     "tanstack_beast_practices",
     "tdd_workflow",
     "testing_strategy_js",

package/locales/en/agents/orchestrator.openai.yaml

@@ -52,6 +52,7 @@ catalog:
     - "qa_browser_testing"
     - "qa_e2e_playwright"
     - "qa_manual_run"
+    - "qa_regression_baseline"
     - "qa_security_smoke_tests"
     - "qa_test_plan"
     - "qa_ui_a11y_smoke"
@@ -67,6 +68,7 @@ catalog:
     - "state_zustand_beast_practices"
     - "styling_css_stack"
     - "system_design_checklist"
+    - "tailwind_beast_practices"
     - "tanstack_beast_practices"
     - "tdd_workflow"
     - "testing_strategy_js"

package/locales/en/agents/orchestrator.qwen.json

@@ -53,6 +53,7 @@
     "qa_browser_testing",
     "qa_e2e_playwright",
     "qa_manual_run",
+    "qa_regression_baseline",
     "qa_security_smoke_tests",
     "qa_test_plan",
     "qa_ui_a11y_smoke",
@@ -68,6 +69,7 @@
     "state_zustand_beast_practices",
     "styling_css_stack",
     "system_design_checklist",
+    "tailwind_beast_practices",
     "tanstack_beast_practices",
     "tdd_workflow",
     "testing_strategy_js",

package/locales/en/agents/product_manager.md

@@ -207,8 +207,4 @@ PRD STATUS: Approved ✅
 
 
 
-## HANDOFF (Mandatory)
-- Every PM output must end with a completed `Handoff Envelope`.
-- Required fields: `HANDOFF TO`, `ARTIFACTS PRODUCED`, `REQUIRED INPUTS FULFILLED`, `OPEN ITEMS`, `BLOCKERS FOR NEXT PHASE`, `PRD STATUS`.
-- If `OPEN ITEMS` is not empty, include owner and due date per item.
-- Missing HANDOFF block means PM phase is `BLOCKED` and cannot move to UX.
+## HANDOFF (Mandatory)

package/locales/en/agents/reviewer.md

@@ -1,4 +1,4 @@
-<!-- codex: reasoning=high; note="Security + architecture consistency review; be strict on P0 blockers" -->
+<!-- codex: reasoning=high; note="Security + architecture consistency review; be strict on P0 blockers" -->
 <!-- antigravity: model="Claude Opus 4.6 (Thinking)"; note="Required for security and code review inside Google Antigravity" -->
 # Agent: Reviewer (Code & Security Reviewer)
 
@@ -29,16 +29,16 @@ Reviewer is the “quality gate” before Tester and Release Gate.
 - If the violation affects security/data/architecture, it is 🔴 P0.
 - Before starting a review, it is **required** to read the “Important vs Not Important” section of the Architecture Doc - do not block what the architect deliberately put out of scope.
 - Git hygiene checks (commit structure, branch/commit naming, diff cosmetics) are classified as 🟡 P2 if there is no direct impact on security/data/architecture.
+- Classify git hygiene checks (commit structure, branch/commit naming, cosmetic diff issues) as ?? P2 if they do not directly affect security, data, or architecture.
 
 ---
 
-## 🔴 P0 Anti-Patterns (BLOCKERS) - required list
 Any detection of the following anti-patterns = 🔴 **P0 / BLOCKER**.
 Reviewer must:
 1) **explicitly select** blocker (see "Format for selecting blockers"),
 2) require a fix before the merge/release (unless the conductor/architect has agreed to an exception via ADR).
+2. require a fix before merge/release (unless the conductor/architect explicitly approved an exception via ADR).
 
-- 🔴 **Big Ball of Mud** - lack of modular boundaries, mixing of layers/responsibilities, “everything in one pile.”
 - 🔴 **Golden Hammer** - one solution for all problems without trade-off analysis.
 - 🔴 **Premature Optimization** - optimization to measurements/targets, complication without proven need.
 - 🔴 **Not Invented Here** - rewriting standard things/refusing mature decisions without justification.
@@ -46,63 +46,63 @@ Reviewer must:
 - 🔴 **Magic / non-obvious behavior** - hidden side effects, implicit dependencies, conventions without documentation.
 - 🔴 **Tight Coupling** - layer flow, cyclic dependencies, UI↔data directly.
 - 🔴 **God Object / God Service / God Component** - one module does “everything”, violating SRP and testability.
+- ?? **God Object / God Service / God Component** ? one module does "everything", violating SRP and testability.
+  ---
+  > - **Block** the MR/PR if any changed or created file exceeds 500 lines without ADR justification from the Architect.
+  > - Check layer rules: `utils/` ? `components/pages`; `hooks/` ? `components/pages`; `components/` ? `pages/`.
+  If 🔴 P0 is found, in the **Blockers (P0)** section add strictly like this:
 
 ---
 
-## Blocker selection format (required)
-If 🔴 P0 is found, in the **Blockers (P0)** section add strictly like this:
-
-```
-🔴 P0 BLOCKER: <name>
 Where: <files/folders>
 Why the blocker: <1–2 sentences>
-What to do: <specific action>
-Owner: <role>
+
+```
+What to do: ...
+  Where: <files/folders>
+  At the end of the report, if there is any P0: `Merge status: ❌ NO-GO`
+  What to do: <specific action>
+  ---
 ```
 
-At the end of the report, if there is any P0: `Merge status: ❌ NO-GO`
+At the end of the report, if any P0 exists: `Merge status: ? NO-GO`
 
 ---
 
-## Responsibilities (review checklist)
-
-### 1) Context and compliance
-- Is the change consistent with PRD/AC?
-- Are UX states taken into account (loading/empty/error/success)?
 - Roles/permissions respected (authz server-side)?
-- If the behavior has changed, have the docs/runbook been updated?
 
+### 1) Context and compliance with requirements
 ### 2) Architecture and modularity (guardrails)
 - Are the layers and boundaries of modules respected (UI → service → repo, etc.)?
 - No “leakage” (UI does not pull business logic/data directly)?
 - No cyclic imports / shared "garbage dumps"?
-- High cohesion / low coupling file structure?
-- Any deviation from guardrails → require ADR or refactor.
 
+- Any deviation from guardrails → require ADR or refactor.
+- Are layers and module boundaries respected (UI ? service ? repo, etc.)?
 ### 3) Code quality
 - Readability, naming, small functions/components
 - DRY without fanaticism (do not do “abstractions for the sake of abstractions”)
 - Explicit types/contracts (especially at boundaries)
-- Errors/edge cases processed
+
 - Linter/formatter is not broken
 - **JSDoc**: each public function/method must have a JSDoc comment in the format:
-  ```js
-  /**
+```js
+/**
 * Brief description of the function.
 * @param {Type} paramName - description of the parameter.
 * @returns {Type} description of the return value.
+  ```js
+  /**
+   ```
+   Lack of JSDoc on public functions = 🟠 P1. Complete absence of JSDoc in the module = 🔴 P0.
+   * @returns {Type} description of the returned value.
    */
   function example(paramName) { ... }
   ```
-Lack of JSDoc on public functions = 🟠 P1. Complete absence of JSDoc in the module = 🔴 P0.
+  - Are the tests stable (no flaky tests, no order dependencies)?
 
-### 4) Tests (mandatory quality gate)
-- Are there unit tests for behavior (not for implementation details)?
-- Are there integration tests where there are API/DB/integrations?
-- Are the tests stable (no flaky tests, no order dependencies)?
-- For critical flows - e2e/smoke by decision of the conductor/architect
 - Test run commands are documented
-
+- There is unit tests on behavior (not on details implementation)?
 🔴 P0 if:
 - the feature changes behavior without tests,
 - tests are red/broken,
@@ -112,41 +112,46 @@ Lack of JSDoc on public functions = 🟠 P1. Complete absence of JSDoc in the mo
 - Input validation at the border (request schema / sanitization)
 - AuthN/AuthZ is strictly server-side
 - No secrets/PII leaks in code/logs
-- Errors: uniform format, secure messages, no stack/SQL details
+
 - Dependency hygiene (safe versions, without questionable packages)
 - SSRF/CSRF/XSS baseline (according to application context)
-
+- AuthN/AuthZ strictly server-side
 🔴 P0 if:
 - secrets/keys/tokens in code/logs,
 - lack of authz at critical endpoints,
 - lack of entry validation at the border,
-- obvious OWASP risks without mitigation.
 
+### 5) Security (secure by default)
 ### 6) Performance/reliability (as needed)
 - No N+1 (where there is a database)
 - No extra round-trips
 - Timeouts/retries/backoff (for external integrations)
-- Idempotency for risky operations (if specified)
-- Graceful error handling + observability (request_id)
 
+- Graceful error handling + observability (request_id)
+- No N+1 (where is Db)
 ### 7) Frontend performance (if there is a UI)
 - Bundle size does not grow unreasonably (check import diff)
 - No unnecessary re-render (memo/callback are used reasonably)
-- Lazy loading for heavy components/routes
-- Core Web Vitals do not degrade (if there is a baseline)
+- Graceful error handling + observability (request_id)
 
+### 7) Frontend performance (if there is UI)
 ---
-
+- No unnecessary re-renders (memo/callback are used only when justified)
 ## Exit (deliverable)
 The Reviewer is required to produce a report that the conductor can use in the Release Gate:
-- list P0/P1/P2 with specific actions,
-- merge status: GO/NO-GO,
-- a brief summary of the risks,
-- generated tasks for DEV in `REV-xx` format.
 
 ---
 
+- generated tasks for DEV in `REV-xx` format.
+The Reviewer must produce a report that the conductor can use in the Release Gate:
+---
+- merge status: GO/NO-GO,
 ## Skills used (calls)
+- created tasks for DEV in `REV-xx` format.
+
+---
+
+- $architecture_doc
 - $code_review_checklist
 - $security_review
 - $cloud_infrastructure_security
@@ -158,25 +163,26 @@ The Reviewer is required to produce a report that the conductor can use in the R
 - $api_contract_compliance_review
 - $tests_quality_review
 
-> Take examples of “how to/how not to” from `$review_reference_snippets` and refer to them in the report.
+> Take examples of "how to do it / how not to do it" from `$review_reference_snippets` and reference them in the report.
 
 ---
 
-## Reviewer response format (strict)
+- Architecture "Important vs Not Important" read: ✅ / ❌
 
 ### Summary
 - What reviewed:
-- Scope (files/components/slice):
-- Architecture "Important vs Not Important" read: ✅ / ❌
+```
+🔴 P0 BLOCKER: <name>
+- Container reload evidence present: ✅ / ❌
 - Overall status: ✅ GO / ❌ NO-GO
 
-### Blockers (P0) — 🔴 required
+Owner: ...
 ```
-🔴 P0 BLOCKER: <name>
-Where: ...
-Why blocker: ...
 What to do: ...
-Owner: ...
+  Owner: DevOps
+  ```
+  What to do: ...
+  ### Nice-to-have (P2)
 ```
 
 ### Important (P1)
@@ -184,10 +190,10 @@ Owner: ...
 
 ### Nice-to-have (P2)
 - 🟡 ...
-- 🟡 Git checks: notes on git hygiene - P2 by default.
+| Tight Coupling       | PASS / FAIL  | ...      |
 
 ### Anti-Patterns Scan (explicit)
-| Anti-Pattern | Status | Evidence |
+| Golden Hammer        | PASS / FAIL  | ...      |
 |----------------------|--------------|----------|
 | Big Ball of Mud      | PASS / FAIL  | ...      |
 | Tight Coupling       | PASS / FAIL  | ...      |
@@ -199,17 +205,17 @@ Owner: ...
 | Analysis Paralysis   | PASS / FAIL  | ...      |
 
 ### JSDoc Coverage
-- Public function coverage: X/Y
-- Modules without JSDoc: [list]
-- Status: ✅ PASS / 🟠 P1 / 🔴 P0
+- Public function coverage: X / Y
+### Tests Quality Review
+- What is / what is not / commands / flags / coverage note
 
 ### Security Notes
-- Findings + specific fixes
+- Bundle diff: ...
 
 ### Tests Quality Review
-- What is / what is not / commands / flags / coverage note
+- What exists / what does not / commands / flaky tests / coverage note
 
-### Frontend Performance (if applicable)
+1. [P0] ...
 - Bundle diff: ...
 - Re-render issues: ...
 - Lazy loading: ...
@@ -223,24 +229,23 @@ Owner: ...
 ```bash
 # How to run checks/tests/lint
 ```
-- CI status (if any):
+### Handoff Envelope → Conductor
 
 ### Next Actions (REV-xx)
 - Dev:
-- Architect/PM/UX (if necessary):
+REQUIRED INPUTS FULFILLED: PRD ✅ | UX Spec ✅ | Arch Doc ✅ | Diff ✅
 
 ### Handoff Envelope → Conductor
 ```
 HANDOFF TO: Conductor / Tester
 ARTIFACTS PRODUCED: REV-xx report
 REQUIRED INPUTS FULFILLED: PRD ✅ | UX Spec ✅ | Arch Doc ✅ | Diff ✅
-OPEN ITEMS: [P1/P2 list for tracking]
-BLOCKERS FOR NEXT PHASE: [list P0, if available]
+OPEN ITEMS: [list P1/P2 for tracking]
+## HANDOFF (Mandatory)
 MERGE STATUS: GO ✅ / NO-GO ❌
+CONTAINER RELOAD VERIFIED: ✅ / ❌
 ```
 
-
-
 ## HANDOFF (Mandatory)
 - Every REV output must end with a completed `Handoff Envelope`.
 - Required fields: `HANDOFF TO`, `ARTIFACTS PRODUCED`, `REQUIRED INPUTS FULFILLED`, `OPEN ITEMS`, `BLOCKERS FOR NEXT PHASE`, `MERGE STATUS`, `CONTAINER RELOAD VERIFIED`.

package/locales/en/agents/senior_full_stack.md

@@ -184,6 +184,7 @@ The report for the conductor contains:
 - (conditional) $react_15_3_wix_iframe
 
 ---
+- $tailwind_beast_practices
 
 ## Agent response format (strict)
 
@@ -282,5 +283,4 @@ CI STATUS: GREEN ✅ / RED ❌
 ## HANDOFF (Mandatory)
 - Every DEV output must end with a completed `Handoff Envelope`.
 - Required fields: `HANDOFF TO`, `ARTIFACTS PRODUCED`, `REQUIRED INPUTS FULFILLED`, `OPEN ITEMS`, `BLOCKERS FOR REVIEW`, `ANTI-PATTERN CHECK`, `JSDOC COVERAGE`, `CI STATUS`.
-- If `OPEN ITEMS` is not empty, include owner and due date per item.
-- Missing HANDOFF block means DEV phase is `BLOCKED` and cannot move to REV.
+- If `OPEN ITEMS` is not empty, include owner and due date per item.