Mover themes e integraciones Cortex al repo cortex OSS #31

Activity

1. barbatdev commented on Jul 2, 2026

   

   barbatdev

   on Jul 2, 2026

   OwnerAuthor

   More actions

   Aclaración: cortex, cortex-dotfiles y cortex-dots siguen siendo repos independientes. Esta migración ordena ownership de integraciones UX de Cortex y evita que cortex dependa de dotfiles externos; no vuelve a cortex-dotfiles un downstream obligatorio de cortex. cortex-dotfiles puede conservar configs/ejemplos propios, pero no debería ser la source of truth de artefactos product-owned de Cortex. Orden seguro: primero upstream en cortex; después ajustar duplicados acá si hace falta.
2. barbatdev commented on Jul 3, 2026

   

   barbatdev

   on Jul 3, 2026

   OwnerAuthor

   More actions

   Sugerencia de precisión: agregar explícitamente que esto no implica dependencia obligatoria de cortex para usar cortex-dotfiles. Redacción propuesta: “Esto no implica dependencia obligatoria de cortex para usar cortex-dotfiles; solo define que los artefactos product-owned de Cortex no deben tener aquí su source of truth.”
3. barbatdev commented on Jul 3, 2026

   

   barbatdev

   on Jul 3, 2026

   OwnerAuthor

   More actions

   Progreso seguro realizado: PR #32 dejó documentado en README el boundary con Cortex sin cambiar comportamiento de instalación. Esto cubre la parte docs-only que podía hacerse en cortex-dotfiles ahora.

   Siguiente paso no debería hacerse acá todavía: no borrar ni mover themes/statusline/agent-state desde cortex-dotfiles hasta que cortex #1038 incorpore reemplazos validados como artefactos propios del producto.
4. barbatdev commented on Jul 17, 2026

   

   barbatdev

   on Jul 17, 2026

   OwnerAuthor

   More actions

   Checkpoint: #31 cubre la migración y source of truth de artefactos product-owned, pero no la coexistencia OSS con configuraciones preexistentes ni el ownership granular del instalador. Ese alcance queda separado en #41.
5. barbatdev commented on Oct 17, 2026

   

   barbatdev

   on Oct 17, 2026

   OwnerAuthor

   More actions

   Fleet issue review (glm)

   Recommendation: approve

   Well-governed boundary issue: it decides that cortex (OSS) becomes the source of truth for product-owned UX integrations (opencode/claude themes, docs/agent-state-v1.md, check-agent-state.sh, agent-state.sh, postcompact-hook.sh, memsave-nudge.sh, claude/statusline.sh) while cortex-dotfiles stays an installation/adaptation layer, and its six acceptance criteria are verifiable (documented boundary both ways, per-candidate migration plan, agreed target layout under integrations/, adaptation points identified, code migration in separate follow-up issues/PRs). The comment thread records exactly the right controls: independence clarified (not a mandatory downstream), the docs-only step already done via PR #32, the safe ordering gate (do not delete/move artifacts here until cortex#1038 ships validated replacements), and the scope split with #41. Explicitly a plan issue with no code migration.

   Item	Pass	Evidence
   clear problem	yes	Concrete ownership problem: product-owned Cortex artifacts live in the personal dotfiles repo, making cortex depend on dotfiles; the issue records the decision to move the source of truth.
   acceptance criteria present and testable	yes	Six checkboxes: both directions of the boundary documented, a migration plan per candidate (eight named paths), agreed destination layout, adaptation points identified, and code migration deferred to separate follow-ups.
   scope bounded	yes	Boundary and plan only ('No migrar código en este issue'), with an explicit keep-list for cortex-dotfiles and the execution gated on cortex#1038.
   no open questions	yes	The comment thread resolves the independence framing, the safe ordering and the #41 split; no unresolved decisions remain.

   Only Juan adds the status:approved label; this review is advisory.