fix(docs): correct broken internal links after restructure

docs/apps/resources/templates.mdx

@@ -71,21 +71,21 @@ This demo serves as the ultimate reference implementation, showcasing every Mini
   <Card
     title="Viral Mini Apps"
     icon="sparkles"
-    href="/mini-apps/growth/build-viral-mini-apps"
+    href="/apps"
   >
     Strategies and examples for building highly shareable, viral mini apps.
   </Card>
   <Card
     title="Data Driven Growth"
     icon="chart-bar"
-    href="/mini-apps/technical-guides/data-driven-growth"
+    href="/apps"
   >
     Learn how to use analytics and Base.dev to optimize your mini app's growth.
   </Card>
   <Card
     title="Optimize Onboarding"
     icon="user-plus"
-    href="/mini-apps/growth/optimize-onboarding"
+    href="/apps"
   >
     Best practices for onboarding users and maximizing retention.
   </Card>

docs/base-account/basenames/basenames-faq.mdx

@@ -107,7 +107,7 @@ Currently, only one address at a time can be linked to a Basename. However, we p
 
 ### 14. I am a builder. How do I integrate Basenames to my app?
 
-If you're a builder looking to integrate Basenames into your app, follow the [Basenames + Wagmi tutorial](/base-account/basenames/basenames-wagmi-tutorial) to get started. If you have ideas for new features or badges that you'd like to integrate with Basenames, we'd love to [hear from you](https://app.deform.cc/form/b9c1c39f-f238-459e-a765-5093ca638075/?page_number=0).
+If you're a builder looking to integrate Basenames into your app, follow the [Basenames + Wagmi tutorial](https://github.com/base/learn-docs) to get started. If you have ideas for new features or badges that you'd like to integrate with Basenames, we'd love to [hear from you](https://app.deform.cc/form/b9c1c39f-f238-459e-a765-5093ca638075/?page_number=0).
 
 ### 15. How do I get a Basename for my app or project?
 

docs/base-account/guides/verify-social-accounts.mdx

@@ -432,7 +432,7 @@ function redirectToVerifyMiniApp(provider: string) {
 }
 ```
 
-After verification, the user returns to your `redirect_uri` with `?success=true`. Run the check again (step 3) and it now returns 200 with a token. If you're building for the Base app, see the [Apps overview](/apps/introduction/overview) for broader app structure and lifecycle guidance.
+After verification, the user returns to your `redirect_uri` with `?success=true`. Run the check again (step 3) and it now returns 200 with a token. If you're building for the Base app, see the [Apps overview](/apps) for broader app structure and lifecycle guidance.
 
 </Step>
 </Steps>

docs/base-chain/api-reference/ethereum-json-rpc-api/eth_getBlockReceipts.mdx

@@ -7,7 +7,7 @@ description: 'Returns all transaction receipts for a block. Use pending for pre-
 Returns all transaction receipts for a given block.
 
 <Warning>
-This method returns HTTP 403 on the public Base RPC endpoints (`mainnet.base.org`, `sepolia.base.org`). It requires a dedicated or third-party RPC provider. See the [node providers page](/base-chain/network-information/node-providers) for options.
+This method returns HTTP 403 on the public Base RPC endpoints (`mainnet.base.org`, `sepolia.base.org`). It requires a dedicated or third-party RPC provider. See the [node providers page](/base-chain/node-operators/node-providers) for options.
 </Warning>
 
 <Tip>

docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx

@@ -106,7 +106,7 @@ Contains the incremental block state changes for this specific Flashblock. Prese
 
 As of v0.8.0, `new_account_balances` and `receipts` are no longer present in the `metadata` object. Only `block_number` remains.
 
-<Card>
+<Card title="Metadata fields">
 <ParamField path="block_number" type="number">Block number as a decimal integer.</ParamField>
 </Card>
 
@@ -116,7 +116,7 @@ As of v0.8.0, `new_account_balances` and `receipts` are no longer present in the
 `metadata.receipts` was removed in v0.8.0. This schema is preserved for reference for older node versions. On v0.8.0+, use [`eth_getTransactionReceipt`](/base-chain/api-reference/ethereum-json-rpc-api/eth_getTransactionReceipt) for polling-based receipt data, or subscribe to [`newFlashblockTransactions`](/base-chain/api-reference/flashblocks-api/newFlashblockTransactions) with `full: true` for a real-time stream of pre-confirmed transaction data including logs.
 </Note>
 
-<Card>
+<Card title="Receipt fields">
 <ParamField path="type" type="string">Transaction type: `0x0` Legacy, `0x1` Access List, `0x2` EIP-1559, `0x7e` Deposit (L1→L2).</ParamField>
 <ParamField path="status" type="string">Transaction status: `0x1` for success, `0x0` for failure.</ParamField>
 <ParamField path="cumulativeGasUsed" type="string">Total gas used in the block up to and including this transaction (hex).</ParamField>
@@ -127,7 +127,7 @@ As of v0.8.0, `new_account_balances` and `receipts` are no longer present in the
 
 ### Log Object
 
-<Card>
+<Card title="Log fields">
 <ParamField path="address" type="string">Contract address that emitted the event.</ParamField>
 <ParamField path="topics" type="string[]">Array of indexed event parameters. Topic 0 is typically the event signature hash.</ParamField>
 <ParamField path="data" type="string">ABI-encoded non-indexed event parameters.</ParamField>
@@ -137,7 +137,6 @@ As of v0.8.0, `new_account_balances` and `receipts` are no longer present in the
 <ParamField path="transactionHash" type="string">Hash of the transaction that emitted this log.</ParamField>
 <ParamField path="transactionIndex" type="string">Index of the transaction in the block (hex).</ParamField>
 <ParamField path="logIndex" type="string">Log's index position within the block (hex).</ParamField>
-<ParamField path="removed" type="boolean">`true` if the log was removed due to a chain reorg.</ParamField>
 </Card>
 
 ### Complete Examples

docs/base-chain/network-information/bridges.mdx

@@ -49,7 +49,7 @@ code to withdraw the assets.
 
 ### For Token Issuers
 
-If you have an ERC-20 token deployed on Ethereum and want to enable bridging to Base, see our guide on [Bridging an L1 Token to Base](/base-chain/quickstart/bridge-token). This covers deploying your token on Base using the standard bridge contracts and getting it listed on the Superchain token list.
+If you have an ERC-20 token deployed on Ethereum and want to enable bridging to Base, see our guide on [Bridging an L1 Token to Base](/base-chain/specs/protocol/bridging/deposits). This covers deploying your token on Base using the standard bridge contracts and getting it listed on the Superchain token list.
 
 ---
 

docs/base-chain/quickstart/deploy-on-base.mdx

@@ -168,6 +168,6 @@ This will return the initial value of the Counter contract's `number` storage va
 ## Next Steps
 
 - Use [wagmi](https://wagmi.sh) or [viem](https://viem.sh) to connect your frontend to your contracts.
-- Learn more about interacting with your contracts in the command line using Foundry from our [Foundry tutorial](/learn/foundry/deploy-with-foundry).
+- Learn more about interacting with your contracts in the command line using Foundry from our [Foundry tutorial](https://github.com/base/learn-docs).
 
 

docs/base-chain/specs/upgrades/ecotone/derivation.mdx

@@ -126,7 +126,7 @@ A deposit transaction is derived with the following attributes:
 - `mint`: `0`
 - `value`: `0`
 - `gasLimit`: `375,000`
-- `data`: `0x60806040523480156100105...` (<a href="/static/bytecode/ecotone-l1-block-deployment.txt">full bytecode</a>)
+- `data`: `0x60806040523480156100105...` (full bytecode)
 - `sourceHash`: `0x877a6077205782ea15a6dc8699fa5ebcec5e0f4389f09cb8eda09488231346f8`,
   computed with the "Upgrade-deposited" type, with `intent = "Ecotone: L1 Block Deployment"
 
