create-quiver 0.15.3 → 0.16.0

package/docs/GITFLOW_PR_GUIDE.md

@@ -1,21 +1,78 @@
 # Git and PR Guide
 
-**Version:** 2.0
-**Last updated:** 2026-05-26
+**Version:** 2.1
+**Last updated:** 2026-06-02
 
 ## Purpose
 
-This guide explains how to open and review spec PRs without breaking the canonical workflow.
+This guide explains how to open, review, and merge slice PRs without breaking the canonical workflow.
 
 ## Core Rule
 
-- One slice = one commit
-- One spec = one PR
-- One spec should be worked from one dedicated worktree/branch.
+- One slice = one commit.
+- One slice = one PR by default.
+- One spec can produce multiple PRs. Grouped PRs are exceptions and must meet the grouped PR policy below.
+- One active PR should be worked from one dedicated worktree/branch.
 - Slice numbers reset per spec. `slice-01` is the first slice in each spec.
-- Do not commit directly to `develop`
-- Open and merge the documentation PR before the first slice starts execution
-- Do not open the spec PR before the documentation PR is merged
+- Do not commit directly to `develop` or any protected base branch.
+- Open and merge the documentation PR that establishes `slice-00` before runtime slices start execution.
+- Do not open runtime slice PRs before the documentation foundation is merged.
+
+## PR Sizing Policy
+
+### Individual PR Required
+
+Open an individual PR for any slice that includes:
+
+- Functional code.
+- UI/UX changes.
+- Supabase, Edge Functions, auth, or storage changes.
+- Preview or deployment behavior.
+- Performance or code-splitting changes.
+- Refactors.
+- Tests or CI changes that affect gates.
+
+### Grouped PR Exception
+
+A grouped PR is allowed only when all conditions are true:
+
+- It contains at most 2-3 slices.
+- Every included slice is docs-only, research-only, or low-risk mechanical cleanup.
+- It does not change behavior.
+- It does not mix docs with UI, backend, refactor, or performance work.
+- Each slice keeps separate evidence.
+- The whole PR can be reverted without leaving partial state.
+
+If any condition fails, split the work into individual slice PRs.
+
+## Merge Policy
+
+- Human merge is the default.
+- AI agents may create PRs, fix CI, monitor checks, and mark PRs as ready.
+- Assisted auto-merge is allowed only when explicitly authorized by a human for that PR or for a documented category.
+
+## Assisted Auto-Merge Policy
+
+Assisted auto-merge is allowed only when all conditions are true:
+
+- The PR is docs-only or chore-only.
+- Risk is low.
+- There are no runtime changes.
+- There are no production configuration changes.
+- Checks are green.
+- There are no pending comments.
+
+Assisted auto-merge is prohibited for:
+
+- UI.
+- Supabase.
+- Edge Functions.
+- Auth.
+- Storage.
+- Preview.
+- Performance.
+- Refactors.
+- Changes with doubtful rollback.
 
 ## AI PR Preflight
 
@@ -36,10 +93,11 @@ Use the SSH host alias from your Git remote separately from the key path. Quiver
 
 ## Required PR Headings
 
-All spec PR notes must use:
+All slice PR notes must use:
 
 - `## Title`
 - `## Summary`
+- `## PR Policy`
 - `## Scope`
 - `## Files`
 - `## How to Test (DETAILED - REQUIRED)`
@@ -66,5 +124,9 @@ Inside `How to Test`, use:
 ## Anti-Patterns
 
 - Pushing directly to `develop`
-- Reusing the same branch for multiple specs
+- Reusing the same branch for unrelated PRs
+- Grouping behavior-changing slices
+- Mixing docs-only slices with UI, backend, refactor, or performance work
+- Auto-merging without explicit human authorization
+- Auto-merging prohibited categories
 - Writing PR bodies outside `pr.md`

package/docs/GITFLOW_PR_GUIDE.md.es.template

