docs: capa release (RFC-014) + reapuntar composites al artefacto - #20
Merged
Conversation
Cierra el warning de critias --full: la capa release aplicaba (version.rb + CHANGELOG.md + .github/workflows/release.yml) pero no existía docs/release/ y los composites declaraban "presente" apuntando al workflow CI (código del pipeline, no artefacto RFC-014). - docs/release/release.md (RFC-014 híbrido arch-structure + arch-enrich): - §a estructural: versión 1.9.0 · changelog · build-trigger (tag v*) · anchor - patrón de trigger 1/4 (publish de gema a RubyGems) - §b enriquecido 4/4: deploy · rollback (gem yank) · ambientes · dueño @gedera - AGENTS.md / README.md / skill/SKILL.md: índice de release reapunta de .github/workflows/release.yml -> docs/release/release.md Verificado con critias --full: 0 errores, 0 warnings tras el fix. Decisión A validada con multi-vendor-feedback (opencode + agy). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contexto
Cierra el único warning activo de
critias --full(gema DB-less): la capa release aplica (triggerslib/cobro_digital/version.rb,CHANGELOG.md,.github/workflows/release.yml) pero faltaba el artefactodocs/release/release.md— los 3 composites declaraban release "presente" apuntando al workflow CI (código del pipeline), no al artefacto RFC-014. Inconsistencia mapa↔disco.Resuelto por opción A (generar el artefacto), validada con
multi-vendor-feedback(opencode + agy).Cambios
docs/release/release.md(nuevo) — RFC-014 híbridoarch-structure+arch-enrich:1.9.0· changelog (Keep a Changelog) · build-trigger (push tagv*→gem build/gem push, runner Ruby 2.7,GEM_HOST_API_KEY←RUBYGEMS_API_KEY) · anchor (documentation_uriversion-locked)gem yank, preferido publicar versión nueva) · ambientes (registry, no runtime propio) · dueño (@gedera)AGENTS.md/README.md/skill/SKILL.md— índice de release reapunta de.github/workflows/release.yml→docs/release/release.mdVerificación
critias --fullpost-fix: 0 errores, 0 warnings. Contenido anclado a fuentes reales (sin alucinación); SEC-COMPOSE limpio; SEED-001/002 honestos (§b 4/4 consistente meta↔cuerpo↔fronteras).🤖 Generated with Claude Code