Fold PR #72 into PR #29 — consolidate the DIN-Indexer work before #153's handlers land

[umeradl]

@robertocarlous: proposal to consolidate the indexer work into a single PR before the #153 subgraph handlers land on it (task_240926_16 Part C).

Where things stand

Checked 2026-09-24 against develop @ d321c2a.

	Head	Base	Commits	Files
PR #29	robertocarlous:feat/din-indexer @ 866521a (2026-07-14)	feat/din-indexer	18	26
PR #72	robertocarlous:feat/din-indexer-65 @ 1a2a877 (2026-08-04)	feat/din-indexer	43	185

• feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72 is stacked on feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29. It contains all 18 of feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29's commits plus 25 more, so feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29 → feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72 is a clean fast-forward.
• Of those 25 extra commits, only 2 are new indexer work:
  • 2b015f5: documents the 1000-result GraphQL cap and adds subgraph/scripts/update-subgraph-addresses.sh.
  • 1a2a877: wires the P3-staking events into the subgraph (ValidatorJailed/Reactivated, MinStakeUpdated, ModelStakeBoundsUpdated, MaxConcurrentRegistrationsPerStakeUnitUpdated, JailEvent entity).
• The other 23 came in through the origin/feat/p3-staking merge (ecdd87b), and every one of them is already on develop. That's why feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72 shows 185 files. Its real diff is small.
• The base branch feat/din-indexer is 230 commits behind develop. It's a strict ancestor, so it can fast-forward.
• Merging develop into feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72's head is conflict-free (checked with git merge-tree). After that, the only non-subgraph/ differences from develop are 4 files:
  • Developer/issues/indexer.md
  • Documentation/technical/audits/task-contract-event-audit.md
  • dincli/cli/dindao.py
  • tests/test_list_pending_requests.py
• The staking event signatures feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72's subgraph.yaml handles still match develop's DinValidatorStake (ValidatorSlashed, ValidatorJailed, ModelStakeBoundsUpdated, etc.).

Proposed steps

1. @robertocarlous: fold feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72 into feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29.
   • On your fork: git checkout feat/din-indexer && git merge --ff-only feat/din-indexer-65 && git push.
   • feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29 then carries feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72's work. Close feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72 with a "folded into feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29" note.
2. @umeradl: fast-forward the base branch. Move the upstream feat/din-indexer to develop, so feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29's diff only shows indexer changes rather than 230 commits of develop history.
3. @robertocarlous: refresh feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29 against develop.
   • Merge develop into your feat/din-indexer. It should be conflict-free, as noted above.
   • Regenerate subgraph/abis/ from current develop contracts, and re-check that graph codegen && graph build passes.
4. Then feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29 is the home for task_240926_16 Part C5. The six Add missing task-level Solidity events to unblock 5 subgraph handlers #153 handlers, the GIstates enum-mapping regeneration, the RewardDeposited handler, and the ETHTreasuryWithdrawn stub go on as further commits to feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29, not as a separate PR.

Coverage gaps to note (not blocking the consolidation)

DinValidatorStake on develop now emits several events that #72 doesn't handle yet:

• UnbondingPeriodUpdated
• SlashTreasuryUpdated
• EncryptionKeyRegistered
• ActiveRegistrationIncremented/Decremented
• the S5/S6 events: S5RecidivismParamsUpdated, ValidatorEscalatedS5, S6ParamsUpdated, S6NoParticipationRecorded, S6PartialSlashFired

Worth a pass once step 3 is done. Doing it in the same refresh is fine if it's small; otherwise list it in #29's description as a follow-up.

Related: #24 (Start DIN-Indexer), #153 (task-level events), task_240926_16 Part C.

[umeradl]

@robertocarlous: step 2 is done. The upstream feat/din-indexer has been fast-forwarded to develop (805ce9d → d321c2a, a normal non-force push).

You're clear to do steps 1 and 3:

1. Fold feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72 into feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29: git checkout feat/din-indexer && git merge --ff-only feat/din-indexer-65 && git push on your fork, then close feat(indexer): wire P3-staking events — ValidatorJailed/Reactivated, governable MIN_STAKE, JailEvent entity #72 as folded into feat(indexer): implement DIN Protocol subgraph — platform + task-level contracts #29.
2. Merge develop into your feat/din-indexer (conflict-free as of d321c2a), regenerate subgraph/abis/, and re-run graph codegen && graph build.

#29 and #72 still show their old commit/file counts. GitHub hasn't recomputed them against the new base yet, and they should reflect it once you push. After step 3, #29's diff against feat/din-indexer should only contain the indexer work.

This is also tracked as task_240926_16 Part C0.