@@ -0,0 +1,84 @@
+# Guia Git y PR
+
+## Reglas principales
+
+- Un slice equivale a un commit.
+- Un slice equivale a un PR por defecto.
+- Un spec puede generar multiples PRs.
+- Los PRs agrupados son excepciones y deben cumplir la politica de agrupacion.
+- No mezclar PRs no relacionados en la misma branch.
+- No abrir PR sin evidencia de validacion.
+
+## Politica de tamano de PR
+
+### PR individual obligatorio
+
+Abri un PR individual para cualquier slice que incluya:
+
+- codigo funcional;
+- UI/UX;
+- Supabase, Edge Functions, auth o storage;
+- preview o comportamiento de deploy;
+- performance o code-splitting;
+- refactors;
+- tests o CI que afecten gates.
+
+### PR agrupado permitido
+
+Un PR agrupado esta permitido solo si:
+
+- incluye como maximo 2-3 slices;
+- todos los slices son docs-only, research-only o limpieza mecanica de bajo riesgo;
+- no cambia comportamiento;
+- no mezcla docs con UI, backend, refactor o performance;
+- cada slice mantiene evidencia separada;
+- el PR completo puede revertirse sin dejar estado parcial.
+
+Si una condicion falla, separa el trabajo en PRs individuales por slice.
+
+## Politica de merge
+
+- El merge humano es el default.
+- Los agentes IA pueden crear PRs, corregir CI, monitorear checks y marcar PRs como listos.
+- El auto-merge asistido solo esta permitido con autorizacion humana explicita para ese PR o para una categoria documentada.
+
+## Politica de auto-merge asistido
+
+El auto-merge asistido esta permitido solo si:
+
+- el PR es docs-only o chore-only;
+- el riesgo es bajo;
+- no hay cambios runtime;
+- no hay cambios de configuracion productiva;
+- los checks estan verdes;
+- no hay comentarios pendientes.
+
+El auto-merge asistido esta prohibido para:
+
+- UI;
+- Supabase;
+- Edge Functions;
+- auth;
+- storage;
+- preview;
+- performance;
+- refactors;
+- cambios con rollback dudoso.
+
+## Preflight de PR
+
+```bash
+npx create-quiver ai pr --dry-run --ssh-host-alias <alias> --identity-file <key> --input <pr.md>
+```
+
+## Secciones requeridas del PR
+
+- `## Title`
+- `## Summary`
+- `## PR Policy`
+- `## Scope`
+- `## Files`
+- `## How to Test (DETAILED - REQUIRED)`
+- `## Evidence`
+- `## Rollback`
+- `## Risks / Notes`

package/docs/GITFLOW_PR_GUIDE.md.template

@@ -1,21 +1,78 @@
 # Git and PR Guide
 
-**Version:** 2.0
+**Version:** 2.1
 **Last updated:** {{FECHA}}
 
 ## Purpose
 
-This guide explains how to open and review spec PRs without breaking the canonical workflow.
+This guide explains how to open, review, and merge slice PRs without breaking the canonical workflow.
 
 ## Core Rule
 
-- One slice = one commit
-- One spec = one PR
-- One spec should be worked from one dedicated worktree/branch.
+- One slice = one commit.
+- One slice = one PR by default.
+- One spec can produce multiple PRs. Grouped PRs are exceptions and must meet the grouped PR policy below.
+- One active PR should be worked from one dedicated worktree/branch.
 - Slice numbers reset per spec. `slice-01` is the first slice in each spec.
-- Do not commit directly to `develop`
-- Open and merge the documentation PR before the first slice starts execution
-- Do not open the spec PR before the documentation PR is merged
+- Do not commit directly to `develop` or any protected base branch.
+- Open and merge the documentation PR that establishes `slice-00` before runtime slices start execution.
+- Do not open runtime slice PRs before the documentation foundation is merged.
+
+## PR Sizing Policy
+
+### Individual PR Required
+
+Open an individual PR for any slice that includes:
+
+- Functional code.
+- UI/UX changes.
+- Supabase, Edge Functions, auth, or storage changes.
+- Preview or deployment behavior.
+- Performance or code-splitting changes.
+- Refactors.
+- Tests or CI changes that affect gates.
+
+### Grouped PR Exception
+
+A grouped PR is allowed only when all conditions are true:
+
+- It contains at most 2-3 slices.
+- Every included slice is docs-only, research-only, or low-risk mechanical cleanup.
+- It does not change behavior.
+- It does not mix docs with UI, backend, refactor, or performance work.
+- Each slice keeps separate evidence.
+- The whole PR can be reverted without leaving partial state.
+
+If any condition fails, split the work into individual slice PRs.
+
+## Merge Policy
+
+- Human merge is the default.
+- AI agents may create PRs, fix CI, monitor checks, and mark PRs as ready.
+- Assisted auto-merge is allowed only when explicitly authorized by a human for that PR or for a documented category.
+
+## Assisted Auto-Merge Policy
+
+Assisted auto-merge is allowed only when all conditions are true:
+
+- The PR is docs-only or chore-only.
+- Risk is low.
+- There are no runtime changes.
+- There are no production configuration changes.
+- Checks are green.
+- There are no pending comments.
+
+Assisted auto-merge is prohibited for:
+
+- UI.
+- Supabase.
+- Edge Functions.
+- Auth.
+- Storage.
+- Preview.
+- Performance.
+- Refactors.
+- Changes with doubtful rollback.
 
 ## AI PR Preflight
 
