**New Update Dramatically Simplifies Hub Subscriber Design!**

**Shard ID Now Mandatory, Streamlining Client Resumption Across Multiple Shards**

Commit Details:

fix: make shard id required for the hub subscriber (#2623) ## Why is this change needed? It's hard for the client to determine where to resume from if they're subscribed to multiple shards. ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review_ - [x] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard - [x] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets) - [x] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore) - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on making the `shardIndex` parameter required for the `hubSubscriber` and removing the optional `totalShards` parameter. It ensures that the `shardIndex` is always provided when creating instances of `BaseHubSubscriber` and `EventStreamHubSubscriber`. ### Detailed summary - Made `shardIndex` a required parameter in the constructors of `BaseHubSubscriber` and `EventStreamHubSubscriber`. - Removed the optional `totalShards` parameter from both constructors. - Updated the constructor calls to reflect the removal of `totalShards`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->