chore(oss): cleanup — remove community desktop, strip hosted defaults, premium pre-push guard#28
Merged
Merged
Conversation
…ate product Open-core cleanup: the desktop GUI ships as the private official product (free+premium). OSS self-host is via the CLI + protocol packages. Removes packages/dcp-desktop, its build-desktop workflow, and its cargo dependabot entry. No OSS package depends on it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…telegram metadata - Default-URL refactor: OSS no longer defaults to our hosted relay/telegram infra. DEFAULT_RELAY_URL / RELAY_URLS / TELEGRAM_CLOUD_URL / mobile-relay are now env-driven (DCP_RELAY_URL / DCP_TELEGRAM_CLOUD_URL) with empty (require-config) defaults. CLI proxy/connect gain require-config guards; vault telegram paths are inert (clean errors) until an operator points at their own service. Self-host = bring-your-own-infra; managed product injects our endpoints explicitly. - Pre-push premium guard: publish-guard.mjs scans git-tracked files for premium markers (dcp-premium-cloud, DCP_PREMIUM_*, ~/.dcp/premium, dcp_premium, mobile consent-bridge symbols) and fails. Wired via .githooks/pre-push + core.hooksPath (auto-installed by the prepare script). - Removed our Fly infra configs (fly.toml, fly.telegram.toml) from tracking + gitignored them; added sanitized *.example templates with placeholder app names. - dcp-telegram package.json: license MIT->Apache-2.0, added repository/homepage/bugs. All protocol packages build clean; unit tests + 12/12 security regression tests pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes the OSS repo a clean, self-sufficient protocol stack before new feature work lands.
What changed
DEFAULT_RELAY_URL/RELAY_URLS/ vault telegram-cloud URL / mobile-relay are now env-driven (DCP_RELAY_URL,DCP_TELEGRAM_CLOUD_URL) with empty (require-config) defaults, so self-hosters point at their own infra instead of ours. CLIproxy/connectgained require-config guards; vault telegram paths go inert (clean errors) until configured.scripts/publish-guard.mjsnow scans git-tracked files for premium markers and fails; wired as a real pre-push hook (.githooks/pre-push+core.hooksPath, auto-installed by thepreparescript). Negative-tested.fly.toml/fly.telegram.tomluntracked + gitignored; sanitized*.exampletemplates added with placeholder app names + BYO-token note.@dcprotocol/telegrammetadata: license MIT→Apache-2.0, addedrepository/homepage/bugs. Telegram stays generic (BYO bot token).Verification
No npm publish and no relay redeploy in this PR — those stay gated.