@@ -36,10 +93,11 @@ Use the SSH host alias from your Git remote separately from the key path. Quiver
 
 ## Required PR Headings
 
-All spec PR notes must use:
+All slice PR notes must use:
 
 - `## Title`
 - `## Summary`
+- `## PR Policy`
 - `## Scope`
 - `## Files`
 - `## How to Test (DETAILED - REQUIRED)`
@@ -66,5 +124,9 @@ Inside `How to Test`, use:
 ## Anti-Patterns
 
 - Pushing directly to `develop`
-- Reusing the same branch for multiple specs
+- Reusing the same branch for unrelated PRs
+- Grouping behavior-changing slices
+- Mixing docs-only slices with UI, backend, refactor, or performance work
+- Auto-merging without explicit human authorization
+- Auto-merging prohibited categories
 - Writing PR bodies outside `pr.md`

package/docs/INDEX.md

@@ -1,6 +1,6 @@
 # Quiver Documentation Index
 
-**Last updated:** 2026-05-28
+**Last updated:** 2026-05-29
 
 Use this file as the first documentation map before planning, implementing, reviewing, or opening PRs in this repository. Prefer the smallest set of linked documents that fits the task.
 
@@ -10,6 +10,7 @@ Use this file as the first documentation map before planning, implementing, revi
 - **AI guide:** [`../README_FOR_AI.md`](../README_FOR_AI.md)
 - **CLI UX standards:** [`./CLI_UX_GUIDE.md`](./CLI_UX_GUIDE.md)
 - **Command reference:** [`./reference/commands.md`](./reference/commands.md)
+- **Slice JSON schema:** [`./reference/slice-schema.md`](./reference/slice-schema.md)
 - **Troubleshooting:** [`./TROUBLESHOOTING.md`](./TROUBLESHOOTING.md)
 - **Git and PR workflow:** [`./GITFLOW_PR_GUIDE.md`](./GITFLOW_PR_GUIDE.md)
 
@@ -39,6 +40,15 @@ Canonical specs live outside `docs/` in [`../specs/`](../specs/).
 
 Recent specs:
 
+- [`../specs/quiver-v45-ci-actions-node24-readiness/SPEC.md`](../specs/quiver-v45-ci-actions-node24-readiness/SPEC.md)
+- [`../specs/quiver-v44-provider-live-output-tui-lite/SPEC.md`](../specs/quiver-v44-provider-live-output-tui-lite/SPEC.md)
+- [`../specs/quiver-v43-cli-i18n-audit-release-readiness/SPEC.md`](../specs/quiver-v43-cli-i18n-audit-release-readiness/SPEC.md)
+- [`../specs/quiver-v42-cli-i18n-generated-docs/SPEC.md`](../specs/quiver-v42-cli-i18n-generated-docs/SPEC.md)
+- [`../specs/quiver-v41-cli-i18n-ai-lifecycle/SPEC.md`](../specs/quiver-v41-cli-i18n-ai-lifecycle/SPEC.md)
+- [`../specs/quiver-v40-cli-i18n-spec-slice-workflows/SPEC.md`](../specs/quiver-v40-cli-i18n-spec-slice-workflows/SPEC.md)
+- [`../specs/quiver-v39-cli-i18n-setup-onboarding/SPEC.md`](../specs/quiver-v39-cli-i18n-setup-onboarding/SPEC.md)
+- [`../specs/quiver-v38-cli-i18n-read-only-commands/SPEC.md`](../specs/quiver-v38-cli-i18n-read-only-commands/SPEC.md)
+- [`../specs/quiver-v37-cli-i18n-foundation/SPEC.md`](../specs/quiver-v37-cli-i18n-foundation/SPEC.md)
 - [`../specs/quiver-v36-ai-run-watch-portable/SPEC.md`](../specs/quiver-v36-ai-run-watch-portable/SPEC.md)
 - [`../specs/quiver-v35-compact-dashboard-version-ux/SPEC.md`](../specs/quiver-v35-compact-dashboard-version-ux/SPEC.md)
 - [`../specs/quiver-v34-cli-dashboard-status/SPEC.md`](../specs/quiver-v34-cli-dashboard-status/SPEC.md)

