feat: add minor details in how it works

[keyvankhademi]

Summary

Rationale

How has this been tested?

• Current tests cover my changes
• Added new tests
• Manually tested the code

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
component-library	Ready	Preview, Comment	May 20, 2026 8:21pm
developer-hub	Error		May 20, 2026 8:21pm

5 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
api-reference	Skipped		May 20, 2026 8:21pm
entropy-explorer	Skipped		May 20, 2026 8:21pm
insights	Skipped		May 20, 2026 8:21pm
proposals	Skipped		May 20, 2026 8:21pm
staking	Skipped		May 20, 2026 8:21pm

[devin-ai-integration]

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🔴 Placeholder text "[insert link here]" shipped in production documentation

Line 33 contains the literal placeholder [insert link here] which would be rendered as-is to users visiting the documentation site. This is clearly an unfinished TODO that should either be replaced with an actual link (e.g., to a Pyth Pro routers page) or the sentence should be removed until a proper link is available.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[Copilot]

Pull request overview

This PR updates the Developer Hub documentation for the Pyth Core upgrade by adding a brief note about routers and clarifying upgraded Hermes endpoint requirements.

Changes:

• Adds a new sentence in the “Routers” section intended to link to more information (currently a placeholder).
• Splits the upgraded Hermes description into shorter lines and notes that an API key is required.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[devin-ai-integration]

Devin Review found 6 new potential issues.

View 5 additional findings in Devin Review.

[devin-ai-integration]

🚩 Missing meta.json for upgrade subdirectory

The new content/docs/price-feeds/core/upgrade/ directory has three pages (index.mdx, contracts.mdx, how-it-works.mdx) but no meta.json file. Other sibling subdirectories under core/ (e.g., how-pyth-works/, use-real-time-data/, troubleshoot/) all have meta.json files that define page ordering in the sidebar. Without one, fumadocs will auto-sort the upgrade sub-pages alphabetically, which may produce an unexpected sidebar order (contracts → how-it-works → index) rather than the likely intended (index → how-it-works → contracts). This isn't a breaking issue — fumadocs handles missing meta.json gracefully — but it's inconsistent with established patterns per the AGENTS.md guidance.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 LLM endpoint content corrupted with JavaScript wrapper text

The CONTENT template literal in apps/developer-hub/src/app/llms-price-feeds-core.txt/route.ts was modified to wrap the entire markdown content in spurious JavaScript syntax. The string now starts with a backtick + newline + function () { return (\`` and ends with `) };. When the GET` handler serves this content, LLM consumers will receive literal garbage text:

What the endpoint now returns

`
function () { return (`# Pyth Core — Quick Start
...
`) };

The previous version cleanly started with # Pyth Core — Quick Start.

This completely breaks the /llms-price-feeds-core.txt endpoint for any LLM or AI agent that consumes it, as it will parse the JavaScript wrapper as part of the content.

Suggested change

	const CONTENT = `\`
	function () { return (\`# Pyth Core — Quick Start
	const CONTENT = `# Pyth Core — Quick Start

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 Closing JavaScript wrapper text appended to LLM endpoint content

The closing counterpart to BUG-0001: the end of the CONTENT string at apps/developer-hub/src/app/llms-price-feeds-core.txt/route.ts:205 appends literal \) };` text to the LLM-facing output. This must be removed along with the opening wrapper (lines 5-6) to restore the clean markdown output.

Suggested change

\`) };

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 Placeholder "New Address Here" shipped in LLM-facing content

The Ethereum contract address was replaced with the placeholder **New Address Here** at apps/developer-hub/src/app/llms-price-feeds-core.txt/route.ts:104. This is clearly unfinished — LLM consumers and AI agents relying on this endpoint for Ethereum's Pyth contract address will receive a non-functional placeholder instead of an actual address. The previous value was 0x4305FB66699C3B2702D4d05CF36551390A4c69C6.

Prompt for agents

The Ethereum contract address on line 104 of apps/developer-hub/src/app/llms-price-feeds-core.txt/route.ts was replaced with the placeholder string "**New Address Here**". This needs to be replaced with the actual upgraded Pyth Core contract address for Ethereum mainnet. If the upgraded address is not yet known, revert to the previous address (0x4305FB66699C3B2702D4d05CF36551390A4c69C6) with a TODO comment, or remove the Ethereum entry until the address is finalized.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🟡 Redirect exclusion uses migration but the route is upgrade

The catch-all redirect regex in apps/developer-hub/next.config.js:261 was updated to exclude migration from being redirected to /price-feeds/core/, but the actual new route is /price-feeds/core/upgrade (not /price-feeds/migration). The migration exclusion is dead code — it protects a non-existent path. While the /price-feeds/core/upgrade route works correctly because core is already excluded, the unnecessary migration exclusion suggests a naming mistake and adds confusion for future maintainers.

Suggested change

	source: String.raw`/price-feeds/:path((?!core(?:/|$|\.mdx?$)|pro(?:/|$|\.mdx?$)|hip-3-service(?:/|$|\.mdx?$)|migration(?:/|$|\.mdx?$)).*)`,
	source: String.raw`/price-feeds/:path((?!core(?:/|$|\.mdx?$)|pro(?:/|$|\.mdx?$)|hip-3-service(?:/|$|\.mdx?$)).*)`,

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🚩 MigrationContractsTable filters by "lazer-prod" which has no matching entries

The buildDeployments function at apps/developer-hub/src/components/MigrationContractsTable/index.tsx:54-58 filters evmPriceFeedContracts for entries with deploymentType === "lazer-prod". However, the current contract_manager/src/store/contracts/EvmPriceFeedContracts.json contains only "pro-compatible-production" as deployment types — no entries with "lazer-prod" exist. This means both the mainnet and testnet tables will always render "No contracts published yet for this network type." This may be intentional staging (the contracts page is ready before data is populated), but it could also indicate a naming mismatch between the expected deployment type and the actual data. Worth confirming with the author whether "lazer-prod" is the intended future value or if "pro-compatible-production" should be used instead.

---

Was this helpful? React with 👍 or 👎 to provide feedback.