feat: make Rocket reloadable via on-chain restart trigger

[GTC6244]

Summary

On-chain restart trigger: Adds a serverTrigger(uint256) function to APIConfigFacet (owner-only via LibDiamond.enforceIsContractOwner()) that emits a ServerTriggered event. A new Rust listener (restart.rs) polls for these events and signals the main loop to restart Rocket.

Restart loop: Refactors main() into a restart-aware loop that rebuilds Rocket on signal while preserving long-lived state (signer pool, chain config, CPU monitor, IPFS cache). Includes restart-loop protection (max 3 restarts per 60s window).

Reliability hardening (from pre-landing review):

• Listener retries with exponential backoff on startup failure (up to 5 attempts)
• Propagates error on initial block fetch instead of silently falling back to block 0
• Uses try_send so the listener is never blocked by the main loop
• Saturating arithmetic for block number operations
• Correct off-by-one fix in restart loop protection gate

Files changed

• APIConfigFacet.sol — new serverTrigger() function + ServerTriggered event
• AppStorage.sol — new serverTriggerValue storage slot
• AccountConfig.json / account_config_contract.rs — regenerated bindings
• restart.rs — new event listener module
• main.rs — restart loop, extracted build_rocket() function
• cpu_overload.rs — derive Clone for sharing across restart iterations
• lib.rs — expose restart module

Pre-Landing Review

No critical issues. Adversarial review findings addressed in second commit.

Test plan

• cargo check passes (rustc 1.91)
• Hardhat compiles all 22 Solidity files
• Contract bindings regenerated cleanly (82 ABI entries)
• Manual: deploy to testnet, call serverTrigger(1) from owner, verify server restarts
• Manual: verify restart loop protection trips after 3 rapid restarts

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds an on-chain “restart trigger” mechanism to the AccountConfig diamond and wires a new Rust background listener into lit-api-server so the Rocket server can be cleanly restarted in-process when the contract owner emits a ServerTriggered event.

Changes:

• Added serverTrigger(uint256) (owner-only) + ServerTriggered event to the diamond, plus storage for the trigger value.
• Introduced lit-api-server restart listener (restart.rs) that polls for ServerTriggered and signals main via an mpsc channel.
• Refactored main into a restart-aware loop and preserved long-lived state across restarts (signer pool, chain config, CPU monitor, IPFS cache).

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
lit-api-server/src/restart.rs	New polling listener for on-chain restart events; sends restart signals to main loop.
lit-api-server/src/main.rs	Restart-aware launch loop; extracts build_rocket() and adds loop protection.
lit-api-server/src/lib.rs	Exposes the new restart module.
lit-api-server/src/core/v1/guards/cpu_overload.rs	Makes CpuOverloadMonitor clonable so it can be shared across restarts.
lit-api-server/src/accounts/contracts/AccountConfig.json	Regenerated ABI including ServerTriggered + serverTrigger.
lit-api-server/src/accounts/contracts/account_config_contract.rs	Regenerated Rust bindings to match updated ABI (event/function/error).
lit-api-server/blockchain/lit_node_express/contracts/AccountConfigFacets/AppStorage.sol	Adds serverTriggerValue to diamond storage.
lit-api-server/blockchain/lit_node_express/contracts/AccountConfigFacets/APIConfigFacet.sol	Adds owner-only serverTrigger() and emits ServerTriggered.

---

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