docs: document native Cloudflare GitHub access

[robin-liquidium]

Document the GitHub app repository-access requirement behind the disconnected Cloudflare build connection. Public-repository cloning allowed manual builds to succeed while automatic push-triggered builds did not start.

GitHub now lists RunesSwap.app in the app's selected repositories, and Cloudflare's disconnected warning has cleared. This merge verifies push-triggered production deployment through the native integration. No application behavior changes.

Validation: pre-push ai-check passed, including 208 tests and the production build. The existing v0.3.0 Worker remains live.

[coderabbitai]

Warning

Review limit reached

Next included review available in 37 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 89629468-a7d3-4d6c-8132-82f3a5f624f6

📥 Commits

Reviewing files that changed from the base of the PR and between b489254 and e81280f.

📒 Files selected for processing (2)

• CHANGELOG.md
• docs/cloudflare-migration.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[opencode-agent]

Review of PR #202 — docs: document native Cloudflare GitHub access

Scope: 2 files, +5/-0, docs-only (CHANGELOG.md, docs/cloudflare-migration.md). I reviewed the full diff.

Summary

This is a clean, minimal documentation change. No code quality issues or bugs are possible here, and both edits are accurate and well-placed.

What looks good

• Changelog discipline followed: Entry added under ## [Unreleased] in a Keep a Changelog category (Fixed), no version bump — exactly per the repo's AGENTS.md conventions.
• Categorization is correct: "Fixed" fits — automatic push-triggered deployments were broken and are now restored.
• Docs placement is correct: The new paragraph sits in the deployment/secrets section of docs/cloudflare-migration.md, right after the note about the native Git integration, which is the natural place for it.
• Content is accurate and useful: The troubleshooting guidance is the valuable part — documenting that a manual build can succeed on a public repo even when push events aren't reaching Cloudflare is a genuinely non-obvious failure mode that would otherwise cost someone debugging time. Telling the reader to check GitHub app repository access first is the right first step.
• No secrets or sensitive info leaked.

Minor nits (non-blocking)

1. Wording polish (optional): "a manually started build can still clone this public repository and deploy even when GitHub push events are not reaching Cloudflare" — slightly long sentence; could be split, but it's perfectly readable as-is.
2. Changelog phrasing (optional): "Restored GitHub app access" describes an external/config change rather than a repo change. Since the changelog is public-facing per the docs, this is fine, but something like "Documented and restored GitHub app repository access for automatic Cloudflare Worker deployments" would be marginally more precise. Not worth changing.

Verdict

✅ Approve. Docs-only, follows repo conventions (changelog under Unreleased, no version bump), and adds useful operational troubleshooting knowledge. Nothing to fix; safe to merge.

opencode session  |  github run