chore: alinea P0 mínimo (fork de models.dev)

[Alexendros]

Este repositorio es un fork de anomalyco/models.dev. El canon Iniciativas-Alexendros/repo-standard devolvió 404; se aplicó el contrato P0 del prompt usando Alexendros/neubat como referencia de formato, sin clonar a ciegas.

Perfil: fork. Rama por defecto: dev. Se aplica solo P0 mínimo sensato. No se reescribe el producto, el frontend, el esquema ni el dataset (models/, providers/, models.json). LICENSE MIT del upstream no se toca.

Inventario (conservado)

• Catálogo TOML (models/, providers/, labs/), generador, AGENTS.md, sync.md.
• Workflows de producto del upstream (Validate Models, Deploy, Sync Model Catalogs, Publish SDK, fixers/reviewers). Siguen gated a anomalyco/models.dev y no se activan en este fork.
• package.json / Bun: bun validate, bun test.

Qué se ha hecho (P0)

• README: meta-sección Propósito + aviso de fork; se conserva la guía de API/TOML/esquema.
• LICENSE intacta.
• Nuevos: SECURITY.md, CONTRIBUTING.md, CHANGELOG.md.
• .github/CODEOWNERS (* @Alexendros).
• Plantillas mínimas de issue (bug/feature + config.yml) y PR.
• CI nuevo .github/workflows/p0.yml (solo Alexendros/models.dev):
  • quality: bun validate (verificado en local, OK).
  • test: subconjunto unitario (schema, helpers, cliente SDK; 44 tests, OK). El bun test completo del workspace falla hoy en el dev del upstream (enlaces de pesos en labs open-weight, snapshot generado del SDK); no se reescribe el dataset para ponerlo verde.
  • smoke: ficheros P0 + models.json parseable.
• Meta-sección Propósito en todos los docs contractuales nuevos o tocados (excepto LICENSE y CHANGELOG).

CI: por qué no se tocan los workflows del upstream

Activar Deploy, Sync Model Catalogs o Publish SDK en este fork rompería el flujo (secretos de Cloudflare/npm, PRs de sync horarios, publicación del SDK). Se deja el gating existente y se añade un CI P0 ligero propio.

Checklist de alineación

• Inventario hecho; stack, catálogo y herramientas conservados
• Es fork; documentado en README, CONTRIBUTING, CHANGELOG y este PR
• P0 raíz: README, LICENSE (no pisada), SECURITY, CONTRIBUTING, CHANGELOG
• .github/CODEOWNERS mínimo * @Alexendros; ISSUE + PR templates
• CI quality / test / smoke en este fork; deploy/sync/publish omitidos a propósito
• Meta-sección presente tras cada H1 contractual tocado/nuevo
• Sin cambios a branch protection, org settings ni secretos
• Sin reescritura del dataset ni del producto

  

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 9397b0db-81b7-4533-a5b0-84f630cae2f3

📥 Commits

Reviewing files that changed from the base of the PR and between 98b7e9a and 59aaf3b.

📒 Files selected for processing (10)

• .github/CODEOWNERS
• .github/ISSUE_TEMPLATE/bug.md
• .github/ISSUE_TEMPLATE/config.yml
• .github/ISSUE_TEMPLATE/feature.md
• .github/PULL_REQUEST_TEMPLATE.md
• .github/workflows/p0.yml
• CHANGELOG.md
• CONTRIBUTING.md
• README.md
• SECURITY.md

 ______________________________________________________________________________________________________________________________________________________________________________________________________
< Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. - Brian Kernighan >
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_650bf4d0-0b26-4fc9-b7a6-99d9d4e8b0e3)