@aurorajs.dev/catalyst-cli 1.1.3 → 2.0.0

package/dist/templates/monorepo/.claude/hooks/lint-barrels.test.ts

@@ -128,10 +128,11 @@ describe('the hook process, run against a file outside CLAUDE_PROJECT_DIR', () =
       join(checkout, 'cliter', 'harness-rules-index.json'),
       JSON.stringify({
         byId: {
-          // HR-BARRELS-003 governs the deep-path check today (HR-BARRELS-001
-          // was derogated in its favor — task 5.1/5.7); this fixture mirrors
-          // the real catalog shape rather than the retired id.
-          'HR-BARRELS-003': { severity: 'informational', state: 'active' },
+          // HR-BARRELS-004 governs the deep-path check today (HR-BARRELS-001
+          // was derogated in its favor — task 5.1/5.7 — and its successor
+          // HR-BARRELS-003 was in turn derogated by T-45); this fixture
+          // mirrors the real catalog shape rather than a retired id.
+          'HR-BARRELS-004': { severity: 'informational', state: 'active' },
           'HR-BARRELS-002': { severity: 'blocking', state: 'active' },
         },
       }),
@@ -149,7 +150,7 @@ describe('the hook process, run against a file outside CLAUDE_PROJECT_DIR', () =
 
     offender = join(checkout, 'backend', 'src', '@app', 'other', 'consumer.ts');
     mkdirSync(dirname(offender), { recursive: true });
-    // Deep-path import instead of the module barrel — an HR-BARRELS-003 finding.
+    // Deep-path import instead of the module barrel — an HR-BARRELS-004 finding.
     writeFileSync(offender, "import { thing } from '@app/bc/mod/thing';\n");
   });
 
@@ -161,7 +162,7 @@ describe('the hook process, run against a file outside CLAUDE_PROJECT_DIR', () =
     });
 
     assert.equal(run.status, 0, `hook exited ${run.status}: ${run.stderr}`);
-    assert.match(run.stdout, /HR-BARRELS-003/);
+    assert.match(run.stdout, /HR-BARRELS-004/);
     assert.match(run.stdout, /@app\/bc\/mod\/thing/);
   });
 });
