feat(shuttle): Add rewind seconds option to EventStreamHubSubscriber

[DeVikingMark]

Why is this change needed?

When Shuttle restarts, there's a risk of missing events that were emitted out of order. Adding a rewindSeconds option allows Shuttle to rewind a few seconds in the event stream when resuming, ensuring no messages are missed. This addresses the issue described in #2172.

Merge Checklist

Choose all relevant options below by adding an x now or at any time before submitting for review

• PR title adheres to the conventional commits standard
• PR has a changeset
• PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
• PR includes documentation if necessary.

---

PR-Codex overview

This PR updates the @farcaster/shuttle package to version 0.6.16, introducing a new feature for event stream management and several configuration changes.

Detailed summary

• Bump version from 0.6.15 to 0.6.16.
• Add rewindSeconds option to EventStreamHubSubscriber to manage event stream rewinding.
• Update README.md with new configuration details for rewindSeconds.
• Change default values for HUB_HOST, POSTGRES_URL, REDIS_URL, and CONCURRENCY in env.ts.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 40dd6a8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​elliptic@​6.6.1 ⏵ 6.6.0		-75
	npm/​@​types/​axios@​0.14.0
	npm/​@​parcel/​watcher-android-arm64@​2.4.1
	npm/​@​parcel/​watcher-darwin-arm64@​2.4.1
	npm/​@​parcel/​watcher-darwin-x64@​2.4.1
	npm/​@​parcel/​watcher-freebsd-x64@​2.4.1
	npm/​@​parcel/​watcher-linux-arm-glibc@​2.4.1
	npm/​@​parcel/​watcher-linux-arm64-glibc@​2.4.1
	npm/​@​parcel/​watcher-linux-arm64-musl@​2.4.1
	npm/​@​parcel/​watcher-linux-x64-glibc@​2.4.1
	npm/​@​parcel/​watcher-linux-x64-musl@​2.4.1
	npm/​@​parcel/​watcher-win32-arm64@​2.4.1
	npm/​@​parcel/​watcher-win32-ia32@​2.4.1
	npm/​@​parcel/​watcher-win32-x64@​2.4.1
	npm/​@​esbuild/​android-arm64@​0.17.11 ⏵ 0.18.20
	npm/​@​esbuild/​android-arm64@​0.17.11 ⏵ 0.17.12				+2
	npm/​@​esbuild/​darwin-arm64@​0.17.11 ⏵ 0.18.20
	npm/​@​esbuild/​darwin-arm64@​0.17.11 ⏵ 0.17.12				+2
	npm/​@​esbuild/​darwin-x64@​0.17.11 ⏵ 0.18.20
	npm/​@​esbuild/​darwin-x64@​0.17.11 ⏵ 0.17.12				+2
	npm/​@​esbuild/​freebsd-arm64@​0.17.11 ⏵ 0.18.20
	npm/​@​esbuild/​freebsd-arm64@​0.17.11 ⏵ 0.17.12				+2
	npm/​@​esbuild/​freebsd-x64@​0.17.11 ⏵ 0.18.20
	npm/​@​esbuild/​freebsd-x64@​0.17.11 ⏵ 0.17.12				+2
	npm/​@​esbuild/​linux-arm@​0.17.11 ⏵ 0.18.20
See 335 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		npm/[email protected] has a Critical CVE. CVE: GHSA-vjh7-7g9h-fjfh Elliptic's private key extraction in ECDSA upon signing a malformed input (e.g. a string) (CRITICAL) Affected versions: <= 6.6.0 Patched version: 6.6.1 From: packages/hub-nodejs/examples/contract-signatures/yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report