Skip to content

docs: add PDS credible exit guide#135

Open
DonGuillotine wants to merge 2 commits into
hypercerts-org:mainfrom
DonGuillotine:docs/pds-credible-exit
Open

docs: add PDS credible exit guide#135
DonGuillotine wants to merge 2 commits into
hypercerts-org:mainfrom
DonGuillotine:docs/pds-credible-exit

Conversation

@DonGuillotine
Copy link
Copy Markdown

@DonGuillotine DonGuillotine commented May 19, 2026

Summary by CodeRabbit

  • Documentation
    • Added comprehensive reference guide for PDS Credible Exit detailing how to migrate AT Protocol accounts between PDS hosts while preserving account identity.
    • Includes prerequisites, step-by-step instructions, verification checklists, and bulk migration recommendations.
    • Updated navigation menu to include the new reference documentation.

Review Change Stack

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 19, 2026

@DonGuillotine is attempting to deploy a commit to the Hypercerts Foundation Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 19, 2026

Warning

Rate limit exceeded

@DonGuillotine has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 31 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 15895365-11a0-44ab-9470-67bb772e69ed

📥 Commits

Reviewing files that changed from the base of the PR and between c678988 and 4a8f022.

📒 Files selected for processing (1)
  • pages/reference/pds-credible-exit.md
📝 Walkthrough

Walkthrough

This PR adds a new reference documentation page for "PDS Credible Exit"—a procedure for migrating AT Protocol accounts between PDS hosts while preserving the account DID. The navigation structure is updated to register the page, and comprehensive documentation covering prerequisites, single-account migration steps, verification procedures, and bulk migration workflows is provided.

Changes

PDS Credible Exit Reference

Layer / File(s) Summary
Navigation registration
lib/navigation.js
New navigation entry for "PDS Credible Exit" is added under the Reference section to surface the documentation page.
PDS Credible Exit reference documentation
pages/reference/pds-credible-exit.md
Complete reference guide covering DID preservation overview with safety callouts, tested migration example with before/after outcomes, prerequisites (tooling and access), single-account migration steps with bash commands, verification checklist using PLC and PDS queries plus goat CLI commands, and bulk migration guidance with CSV manifest format and serialization recommendations.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A reference page hops into place,
Migration paths now find their grace,
From PDS to PDS we gently stride,
The DID stays safe, a verified guide,
With checksums and care, the account glides!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add PDS credible exit guide' accurately describes the main changeset which adds a new documentation page about PDS credible exit and corresponding navigation entry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
pages/reference/pds-credible-exit.md (1)

43-45: ⚡ Quick win

Use “invitation code” for formal consistency.

At Line 44, consider “an invitation code” instead of “an invite code” to match formal reference tone.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@pages/reference/pds-credible-exit.md` around lines 43 - 45, Update the
informal phrase "an invite code or admin access on the destination PDS" to the
more formal "an invitation code or admin access on the destination PDS" to
ensure consistent terminology; locate the list item containing the exact text
"an invite code or admin access on the destination PDS" in the pds-credible-exit
documentation and replace "invite code" with "invitation code".
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pages/reference/pds-credible-exit.md`:
- Around line 57-70: The migration variable block is missing OLD_PASSWORD which
is referenced later during login; add an export for OLD_PASSWORD (e.g., export
OLD_PASSWORD="current-password") to the top variable setup so the login step
that uses OLD_PASSWORD will have the value available, and ensure the exported
OLD_PASSWORD appears alongside OLD_PDS/NEW_PDS and the other NEW_* variables
before any login steps that reference it.

---

Nitpick comments:
In `@pages/reference/pds-credible-exit.md`:
- Around line 43-45: Update the informal phrase "an invite code or admin access
on the destination PDS" to the more formal "an invitation code or admin access
on the destination PDS" to ensure consistent terminology; locate the list item
containing the exact text "an invite code or admin access on the destination
PDS" in the pds-credible-exit documentation and replace "invite code" with
"invitation code".
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 060eb3bf-7379-45f5-bddb-5cfa1e8f4c41

📥 Commits

Reviewing files that changed from the base of the PR and between 20b2648 and c678988.

📒 Files selected for processing (2)
  • lib/navigation.js
  • pages/reference/pds-credible-exit.md

Comment thread pages/reference/pds-credible-exit.md
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