chore: update replicator scaffolding and constitution for unbound-force v0.16.0

Abierto
#92 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
github-actions, json, yaml
Área
ci-cd, tooling

Línea de trabajo

Start by reading the v0.16.0 release notes and reviewing the replicator repo’s current scaffold; then run uf init --force as specified. Review .specify/memory/constitution.md, opencode.json, .github/workflows/ci.yml, release.yml, and .opencode/agents/ against the org constitution and workflow pins. Done means the manual follow-ups are complete, stale agent references are resolved, and the scaffold and permissions align with v0.16.0.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

Update the replicator repo to align with unbound-force v0.16.0. uf init --force handles the bulk of the work — this issue tracks that step plus the manual follow-ups init cannot touch.

Tasks

1. Run uf init --force

This single command handles ~80% of the update:

  • Overwrites all tool-owned files with v0.16.0 content (commands, skills, canonical convention packs, OpenSpec schemas, Speckit framework)
  • Stamps v0.16.0 version markers (replacing vdev)
  • Deploys new/updated skills (always-on-guidance, pre-flight, review-context, speckit-workflow)
  • Refreshes DCP config (.opencode/dcp.jsonc)
  • Cleans up legacy command names (pre-uf. namespace prefix)
  • Re-initializes sub-tools (Dewey, Specify, OpenSpec, Gaze)
2. Constitution alignment (manual — NEVER-OVERWRITE) .specify/memory/constitution.md is protected from --force.

Manual updates required:

  • Bump parent_constitution reference from v1.1.0 → v1.2.0
  • Add Principle V: Security by Default section aligned with org constitution v1.2.0
  • Review existing 4 principles for any conflicts with org v1.2.0 wording
  • Bump constitution version (currently v1.0.0)
3. Add permission gates to opencode.json

The org repo now enforces granular bash permissions (#477, #493). Replicator currently has no permission gates. Add:

  • gh issue / gh pr mutation gates
  • git push gate
  • rm safety gate
  • Any replicator-specific sensitive operations
4. CI action pin audit

Review .github/workflows/ci.yml and release.yml for stale action SHAs. Verify alignment with org-level pins:

  • actions/checkout → v7.0.1 SHA
  • actions/setup-go → v7.0.0 SHA
  • org-infra reusable workflows → latest SHA
5. Verify stale agent refs

After init, check user-owned agent files in .opencode/agents/ for references to old command names (pre-uf. prefix). Init warns but does not auto-fix these.

Context

Release: https://github.com/unbound-force/unbound-force/releases/tag/v0.16.0
Current constitution: v1.0.0 (parent ref: org v1.1.0)

Lenguaje dominante
Go
Estrellas
0
Forks
9
Merge medio
1 d 14 h
PR fusionados (30 d)
18

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de unbound-force/replicator

Todos los issues de unbound-force/replicator

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.