feat(actions): add PRESENT_POI action type for Horizon allocations

[MoonBoi9001]

Summary

Add a new action type that posts a POI on-chain to collect indexing rewards from Horizon allocations without closing them. This enables periodic reward collection while keeping allocations active.

The action is named PRESENT_POI (rather than COLLECT) to avoid confusion with TAP receipt collection, since the primary function is posting a proof of indexing on-chain.

Changes

• ActionType.PRESENT_POI enum value - New action type in the actions system (present_poi)
• GraphQL schema - presentPOI mutation and PresentPOIResult type
• Database model validation - PRESENT_POI type support in Action model
• AllocationManager methods - preparePresentPOI, populatePresentPOITransaction, confirmPresentPOI
• presentPOI resolver - With shared helper functions for transaction execution
• CLI support - graph indexer actions queue present_poi ...
• Input validation - POI parameter normalization and block number validation

Usage

# Basic usage - POI is auto-resolved from indexer state
graph indexer actions queue present_poi <deploymentID> <allocationID> -n <network>

# With optional overrides
graph indexer actions queue present_poi <deploymentID> <allocationID> [poi] [force] [blockNumber] [publicPOI] -n <network>

The POI parameters are optional. The system automatically resolves the POI from the indexer's current state. Use force=true only if you need to submit with a zero POI when auto-resolution fails.

Test plan

• CLI unit tests for action input building and validation
• indexer-common unit tests for action querying and filtering
• Manual testing with Horizon allocation on testnet

---

Generated with Claude Code

[tmigone]

Have not reviewed in detail yet, but first comment is I think we should rename from COLLECT to something else. Collect refers generically to any payment type, could be indexing rewards, query fees or something else. Historically also "collect" has been associated with query fees, so this would be confusing I think.

What do you think about switching to something thats more related to what happens to the allocation (poi is posted on chain) and not the side effect (which is rewards are collected). So could be "present/post poi": graph indexer actions queue present-poi ... or something along that vein.

[MoonBoi9001]

Sounds good, will update.