fix(developer-hub): drop mock changelog entries and polish new Aug entries

- Remove four pre-populated mock July entries (2026-07-02, 07-08, 07-10, 07-15) since this is the first real changelog publish.
- Bold the "Why it matters" and "What to do" prefixes across all five new entries so the customer-facing structure reads consistently.
- Reframe the Entropy chain-deprecation entry with a per-chain table for the eight affected chains (ZetaChain, Unichain, Taiko, Tabi, Story, Blast, Etherlink, Sei EVM — mainnet and testnet) and keep the explicit statement that Entropy continues to run on every other supported network.

Author: KemarTiti

apps/developer-hub/content/changelog/2026-07-02-pyth-pro-terminal-docs.mdx

@@ -7,19 +7,32 @@ area: network
 ---
 
 Entropy continues to run on every currently supported network. Separately, on
-**August 15, 2026**, Entropy is being deprecated on eight specific chains —
-**ZetaChain, Unichain, Taiko, Tabi, Story, Blast, Etherlink, and Sei EVM**
-(mainnet and testnet) — and the Entropy chainlist no longer advertises those
-chains so new integrators do not pick them up.
+**August 15, 2026**, Entropy is being deprecated on eight specific chains, and
+the Entropy chainlist no longer advertises those chains so new integrators do
+not pick them up.
 
-Why it matters: this is a per-chain deprecation, not a change to the Entropy
-product. Apps running Entropy on any of the other supported chains keep working
-exactly as before. Only apps deployed on one of the eight chains listed above
-need to take action ahead of the August 15 date.
+Chains scheduled for deprecation on **August 15, 2026**:
 
