Feat/modernize node npm

.atl/.skill-registry.cache.json

@@ -0,0 +1,3 @@
+{
+  "fingerprint": "57a67d9906a0df1266417d5c1d567b607dd3d834"
+}

.atl/skill-registry.md

@@ -0,0 +1,58 @@
+# Skill Registry — ui-kit
+
+<!-- Auto-generated by gentle-ai skill-registry refresh. Run `gentle-ai skill-registry refresh --force` to regenerate. -->
+
+Last updated: 2026-10-21
+
+## Sources scanned
+
+- /Users/eclass/.agents/skills
+- /Users/eclass/.codex/skills
+
+## Contract
+
+**Delegator use only.** This registry is an index, not a summary. Any agent that launches subagents reads it to select relevant skills, then passes exact `SKILL.md` paths for the subagent to read before work.
+
+`SKILL.md` remains the source of truth. Do not inject generated summaries or compact rules by default; pass paths so subagents load the full runtime contract and preserve author intent.
+
+## Skills
+
+| Skill | Trigger / description | Scope | Path |
+| --- | --- | --- | --- |
+| `branch-pr` | Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review. | user | `/Users/eclass/.agents/skills/branch-pr/SKILL.md` |
+| `chained-pr` | Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus. | user | `/Users/eclass/.agents/skills/chained-pr/SKILL.md` |
+| `chakra-sx-migration` | Use when converting React view/component styles from styled-components to Chakra UI `sx` objects in this codebase. Apply it when a file defines styled wrappers that should become `sx...` constants or functions, and update the consuming JSX to use Chakra `Box` with `sx` and semantic `as` tags while preserving nesting, media queries, and project conventions. | user | `/Users/eclass/.codex/skills/chakra-sx-migration/SKILL.md` |
+| `cognitive-doc-design` | Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs. | user | `/Users/eclass/.agents/skills/cognitive-doc-design/SKILL.md` |
+| `comentarios` | Escribe comentarios y JSDoc útiles en español para funciones con lógica no obvia, efectos o invariantes relevantes. | user | `/Users/eclass/.codex/skills/comentarios/SKILL.md` |
+| `comment-writer` | Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments. | user | `/Users/eclass/.agents/skills/comment-writer/SKILL.md` |
+| `contra-revisor` | Trigger: contra-revisor, reviewer feedback, MR observations. Verify review findings and apply only necessary, safe corrections. | user | `/Users/eclass/.codex/skills/contra-revisor/SKILL.md` |
+| `e2e-playwright-testing` | End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, form submission testing, or user flow testing. Triggers on "playwright", "e2e test", "browser test", "end-to-end", "form flow testing", or test files in tests/e2e/. | user | `/Users/eclass/.codex/skills/e2e-playwright-testing/SKILL.md` |
+| `fill-mr-template` | Completa plantillas de Merge Request o Pull Request en Markdown usando los cambios actuales del repositorio. Usar cuando el usuario pida redactar, crear o completar un MR/PR, especialmente si comparte una plantilla específica que debe respetarse. | user | `/Users/eclass/.codex/skills/fill-mr-template/SKILL.md` |
+| `find-skills` | Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill. | user | `/Users/eclass/.agents/skills/find-skills/SKILL.md` |
+| `generate-commit-text` | Generate only the commit message text after reviewing the current git changes and the repository's recent commit style. Use when the user asks things like "generame el commit", "dame el mensaje del commit", "redacta el commit", or needs a Conventional Commit style message without executing `git commit`. | user | `/Users/eclass/.codex/skills/generate-commit-text/SKILL.md` |
+| `gentle-ai-bench` | Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution. | user | `/Users/eclass/.agents/skills/gentle-ai-bench/SKILL.md` |
+| `go-testing` | Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns. | user | `/Users/eclass/.agents/skills/go-testing/SKILL.md` |
+| `issue-creation` | Create and triage GitHub issues from repository evidence. Trigger: issue creation, bug reports, feature requests, or issue approval. | user | `/Users/eclass/.agents/skills/issue-creation/SKILL.md` |
+| `jest` | Jest best practices, patterns, and API guidance for JavaScript/TypeScript testing. Covers mock design, async testing, matchers, timer mocks, snapshots, module mocking, configuration, and CI optimization. Baseline: jest ^30.0.0. Triggers on: jest imports, describe, it, test, expect, jest.fn, jest.mock, jest.spyOn, mentions of "jest", "unit test", "test suite", or "mock". | user | `/Users/eclass/.codex/skills/jest/SKILL.md` |
+| `jira-comment-format` | Redacta comentarios de Jira en español para documentar bugs, fixes, comportamientos esperados, hallazgos técnicos, validaciones o seguimiento de tickets. Usar cuando el usuario pida "formato comentario Jira", "comentario de Jira", "déjalo para Jira", "describir bug para Jira" o quiera convertir contexto técnico en un comentario claro para un ticket. | user | `/Users/eclass/.codex/skills/jira-comment-format/SKILL.md` |
+| `judgment-day` | Trigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds. | user | `/Users/eclass/.agents/skills/judgment-day/SKILL.md` |
+| `manhwa-offline` | Trigger: manhwa URL, manga URL, descargar capítulos, ZIP por capítulos, offline comics. Download ordered images into one ZIP per chapter. | user | `/Users/eclass/.codex/skills/manhwa-offline/SKILL.md` |
+| `pokeshort-solver` | Resuelve cadenas compactas de PokeShort cuando el usuario pega JSON con formato {"p":[...],"c":[...]} o pide ordenar Pokémon según condiciones como Gen>, Gen=, Supera>, Supera=, Altura, Peso, Dex, etc. Use when Codex receives compact PokeShort data from a mobile bookmarklet and must return the correct Pokémon order. | user | `/Users/eclass/.codex/skills/pokeshort-solver/SKILL.md` |
+| `rdd-defect-workflow` | Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work. | user | `/Users/eclass/.agents/skills/rdd-defect-workflow/SKILL.md` |
+| `requerimiento` | Guide software requirements with a safe, scalable workflow. Use when the user invokes $requerimiento or says a task is feat, feature, fix, bugfix, refactor, hotfix, review follow-up, or asks for a plan before changing code; helps Codex classify the work, define scope, identify break risks, implement narrowly, validate, and document the change. | user | `/Users/eclass/.codex/skills/requerimiento/SKILL.md` |
+| `revision-doctor` | Run react-doctor when the user asks for "revision doctor", a React doctor review, or a React health check in the current workspace. Execute the tool, summarize findings, and recommend concrete fixes. | user | `/Users/eclass/.codex/skills/revision-doctor/SKILL.md` |
+| `revision-final-front` | Trigger: frontend final review, frontend MR review, revisión final frontend. Review frontend readiness; exclude ordinary edits and implementation requests. | user | `/Users/eclass/.codex/skills/revision-final-front/SKILL.md` |
+| `skill-creator` | Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter. | user | `/Users/eclass/.agents/skills/skill-creator/SKILL.md` |
+| `skill-improver` | Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills. | user | `/Users/eclass/.agents/skills/skill-improver/SKILL.md` |
+| `systemic-issue-triage` | Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it. | user | `/Users/eclass/.agents/skills/systemic-issue-triage/SKILL.md` |
+| `translation-keys-sync` | Add or update translation keys in repositories that store language catalogs in files like src/spa/*.ts, src/eng/*.ts, src/por/*.ts and matching tests. Use when the user provides new translation rows or asks Codex to add keys to the translation project, especially when Portuguese must remain identical to Spanish instead of being translated. | user | `/Users/eclass/.codex/skills/translation-keys-sync/SKILL.md` |
+| `vercel-react-best-practices` | React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements. | user | `/Users/eclass/.codex/skills/react-best-practices/SKILL.md` |
+| `web-accessibility` | Routing-first skill for web accessibility remediation and verification. Use when the main job is classifying which accessibility surface is failing — semantics, keyboard/focus, labels/announcements, visual perception/reflow, media alternatives, or routed-app navigation feedback — and turning vague audit, WCAG, axe/Lighthouse, or "make this accessible" requests into one concrete remediation packet. Broad UI critique for hierarchy, polish, and launch readiness belongs here too. Route component API architecture and system governance to `design-system`, and responsive layout strategy to `responsive-design`. | user | `/Users/eclass/.codex/skills/web-accessibility/SKILL.md` |
+| `work-unit-commits` | Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code. | user | `/Users/eclass/.agents/skills/work-unit-commits/SKILL.md` |
+
+## Loading protocol
+
+1. Match task context and target files against the `Trigger / description` column.
+2. Pass only the matching `Path` values to the subagent under `## Skills to load before work`.
+3. Instruct the subagent to read those exact `SKILL.md` files before reading, writing, reviewing, testing, or creating artifacts.
+4. If no matching skill exists, proceed without project skill injection and report `skill_resolution: none`.

.github/workflows/nodejs.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node: [14.21.3]
+        node: [24.22.0]
     steps:
       - uses: actions/checkout@v4
         with:
@@ -32,11 +32,8 @@ jobs:
       - name: Add Known Hosts
         run: ssh-keyscan gitlab.com >> ~/.ssh/known_hosts
 
-      - name: Regenerate package-lock.json
-        run: npm i
-
-      - name: Clean node_modules after regenerate
-        run: rm -rf node_modules
+      - name: Pin npm version
+        run: npm install --global npm@11.13.0
 
       - name: Clean install on CI
         run: npm ci
@@ -54,6 +51,8 @@ jobs:
     permissions:
       contents: write
       issues: write
+      pull-requests: write
+      id-token: write
 
     steps:
       - uses: actions/checkout@v4
@@ -71,8 +70,7 @@ jobs:
 
       - uses: actions/setup-node@v4
         with:
-          node-version: 14.21.3
-          cache: 'npm'
+          node-version: 24.22.0
 
       - uses: webfactory/ssh-agent@v0.7.0
         with:
@@ -81,11 +79,8 @@ jobs:
       - name: Add Known Hosts
         run: ssh-keyscan gitlab.com >> ~/.ssh/known_hosts
 
-      - name: Regenerate package-lock.json
-        run: npm i
-
-      - name: Clean node_modules after regenerate
-        run: rm -rf node_modules
+      - name: Pin npm version
+        run: npm install --global npm@11.13.0
 
       - name: Clean install on CI
         run: npm ci
@@ -94,10 +89,9 @@ jobs:
         run: npm run build
 
       - name: Release version
-        run: npx semantic-release@18
+        run: npm exec --no -- semantic-release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
 
   build-pages:
     name: Build to GitHub Pages
@@ -113,7 +107,7 @@ jobs:
 
       - uses: actions/setup-node@v4
         with:
-          node-version: 14.21.3
+          node-version: 24.22.0
           cache: 'npm'
 
       - uses: webfactory/ssh-agent@v0.7.0
@@ -123,11 +117,8 @@ jobs:
       - name: Add Known Hosts
         run: ssh-keyscan gitlab.com >> ~/.ssh/known_hosts
 
-      - name: Regenerate package-lock.json
-        run: npm i
-
-      - name: Clean node_modules after regenerate
-        run: rm -rf node_modules
+      - name: Pin npm version
+        run: npm install --global npm@11.13.0
 
       - name: Clean install on CI
         run: npm ci

.nvmrc

@@ -1 +1 @@
-14.21.3
+24.22.0

README.md

@@ -8,6 +8,8 @@ La fuente de donde se basan los componentes se encuentran en este [**Sistema de
 
 ## Scripts
 
+El desarrollo y CI usan Node.js `24.22.0` y npm `11.13.0` (npm `11.5.1` o superior es requisito para Trusted Publishing de npm). Instale las dependencias bloqueadas con `npm ci`; CI no regenera el lockfile.
+
 Los componentes están al 100% en escritas en archivos `typescript`.
 
 Además deben ser testeadas en donde el enfoque del `testing` es asegurarse de que se muestre todo lo que se promete
@@ -31,6 +33,27 @@ Levanta el entorno de `storybook`
 
 Ejecuta los test con `jest`
 
+## Publicación en npm con Trusted Publishing
+
+El workflow de release usa semantic-release en GitHub Actions y autentica las publicaciones de npm mediante OIDC. Antes de fusionar este cambio o ejecutar una publicación, una persona administradora debe configurar en npm el paquete `@eclass/ui-kit`, en **Settings → Trusted Publisher → GitHub Actions**:
+
+| Campo | Valor |
+| --- | --- |
+| Organization or user | `eclass` |
+| Repository | `ui-kit` |
+| Workflow filename | `nodejs.yml` (solo el nombre del archivo) |
+| Environment name | Vacío |
+
+Complete la primera publicación exitosa dentro de los dos días posteriores a crear el trusted publisher; si vence, deberá eliminarlo y volver a configurarlo.
+
+En **Allowed actions**, habilite la publicación directa con `npm publish`: semantic-release publica directamente y no usa `npm stage publish`. Las configuraciones nuevas permiten por defecto solo la publicación por etapas; habilite la administración de `dist-tags` únicamente si se agrega un flujo de canales que la necesite.
+
+El job de release solicita OIDC con `id-token: write`; npm obtiene automáticamente credenciales de corta duración para esa ejecución. No se configura ni se usa `NPM_TOKEN` como alternativa: si el trusted publisher no está configurado o no coincide, la publicación falla. Revoque o elimine el antiguo secreto `NPM_TOKEN` solo después de confirmar una publicación exitosa con OIDC. `GITHUB_TOKEN` sigue disponible para las operaciones de GitHub de semantic-release. La configuración SSH de GitLab, usada por separado para dependencias privadas, no cambia.
+
+semantic-release determina si corresponde una nueva versión según los commits; este cambio no publica automáticamente en cada commit. npm genera provenance automáticamente cuando la publicación cumple sus requisitos de elegibilidad.
+
+Referencias oficiales: [Trusted Publishing de npm](https://docs.npmjs.com/trusted-publishers/) y [GitHub Actions en semantic-release](https://semantic-release.org/recipes/ci-configurations/github-actions/).
+
 ## Instalación
 
 Se debe instalar este repositorio más unas dependencias