chore(docs): wholesale refresh (#1384)

Author: nikerzetic-aflabs

docs/2-run-node.mdx

@@ -68,7 +68,8 @@ You can track validator status, uptime, and software versions on the [Flare Vali
 
 Runs alongside a Validator to provide crucial data for Flare's FTSO and FDC protocols.
 Required for full reward eligibility.
-Requires a running [Validator Node](#validator-node). To set up a Flare Entity:
+Requires a running [Validator Node](#validator-node).
+To set up a Flare Entity:
 
 <DocCardList
   items={[

docs/fassets/developer-guides/1-fassets-asset-manager-address-contracts-registry.mdx

@@ -8,6 +8,9 @@ sidebar_position: 1
 ---
 
 import ExploringAdditionalParameters from "./_exploring-additional-parameters.mdx";
+import MainnetNote from "./_mainnet-note.mdx";
+
+<MainnetNote />
 
 ## Overview
 

docs/fassets/developer-guides/11-fassets-redeem.mdx

@@ -252,7 +252,7 @@ main().catch((error) => {
 To run the script, use the [Flare Hardhat Starter Kit](/network/guides/hardhat-foundry-starter-kit) with the following command:
 
 ```bash
-npx hardhat run scripts/fassets/getLotSize.ts --network coston2
+yarn hardhat run scripts/fassets/redeem.ts --network coston2
 ```
 
 Once the script is executed, two events hold the important information:
@@ -293,9 +293,9 @@ RedemptionRequested Result {
 
 When decoding an event, the most important data from the event is:
 
-- The agent vault address that will redeem the FAssets is `0x3c831Fe4417bEFFAc721d24996985eE2dd627053`;
+- The agent vault address that will redeem the FAssets is `0xaADbF766Fd9131996C7B270A0cCB2b5c88Fc810D`;
 - The redeemer address is `0xCA7C9fBbA56E44C508bcb4872775c5fEd169cDb3`;
-- The redemption ticket id is `1898730`;
+- The redemption ticket id is `1628`;
 - The underlying chain address is `rSHYuiEvsYsKR8uUHhBTuGP5zjRcGt4nm`;
 - The amount of FAssets to redeem is `20000000`;
 - The redemption fee is `20000`;
@@ -322,9 +322,9 @@ RedemptionTicketUpdated Result {
 
 Once decoding the most important data from the event is:
 
-- The agent vault address that will redeem the FAssets is `0x3c831Fe4417bEFFAc721d24996985eE2dd627053`;
-- The redemption ticket id is `870`;
-- The value of the redemption ticket in underlying chain currency is `3440000000` (partially redeemed).
+- The agent vault address that will redeem the FAssets is `0xaADbF766Fd9131996C7B270A0cCB2b5c88Fc810D`;
+- The redemption ticket id is `1628`;
+- The value of the redemption ticket in underlying chain currency is `5360000000` (partially redeemed).
 
 You can read the full event description [here](/fassets/reference/IAssetManagerEvents#redemptionticketupdated).
 

docs/fassets/developer-guides/12-fassets-swap-redeem.mdx

@@ -117,6 +117,8 @@ To execute the swap and redeem process, you need to deploy the smart contract in
 
 - **4. Approve Tokens**
   - Uses the ERC-20 `approve` method to allow the contract to spend WCFLR.
+    The approved allowance must cover `amountIn` (the WCFLR being spent), not `amountOut` (the FXRP received).
+    The current starter script over-approves on `amountOut`; a follow-up starter PR will switch it to `amountIn`.
     :::warning
     In a production environment, you should use a secure method to approve spending the tokens.
     :::
@@ -129,7 +131,7 @@ To execute the swap and redeem process, you need to deploy the smart contract in
 To run the script, use the [Flare Hardhat Starter Kit](/network/guides/hardhat-foundry-starter-kit) with the following command:
 
 ```bash
-npx hardhat run scripts/fassets/swapAndRedeem.ts --network coston
+yarn hardhat run scripts/fassets/swapAndRedeem.ts --network coston2
 ```
 
 The script outputs transaction details, including swap amounts and redemption results.

docs/fassets/developer-guides/15-fassets-redemption-queue.mdx

@@ -46,7 +46,7 @@ The [`redemptionQueue`](/fassets/reference/IAssetManager#redemptionqueue) functi
 Each `RedemptionTicketInfo` includes:
 
 - `agentVault`: address of the backing agent.
-- `valueUBA`: value in underlying base amount.
+- `ticketValueUBA`: value of the ticket in underlying base amount (UBA).
 - `lots`: number of lots.
 - `createdAt`: creation timestamp.
 
@@ -78,8 +78,8 @@ The script:
 4. Get the `maxRedeemedTickets` value from the system settings (maximum number of tickets that can be redeemed in a single request).
    The actual number of tickets returned may be less than `maxRedeemedTickets` if the queue is shorter.
 5. Get the lot size value from the settings (minimum quantity required for minting FAssets).
-6. Get the redemption queue by calling the contract method `redemptionQueue` starting from `0` and up to `maxRedeemedTickets`.
-   You can paginate over the queue.
+6. Get the redemption queue by calling the contract method `redemptionQueue(_firstRedemptionTicketId, _pageSize)` — passing `0` as the first id starts at the **beginning of the queue** (it does not refer to ticket index `0`).
+   The method returns `(_queue, _nextRedemptionTicketId)`; use `_nextRedemptionTicketId` to paginate.
 7. Sum all ticket values in the redemption queue to calculate the total value in UBA (Underlying Asset Base Amount)
 8. Calculate the total lots in the redemption queue by dividing the total value by the lot size.
 

docs/fassets/developer-guides/3-fassets-settings-solidity.mdx

@@ -97,7 +97,7 @@ main().catch((error) => {
 Now you can run the script using the Hardhat tool with the following command:
 
 ```bash
-npx hardhat run scripts/fassets/getLotSize.ts --network coston2
+yarn hardhat run scripts/fassets/getLotSize.ts --network coston2
 ```
 
 You should see the following output:
@@ -121,7 +121,8 @@ This script is included in the [Flare Hardhat Starter Kit](https://github.com/fl
 
 ## Summary
 
-Congratulations! You have now deployed a Solidity helper contract and used a TypeScript script to:
+Congratulations!
+You have now deployed a Solidity helper contract and used a TypeScript script to:
 
 - Fetch FAsset FXRP lot size and decimals
 - Convert the value to a user-friendly format using decimal precision.

docs/fassets/developer-guides/4-fassets-settings-node.mdx

@@ -284,7 +284,8 @@ Timestamp: 1756977702
 
 ## Summary
 
-Congratulations! You have built a TypeScript script that connects to the Coston2 network and retrieves the FAsset configuration settings and the price of XRP in USD.
+Congratulations!
+You have built a TypeScript script that connects to the Coston2 network and retrieves the FAsset configuration settings and the price of XRP in USD.
 
 :::tip[What's next]
 

docs/fassets/developer-guides/8-fassets-mint-executor.mdx

@@ -130,7 +130,7 @@ This script demonstrates how to retrieve the FDC proof and execute minting.
 ### Execute Minting Script Breakdown
 
 1. Get environment variables.
-2. Declare the constant `ASSET_MANAGER_ADDRESS` pointing to the FXRP AssetManager on the Songbird Testnet (Coston network).
+2. Resolve the FXRP AssetManager address dynamically on Coston2 by calling `getAssetManagerFXRP()` from the registry helper rather than hard-coding it.
 
 3. Set the collateral reservation ID to the previously reserved minting request.
 4. Set the FDC round ID to retrieve the proof.
@@ -139,7 +139,7 @@ This script demonstrates how to retrieve the FDC proof and execute minting.
    It sends a POST request to the [Flare Data Availability Layer](/fdc/overview#data-availability-layer) and returns a Merkle proof and attestation response from FDC.
 7. Retrieve the FDC proof from the Data Availability Layer.
 8. Call the [`executeMinting`](/fassets/reference/IAssetManager#executeminting) function on the AssetManager contract and send a transaction to the Flare network to convert the attested XRP payment into FXRP (minting).
-9. On a successful transaction call `parseExecutemintingEvents` to extract and log events [`RedemptionTicketCreated`](/fassets/reference/IAssetManagerEvents#redemptionticketcreated) and [`MintingExecuted`](/fassets/reference/IAssetManagerEvents#mintingexecuted).
+9. On a successful transaction call `parseEvents` to extract and log events [`RedemptionTicketCreated`](/fassets/reference/IAssetManagerEvents#redemptionticketcreated) and [`MintingExecuted`](/fassets/reference/IAssetManagerEvents#mintingexecuted).
 
 ## Video Tutorial
 

docs/fassets/developer-guides/_mainnet-note.mdx

@@ -0,0 +1,7 @@
+:::note Network coverage
+
+Examples in this guide target the **Coston2** testnet for safety.
+For Songbird or Flare mainnet, swap the `coston2/` segment of every `@flarenetwork/flare-periphery-contracts/coston2/...` import for `songbird/` or `flare/` respectively, and resolve the AssetManager via the corresponding network's `IFlareContractRegistry`.
+RPC endpoints, faucet links, and the FAssets agents available on each network are listed on the [FAssets overview](/fassets/overview).
+
+:::

docs/fassets/reference/IAgentPing.mdx

@@ -0,0 +1,48 @@
+---
+title: IAgentPing
+sidebar_position: 9
+description: On-chain liveness ping/response between users and FAssets agent bots.
+---
+
+`IAgentPing` exposes a simple ping/response protocol for verifying that an FAssets agent's off-chain bot is alive.
+Users (or anyone) call `agentPing(agentVault, query)` to emit a `AgentPing` event; the bot listens for these events and replies with `agentPingResponse(agentVault, query, response)`, which emits an `AgentPingResponse` event identifying the owner address.
+
+Sourced from `IAgentPing.sol` on [GitHub](https://github.com/flare-foundation/fassets/blob/main/contracts/userInterfaces/IAgentPing.sol).
+
+## Functions
+
+### agentPing
+
+```solidity
+function agentPing(address _agentVault, uint256 _query) external;
+```
+
+Emits an `AgentPing` event addressed at `_agentVault`.
+`_query` is an off-chain-defined identifier that helps the bot decide which kind of response is required (and whether the request is worth responding to at all).
+
+### agentPingResponse
+
+```solidity
+function agentPingResponse(
+    address _agentVault,
+    uint256 _query,
+    string calldata _response
+) external;
+```
+
+Called by the agent owner address in response to an `AgentPing`.
+Emits `AgentPingResponse(agentVault, owner, query, response)`.
+
+## Events
+
+### AgentPing
+
+```solidity
+event AgentPing(address indexed agentVault, address indexed sender, uint256 query);
+```
+
+### AgentPingResponse
+
+```solidity
+event AgentPingResponse(address indexed agentVault, address indexed owner, uint256 query, string response);
+```