@@ -167,7 +167,7 @@ A deposit transaction is derived with the following attributes:
 - `mint`: `0`
 - `value`: `0`
 - `gasLimit`: `1,000,000`
-- `data`: `0x60806040523480156100...` (<a href="/static/bytecode/ecotone-gas-price-oracle-deployment.txt">full bytecode</a>)
+- `data`: `0x60806040523480156100...` (full bytecode)
 - `sourceHash`: `0xa312b4510adf943510f05fcc8f15f86995a5066bd83ce11384688ae20e6ecf42`
   computed with the "Upgrade-deposited" type, with `intent = "Ecotone: Gas Price Oracle Deployment"
 

docs/base-chain/specs/upgrades/fjord/derivation.mdx

@@ -154,7 +154,7 @@ To perform this upgrade, a deposit transaction is derived with the following att
 - `mint`: `0`
 - `value`: `0`
 - `gasLimit`: `1,450,000`
-- `data`: `0x60806040523...` (<a href="/static/bytecode/fjord-gas-price-oracle-deployment.txt">full bytecode</a>)
+- `data`: `0x60806040523...` (full bytecode)
 - `sourceHash`: `0x86122c533fdcb89b16d8713174625e44578a89751d96c098ec19ab40a51a8ea3`
   computed with the "Upgrade-deposited" type, with `intent = "Fjord: Gas Price Oracle Deployment"
 

docs/base-chain/specs/upgrades/isthmus/derivation.mdx

@@ -33,7 +33,7 @@ A deposit transaction is derived with the following attributes:
 - `mint`: `0`
 - `value`: `0`
 - `gasLimit`: `425,000`
