docs: fix broken external links in snapshots and blobstream pages

[jcstein]

fix lint errs

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the robustness and accuracy of the documentation by resolving issues with external links. It specifically targets links that were either failing TLS checks or returning HTTP 403 errors, ensuring that users and automated systems encounter fewer broken references. The changes aim to provide a more stable and trustworthy resource without removing valuable information.

Highlights

• Broken Link Removal: Removed QubeLabs snapshot links that were failing TLS checks, ensuring documentation integrity.
• Arbiscan Link Replacement: Replaced Arbiscan links that were returning Cloudflare 403 errors with plain contract addresses to prevent automated link check failures.
• Documentation Reliability: Improved the overall reliability of external links within the documentation by addressing specific issues with TLS and Cloudflare errors, while keeping essential data visible.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• app/build/blobstream/integrate-contracts/page.mdx
  • Removed external Arbiscan links for Arbitrum One and Arbitrum Sepolia contract addresses, displaying them as plain text instead.
• app/operate/maintenance/snapshots/page.mdx
  • Removed QubeLabs archive snapshot links for both Mainnet Beta and Mocha testnet due to TLS check failures.

Activity

• No specific activity (comments, reviews, etc.) was provided in the context for this pull request.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request fixes broken external links in the documentation by removing links that are failing automated checks. The changes in blobstream/integrate-contracts/page.mdx remove links to Arbiscan, and the changes in snapshots/page.mdx remove links for QubeLabs snapshots. The changes are correct and address the issue described. I've added a few suggestions to preserve the removed URLs in comments within the source files. This improves maintainability by making it easier for future contributors to check if the links have been fixed and can be restored, without affecting the link checker or the rendered output.

[gemini-code-assist]

While removing the link fixes the automated checks, it's a good practice to keep the original URL available for maintainers. You can add it in a JSX comment so it doesn't affect the link checker or the rendered output. This will help if the link becomes stable again in the future.

| SP1 Blobstream | Arbitrum One           | `0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794`{/* https://arbiscan.io/address/0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794#events */} | [Mainnet Beta](/operate/networks/mainnet-beta)        | [Deployment on Celenium](https://celenium.io/blobstream?network=arbitrum&page=1)       |

[gemini-code-assist]

Similar to the above, consider adding the removed Arbiscan link in a JSX comment to preserve it for future reference. This helps with maintainability.

| SP1 Blobstream | Arbitrum Sepolia       | `0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2`{/* https://sepolia.arbiscan.io/address/0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2#events */} | [Mocha testnet](/operate/networks/mocha-testnet) | [Deployment on Celenium](https://mocha.celenium.io/blobstream?network=arbitrum&page=1) |

[gemini-code-assist]

It's good practice to keep the removed link in a comment for future reference, especially since the removal is due to a potentially temporary issue (TLS checks failing). This makes it easier for future maintainers to check if the link is working again and restore it. You can use a JSX comment.

| QubeLabs    | -{/* Archive: https://snaps.qubelabs.io/celestia/ */}                                                                                                | -                                                                          |

[gemini-code-assist]

Similar to the mainnet table, consider adding a JSX comment here to preserve the removed link for future reference. This helps maintainers easily find and verify the link in the future.

| QubeLabs    | -{/* Archive: https://snaps.qubelabs.io/celestia/ */}                                                                                                | -                                                                          |

[github-actions]

🚀 Preview Deployment

Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2430/