Merged
Conversation
…X improvements Migrate use0GBroker hook to BrokerProvider context to eliminate duplicate broker instances. Fix isInitializing lifecycle by fetching ledger data directly via broker instance in initializeBroker, replacing fragile cross-effect handoff. Add cancellation-safe finally block. Key changes: - Extract BrokerProvider with Symbol-based cancellation and self-contained init lifecycle - Add neuronToA0giString for lossless BigInt-to-string conversion - Unify formatNumber across 5 components with optional full-precision mode - Fix XSS: replace dangerouslySetInnerHTML with React.ReactNode - Fix balance validation: use availableBalance instead of totalBalance - Fix scroll: increase threshold to 50px, use refs to avoid stale closures - Centralize minimum deposit constants in limits.ts - Extract ChainAwareDataCache to shared chainCache module Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix spurious chain switch during initial wallet connection by initializing currentChainIdRef as undefined and only recording chainId when wallet is connected - Reset currentChainIdRef on disconnect to prevent false chain switch on reconnection - Remove deprecated use0GBroker hook (no consumers remain) - Remove redundant refreshLedgerInfo effect from OptimizedChatPage - Simplify scroll handler by removing unnecessary refs and using proper useEffect deps Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Replace props-driven auto-advance logic with localStorage-driven step tracking to prevent steps from cascading 1→2→3 on page load when hasProvider and hasBalance are already true. - Change localStorage key from 'chat-onboarding-completed' to 'chat-onboarding-step' storing "1"/"2"/"3"/"completed" - Remove hasProvider/hasBalance props and internal useEffect auto-advance logic from ChatOnboarding component - Move step state management to useChatOnboarding hook with advanceStep/completeOnboarding/resetOnboarding - Make step indicator dots clickable (forward-only persistence) - Remove unnecessary typeof window guards inside useEffect/callbacks Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…egression advanceStep was comparing against React state which gets updated on dot navigation, causing localStorage to regress when viewing earlier steps then clicking forward (e.g. step 3 → dot 1 → dot 2 wrote "2"). Compare against localStorage value instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…y broker support Major refactoring and new features: - Add DepositGuardProvider for centralized deposit flow management - Add model aggregation view with ModelCard and ModelFilters components - Add read-only broker support for browsing without wallet connection - Add new hooks: useChainRestore, useReadOnlyBroker, useWalletGuard - Refactor BrokerProvider to support both connected and read-only modes - Simplify LayoutContent and useMessageHandling by removing duplicate logic - Extract DepositModal as standalone component - Move Message type to shared broker types - Improve provider management with better type safety - Remove redundant wallet connection checks from chat page - Update all inference pages to support read-only browsing Breaking changes: - Provider management hooks now require both broker and readOnlyBroker params - LedgerInfo refresh function signature changed Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Ravenyjh
approved these changes
Feb 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.