@@ -171,15 +172,18 @@ describe('the hook process, run against a file outside CLAUDE_PROJECT_DIR', () =
  * `HR-BARRELS-001` independently of the shared script. Task 5.1 derogated
  * that id and replaced it with `HR-BARRELS-003` for the same deep-path
  * check — the shared script was re-pointed in 5.5, but the hook was not.
+ * `HR-BARRELS-003` was itself later derogated and replaced by
+ * `HR-BARRELS-004` (T-45).
  *
- * This fixture mirrors the REAL current catalog shape (HR-BARRELS-001
- * derogated, HR-BARRELS-003 active/informational), not the older fixture
- * above (which fakes 001 as still active and therefore stays green
- * regardless of this bug). Under the current catalog, an unfixed hook reads
- * `rule001.state === 'active'` as false, `findings001` becomes `[]`, and the
- * hook goes silent — this is the false negative the task describes.
+ * This fixture mirrors the REAL current catalog shape (HR-BARRELS-001 and
+ * HR-BARRELS-003 both derogated, HR-BARRELS-004 active/informational), not
+ * the older fixture above (which fakes 001 as still active and therefore
+ * stays green regardless of this bug). Under the current catalog, an
+ * unfixed hook reads `rule001.state === 'active'` as false, `findings001`
+ * becomes `[]`, and the hook goes silent — this is the false negative the
+ * task describes.
  */
-describe('the hook process, under the current catalog (HR-BARRELS-001 derogated, HR-BARRELS-003 active)', () => {
+describe('the hook process, under the current catalog (HR-BARRELS-001 and HR-BARRELS-003 derogated, HR-BARRELS-004 active)', () => {
   let checkout: string;
   let elsewhere: string;
   let offender: string;
@@ -196,7 +200,8 @@ describe('the hook process, under the current catalog (HR-BARRELS-001 derogated,
         byId: {
           'HR-BARRELS-001': { severity: 'informational', state: 'derogated' },
           'HR-BARRELS-002': { severity: 'blocking', state: 'active' },
-          'HR-BARRELS-003': { severity: 'informational', state: 'active' },
+          'HR-BARRELS-003': { severity: 'informational', state: 'derogated' },
+          'HR-BARRELS-004': { severity: 'informational', state: 'active' },
         },
       }),
     );
@@ -214,11 +219,11 @@ describe('the hook process, under the current catalog (HR-BARRELS-001 derogated,
     offender = join(checkout, 'backend', 'src', '@app', 'other', 'consumer.ts');
     mkdirSync(dirname(offender), { recursive: true });
     // Deep-path import instead of the module barrel — a deep-path finding,
-    // governed today by HR-BARRELS-003, not the derogated HR-BARRELS-001.
+    // governed today by HR-BARRELS-004, not the derogated HR-BARRELS-001/-003.
     writeFileSync(offender, "import { thing } from '@app/bc/mod/thing';\n");
   });
 
-  it('still reports the deep-path violation, attributed to HR-BARRELS-003', () => {
+  it('still reports the deep-path violation, attributed to HR-BARRELS-004', () => {
     const run = spawnSync(process.execPath, ['--import', 'tsx', HOOK], {
       input: JSON.stringify({ tool_input: { file_path: offender } }),
       env: { ...process.env, CLAUDE_PROJECT_DIR: elsewhere },
@@ -226,7 +231,7 @@ describe('the hook process, under the current catalog (HR-BARRELS-001 derogated,
     });
 
     assert.equal(run.status, 0, `hook exited ${run.status}: ${run.stderr}`);
-    assert.match(run.stdout, /HR-BARRELS-003/);
+    assert.match(run.stdout, /HR-BARRELS-004/);
     assert.match(run.stdout, /@app\/bc\/mod\/thing/);
   });
 });

package/dist/templates/monorepo/.claude/hooks/lint-barrels.ts

@@ -1,6 +1,6 @@
 #!/usr/bin/env tsx
 /**
- * PostToolUse hook — lint de imports según HR-BARRELS-003 y HR-BARRELS-002 sobre
+ * PostToolUse hook — lint de imports según HR-BARRELS-004 y HR-BARRELS-002 sobre
  * el fichero que Claude acaba de escribir o editar.
  *
  * Por qué un hook y no solo el pre-commit: el pre-commit corre sobre staged
@@ -27,7 +27,7 @@
  *
  * Respuesta JSON al harness:
  *   - Violación blocking (HR-BARRELS-002 hoy) → { decision: "block", reason: "..." }
- *   - Solo informational (HR-BARRELS-003 hoy) → { hookSpecificOutput: { ... } }
+ *   - Solo informational (HR-BARRELS-004 hoy) → { hookSpecificOutput: { ... } }
  *   - Fichero generado, sin hallazgos, o cualquier error interno → exit 0 sin output
  *
  * Fail-open: el hook NUNCA revienta el flujo del agente por un fallo propio.
@@ -104,9 +104,9 @@ interface RuleMeta {
 }
 
 interface RuleIndex {
-  rule003: RuleMeta;
+  rule004: RuleMeta;
   rule002: RuleMeta;
-  rule003Active: boolean;
+  rule004Active: boolean;
   rule002Active: boolean;
 }
 
@@ -126,16 +126,18 @@ function loadRuleMeta(repoRoot: string): RuleIndex {
     };
   }
 
-  // HR-BARRELS-001 was derogated and replaced by HR-BARRELS-003 (task 5.1/5.5):
-  // the deep-path check is now governed by the new id, matching the shared
-  // script's own `loadRuleMeta` (scripts/harness-rules/lint-barrels.ts).
-  const rule003 = toMeta('HR-BARRELS-003');
+  // HR-BARRELS-001 was derogated and replaced by HR-BARRELS-003 (task 5.1/5.5), which was in
+  // turn derogated and replaced by HR-BARRELS-004 (T-45: the dynamic-import exception had been
+  // edited in place onto HR-BARRELS-003 instead of derogate+create — see
+  // cliter/harness-rules/barrels.md). The deep-path check is now governed by the new id,
+  // matching the shared script's own `loadRuleMeta` (scripts/harness-rules/lint-barrels.ts).
+  const rule004 = toMeta('HR-BARRELS-004');
   const rule002 = toMeta('HR-BARRELS-002');
 
   return {
-    rule003,
+    rule004,
     rule002,
-    rule003Active: rule003.state === 'active',
+    rule004Active: rule004.state === 'active',
     rule002Active: rule002.state === 'active',
   };
 }
@@ -207,15 +209,15 @@ async function main(): Promise<void> {
       filePath,
       process.env.CLAUDE_PROJECT_DIR ?? process.cwd(),
     );
-    const { rule003, rule002, rule003Active, rule002Active } = loadRuleMeta(repoRoot);
+    const { rule004, rule002, rule004Active, rule002Active } = loadRuleMeta(repoRoot);
     const tsconfigPaths = loadBackendPaths(repoRoot);
 
     const rawFindings = lintFile(filePath, content, tsconfigPaths, repoRoot);
 
     // Filtrar por reglas activas. El tag interno 'kind: 001' identifica la
     // FAMILIA de chequeo (deep-path) heredada de HR-BARRELS-001, no el id de
-    // catálogo que la gobierna hoy — ese es HR-BARRELS-003 (task 5.1/5.5).
-    const findings001 = rule003Active
+    // catálogo que la gobierna hoy — ese es HR-BARRELS-004 (T-45).
+    const findings001 = rule004Active
       ? rawFindings.filter((f) => f.kind === '001')
       : [];
     const findings002 = rule002Active
@@ -229,18 +231,18 @@ async function main(): Promise<void> {
     // Calcular severidad predominante (D6 del design)
     const exitCode = computeExitCode(
       allFindings.map((f) => ({ kind: f.kind, isGenerated: false })),
-      rule003.severity,
+      rule004.severity,
       rule002.severity,
-      rule003Active,
+      rule004Active,
       rule002Active,
     );
 
     if (exitCode === 1) {
       // Violación blocking → decision: block. Los hallazgos que bloquean son los de
-      // CUALQUIER regla cuya severidad sea blocking (D6: si la 003 sube a blocking en
+      // CUALQUIER regla cuya severidad sea blocking (D6: si la 004 sube a blocking en
       // el catálogo, entra aquí sola, con su título y detalle correctos).
       const blockingFindings = allFindings.filter(
-        (f) => (f.kind === '001' ? rule003.severity : rule002.severity) === 'blocking',
+        (f) => (f.kind === '001' ? rule004.severity : rule002.severity) === 'blocking',
       );
       const ruleIds = [...new Set(blockingFindings.map((f) => `HR-BARRELS-${f.kind}`))].join(', ');
       const lines = blockingFindings.map((f) => {
@@ -275,7 +277,7 @@ async function main(): Promise<void> {
       });
 
       const additionalContext = [
-        `HR-BARRELS-003 (informational): deep-path imports detectados.`,
+        `HR-BARRELS-004 (informational): deep-path imports detectados.`,
         ...infLines,
         'Importa por barrel en lugar de por fichero de implementación.',
       ].join('\n');

package/dist/templates/monorepo/.claude/rules/route-backend-test.md

@@ -16,7 +16,7 @@ El gotcha específico de catalyst, y el que más tests rompe: `@ApplySchema` / `
   mock del service recibe el hash, no el texto plano.
 - `@Format` enmascara el valor de retorno: `expect(result.password).toBeDefined()` **falla** en un
   read handler.
-- `@EmitEvent` lee `this.eventEmitter`: sin `{ provide: EventEmitter2, useValue: { emit: jest.fn() } }`
+- `@EmitEvent` lee `this.eventEmitter`: sin `{ provide: EventEmitter2, useValue: { emit: vi.fn() } }`
   en `providers`, el emit revienta o se fuga a un bus real.
 
 Los handlers de catalyst tienen `main()`, no `execute()`.

package/dist/templates/monorepo/.claude/rules/scope-backend.md

@@ -4,7 +4,7 @@ paths:
   - "backend/test/**"
 ---
 
-# Ámbito backend (NestJS 11 + Drizzle + DDD por capas)
+# Ámbito backend (NestJS 12 + Drizzle + DDD por capas)
 
 Antes de escribir código, lee **`backend/CLAUDE.md`** — lleva la tabla
 `Skills (Auto-invoke based on context)` que enruta cada tarea a su skill.

package/dist/templates/monorepo/.claude/scripts/catalyst-dev-mode.sh

@@ -18,7 +18,6 @@ Current development mode: **Framework**
 Mindset: "Who else might need this?" — generalize, extract, document.
 
 Rules for this mode:
-- Plan and prepare code for future uses even if not needed right now (unless cost is high).
 - Extract composables, shared components, and utilities to @aurora/.
 - Create and update skills to document patterns.
 - Write code that is easy for AI to read, understand, and reuse.

package/dist/templates/monorepo/.claude/settings.json

@@ -199,9 +199,11 @@
       "Bash(pnpm test:packager:*)",
       "Bash(pnpm test:catalyst-regen:*)",
       "Bash(pnpm cli:test:*)",
+      "Bash(node packages/cli/bin/run.js:*)",
+      "Bash(pnpm cli:build:*)",
       "Bash(pnpm --filter aurora-back test:*)",
       "mcp__claude-in-chrome__read_console_messages",
       "mcp__claude-in-chrome__tabs_context_mcp"
     ]
   }
-}
+}

package/dist/templates/monorepo/.claude/skills/REGISTRY.md

@@ -36,7 +36,7 @@ Apply to the whole project, stack-agnostic.
 
 | Skill          | Trigger                                                                                                    | Path                                    |
 | -------------- | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------- |
-| `judgment-day` | Blind dual / adversarial review of a diff ("judgment day", "dual review", "juzgar"): two independent judges, fix confirmed issues, then re-judge | `.claude/skills/judgment-day/SKILL.md`  |
+| `judgment-day` | judgment day, dual review, adversarial review, juzgar. Run blind judges, verify every severe finding against the code, fix, then re-judge the fixed hunks | `.claude/skills/judgment-day/SKILL.md`  |
 | `typescript`   | Implementing or refactoring TS in `.ts`/`.tsx` (types, interfaces, generics, type guards, removing `any`)  | `.claude/skills/typescript/SKILL.md`    |
 
 ### Workflow — OpenSpec SDD
@@ -53,7 +53,7 @@ Apply to the whole project, stack-agnostic.
 
 | Skill              | Trigger                                                                                                                                                                                                                                                        | Path                                          |
 | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
-| `catalyst-backlog` | Creating a task for a Medium/Complex request, queueing or releasing a task, planning a PRD, or ANY mention of backlog, Queued, Blocked, dispatcher, encolar, PRD, subtarea, milestone, `tier:` or `lane:` | `.claude/skills/catalyst-backlog/SKILL.md`    |
+| `catalyst-backlog` | Creating a task for a Medium/Complex request, queueing or releasing a task, planning a PRD, archiving a document under `.backlog/docs/`, writing the «Registro de ejecución» block when a task moves to `Done`, or ANY mention of backlog, Queued, Blocked, dispatcher, encolar, PRD, subtarea, milestone, `--depends-on`, grafo, `board:graph`, supervisada, headless, `tier:`, `lane:` or `mode:` | `.claude/skills/catalyst-backlog/SKILL.md`    |
 
 ### Meta
 
@@ -127,14 +127,14 @@ NestJS-specific.
 | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
 | `catalyst-handler-composer`  | Fill in business logic inside CLI-generated handlers in `@app/*/application/*/` (CRUD archetypes + `additionalApis` scaffolds); wire `@EmitEvent` / `@ApplySchema` / `@Format`; decide handler-vs-service split. Step 0 routes CLI-territory through the CLI before any hand edit. ALSO covers hand-written COMPOSITE HANDLERS for protocol-flow endpoints (OAuth token, JWKS, webhooks): the dispatch lives in the handler, NEVER duplicated across transports. Antipattern detection on `if (grantType==='X') ... else if ...` repeated in controller AND resolver | `backend/.claude/skills/catalyst-handler-composer/SKILL.md`  |
 | `catalyst-field-schema`      | Declarative data-access layer: `FieldSchema` + 16 type handlers, the three decorators `@ApplySchema` / `@Format` / `@Sanitize` with decision tree + `payloadIndex`, the `Obj.diffAtomic` / `Obj.diff` pair (persistence delta vs structural report, `HR-PERSISTENCE-001`), and the BACKEND application of the Aurora Query DSL (`queryStatement` vs `constraint` in handlers, Drizzle translation gotchas — unknown-relation crashes, per-BC relation declarations, core-builder fallback). The DSL language itself is taught by `catalyst-query-dsl` (monorepo root) — read that first. NOT YAML authoring (→ `catalyst-schema`), full-module audits (→ `catalyst-review-module`), or the DSL language reference (→ `catalyst-query-dsl`)                                       | `backend/.claude/skills/catalyst-field-schema/SKILL.md`      |
-| `catalyst-nestjs-primitives` | Catalog + reuse-first gate for NestJS primitives: the 3 catalyst-authored items (`@Auth` composite, `AuthenticationJwtGuard`, `AuthorizationPermissionsGuard`), upstream decorator catalog (`@Timezone`, `@Auditing`, `@CurrentAccount`, `@ContentLanguage`, `@TenantPolicy`, `@TenantConstraint`), dual REST/GraphQL context via `Api.getRequestFromExecutionContext()`, `dPermissions.all` convention, and last-resort templates                             | `backend/.claude/skills/catalyst-nestjs-primitives/SKILL.md` |
-| `catalyst-backend-testing`   | Starting-point testing conventions for catalyst backend: the decorator-fires-in-TestingModule gotcha (`@ApplySchema` / `@Format` / `@Sanitize` / `@EmitEvent` all run during `handler.main()` in tests), synthesized write/read handler templates anchored on `IamCreateTagHandler` + `IamFindTagByIdHandler`, dual-context guard tests, supertest REST+GraphQL patterns, and the `dPermissions.all` seed utility pattern for `@Auth`-protected endpoint tests | `backend/.claude/skills/catalyst-backend-testing/SKILL.md`   |
+| `catalyst-nestjs-primitives` | Catalog + reuse-first gate for NestJS primitives: the 5 catalyst-authored items (`@Auth` composite, `AuthenticationJwtGuard`, `AuthorizationPermissionsGuard`, `@TenantConstraint`, `@TenantPolicy` — the last two reach consumers via the `@aurorajs.dev/core-back` specifier but live in `packages/core-back`, NOT upstream), upstream decorator catalog (`@Timezone`, `@Auditing`, `@CurrentAccount`, `@ContentLanguage`, `Permissions`), dual REST/GraphQL context via `Api.getRequestFromExecutionContext()`, `dPermissions.all` convention, tenant-scoping arguments/fail-closed/transport-boundary contract + the `hasTenant: true` module inventory, and last-resort templates | `backend/.claude/skills/catalyst-nestjs-primitives/SKILL.md` |
+| `catalyst-backend-testing`   | Vitest testing conventions for catalyst backend: the decorator-fires-in-TestingModule gotcha (`@ApplySchema` / `@Format` / `@Sanitize` / `@EmitEvent` all run during `handler.main()` in tests), write/read handler and dual-context guard anchors on real converted suites, `vi.hoisted` / `importOriginal` module mocking, supertest REST+GraphQL patterns, and the `dPermissions.all` seed pattern for `@Auth`-protected endpoint tests | `backend/.claude/skills/catalyst-backend-testing/SKILL.md`   |
 
 ### Platform Tooling
 
 | Skill            | Trigger                                                                                                                                                                                                                                                                                                                                          | Path                                          |
 | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
-| `catalyst-schema-migrations` | Two-stage drizzle-kit workflow: `generate` (offline, diffs `*.schema.ts` vs last `snapshot.json`, never the DB) + boot `migrate()` (`DrizzleMigrationsRunner`, gated by `DATABASE_MIGRATE_ON_BOOT`, matches by folder name vs `drizzle.__drizzle_migrations.name`). Covers `db:generate`/`db:migrate`/`db:check`, generate-vs-migrate-vs-push, `DATABASE_MIGRATIONS_SCHEMA`/`_TABLE` + restricted-hosting gotcha, and verified failure modes (hand-edited `.sql` without snapshot regen, worktrees sharing dev DB, index-name collisions, CLI ships definitions not migrations). Fires on editing any `*.schema.ts`, running `drizzle-kit`/`db:*`, a failing `schema-drift-check.yml`, or touching `drizzle-migrations.module.ts` — even if the user only says "I added a field to the schema". NOT ad-hoc ALTERs/data backfills via the `tools` BC (→ `catalyst-tools`) | `backend/.claude/skills/catalyst-schema-migrations/SKILL.md` |
+| `catalyst-schema-migrations` | Two-stage drizzle-kit workflow: `generate` (offline, diffs `*.schema.ts` vs last `snapshot.json`, never the DB) + boot `migrate()` (`DrizzleMigrationsRunner`, gated by `DATABASE_MIGRATE_ON_BOOT`, matches by folder name vs `drizzle.__drizzle_migrations.name`). Covers `db:generate`/`db:migrate`/`db:check`/`db:query` (the last one being the read-only path to the LIVE Postgres catalog when the environment has no `psql`), generate-vs-migrate-vs-push, `DATABASE_MIGRATIONS_SCHEMA`/`_TABLE` + restricted-hosting gotcha, and verified failure modes (hand-edited `.sql` without snapshot regen, worktrees sharing dev DB, index-name collisions, CLI ships definitions not migrations). Fires on editing any `*.schema.ts`, running `drizzle-kit`/`db:*`, needing to read the live catalog or a row count from a headless session, a failing `schema-drift-check.yml`, or touching `drizzle-migrations.module.ts` — even if the user only says "I added a field to the schema". NOT ad-hoc ALTERs/data backfills via the `tools` BC (→ `catalyst-tools`) | `backend/.claude/skills/catalyst-schema-migrations/SKILL.md` |
 | `catalyst-tools` | Reusable capabilities of the `tools` BC: **key-value** (runtime app-wide config / feature flags / encrypted secrets via the `TOOLS_KEY_VALUE_CONFIG` port; bootstrap seeding of a BC's config keys via `TOOLS_KEY_VALUE_SEEDER`), **procedures** (lifecycle of Postgres FUNCTIONs/PROCEDUREs/TRIGGERs), **migrations** (DDL/DML schema evolution + rollback). Fires whenever a design needs runtime config, seeding config keys at boot, a stored procedure, or a schema/data migration — even if the `tools` BC is not named. Excludes webhook (not implemented) | `backend/.claude/skills/catalyst-tools/SKILL.md` |
 
 ### Structure & Review