package/docs/INDEX.md.es.template

@@ -0,0 +1,36 @@
+# Indice de documentacion de {{PROJECT_NAME}}
+
+**Ultima actualizacion:** {{FECHA}}
+
+## Empezar aca
+
+- **Contexto** - `./CONTEXTO.md`
+- **Contexto para IA** - `./AI_CONTEXT.md`
+- **Decisiones** - `./DECISIONS.md`
+- **Prompt de onboarding IA** - `./AI_ONBOARDING_PROMPT.md`
+- **Workflow** - `./WORKFLOW.md`
+- **Comandos** - `./COMMANDS.md`
+- **Matriz de soporte** - `./SUPPORT_MATRIX.md`
+- **Troubleshooting** - `./TROUBLESHOOTING.md`
+
+## Configuracion de IA
+
+- **Principios** - `./ai/PRINCIPLES.md`
+- **Reglas** - `./ai/RULES.yaml`
+- **Lecciones** - `./ai/LESSONS.md`
+
+## Mapa del proyecto
+
+`docs/PROJECT_MAP.md` se crea con:
+
+```bash
+npx create-quiver analyze
+```
+
+Usalo despues del analisis para stack, package manager, comandos y pistas de archivos.
+
+## Docs opcionales y perfiles
+
+- `npx create-quiver init --full` agrega notas multi-agente, ejemplos y assets iniciales de spec.
+- Los specs y slices reales se crean despues de aprobar criterios y plan tecnico con `npx create-quiver spec create`.
+- Los wrappers Bash heredados solo se agregan con `--full` o `--legacy-scripts`.

package/docs/QUICK.md.template

@@ -15,7 +15,8 @@ Use `docs/PROJECT_MAP.md` for the package manager, project stack, test commands,
 ## Hard Rules
 
 - One slice = one commit.
-- One spec = one PR.
+- One slice = one PR by default.
+- Grouped PRs are exceptions and must follow `docs/GITFLOW_PR_GUIDE.md`.
 - Read `./STANDARD.md` for workflow details.
 - Read `./DEEP.md` for history and context.
 - Do not edit files outside the active slice.

package/docs/STANDARD.md.template

@@ -19,7 +19,8 @@ This is the default context pack for everyday AI work.
 - Use maps, metadata, and diffs before opening full source files.
 - Keep scope inside the active slice.
 - Make one commit per slice.
-- Open one PR per spec.
+- Open one PR per slice by default.
+- Group slices in one PR only when `docs/GITFLOW_PR_GUIDE.md` allows it.
 - Record durable decisions in `docs/DECISIONS.md`.
 - Treat `docs/PROJECT_MAP.md` as the single source of truth for stack, package manager, and command references.
 

package/docs/STATUS.md.es.template

@@ -0,0 +1,28 @@
+# Estado de {{PROJECT_NAME}}
+
+Este archivo registra progreso, bloqueos y slice actual. Stack y comandos viven en `docs/PROJECT_MAP.md`.
+
+## Estado general
+
+- Progreso: {{X}}% completo
+- Fase actual: {{FASE}}
+- Proximo hito: [Descripcion]
+
+## Resumen de slices
+
+Todavia no hay slices de implementacion. Crea specs y slices solo despues de aprobar criterios de aceptacion y plan tecnico.
+
+| Slice | Titulo | Estado | Progreso | Spec |
+|---|---|---|---|---|
+| slice-00 | Fundacion documental | Pendiente | 0% | `specs/<spec>/slices/slice-00-.../slice.json` |
+
+## Bloqueos
+
+| Bloqueo | Impacto | Mitigacion |
+|---|---|---|
+| - | - | - |
+
+## Notas
+
+- Actualiza este archivo al cerrar cada slice.
+- Registra incertidumbre con `TODO`, `Assumption` o `Pending confirmation`.

package/docs/SUPPORT_MATRIX.md.es.template

