chore: replace remaining remoteclaw.ai URLs with .org#2386
Merged
alexey-pelykh merged 1 commit intomainfrom Apr 17, 2026
Merged
chore: replace remaining remoteclaw.ai URLs with .org#2386alexey-pelykh merged 1 commit intomainfrom
alexey-pelykh merged 1 commit intomainfrom
Conversation
Fork owns remoteclaw.org, not remoteclaw.ai. PR #2379 cleaned up docs.remoteclaw.ai references; this picks up the long tail: production code (website const, onboarding messages, Swift share-self-test URL, docker OCI label), docs (install scripts, trust page, security emails, FAQ, fastlane privacy/marketing/support URLs), and test fixtures ($schema URL, team email, OSC-8 hyperlink). 21 files, symmetric 37 insertions / 37 deletions (pure TLD swap). Verified endpoints resolve on .org: - remoteclaw.org/install.sh, install.ps1 → 200 - docs.remoteclaw.org/platforms/ios/ → 200 Aspirational .org subdomains (trust.remoteclaw.org, /showcase, /privacy, /share-self-test, /config.json) match fork's established SECURITY.md convention — pages to be stood up separately. Follow-up: #2385 tracks a regression-prevention CI gate. Co-Authored-By: Claude Opus 4.7 (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
1 participant
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.
Closes #2382. Follows up on PR #2379 (which cleaned up
docs.remoteclaw.aireferences) by sweeping the long tail ofremoteclaw.aiURLs — we ownremoteclaw.org, not.ai.Summary
21 files, symmetric 37 insertions / 37 deletions (pure TLD swap; one oxfmt reflow in a test file accounts for the +2 line delta):
$schemaURL fixture,team@email fixture, website URL assertionimage.urllabel (was inconsistent with.documentation=.org), install script commands (FAQ, raspberry-pi, RELEASING), trust page links, security contact emails, fastlane READMEVerification
grep -r "remoteclaw\.ai"returns only attribution/shimsdocs/install/docker.md:175-177all.org(was.ai/.orgmismatch)docs.remoteclaw.org/platforms/ios/→ HTTP 200remoteclaw.org/install.sh+install.ps1→ HTTP 200trust.remoteclaw.aireferences resolve or replacedtrust.remoteclaw.org(matches fork's pre-existing SECURITY.md convention; aspirational subdomain consistent with how.orgtrust page is referenced throughout)Aspirational
.orgpathsA few
.orgpaths introduced here are aspirational (don't yet resolve):/showcase,/privacy,/share-self-test,/config.json,trust.remoteclaw.org. This matches the fork's existing convention —SECURITY.mdat fork HEAD references aspirationaltrust.remoteclaw.org. Pages can be stood up (or redirects added) separately; the rebrand consistency is the load-bearing fix.Non-goals
.aiTLD for the forkTest plan
🤖 Generated with Claude Code