docs: Add Launchtube plugin documentation

[dylankilkenny]

Summary

Testing Process

Checklist

• Add a reference to related issues in the PR description.
• Add unit tests if applicable.

Summary by CodeRabbit

• Documentation
  • Added comprehensive documentation for the Launchtube plugin, including features overview, installation, configuration, setup workflow, API usage, and management endpoints.

[coderabbitai]

Walkthrough

A new documentation page for the Launchtube plugin is added to the site navigation. The comprehensive page covers the plugin's features, installation, configuration, API endpoints, and operational workflows for transaction processing within OpenZeppelin Relayer.

Changes

Cohort / File(s)	Summary
Documentation Addition docs/modules/ROOT/nav.adoc, docs/modules/ROOT/pages/launchtube.adoc	Added new navigation entry and corresponding documentation page for Launchtube plugin, detailing features (fee bumping, sequence management, simulation, retry logic), prerequisites, installation, configuration, Management API usage, transaction submission patterns, and end-to-end workflow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Hop along and see what's new,
Launchtube docs, both shiny and true!
Navigation links and guides so grand,
A plugin journey through relayer land!
No code to check, just words that sing,
Pure documentation—what a thing! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description follows the required template structure with sections for Summary, Testing Process, and Checklist, but the Summary and Testing Process sections are entirely empty with no content describing what documentation was added, why it was added, or what testing or review process was undertaken. While the checklist items are present (both unchecked), the lack of substantive information in the main content sections means the description provides no meaningful context for reviewers to understand the scope or intent of the changes.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "docs: Add Launchtube plugin documentation" directly and clearly reflects the main changes in the pull request, which add comprehensive documentation for the Launchtube plugin to two files in the docs directory. The title is concise, specific, and uses the conventional "docs:" prefix, making it immediately clear to someone scanning the repository history that this PR adds documentation content.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-launchtube-docs

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/modules/ROOT/pages/launchtube.adoc (1)

150-151: Gitleaks warnings are false positives—documentation placeholders are correctly marked.

The flagged curl command headers use explicit placeholder strings (YOUR_API_KEY, your-secret-here) rather than actual secrets. This is standard documentation practice. However, to further reinforce that these are examples requiring substitution, consider adding a brief note in the API Usage section clarifying that all placeholder values must be replaced with actual credentials before use.

Optional improvement—add a callout block in the "API Usage" section:

CAUTION: All examples use placeholder values (`YOUR_API_KEY`, `your-secret-here`, etc.). Replace these with your actual credentials before running any commands.

Also applies to: 259-260, 276-277, 355-356, 387-388

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23c9c7d and 27ea6e4.

📒 Files selected for processing (2)

• docs/modules/ROOT/nav.adoc (1 hunks)
• docs/modules/ROOT/pages/launchtube.adoc (1 hunks)

🧰 Additional context used

🪛 Gitleaks (8.28.0)

docs/modules/ROOT/pages/launchtube.adoc

[high] 150-151: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

(curl-auth-header)

---

[high] 259-260: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

(curl-auth-header)

---

[high] 276-277: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

(curl-auth-header)

---

[high] 355-356: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

(curl-auth-header)

---

[high] 387-388: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

(curl-auth-header)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: boostsecurity - boostsecurityio/semgrep-pro
• GitHub Check: boostsecurity - boostsecurityio/boost-sca
• GitHub Check: boostsecurity - boostsecurityio/scanner
• GitHub Check: boostsecurity - boostsecurityio/osv-scanner
• GitHub Check: Redirect rules - openzeppelin-relayer
• GitHub Check: Header rules - openzeppelin-relayer
• GitHub Check: Pages changed - openzeppelin-relayer
• GitHub Check: Analyze (rust)
• GitHub Check: semgrep/ci

🔇 Additional comments (5)

docs/modules/ROOT/pages/launchtube.adoc (4)

4-142: Comprehensive and well-structured configuration documentation.

The overview, prerequisites, installation, and configuration sections are clear, progressive, and provide good examples. Fund account requirements and concurrent transaction policies are well-explained, and environment variable constraints are properly documented. The distinction between required and optional configuration is clear.

---

144-343: API workflow documentation is clear and comprehensive.

The progression from manual initialization to automated setup is logical, and script options are well-documented. The API section effectively explains both transaction submission methods (XDR vs func+auth) with good parameter documentation and realistic TypeScript SDK examples. The important notes about resource requirements and constraints are appropriately positioned.

---

345-473: Error handling and response documentation are professional and complete.

The Management API section clearly documents authentication requirements, constraints (minimum sequence account, locked conflict handling), and the HTTP 409 response for LOCKED_CONFLICT scenarios. Response schemas for both success and error cases are well-documented with field explanations and common error codes. This provides good guidance for API consumers.

---

482-518: Workflow and resources documentation provides good context.

The "How It Works" section clearly sequences the 7-step transaction processing pipeline and articulates the architectural benefits. Example setup references are well-structured with deterministic GitHub commit links, and additional resources point to relevant documentation.

docs/modules/ROOT/nav.adoc (1)

14-14: Navigation entry is correctly placed and properly formatted.

The Launchtube entry is properly nested under the Plugins section with correct AsciiDoc syntax and indentation. The cross-reference correctly points to the new documentation file.

[zeljkoX]

LGTM