-- `data`: `0x60806040523480156100105...` (<a href="/static/bytecode/isthmus-l1-block-deployment.txt">full bytecode</a>)
+- `data`: `0x60806040523480156100105...` (full bytecode)
 - `sourceHash`: `0x3b2d0821ca2411ad5cd3595804d1213d15737188ae4cbd58aa19c821a6c211bf`,
   computed with the "Upgrade-deposited" type, with `intent = "Isthmus: L1 Block Deployment"
 
@@ -81,7 +81,7 @@ A deposit transaction is derived with the following attributes:
 - `mint`: `0`
 - `value`: `0`
 - `gasLimit`: `1,625,000`
-- `data`: `0x60806040523480156100105...` (<a href="/static/bytecode/isthmus-gas-price-oracle-deployment.txt">full bytecode</a>)
+- `data`: `0x60806040523480156100105...` (full bytecode)
 - `sourceHash`: `0xfc70b48424763fa3fab9844253b4f8d508f91eb1f7cb11a247c9baec0afb8035`,
   computed with the "Upgrade-deposited" type, with `intent = "Isthmus: Gas Price Oracle Deployment"
 
@@ -134,7 +134,7 @@ A deposit transaction is derived with the following attributes:
 - `mint`: `0`
 - `value`: `0`
 - `gasLimit`: `500,000`
-- `data`: `0x60806040523480156100105...` (<a href="/static/bytecode/isthmus-operator-fee-deployment.txt">full bytecode</a>)
+- `data`: `0x60806040523480156100105...` (full bytecode)
 - `sourceHash`: `0x107a570d3db75e6110817eb024f09f3172657e920634111ce9875d08a16daa96`,
   computed with the "Upgrade-deposited" type, with `intent = "Isthmus: Operator Fee Vault Deployment"
 

docs/base-chain/specs/upgrades/jovian/derivation.mdx

@@ -45,7 +45,7 @@ A deposit transaction is derived with the following attributes:
 - `value`: `0`
 - `nonce`: `0`
 - `gasLimit`: `447315`
-- `data`: `0x0x608060405234801561001057600080...` (<a href="/static/bytecode/jovian-l1-block-deployment.txt">full bytecode</a>)
+- `data`: `0x0x608060405234801561001057600080...` (full bytecode)
 - `sourceHash`: `0x98faf23b9795967bc0b1c543144739d50dba3ea40420e77ad6ca9848dbfb62e8`,
   computed with the "Upgrade-deposited" type, with `intent = "Jovian: L1Block Deployment"`
 
@@ -126,7 +126,7 @@ A deposit transaction is derived with the following attributes:
 - `value`: `0`
 - `nonce`: `0`
 - `gasLimit`: `1750714`
-- `data`: `0x0x608060405234801561001057600080...` (<a href="/static/bytecode/jovian-gas-price-oracle-deployment.txt">full bytecode</a>)
+- `data`: `0x0x608060405234801561001057600080...` (full bytecode)
 - `sourceHash`: `0xd939cca6eca7bd0ee0c7e89f7e5b5cf7bf6f7afe7b6966bb45dfb95344b31545`,
   computed with the "Upgrade-deposited" type, with `intent = "Jovian: GasPriceOracle Deployment"`
 

docs/get-started/deploy-smart-contracts.mdx

@@ -140,4 +140,4 @@ This will return the initial value of the Counter contract's `number` storage va
 ## Next Steps
 
 - Use [wagmi](https://wagmi.sh) or [viem](https://viem.sh) to connect your frontend to your contracts.
-- Learn more about interacting with your contracts in the command line using Foundry from our [Foundry tutorial](/learn/foundry/deploy-with-foundry).
+- Learn more about interacting with your contracts in the command line using Foundry from our [Foundry tutorial](https://github.com/base/learn-docs).

docs/get-started/learning-resources.mdx

@@ -18,6 +18,6 @@ We will be adding more learning resources to help you build on Base. Stay tuned
 - New educational content
 
 In the meantime, check out the following resources:
-- [Base Account](/base-account/overview/what-is-base-account), [Apps](/apps/quickstart/create-new-app), and [Base Chain](/base-chain/quickstart/why-base) for building on Base.
+- [Base Account](/base-account/overview/what-is-base-account), [Apps](/apps/quickstart/build-app), and [Base Chain](/base-chain/quickstart/why-base) for building on Base.
 - [CryptoZombies](https://cryptozombies.io/) and [Solidity by Example](https://solidity-by-example.org/) for learning Solidity.
 - [Base Prompt Library](/get-started/prompt-library) for building with AI.

docs/get-started/resources-for-ai-agents.mdx

@@ -77,7 +77,7 @@ Once your agent has docs context, point it at the section that matches what you'
 | Building an AI agent on Base | [AI Agents overview](/ai-agents) |
 | Setting up Base MCP wallet access and signing | [Get Started with Base MCP](/ai-agents/quickstart) |
 | Adding payments or onchain transactions | [Make x402 payments](/ai-agents/guides/x402-payments) |
-| Registering an agent for onchain attribution | [Builder Codes for Agents](/ai-agents/guides/agent-builder-codes) |
+| Registering an agent for onchain attribution | [Builder Codes for Agents](/ai-agents/quickstart) |
 | Using AI tools with Base Account | [Base Account quickstart for AI tools](/base-account/quickstart/ai-tools-available-for-devs) |
 | Deploying contracts | [Deploy on Base](/base-chain/quickstart/deploy-on-base) |
 | Building an app on Base | [Build a Base app](/apps/quickstart/build-app) |