-What to do: if your application uses Entropy on any of the eight chains above,
-plan a migration off that chain before **August 15, 2026**. Applications on any
-other Entropy-supported network do not need to do anything.
+| Chain      | Networks              |
+| ---------- | --------------------- |
+| ZetaChain  | Mainnet and testnet   |
+| Unichain   | Mainnet and testnet   |
+| Taiko      | Mainnet and testnet   |
+| Tabi       | Mainnet and testnet   |
+| Story      | Mainnet and testnet   |
+| Blast      | Mainnet and testnet   |
+| Etherlink  | Mainnet and testnet   |
+| Sei EVM    | Mainnet and testnet   |
+
+**Why it matters:** this is a per-chain deprecation, not a change to the
+Entropy product. Apps running Entropy on any of the other supported chains
+keep working exactly as before. Only apps deployed on one of the eight chains
+listed above need to take action ahead of the August 15 date.
+
+**What to do:** if your application uses Entropy on any of the eight chains
+above, plan a migration off that chain before **August 15, 2026**.
+Applications on any other Entropy-supported network do not need to do
+anything.
 
 - [Deprecation notice: Pyth Entropy deprecation for selected chains (August 15, 2026)](https://dev-forum.pyth.network/t/deprecation-notice-pyth-entropy-deprecation-for-selected-chains-august-15-2026/816)
 - [Entropy chainlist](/entropy/chainlist)

apps/developer-hub/content/changelog/2026-07-08-entropy-v2-arbitrum-base.mdx

@@ -11,15 +11,15 @@ Apps on Flow EVM Mainnet can point their integrations at the upgraded Pyth
 contract and consume the same Pyth Pro-backed price updates already available
 on other upgraded EVM chains.
 
-Why it matters: the upgraded contract is the single integration surface for
-Pyth on EVM going forward, and adding Flow EVM Mainnet keeps Flow apps aligned
-with the same feed catalog and update semantics as the rest of the upgraded
-network. Legacy Flow EVM Mainnet consumers keep working — the previous Pyth
-contract address is unchanged.
+**Why it matters:** the upgraded contract is the single integration surface
+for Pyth on EVM going forward, and adding Flow EVM Mainnet keeps Flow apps
+aligned with the same feed catalog and update semantics as the rest of the
+upgraded network. Legacy Flow EVM Mainnet consumers keep working — the
+previous Pyth contract address is unchanged.
 
-What to do: if you are starting a new integration on Flow EVM Mainnet, use the
-upgraded (Pro-compatible) address. If you are migrating an existing Flow app,
-follow the standard EVM migration steps.
+**What to do:** if you are starting a new integration on Flow EVM Mainnet, use
+the upgraded (Pro-compatible) address. If you are migrating an existing Flow
+app, follow the standard EVM migration steps.
 
 - [EVM contract addresses (upgraded and current)](/price-feeds/core/contract-addresses/evm)
 - [Migrate an app to Pyth](/price-feeds/core/migrate-an-app-to-pyth)

apps/developer-hub/content/changelog/2026-07-10-pyth-core-hermes-v1-sunset.mdx

@@ -10,7 +10,7 @@ The Pyth Pro History API reference now reflects two things in one place: how to
 authenticate requests with your Pyth Pro API key, and how to page through
 historical prices with `GET /{channel}/price/range`.
 
-Why it matters: authentication on the History API has been required since
+**Why it matters:** authentication on the History API has been required since
 [July 24, 2026](https://dev-forum.pyth.network/t/action-required-pyth-pro-history-api-auth-required-starting-july-24/808).
 The docs now describe that requirement in the present tense, so there is a
 single source of truth for how to call `/{channel}/price`,
@@ -19,7 +19,7 @@ returns raw prices for up to 100 feeds across a window of at most 60 seconds,
 with opaque cursor pagination for walking dense results. For long-horizon
 charting or TradingView-style OHLC data, keep using `/{channel}/history`.
 
-What to do:
+**What to do:**
 
 - Present your Pyth Pro API key as
   `Authorization: Bearer <PRO_API_KEY>` on every authenticated History

apps/developer-hub/content/changelog/2026-07-15-pyth-pro-websocket-filters.mdx

@@ -10,13 +10,13 @@ New Pyth Pro users can now see what their plan includes, review a ready-to-run
 API request for their key, and send that request directly from Pyth Terminal —
 without leaving the app to piece together a curl command.
 
-Why it matters: the fastest path to your first successful call is now built
-in. Instead of assembling the endpoint, headers, and channel arguments by
-hand, you can copy or execute the exact call that will work with your key,
+**Why it matters:** the fastest path to your first successful call is now
+built in. Instead of assembling the endpoint, headers, and channel arguments
+by hand, you can copy or execute the exact call that will work with your key,
 and immediately see the response shape.
 
-What to do: sign in to Pyth Terminal and open the onboarding walkthrough on
-first launch, or revisit the getting-started guide at any time. Existing
+**What to do:** sign in to Pyth Terminal and open the onboarding walkthrough
+on first launch, or revisit the getting-started guide at any time. Existing
 integrations are unchanged.
 
 - [Getting Started with Pyth Pro](/price-feeds/pro/getting-started)

apps/developer-hub/content/changelog/2026-08-04-entropy-chainlist-drops-deprecated-networks.mdx

@@ -10,13 +10,13 @@ Sui mainnet apps can now consume a sponsored `XAGM/USD.RR` push feed without
 running their own price pusher. The feed is Pro-compatible and updates on the
 sponsored Sui push schedule alongside the rest of the Sui sponsored list.
 
-Why it matters: sponsored push feeds are automatically kept fresh on-chain by
-Pyth infrastructure, so integrators do not have to build or operate a pusher
-just to read a live price on Sui.
+**Why it matters:** sponsored push feeds are automatically kept fresh on-chain
+by Pyth infrastructure, so integrators do not have to build or operate a
+pusher just to read a live price on Sui.
 
-What to do: read `XAGM/USD.RR` on Sui the same way as any other sponsored feed
-— point at the standard Sui Pyth price feed object and use the feed ID listed
-on the push-feeds page. Existing feed integrations are unchanged.
+**What to do:** read `XAGM/USD.RR` on Sui the same way as any other sponsored
+feed — point at the standard Sui Pyth price feed object and use the feed ID
+listed on the push-feeds page. Existing feed integrations are unchanged.
 
 - [Push feeds on Sui](/price-feeds/core/push-feeds/sui)
 - [Push feeds overview](/price-feeds/core/push-feeds)