docs(drift): draft from internal source

[pedromcunha]

Drafted from an internal source repo, requested by @matirelay.

This PR was auto-generated by the reusable-docs-draft-pr workflow from a Claude-drafted update in the source repo. It is opened as a draft — please review, edit as needed, and mark ready for review before merging.

Review checklist

• Content matches the behavior shipped in the source PR
• No internal-only details (service names, file paths, unreleased names, security internals) leaked into the draft
• Conforms to CLAUDE.md style rules
• Cross-references and internal links resolve
• Any Needs human input items from the source comment are addressed

---

Generated by reusable-docs-draft-pr.yml in relayprotocol/agents-config.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
unevenlabs	🟢 Ready	View Preview	Aug 14, 2026, 8:23 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

Claude encountered an error after 2m 31s —— View job

---

Code review — PR #415

• Read the diff
• Check the changed file in context
• Look for stale references to the removed chain elsewhere in the docs
• Post review

The diff is a single-row deletion (superposition, chain id 55244) from the depository address table. The edit itself is clean — ascending-by-chain-id ordering and column alignment are preserved, and nothing else in the repo mentions superposition, so there are no stale references to clean up. references/protocol/** is out of scope for AGENTS.md v1, so no style-guide rules apply here.

Two things worth resolving before merge.

---

1. This file looks dead — the whole references/protocol/depository/ tree was superseded

references/protocol/depository/addresses.mdx is not in the docs.json navigation, and docs.json:508-510 redirects its URL away:

{ "source": "/references/protocol/depository/addresses",
  "destination": "/references/protocol/addresses" }

That's not a one-off. Every page under references/protocol/depository/ has a redirect to a new home (docs.json:484-510) and none are in the nav — the directory is leftover files from a restructure. The destination, references/protocol/addresses.mdx:29-31, renders the same depository table fetched live from the Chains API via <Depositories />, sorted by chain id:

"The list below is fetched live from the Chains API and stays in sync as new chains are added."

So a reader navigating to this table gets the live version, which already reflects the superposition removal without any PR. Hand-maintaining the static snapshot is exactly the drift this PR is paying for, and the edit is very likely invisible to readers.

Suggested resolution — delete the file rather than patch it, and update the two inbound links that still point at the legacy path:

• references/protocol/guides/for-apps.mdx:67 — "See Contracts Addresses for the Depository address on every supported chain."
• references/protocol/guides/for-apps.mdx:69 — "See Contracts Addresses for the program ID."

Both currently resolve only via the redirect; they should point directly at /references/protocol/addresses.

Fix this →

If the static page is meant to stay, the opposite fix applies: drop the redirect and add the page to the nav, otherwise it stays unreachable and will keep drifting.

2. Please confirm the delisting against the live API — I couldn't

Network access is blocked in this job (WebFetch/curl to api.relay.link denied), so I can't verify that superposition was genuinely removed from depository deployments versus omitted by a partial or transient API snapshot. A single-row deletion is the same shape either cause produces. Worth confirming with the command in the file's own generation comment (references/protocol/depository/addresses.mdx:7):

curl https://api.relay.link/chains | jq '.chains[] | select(.id == 55244)'

If superposition is being delisted rather than just missing from a snapshot, that's a user-visible support change; AGENTS.md §4.5 scopes the changelog to API endpoints only, so nothing is required, but it may deserve an announcement elsewhere.

---

Minor notes (pre-existing, not introduced here)

• references/protocol/depository/addresses.mdx:7 — the documented jq extracts .protocol.v2.chainId for the first column, but that column renders chain slugs (polygon_zkevm, arena_z, onchain_points). If protocol.v2.chainId is a numeric protocol id, the snippet doesn't reproduce this table and should probably read .name. I couldn't check the response shape without network access. Moot if the file is deleted.
• snippets/Depositories.mdx:48 — a stray debugger; statement sits in the live fetchChains path. It will pause execution for any reader with devtools open on /references/protocol/addresses. Unrelated to this PR, but worth a quick cleanup. Fix this →
• Row ordering in the table is ascending by chain id except for bitcoin / eclipse / degen / solana / ancient8 near the end (lines 75-79), where the VM rows with empty chain-id cells interleave. Pre-existing; the live table sorts strictly by chain.id.

No changes were pushed — this is review feedback only, and the main recommendation (delete vs. keep the page) is a call for the PR author.
· docs-drift/src-b4a7d12942-debbbd7

[greptile-apps]

Greptile Summary

This change removes the Superposition depository-address entry from the legacy protocol contracts table. The potential mismatch was disproved by a live request to the Chains API: it returned HTTP 200 and no Superposition or chain ID 55244 record, so removing the stale row keeps the documentation aligned with current chain data.

Confidence Score: 5/5

Safe to merge: the removed chain is absent from the live Chains API, and the updated table no longer advertises a stale depository address.

The exact removed chain entry was compared between the parent and updated documentation revisions and against the live API response. The live response contained no matching Superposition or chain ID 55244 record.

Files Needing Attention: No files need further attention.

T-Rex Logs

What T-Rex did

• • The reproducible API validation script was run to compare the parent and updated references/protocol/depository/addresses.mdx with live data, and it shows the updated doc now aligns with current chain data.
• • The pre-change and post-change API state were reviewed to confirm the removal of the stale entry does not introduce divergence, showing no matching chain in both cases and indicating no security impact.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs(drift): draft from internal source" | Re-trigger Greptile}