Skip to content

Removed GitHub Project board integration

Saga the Watchful — Ops Engineer

By the end of this chapter you’ll understand:

  • What was removed and from which scripts and skills
  • Where work, bug reports, and inbox sync now live after the change
  • Why maintaining two parallel trackers was a net negative

Removed GitHub Project board integration

Status: Delivered
CAS: CAS-2857
Delivered: 2026-05-15
PRs: direct commit to master

What changed

The GitHub Project board (abernerus/casaconomy-app → Projects → Casaconomy) integration has been removed. Creating a GitHub issue no longer auto-adds the issue to the GH Project board.

Removed:

  • create-issue.sh no longer calls gh project item-add after issue creation
  • .agents/skills/casaconomy-github-issue/references/project.md deleted
  • casaconomy-review-protocol and related skills updated to drop any project-board references

Why

Regent directive (2026-05-14): Paperclip is the canonical work-management surface. The GH Project board duplicated the Paperclip issue queue without adding value — triage, assignments, status, and priority all live in Paperclip. Maintaining two parallel trackers created consistency overhead with no benefit.

What to use instead

  • Work queue: Paperclip CAS issues
  • Bug reports and externally-visible tracking: GitHub Issues (labels: bug, improvement, priority:*, paperclip)
  • Inbox sync: Ravens mirrors paperclip-labelled GH issues → Paperclip CAS

GitHub Issues remain the authoritative public tracker; Paperclip is the internal operations layer. The GH Project board layer between them is gone.

Recap

  • create-issue.sh no longer calls gh project item-add; the project reference file and skill mentions of the board are deleted.
  • Work queue: Paperclip CAS issues. Bug reports: GitHub Issues with bug/improvement/priority:*/paperclip labels. Inbox sync: Ravens mirrors paperclip-labelled issues.
  • The GH Project board was a duplication layer; Paperclip is now the single internal operations surface.

What changed {#what-changed}

See: CHANGELOG → 2026-05-18