@@ -0,0 +1,22 @@
+# Matriz de soporte
+
+**Proyecto:** {{PROJECT_NAME}}
+**Ultima actualizacion:** {{FECHA}}
+
+## Entornos soportados
+
+| Area | Soportado | Notas |
+|---|---|---|
+| Sistemas operativos | macOS, Linux y Windows | Runtime principal: Node CLI y scripts `quiver:*`. |
+| Shells | Terminal, shells compatibles con bash, PowerShell y CMD | Bash es compatibilidad heredada, no dependencia obligatoria. |
+| Git | Git 2.40+ | Debe soportar worktrees y refs estandar. |
+| Node.js | Node 22.x LTS | Requerido en todos los OS soportados. |
+| Branch base | `develop` o `main` | Preferir branch local; `origin` es opcional. |
+| Estado del worktree | Limpio | La ejecucion de slices espera no mezclar cambios. |
+
+## Reglas cross-platform
+
+- Usar APIs Node para paths y filesystem.
+- Mantener `--json` como contrato primario de automatizacion.
+- Respetar `NO_COLOR`, CI y terminales sin TTY.
+- No concatenar prompts largos en comandos shell.

package/docs/TESTING_GUIDE_FOR_AI.md.es.template

@@ -0,0 +1,19 @@
+# Guia de testing para IA
+
+**Proyecto:** {{PROJECT_NAME}}
+**Ultima actualizacion:** {{FECHA}}
+
+## Reglas
+
+- Ejecuta primero tests focalizados del slice.
+- Ejecuta validacion amplia solo cuando el cambio toque superficie compartida.
+- No inventes comandos; usa los documentados en `docs/PROJECT_MAP.md` o `package.json`.
+- Registra evidencia en el spec o slice correspondiente.
+
+## Comandos sugeridos
+
+```bash
+npm test
+npx create-quiver spec validate specs/<spec> --strict
+git diff --check
+```

package/docs/TROUBLESHOOTING.md.es.template

@@ -0,0 +1,35 @@
+# Troubleshooting
+
+**Proyecto:** {{PROJECT_NAME}}
+**Ultima actualizacion:** {{FECHA}}
+
+Usa esta guia cuando falle bootstrap, validacion o ejecucion de Quiver.
+
+## Quiver no aparece en node_modules
+
+### Sintoma
+
+- `npx --yes create-quiver@latest ...` funciona.
+- `node_modules/create-quiver` no existe.
+- `package.json` no declara `create-quiver`.
+
+### Recuperacion
+
+1. Esto es esperado cuando se usa `npx`.
+2. Usa `npx --yes create-quiver@latest` para ejecutar la version publicada mas reciente.
+3. Instala localmente solo si el equipo quiere un workflow pineado:
+
+```bash
+npm install --save-dev create-quiver
+```
+
+## Falta branch base
+
+### Sintoma
+
+- `start-slice` no encuentra `develop` o `main`.
+
+### Recuperacion
+
+1. Crea o fetchea la branch base.
+2. Vuelve a ejecutar la validacion del slice.

package/docs/WORKFLOW.md.es.template

@@ -0,0 +1,31 @@
+# Workflow
+
+**Fecha:** {{FECHA}}
+
+Este documento define el workflow canonico de implementacion del proyecto.
+
+## Reglas centrales
+
+- No implementar sin slice.
+- Un slice equivale a un commit.
+- Un slice equivale a un PR por defecto.
+- Un spec puede generar multiples PRs.
+- Los PRs agrupados son excepciones y deben cumplir `docs/GITFLOW_PR_GUIDE.md`.
+- El spec define el plan; el slice define la ejecucion.
+- Ningun slice debe ejecutarse hasta estar listo.
+- La salida JSON y los artefactos machine-readable no se traducen.
+
+## Planificacion
+
+1. Ejecuta `npx create-quiver flow` si no sabes el siguiente paso seguro.
+2. Redacta criterios de aceptacion.
+3. Redacta y revisa el plan tecnico.
+4. Crea el spec con `npx create-quiver spec create`.
+5. Ejecuta slices de a uno, manteniendo scope y evidencia.
+
+## Validacion
+
+```bash
+npx create-quiver spec validate specs/<spec> --strict
+git diff --check
+```

package/docs/WORKFLOW.md.template

@@ -8,7 +8,9 @@ This document is the canonical implementation workflow for the project.
 
 - Do not implement without a slice.
 - One slice maps to one commit.
-- One spec maps to one PR.
+- One slice maps to one PR by default.
+- One spec can produce multiple PRs.
+- Grouped PRs are exceptions and must follow `docs/GITFLOW_PR_GUIDE.md`.
 - Slice numbering is local to each spec. Every spec starts with mandatory `slice-00` as the documentary foundation; `slice-01` is the first implementation slice.
 - The spec defines the plan; the slice defines the execution.
 - No slice should enter execution until it is `ready`.
