Skip to content

engine: stop forwarding player reports to the retired VibeCtl service - #80

Open
jonradoff wants to merge 1 commit into
mainfrom
chore/drop-vibectl-feedback
Open

jonradoff wants to merge 1 commit into
mainfrom
chore/drop-vibectl-feedback

Conversation

@jonradoff

Copy link
Copy Markdown
Collaborator

VibeCtl has been retired, so this removes the code that forwarded player reports to it.

Removed

  • engine/internal/feedback/: the HTTP client that sent reports to VibeCtl
  • engine/cmd/backfill-reports/: a one-off tool that re-sent logged reports to VibeCtl
  • The forwarding step after a report is logged, plus the server's feedback client, its NewServer parameter and the client setup in cmd/lofp/main.go
  • The Feedback config field, the FeedbackConfig type and the feedback: blocks in config/dev.yaml and config/prod.yaml
  • The CLAUDE.md line about the feedback pipeline

Unchanged

  • The REPORT command still logs the report, notifies online GMs and publishes it on the event bus.
  • /healthz stays, because Fly uses it as the health check. Only its comment changed.
  • Historical CHANGELOG and VersionNotes text is left as it was.

go build ./..., go vet ./... and go test ./... pass in engine/.

After this is deployed, the VIBECTL_URL and VIBECTL_API_KEY Fly secrets are no longer read and can be removed.

🤖 Generated with Claude Code

Reports from the REPORT command are still logged, shown to online GMs and published on the event bus.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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