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

Open
#92 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, json, yaml
Domain
ci-cd, tooling

Research direction

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.

Written by the indexing model from the issue text.

Description

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)

Dominant language
Go
Stars
0
Forks
9
Avg merge
1d 14h
Merged PRs (30d)
18

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from unbound-force/replicator

All issues in unbound-force/replicator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.