@@ -63,9 +65,9 @@ Use maps, metadata, diffs, and summaries first. Open full files only when the sm
    - `ai execute-slice` updates `CLOSURE_BRIEF.md`, `EVIDENCE_REPORT.md`, `COMMAND_LOG.md`, `STATUS.md`, and `slice.json` only after the provider changes in-scope files and validation passes.
 9. Validate with `npx create-quiver check-slice <slice.json>` or `npm run quiver:check-slice -- <slice.json>`.
 10. Write evidence. Prefer `npx create-quiver evidence run -- <command>` when you need a compact local Markdown record of validation output.
-11. Repeat for the next slice until the spec is complete.
-12. Open one PR for the spec. Use `npx create-quiver ai pr --dry-run --input specs/<spec-slug>/pr.md --ssh-host-alias <alias> ...` first, then add `--create` only after review. Quiver blocks PR creation while slices in that spec remain open.
-13. After the PR is merged and the spec worktree is clean, close it with `npx create-quiver spec close specs/<spec-slug>`.
+11. Open one PR for the completed slice by default. Use `npx create-quiver ai pr --dry-run --input specs/<spec-slug>/pr.md --ssh-host-alias <alias> ...` first when the generated spec PR body is the intended body, then add `--create` only after review. For slice-level PR bodies, keep the PR aligned with the slice `pr.md` and validate the slice evidence before creating the PR.
+12. Repeat for the next slice until the spec is complete.
+13. After the final PR for the spec is merged and the spec worktree is clean, close it with `npx create-quiver spec close specs/<spec-slug>`.
 
 ## Support Contract
 

package/docs/ai/ACTIVE_SLICE.md

@@ -0,0 +1,61 @@
+---
+purpose: "Active slice execution brief"
+applies_when: "implementation"
+token_cost: 409
+last_updated: "2026-06-09"
+supersedes: null
+---
+
+# Active Slice
+
+## Slice ID
+
+slice-01-json-schema-for-slice-json
+
+## Title
+
+JSON Schema for slice.json
+
+## Objective
+
+Publish a slice.json JSON Schema aligned with runtime behavior.
+
+## allowed_files
+- docs/INDEX.md
+- docs/reference/slice-schema.md
+- docs/schema/**
+- package.json
+- package-lock.json
+- scripts/ci/check-slice-schema.js
+- scripts/package-quiver.sh
+- tests/fixtures/slice-schema/invalid/empty-files.json
+- tests/fixtures/slice-schema/invalid/missing-git-field.json
+- tests/fixtures/slice-schema/invalid/missing-slice-id.json
+- tests/fixtures/slice-schema/invalid/unsafe-allowed-write-path.json
+- tests/schema/slice-schema.test.js
+- specs/quiver-v52-schema-docs-release-hygiene/SPEC.md
+- specs/quiver-v52-schema-docs-release-hygiene/STATUS.md
+- specs/quiver-v52-schema-docs-release-hygiene/EVIDENCE_REPORT.md
+- specs/quiver-v52-schema-docs-release-hygiene/slices/slice-01-json-schema-for-slice-json/CLOSURE_BRIEF.md
+- specs/quiver-v52-schema-docs-release-hygiene/slices/slice-01-json-schema-for-slice-json/slice.json
+- specs/quiver-v52-schema-docs-release-hygiene/slices/slice-01-json-schema-for-slice-json/pr.md
+
+## Validation Commands
+- npm ci
+- npm run schema:slice:check
+- node --test tests/schema/slice-schema.test.js
+- npm run docs:check
+- node --test
+- npm run package:quiver
+- git diff --check
+
+## Definition of Done
+- Schema is valid JSON Schema Draft-07 or higher.
+- Schema validates existing valid slice fixtures.
+- Schema rejects representative invalid fixtures.
+- Docs reference the schema.
+- Package smoke includes the schema if it is public.
+
+## Prohibition
+
+Do not edit any file outside allowed_files.

package/docs/ai/LESSONS.md.es.template

@@ -0,0 +1,24 @@
+# Lecciones aprendidas
+
+**Ultima actualizacion:** {{FECHA}}
+
+## [Titulo de la leccion]
+
+### Contexto
+
+[Que paso]
+
+### Que funciono
+
+- [Item 1]
+- [Item 2]
+
+### Que no funciono
+
+- [Item 1]
+- [Item 2]
+
+### Proxima vez
+
+- [Regla 1]
+- [Regla 2]