data(filecoin): add repair and funding tools

[edras-create]

Summary

Adds four active Filecoin Onchain Cloud tools across the services, SDK, and security catalogs:

• Early Repair CLI for repairing and replicating PDP datasets affected by faulty providers.
• Filecoin Pay Auction Bot for monitoring USDFC Dutch auctions and placing policy-controlled FIL bids.
• Squid EVM Funding, a TypeScript library for planning and executing capped cross-chain token funding routes.
• Session Key Registry for scoped, expiring dApp permissions and EIP-712 signature authorization.

The existing Filecoin Onchain Cloud provider is reused. The changes add 8 CSV rows with 58 populated cells and stay below the grant limits.

Type of change

• Add data rows
• Update data rows
• Remove data rows
• Schema change
• Documentation/metadata only

Scope

• Networks affected: Filecoin
• Categories affected: services, SDKs, security
• Additional notes: 4 canonical offers and 4 Filecoin listings; no schema or provider changes

Duplicate audit

• Searched the current repository and all open and closed Chain.Love pull requests for repository names, package names, offer names, and proposed slugs.
• No matching or competing entries were found.
• A separate candidate set was intentionally excluded after finding it already claimed by open PR feat(filecoin): add Onchain Cloud analytics explorers #2933.

Sources

• https://github.com/FilOzone/early-repair/tree/main/packages/repair-cli
• https://github.com/FilOzone/filecoin-pay-auction-bot
• https://github.com/FilOzone/squid-evm-funding
• https://github.com/FilOzone/SessionKeyRegistry

Validation checklist

• I followed the Style Guide and Column Definitions.
• I personally opened and verified every new link.
• I confirmed the provider currently supports Filecoin and checked every changed cell against the official repositories.
• Repository pre-commit validation passed, including CSV width, sorting, uniqueness, JSON generation, and schema checks.

This contribution was AI-assisted and manually source-checked against the official FilOzone repositories.

Optional

• Rewards address (ERC-20): 0x60079059d9E623fC87b69124Ccb6E4671124a834
• Twitter (X) post link: N/A

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	4
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	4
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[USS-Supervisor]

Verdict: COMMENT
Risk: LOW
Summary: I checked the added Filecoin SDK/security/service rows against the repository data model. The CSV widths are stable, git diff --check is clean, the added listing rows resolve to the new canonical !offer: slugs, existing Filecoin/Filecoin Onchain Cloud provider references are present, and I did not find duplicate slug or chain-logo issues.
Findings: No data-integrity findings from static review. I cannot approve this cycle because the current-cycle link-check run did not appear within the 5-minute budget after resetting check-links; the only observed clean run was the earlier stale 2026-08-24 15:03 UTC run.
Confidence: HIGH

[USS-Supervisor]

Hi @eugene17kotov - this stale PR looks ready for reviewer action. Required CI is passing, and I do not see a current creator-side blocker. I requested your review; could you please take a look when you have a chance?

[USS-Supervisor]

@eugene17kotov following up on this stale PR. Required CI is passing and I do not see a blocking review, so it still looks ready for reviewer action when you have a chance.

[USS-Supervisor]

@edras-create this PR has been idle for more than 3 days after review feedback, and I do not see a newer commit addressing it. Please address the feedback and update the PR when ready.