Skip to content

chore: remove local spec copies, reference cycles-protocol repo#76

Merged
amavashev merged 1 commit into
mainfrom
chore/use-protocol-repo-spec
Apr 12, 2026
Merged

chore: remove local spec copies, reference cycles-protocol repo#76
amavashev merged 1 commit into
mainfrom
chore/use-protocol-repo-spec

Conversation

@amavashev
Copy link
Copy Markdown
Collaborator

Summary

  • Remove stale local copies of the governance admin spec (v0.1.24 and v0.1.25)
  • Update README and AUDIT.md to reference the canonical spec in cycles-protocol

Why

The governance admin spec is canonically maintained in the cycles-protocol repo. The local copy was already stale — v0.1.25.8 here vs v0.1.25.9 in the protocol repo (which added error responses and schema examples in runcycles/cycles-protocol#30). Keeping a local copy creates drift risk.

What changed

File Change
complete-budget-governance-v0.1.25.yaml Deleted (stale v0.1.25.8 copy, 5041 lines)
complete-budget-governance-v0.1.24.yaml Deleted (obsolete version)
README.md Links to cycles-governance-admin-v0.1.25.yaml in cycles-protocol repo
AUDIT.md Same — spec reference updated

No Java code referenced these files — they were documentation-only.

Test plan

  • No Java imports or classpath references to removed files
  • README and AUDIT links point to correct GitHub URLs
  • CI should pass (no build dependency on spec files)

The governance admin spec is canonically maintained in the
cycles-protocol repo. The local copies were already stale
(v0.1.25.8 vs v0.1.25.9 in protocol repo) and created drift risk.

- Remove complete-budget-governance-v0.1.25.yaml (stale local copy)
- Remove complete-budget-governance-v0.1.24.yaml (obsolete version)
- Update README.md to link to cycles-protocol repo
- Update AUDIT.md spec reference to cycles-protocol repo
@amavashev amavashev merged commit e6533c1 into main Apr 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant