fix(consumers): align staking and lifecycle reads with the v0.6 producer

[cgmello]

Problem and outcome

The combined v0.6 producer changes staking reward-field names, claim/commit widths, several staking ABI selectors/events, and the lifecycle return tuple. This updates the existing consumer PR for Consensus #1634 at c4749a42095bcfb9de69bef4f4fd5e9a6a2f86f2 (above #1628), preserving the original live → hasUnclaimedRewards implementation.

• Keep reward state independent of bans/selectable eligibility; test both boolean values and omit the old alias.
• Decode Claim quantity/offset and Commit outstanding as uint256; producer-derived fixtures exercise values above uint120.
• Reconcile the existing staking ABI subset, including changed administrative signatures and removed obsolete entries. Existing error signatures match the producer.
• Include lifecycle executionGeneration, exposed as an exact decimal string when supplied; older Studio APIs leave it absent.
• Discover canonical child IDs through parent-filtered Messages events, including deferred delivery beyond 10,000 blocks; paginate requested history, deduplicate IDs, and propagate RPC errors. Optional fromBlock bounds historical scanning. This is creation history from the registered Messages contract, not current-generation membership or completion.
• Document public migration, exact-commit package selection, and remaining runtime work in docs/consumer-migration-v06.md.

Delivery context

Depends-On: genlayerlabs/genlayer-py#116
Depends-On: genlayerlabs/genlayer-e2e#781
Depends-On: genlayerlabs/genlayer-dev-env#145

Studio draft #1771 pins this SDK head in both applications and carries the initial polling adaptation.

Darien's #145 is the single dev-env source: it includes #147 and merged #148. This replaces the previous #147 edge. The implemented Node cut must select Consensus #1634 and this consumer closure; no reverse Node/Consensus edge is added here. SDK #201, #215 and #221 remain separate work; their changes are not duplicated.

The September 11 frozen consumer cut and its green E2E result are historical. This explicitly supersedes that source selection with the updated head and #145 dependency. No new landing cut is frozen and no E2E/merge is requested. Node #1955/#1956 need synchronization with their current lower heads before final qualification.

Validation

At 2bc5e60052d4a5ef2fef4d9f6931014ca15f20b1:

• npx vitest run --typecheck: 14 files, 200 tests passed, no type errors.
• npm run build: ESM/CJS/declarations passed.
• Focused ESLint on changed transaction source/tests: passed; full lint passed on the preceding commit.
• Producer ABI subset comparison and git diff --check: passed.

The checked-in producer fixture records its exact source revision. No final artifacts/presets or deployed-runtime compatibility are claimed. Tagged npm publication remains a separate release action; downstream consumers can pin this exact commit with regenerated lockfiles.

Remaining qualification / rollback

Keep this draft. Integrated deferred-child journeys, delivery-completion APIs, generation-aware UI receipt invalidation, final source/preset provenance, and cross-repository deploy/read/write/appeal/recompute journeys remain tracked in the migration guide. Parent finalization and child creation events do not prove all terminal obligations complete. No new full E2E was run.

Rollback the new commit together with downstream package pins; do not pair the old lifecycle decoder with a producer requiring the new return layout.

Node changes are explicitly excluded from this follow-up; no Node code, branches, PRs, or dependency pins were modified.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: af3baac8-125a-47ba-8dac-be4dd1d2d024

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cgmello]

Selected consumer full-E2E cut: genlayer-js #220. Frozen direct closure:

• genlayer-js fix(consumers): align staking and lifecycle reads with the v0.6 producer #220: 53f3a834ae29c6e9b602b303f2e00938d5b1a277 → v2-dev
• genlayer-py fix(transactions): handle all DECIDED states in waitForTransactionReceipt #116: 29609f79091e3728a429fb7376bb2dcf22df4cc5 → v0.19-dev
• genlayer-e2e #781: 59fe19d8ce25f6ff19a66d99ac24b63cbe9f107a → main
• genlayer-dev-env fix: handle object response from gen_call on testnet #147: 7aabddf9562b5786824e40fce8e1b4cf906eb19d → main

All four PRs are mergeable. JS/Python/harness native CI is green; dev-env build/vet/tests pass and it has no native CI workflow. No existing E2E run exists for this consumer cut; its checks are unrequested placeholders. Full scope will use the v0.6 matrix for core components and all configured stacks. This is test qualification only; consensus #1595 and final delivery remain separate.

[cgmello]

/run-e2e all

[cgmello]

/run-e2e all

[ci-core-e2e-runner]

Test only — nothing will merge.
genlayerlabs/genlayer-dev-env#147 into genlayerlabs/genlayer-dev-env@main (v0.6).
genlayerlabs/genlayer-e2e#781 into genlayerlabs/genlayer-e2e@main (v0.6).
#220 into genlayerlabs/genlayer-js@v2-dev (v0.6).
genlayerlabs/genlayer-py#116 into genlayerlabs/genlayer-py@v0.19-dev (v0.6).
Descendants and sibling branches are not included.