@the-bearded-bear/claude-craft 8.22.0 → 8.23.0

package/Dev/i18n/en/Vercel/agents/vercel-reviewer.md

@@ -206,9 +206,9 @@ Does any Function declare export const config = { runtime: 'edge' } (or
 "runtime": "edge" in vercel.json's functions block)?
   YES --> Is this Function newly added or recently modified (not purely legacy,
           untouched code)?
-          YES --> MAJOR: Edge Runtime is deprecated by Vercel — migrate to Fluid
+          YES --> MAJOR: Edge Runtime is not recommended by Vercel — migrate to Fluid
                   Compute on the Node.js runtime (default) for full Node API access,
-                  bytecode-cached cold starts (Node 20+), and Active CPU pricing
+                  bytecode-cached cold starts (Node 22+), and Active CPU pricing
           NO  --> MINOR: flag as legacy-migration debt, do not block unmodified code
   NO  --> Function runs on the Node.js/Fluid Compute default --> continue to Node
           version check
@@ -220,7 +220,7 @@ Does any Function declare export const config = { runtime: 'edge' } (or
 Is the Node.js version pinned (package.json "engines.node", or the Vercel project's
 Node.js Version setting) to 20.x or newer?
   NO  --> MINOR: unpinned/old Node version forfeits Fluid Compute's bytecode-caching
-          cold-start improvement (Node 20+ specific) and risks silent runtime drift
+          cold-start improvement (Node 22+ specific) and risks silent runtime drift
           across redeploys
   YES --> OK
 ```
@@ -242,7 +242,7 @@ using it?
 
 **Edge Runtime on new/modified code:**
 ```typescript
-// FORBIDDEN — Edge Runtime declared on a newly-added Function: deprecated pattern
+// FORBIDDEN — Edge Runtime declared on a newly-added Function: discouraged pattern
 export const config = { runtime: 'edge' };
 
 export default function handler(req: Request) {
@@ -251,7 +251,7 @@ export default function handler(req: Request) {
 }
 
 // CORRECT — Node.js/Fluid Compute default, full Node API access, faster cold starts
-// on Node 20+ via bytecode caching
+// on Node 22+ via bytecode caching
 export const config = { maxDuration: 10 };
 
 export default function handler(req: VercelRequest, res: VercelResponse) {
@@ -277,7 +277,7 @@ export default function handler(req: VercelRequest, res: VercelResponse) {
 ```
 ```typescript
 // api/legacy.ts
-// TODO(JIRA-1234): migrate off Edge Runtime — deprecated by Vercel, see Fluid Compute
+// TODO(JIRA-1234): migrate off Edge Runtime — not recommended by Vercel, see Fluid Compute
 export const config = { runtime: 'edge' };
 ```
 
@@ -329,7 +329,7 @@ export default async function handler(req: VercelRequest, res: VercelResponse) {
 |---------|----------|--------------|
 | Runtime | Node.js/Fluid Compute default | `runtime: 'edge'` on new/modified code |
 | Legacy Edge Runtime | Ticketed migration marker (TODO + issue ref) | Silent, un-flagged Edge Runtime left in place |
-| Node version | Pinned to 20+ (`engines.node` or project setting) | Unpinned, drifting default |
+| Node version | Pinned to 22.x or 24.x (Node 20 is deprecated on Vercel since 2026-10-01) (`engines.node` or project setting) | Unpinned, drifting default |
 | Handler input | Validated/parsed (zod, manual guard) before use | Raw `req.body`/`req.query` used unchecked |
 | Handler output | Explicit status + typed body on every path | Implicit 200, inconsistent error shape |
 | Cold-start awareness | Heavy imports lazy-loaded/deferred when not always needed | Every dependency imported eagerly at module top |
@@ -796,7 +796,7 @@ describe('api/cron/daily', () => {
 | Topic | What to check |
 |-------|---------------|
 | **Fluid Compute** | Confirm Functions default to Fluid Compute (Active CPU pricing), not legacy fixed-concurrency Serverless Functions billing |
-| **Edge Runtime deprecation** | Any `runtime: 'edge'` found should carry a migration ticket reference, never be presented as the recommended pattern for new code |
+| **Edge Runtime discouraged** | Any `runtime: 'edge'` found should carry a migration ticket reference, never be presented as the recommended pattern for new code |
 | **Deprecated Storage packages** | `@vercel/kv`/`@vercel/postgres` imports are a MAJOR finding regardless of when they were added — flag for Marketplace migration (Neon/Upstash) |
 | **ISR cache primitive vs vercel.json headers** | Framework-native revalidation and vercel.json `headers` must never target the same route for `Cache-Control` |
 | **Cron plan limits** | The Hobby plan caps Cron Jobs at 1/day — verify the declared schedule matches the actual plan tier in use |

package/Dev/i18n/en/Vite/CLAUDE.md.template

@@ -6,7 +6,7 @@
 
 **Stack**: Vite {{VITE_VERSION}}, TypeScript {{TS_VERSION}}
 
-**Scope**: framework-agnostic Vite usage only — vanilla JS/TS apps, library authoring (build.lib), multi-page apps (rollupOptions.input), Workers/WASM entries. Not for React/Vue/Angular/Svelte dev-server config — see that stack's own tooling.md.
+**Scope**: framework-agnostic Vite usage only — vanilla JS/TS apps, library authoring (build.lib), multi-page apps (rolldownOptions.input), Workers/WASM entries. Not for React/Vue/Angular/Svelte dev-server config — see that stack's own tooling.md.
 
 ### Project Structure
 ```
@@ -32,7 +32,7 @@ project-root/
 ### Architecture: {{ARCHITECTURE_PATTERN}}
 - **Entry point**: `index.html` at the project root (or `root`), never inside `public/`
 - **Library mode**: `build.lib` + `vite-plugin-dts` for packages published to npm
-- **Multi-page**: `build.rollupOptions.input` naming each HTML entry explicitly
+- **Multi-page**: top-level `input` naming each HTML entry explicitly
 - **Workers/WASM**: `new Worker(new URL(...), { type: 'module' })`, `?init`/`?url` suffixes
 
 See `rules/02-architecture.md` for complete patterns.

package/Dev/i18n/en/Vite/agents/vite-reviewer.md

@@ -1,6 +1,6 @@
 ---
 name: vite-reviewer
-description: Vite 8.x framework-agnostic code review specialist — vanilla JS/TS apps, library authoring (build.lib), multi-page apps (rollupOptions.input), Workers/WASM entries, plugin config
+description: Vite 8.x framework-agnostic code review specialist — vanilla JS/TS apps, library authoring (build.lib), multi-page apps (rolldownOptions.input), Workers/WASM entries, plugin config
 model: haiku
 effort: low
 maxTurns: 6
@@ -14,13 +14,13 @@ skills: [solid-principles, testing, security]
 
 ## Identity
 
-I am a specialist in Vite 8.x code review, **framework-agnostic** by design. My scope covers pure Vite usage: vanilla JS/TS applications (index.html as the source entry, never inside public/), library authoring via build.lib and vite-plugin-dts, multi-page applications via build.rollupOptions.input, and Workers/WASM entry points. I do NOT cover Vite integrations specific to React, Vue, Angular, or Svelte -- those stacks already document their own dev-server integration in their respective tooling.md file. I do not perform a generic audit -- I detect what breaks the module graph, bloats the bundle, or unnecessarily complicates a Vite configuration.
+I am a specialist in Vite 8.x code review, **framework-agnostic** by design. My scope covers pure Vite usage: vanilla JS/TS applications (index.html as the source entry, never inside public/), library authoring via build.lib and vite-plugin-dts, multi-page applications via build.rolldownOptions.input, and Workers/WASM entry points. I do NOT cover Vite integrations specific to React, Vue, Angular, or Svelte -- those stacks already document their own dev-server integration in their respective tooling.md file. I do not perform a generic audit -- I detect what breaks the module graph, bloats the bundle, or unnecessarily complicates a Vite configuration.
 
 ## Scoring System (100 points)
 
 | Category | Points | Focus |
 |----------|--------|-------|
-| Config and Architecture Vite | 30 | vite.config.ts, index.html, build.lib, rollupOptions.input, plugins |
+| Config and Architecture Vite | 30 | vite.config.ts, index.html, build.lib, rolldownOptions.input, plugins |
 | TypeScript and Quality | 20 | strict tsconfig, moduleResolution bundler, vite-plugin-dts |
 | Tests | 25 | Vitest config/coverage, tests on the published build |
 | Build Output and Performance | 25 | Bundle size, tree-shaking, externalization, code-splitting |
@@ -49,7 +49,7 @@ Is the package consumed by other packages/apps (published on npm)?
   YES --> Is build.lib configured?
     NO --> CRITICAL: without build.lib, Vite produces an app bundle (index.html
             required, no multiple ESM/CJS formats, no peer dep externalization)
-    YES --> Does rollupOptions.external cover all peerDependencies?
+    YES --> Does rolldownOptions.external cover all peerDependencies?
       NO --> MAJOR: the host framework runtime will be duplicated for the consumer
       YES --> Is vite-plugin-dts configured?
         NO --> MAJOR: no published typings, package unusable in strict TypeScript
@@ -62,7 +62,7 @@ Is the package consumed by other packages/apps (published on npm)?
 ```
 Does the project have several distinct HTML pages (not just client-side routes)?
   NO --> Classic SPA: a single index.html, client-side routing
-  YES --> Is build.rollupOptions.input an object naming each page?
+  YES --> Is build.rolldownOptions.input an object naming each page?
     NO --> MAJOR: secondary pages are not built or depend on a
             manual, unoptimized loading path
     YES --> Do the pages share heavy dependencies?
@@ -133,7 +133,7 @@ export default defineConfig({
       formats: ['es', 'cjs'],
       fileName: (format) => `my-lib.${format}.js`,
     },
-    rollupOptions: {
+    rolldownOptions: {
       // Never bundle peer dependencies
       external: ['react', 'react-dom'],
       output: {
@@ -144,7 +144,7 @@ export default defineConfig({
 });
 ```
 
-**rollupOptions.input for multi-page apps:**
+**rolldownOptions.input for multi-page apps:**
 ```typescript
 // BAD: secondary pages not declared in the config
 export default defineConfig({});
@@ -155,7 +155,7 @@ import { defineConfig } from 'vite';
 
 export default defineConfig({
   build: {
-    rollupOptions: {
+    rolldownOptions: {
       input: {
         main: resolve(__dirname, 'index.html'),
         about: resolve(__dirname, 'pages/about.html'),
@@ -225,8 +225,10 @@ export function vitePluginMyTransform(): Plugin {
 | index.html | At the root of `root`, transformed as a source entry | Copied into public/ |
 | public/ | Static assets only (favicon, robots.txt) | Source HTML/JS imported from public/ |
 | build.lib | Configured for every published package | App bundle published as a library |
-| rollupOptions.external | Peer deps externalized | Host framework bundled inside the library |
-| rollupOptions.input | Object naming each HTML page (multi-page) | Manual, unoptimized loading |
+| rolldownOptions.external | Peer deps externalized | Host framework bundled inside the library |
+| rolldownOptions.input | Object naming each HTML page (multi-page) | Manual, unoptimized loading |
+| rollupOptions / worker.rollupOptions / optimizeDeps.esbuildOptions | rolldownOptions equivalents (deprecated since Vite 8) | Deprecated aliases kept in the config |
+| Node.js | `^20.19.0` or `>=22.12.0` (Vite 8 requirement) | Node 18 or 20 < 20.19 |
 | Custom plugins | vite-plugin-* prefix, explicit `name` property | Anonymous plugin without a name |
 | Environment variables | VITE_ prefix for client exposure | Unprefixed secrets referenced client-side |
 
@@ -237,7 +239,7 @@ export function vitePluginMyTransform(): Plugin {
 | vite.config.ts correct (defineConfig, aliases synced with tsconfig) | 8 |
 | index.html at the root of the right folder, never inside public/ | 6 |
 | build.lib correctly configured (entry, formats, external, vite-plugin-dts) | 8 |
-| rollupOptions.input for multi-page, plugins named per vite-plugin-* convention | 8 |
+| rolldownOptions.input for multi-page, plugins named per vite-plugin-* convention | 8 |
 
 ---
 
@@ -441,7 +443,7 @@ Does package.json declare "sideEffects": false?
 ### Decision Tree: Multi-page Code-splitting
 
 ```
-Does the app have several pages (rollupOptions.input)?
+Does the app have several pages (rolldownOptions.input)?
   YES --> Does manualChunks isolate a shared vendor chunk?
     NO --> MAJOR: each page duplicates the same heavy dependencies
     YES --> Does the largest lazy chunk exceed 80KB gzip?
@@ -486,14 +488,14 @@ export { formatDate, parseDate } from './utils';
 // BAD: the host framework is bundled inside the published library
 export default defineConfig({
   build: { lib: { entry: 'src/index.ts', formats: ['es'] } },
-  // no rollupOptions.external
+  // no rolldownOptions.external
 });
 
 // GOOD: peer deps explicitly externalized
 export default defineConfig({
   build: {
     lib: { entry: 'src/index.ts', formats: ['es', 'cjs'] },
-    rollupOptions: {
+    rolldownOptions: {
       external: (id) => /^(react|react-dom|vue)/.test(id),
     },
   },
@@ -507,7 +509,7 @@ export default defineConfig({
 
 // GOOD: shared vendor chunk across all pages
 build: {
-  rollupOptions: {
+  rolldownOptions: {
     output: {
       manualChunks(id) {
         if (id.includes('node_modules')) return 'vendor';
@@ -564,8 +566,8 @@ build: {
 
 ### Phase 2: Vite-specific Configuration (15 min)
 
-1. If library: verify build.lib, formats, rollupOptions.external, vite-plugin-dts
-2. If multi-page: verify rollupOptions.input, manualChunks
+1. If library: verify build.lib, formats, rolldownOptions.external, vite-plugin-dts
+2. If multi-page: verify rolldownOptions.input, manualChunks
 3. If Workers/WASM: verify new URL(...import.meta.url), ?init/?url suffixes
 4. Verify custom plugin naming convention (vite-plugin-*, name property)
 5. Verify environment variables (VITE_ prefix, no secrets exposed client-side)

package/Dev/i18n/en/Vite/commands/check-compliance.md

@@ -36,7 +36,7 @@ Execute complete configuration and architecture check:
 - vite.config.ts correctness (defineConfig, aliases synced with tsconfig) (8 pts)
 - index.html placement at project root, never inside public/ (6 pts)
 - build.lib configuration for libraries (entry, formats, external, vite-plugin-dts) (8 pts)
-- rollupOptions.input for multi-page apps, plugin naming convention (vite-plugin-*) (8 pts)
+- rolldownOptions.input for multi-page apps, plugin naming convention (vite-plugin-*) (8 pts)
 
 **Reference**: `.claude/agents/vite-reviewer.md` (section 1)
 
@@ -151,7 +151,7 @@ Sub-scores:
   • vite.config.ts correctness       : XX/8
   • index.html placement             : XX/6
   • build.lib configuration          : XX/8
-  • rollupOptions.input / plugins    : XX/8
+  • rolldownOptions.input / plugins    : XX/8
 
 Strengths:
 - [Architecture strengths]

package/Dev/i18n/es/Angular/agents/angular-reviewer.md

@@ -46,8 +46,8 @@ Soy un especialista en revisión de código Angular 22 y TypeScript. Mi enfoque
 
 **Zoneless por defecto (estable) :**
 - Ahorro de ~33 KB de bundle (Zone.js opcional)
-- +30-40% de mejora en el rendimiento de renderizado según Angular DevRel
-- API estable: `provideZonelessChangeDetection()` desde `@angular/core` (ya no `Experimental`)
+- Las mejoras de rendimiento varían según la aplicación (la cifra «+30-40%» proviene de una fuente de 2024): medir, no asumir
+- Ningún provider requerido en v21+/v22: `provideZonelessChangeDetection()` solo es necesario en v20 (https://angular.dev/guide/zoneless)
 
 **Signal Forms (estable v22) :**
 - Alternativa nativa a los Reactive Forms con APIs de señales, **lista para producción**
@@ -421,7 +421,7 @@ it('should load users on init', () => {
     SÍ --> ¿Los event listeners activan correctamente el CD?
   NO --> ¿Se usa Zone.js?
     SÍ --> MENOR en v22+: se recomienda migrar a zoneless (ahorra ~33 KB)
-    NO --> Verificar que provideZonelessChangeDetection() esté configurado (estable desde v20.2)
+    NO --> Verificar que ningún provideZoneChangeDetection() reactive Zone.js (zoneless por defecto desde v21)
 
 ¿Se usa httpResource() para peticiones HTTP repetitivas?
   NO --> ¿Los componentes usan signal + effect + HttpClient?

package/Dev/i18n/es/Common/agents/devops-engineer.md

@@ -7,6 +7,20 @@ maxTurns: 8
 tools: [Read, Glob, Grep, Edit, Write, Bash, WebFetch, WebSearch]
 permissionMode: default
 skills: [git-workflow, security]
+disallowedTools:
+  - "Bash(rm -rf:*)"
+  - "Bash(dd:*)"
+  - "Bash(mkfs:*)"
+  - "Bash(kubectl delete:*)"
+  - "Bash(helm uninstall:*)"
+  - "Bash(terraform destroy:*)"
+  - "Bash(tofu destroy:*)"
+  - "Bash(docker system prune -a*)"
+  - "Bash(docker volume rm:*)"
+  - "Bash(curl * | sh*)"
+  - "Bash(wget * | sh*)"
+  - "Bash(git push --force*)"
+  - "Bash(git push -f*)"
 ---
 
 # Agente Ingeniero DevOps
@@ -31,7 +45,7 @@ Eres un **Ingeniero DevOps Senior** con más de 10 años de experiencia en CI/CD
 | Docker | Builds multi-etapa, optimización de imágenes, escaneo de seguridad |
 | Docker Compose | Orquestación local, perfiles, extensiones |
 | Kubernetes | Deployments, Services, Ingress, ConfigMaps, Secrets |
-| Helm | Charts, values, templating | 4.2.0 (MAJOR — server-side apply, WASM plugins, API v4 ; Helm 3 EOL seguridad nov. 2026) |
+| Helm | Charts, values, templating | 4.2.2 (Helm 4 = MAJOR — server-side apply, WASM plugins, API v4 ; Helm 3 EOL seguridad nov. 2026) |
 
 ### Proveedores Cloud
 | Proveedor | Servicios |

package/Dev/i18n/es/Common/agents/ralph-conductor.md

@@ -5,6 +5,17 @@ model: opus
 effort: xhigh
 maxTurns: 10
 memory: user
+disallowedTools:
+  - "Bash(rm -rf:*)"
+  - "Bash(dd:*)"
+  - "Bash(mkfs:*)"
+  - "Bash(:(){:|:&};:*)"
+  - "Bash(sudo:*)"
+  - "Bash(chmod 777:*)"
+  - "Bash(curl * | sh*)"
+  - "Bash(wget * | sh*)"
+  - "Bash(git push --force*)"
+  - "Bash(git push -f*)"
 ---
 
 # Agente Ralph Conductor v2.0

package/Dev/i18n/es/Common/agents/refactoring-specialist.md

@@ -7,6 +7,15 @@ maxTurns: 8
 tools: [Read, Glob, Grep, Edit, Write, Bash, WebFetch, WebSearch]
 permissionMode: default
 skills: [solid-principles, kiss-dry-yagni, testing]
+disallowedTools:
+  - "Bash(rm -rf:*)"
+  - "Bash(dd:*)"
+  - "Bash(mkfs:*)"
+  - "Bash(:(){:|:&};:*)"
+  - "Bash(sudo:*)"
+  - "Bash(chmod 777:*)"
+  - "Bash(curl * | sh*)"
+  - "Bash(wget * | sh*)"
 ---
 
 # Agente Especialista en Refactoring

package/Dev/i18n/es/Common/agents/security-auditor.md

@@ -22,13 +22,16 @@ Eres un **Auditor de Seguridad Sénior** con más de 15 años de experiencia en
 
 | # | Amenaza | Foco de auditoría |
 |---|---------|-------------------|
-| 1 | Broken Access Control (incluye SSRF) | Verificar permisos por solicitud, denegar por defecto |
-| 2 | Cryptographic Failures | TLS 1.3, Argon2id, sin MD5/SHA1 en código nuevo |
-| 3 | Injection | Consultas parametrizadas, validación, sanitización |
-| 4 | Insecure Design | Modelado de amenazas, rate limiting |
-| 5 | Security Misconfiguration | Hardening, mensajes de error genéricos en producción |
-| 6 | Software Supply Chain Failures | SLSA, SBOM, Sigstore keyless |
-| 7 | Mishandling of Exceptional Conditions | Registrar errores, nunca exponer stack traces |
+| A01 | Broken Access Control (incluye SSRF) | Verificar permisos por solicitud, denegar por defecto |
+| A02 | Security Misconfiguration | Hardening, mensajes de error genéricos en producción |
+| A03 | Software Supply Chain Failures | SLSA, SBOM, Sigstore keyless, Dependabot/Renovate, Trivy/Grype, `npm audit --audit-level=moderate` |
+| A04 | Cryptographic Failures | TLS 1.3, Argon2id, sin MD5/SHA1 en código nuevo |
+| A05 | Injection | Consultas parametrizadas, validación, sanitización |
+| A06 | Insecure Design | Modelado de amenazas, rate limiting |
+| A07 | Authentication Failures | MFA, proteccion contra fuerza bruta, JWT EdDSA, sesiones invalidadas al cerrar sesion |
+| A08 | Software or Data Integrity Failures | Verificacion de firmas/checksums, CI/CD seguro, actualizaciones firmadas |
+| A09 | Security Logging and Alerting Failures | Centralizar logs, alertas ante anomalias, retencion >= 1 ano, nunca registrar credenciales/tokens |
+| A10 | Mishandling of Exceptional Conditions | Registrar errores, nunca exponer stack traces |
 
 ### Dominios de auditoría
 

package/Dev/i18n/es/Common/agents/tdd-coach.md

@@ -7,6 +7,15 @@ maxTurns: 8
 tools: [Read, Glob, Grep, Edit, Write, Bash, WebFetch, WebSearch]
 permissionMode: default
 skills: [testing, solid-principles]
+disallowedTools:
+  - "Bash(rm -rf:*)"
+  - "Bash(dd:*)"
+  - "Bash(mkfs:*)"
+  - "Bash(:(){:|:&};:*)"
+  - "Bash(sudo:*)"
+  - "Bash(chmod 777:*)"
+  - "Bash(curl * | sh*)"
+  - "Bash(wget * | sh*)"
 ---
 
 # Agente Coach TDD/BDD

package/Dev/i18n/es/Common/agents/uiux-orchestrator.md

@@ -4,8 +4,17 @@ description: UI-UX coordination and orchestration
 model: sonnet
 effort: medium
 maxTurns: 10
-tools: [Read, Glob, Grep, Edit, Write, Bash, Task, WebFetch, WebSearch]
+tools: [Read, Glob, Grep, Edit, Write, Bash, Agent, WebFetch, WebSearch]
 permissionMode: default
+disallowedTools:
+  - "Bash(rm -rf:*)"
+  - "Bash(dd:*)"
+  - "Bash(mkfs:*)"
+  - "Bash(:(){:|:&};:*)"
+  - "Bash(sudo:*)"
+  - "Bash(chmod 777:*)"
+  - "Bash(curl * | sh*)"
+  - "Bash(wget * | sh*)"
 ---
 
 # Agente Orquestador UI/UX

package/Dev/i18n/es/Common/commands/getting-started.md

@@ -70,7 +70,7 @@ Based on the detected stack, recommend 3 contextualized commands that provide im
 - `/vuejs:check-security` — XSS, CSP, OWASP audit
 
 **Laravel:**
-- `/laravel:check-code-quality` — PSR-12, Pest 4, coding standards
+- `/laravel:check-code-quality` — PER-CS 3.0, Pest 4/5, coding standards
 - `/laravel:check-testing` — Test coverage with Pest
 - `/laravel:check-security` — OWASP audit, Sanctum config
 
@@ -91,7 +91,7 @@ Based on the detected stack, recommend 3 contextualized commands that provide im
 
 **PHP (standalone):**
 - `/php:check-code-quality` — PSR-12, PHPStan Level 10
-- `/php:check-testing` — Pest 4 test coverage
+- `/php:check-testing` — Pest 5 test coverage
 - `/php:check-security` — Security best practices
 
 **Unknown/Multi-stack:**

package/Dev/i18n/es/Common/commands/setup-rtk.md

@@ -75,9 +75,9 @@ echo "CLAUDE_CODE_FORK_SUBAGENT=${CLAUDE_CODE_FORK_SUBAGENT:-NO DEFINIDO}"
 Si no están definidas, recomendar agregar en `~/.bashrc` (o `~/.zshrc`):
 
 ```bash
-# Usar Sonnet 4.6 para sub-agentes (exploración, grep, lectura de archivos) en lugar de Opus
+# Usar Sonnet 5.5 para sub-agentes (exploración, grep, lectura de archivos) en lugar de Opus
 # → 40-60% de reducción de coste en invocaciones de sub-agentes
-export CLAUDE_CODE_SUBAGENT_MODEL="sonnet"
+export CLAUDE_CODE_SUBAGENT_MODEL="claude-sonnet-5-5"
 
 # Ejecutar sub-agentes en contextos aislados (Claude Code 2.1.117+, ver COMPATIBILITY.md)
 # → Evita contaminar la ventana de contexto principal con el estado intermedio de sub-agentes

package/Dev/i18n/es/Common/rules/04-solid-principles.md

@@ -357,7 +357,7 @@ Es mejor tener varias interfaces especificas que una interfaz general.
 
 #### SRP
 - [ ] Cada clase tiene una sola responsabilidad claramente definida
-- [ ] Los metodos hacen una sola cosa (< 20 lineas)
+- [ ] Los metodos hacen una sola cosa (objetivo < 10, max 20 lineas)
 - [ ] Sin metodos con "y" u "o" en el nombre
 
 #### OCP

package/Dev/i18n/es/Common/rules/05-kiss-dry-yagni.md

@@ -29,7 +29,7 @@ El codigo mas simple es a menudo el mejor codigo.
 
 ### Reglas KISS
 
-1. **Metodos cortos:** Maximo 20 lineas por metodo
+1. **Metodos cortos:** Objetivo < 10 lineas, limite maximo 20 lineas por metodo
 2. **Complejidad ciclomatica:** Maximo 10 por metodo
 3. **Profundidad de indentacion:** Maximo 3 niveles
 4. **Parametros:** Maximo 4 parametros por metodo
@@ -369,7 +369,7 @@ class ConcreteRepository         // Infrastructure
 ### Antes de cada commit
 
 #### KISS
-- [ ] Metodos < 20 lineas
+- [ ] Metodos < 10 lineas (limite 20)
 - [ ] Complejidad ciclomatica < 10
 - [ ] Indentacion max 3 niveles
 - [ ] Parametros max 4 por metodo
@@ -395,11 +395,14 @@ class ConcreteRepository         // Infrastructure
 |---------|----------|--------|
 | Lineas por metodo | < 10 | < 20 |
 | Complejidad ciclomatica | < 5 | < 10 |
+| Complejidad cognitiva | < 7 | < 10 |
 | Lineas por clase | < 150 | < 200 |
 | Duplicacion | 0% | < 3% |
 | Cobertura de tests | > 80% | > 70% |
 | Dependencias por clase | < 5 | < 7 |
 
+> Los umbrales de Cognitive Complexity (SonarQube S3776) < 7 / < 10 son una eleccion interna, deliberadamente mas estricta que el valor por defecto de Sonar (15 por funcion); relajarlos si el contexto del equipo lo requiere.
+
 ---
 
 ## Recursos

package/Dev/i18n/es/Common/rules/10-documentation.md

@@ -289,7 +289,7 @@ docs/
 ### OpenAPI (Swagger)
 
 ```yaml
-openapi: 3.1.1
+openapi: 3.2.1  # current (3.1.x remains valid if your tooling lags)
 info:
   title: User API
   version: 1.0.0