Stake Permission Doc

[rad2520]

Summary by CodeRabbit

• Documentation
  • Added “Wallet Stake Permission” explanation detailing purpose, exclusive delegation, and cold–hot key behavior, with links to related concepts.
  • Introduced “Create Wallet Stake Permission” step-by-step guide covering prerequisites, form fields, signing, and next steps.
  • Updated documentation navigation and tables of contents to include the new pages under Explanations > System and How-to Guides > System for easier discovery.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Adds two new docs pages describing Wallet Stake Permission and a how-to guide, updates Explanations and How-to Guides tables of contents, and inserts corresponding sidebar entries in astro.config.mjs. No code logic changes.

Changes

Cohort / File(s)	Summary
Navigation config astro.config.mjs	Added two sidebar entries linking to new Explanations and How-to Guides pages for Wallet Stake Permission.
Explanations docs src/content/docs/explanations/system/wallet-stake-permission.mdx, src/content/docs/explanations/table-of-contents.mdx	New concept page detailing Wallet Stake Permission and TOC update to include it.
How-to guides src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx, src/content/docs/how-to-guides/table-of-contents.mdx	New step-by-step guide for creating wallet stake permissions and TOC update to link it.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• v06 doc bump version #32 — Also adds docs content and updates navigation, overlapping with new pages plus sidebar edits.
• Finish refactoring folder structure #19 — Reorganizes/updates sidebar config; related to this PR’s new sidebar entries.
• Moved how to guides to the top and added a start here file to guide users #16 — Modifies navigation and adds system-related how-to/explanations entries similar to this addition.

Poem

A whisk of keys, a hop through stakes,
I map the paths a wallet takes.
Cold stays cozy, hot does the run,
Delegated chores beneath the sun.
New guides sprout where carrots gleam—
Click, sign, stake: a burrower’s dream. 🥕🐇

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 5fc9ae2 and ecc3431.

📒 Files selected for processing (5)

• astro.config.mjs (2 hunks)
• src/content/docs/explanations/system/wallet-stake-permission.mdx (1 hunks)
• src/content/docs/explanations/table-of-contents.mdx (1 hunks)
• src/content/docs/how-to-guides/system/create-wallet-stake-permission.mdx (1 hunks)
• src/content/docs/how-to-guides/table-of-contents.mdx (1 hunks)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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 and usage tips.}