Consolidate AgentZero status into a Context by adhorodyski · Pull Request #85535 · Expensify/App

adhorodyski · 2026-03-17T13:28:37Z

Explanation of Change

This PR replaces three scattered modules managing Concierge/AgentZero status with a single AgentZeroStatusContext using a two-level gate pattern:

Outer gate (AgentZeroStatusProvider): A cheap scalar check — if the current report is not a Concierge chat, children render with zero overhead (no hooks, no Pusher, no state).
Inner gate (AgentZeroStatusGate): Owns all logic for Concierge chats: Onyx subscription, Pusher subscription with per-callback cleanup, reasoning state with deduplication, and debounced label updates.

Consumers (ConciergeThinkingMessage, ReportActionCompose) now read from context instead of receiving props drilled through 4 levels (ReportScreen → ReportActionsView → ReportActionsList → ConciergeThinkingMessage).

Deleted modules:

src/hooks/useAgentZeroStatusIndicator.ts (162 lines)
src/libs/ConciergeReasoningStore.ts (122 lines)
Reasoning subscription functions from src/libs/actions/Report/index.ts (~50 lines)

New:

src/pages/inbox/AgentZeroStatusContext.tsx (224 lines)
src/selectors/ReportNameValuePairs.ts — new agentZeroProcessingIndicatorSelector

Tests: 21 new tests replace 3 deleted test files. 15 files changed, +462/-1386 lines.

Note: This PR depends on PR #85355 (useIsInSidePanel) and PR #85356 (Pusher per-callback handles). CI will fail until those merge.

Fixed Issues

$ #84895
PROPOSAL:

Tests

Open Concierge chat → send a message → verify the "thinking" indicator appears with a status label (e.g., "Concierge is looking up...")
Watch the reasoning history expand → tap the chevron to expand/collapse reasoning entries → verify animation works smoothly
Send another message while Concierge is still processing → verify the indicator resets and starts fresh (new request ID clears old reasoning)
Open a non-Concierge chat (any DM, group, or room) → verify no thinking indicator appears and no performance overhead
Open Concierge chat in the side panel → verify the thinking indicator works the same as in the main view
Open Concierge in both main view and side panel simultaneously → send a message → verify both show the indicator in sync
Send a message to Concierge → immediately navigate away before response arrives → navigate back → verify no stale indicators or duplicate subscriptions
Toggle airplane mode on/off during Concierge processing → verify the indicator clears when offline and resumes when back online
Open Concierge → send a message → verify typing indicator still shows below the composer
Log out and log back in → open Concierge → send a message → verify the indicator works fresh with no leaked state from the previous session

Offline tests

N/A

QA Steps

Same as tests, plus:

Open the Concierge DM in the main pane and send a message that triggers AgentZero processing
Wait for the thinking bubble to appear with reasoning entries streaming in — expand it to confirm entries are visible
While AgentZero is still processing, open the side panel showing the same Concierge chat
Send a message in the side panel to dismiss the welcome state
Verify the side panel's thinking bubble appears. New reasoning entries arriving after both panes are open should appear in both.
Once AgentZero finishes and sends its reply, verify both panes clear the thinking bubble and show the final response correctly

Known limitation: The side panel will only show reasoning entries that arrive after it mounts. Earlier entries visible in the main pane won't backfill into the side panel. This is cosmetic — both panes converge once new entries arrive or processing completes. A new user message triggers a new agentZeroRequestID which resets the reasoning chain in both panes anyway.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Replace three scattered modules (useAgentZeroStatusIndicator hook, ConciergeReasoningStore, and Pusher reasoning subscriptions in Report/index.ts) with a single AgentZeroStatusContext that uses a two-level gate pattern: - Outer gate (AgentZeroStatusProvider): cheap scalar check — if not Concierge chat, renders children with no hooks/Pusher/state overhead - Inner gate (AgentZeroStatusGate): owns all logic for Concierge chats: Onyx subscription, Pusher subscription with per-callback cleanup, reasoning state with deduplication, debounced label updates Consumers (ConciergeThinkingMessage, ReportActionCompose) now read from context instead of receiving props drilled through 4 levels. The prop chain ReportScreen → ReportActionsView → ReportActionsList → ConciergeThinkingMessage is eliminated. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

codecov · 2026-03-17T13:50:26Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/libs/actions/Report/index.ts	`67.79% <ø> (-0.48%)`	⬇️
src/pages/inbox/report/ReportActionsList.tsx	`77.40% <ø> (+0.43%)`	⬆️
src/pages/inbox/report/ReportActionsView.tsx	`80.71% <ø> (-0.14%)`	⬇️
src/pages/inbox/report/ReportFooter.tsx	`53.70% <100.00%> (ø)`
src/selectors/ReportNameValuePairs.ts	`100.00% <100.00%> (+100.00%)`	⬆️
src/hooks/useShouldSuppressConciergeIndicators.tsx	`80.00% <80.00%> (ø)`
src/pages/home/report/ConciergeThinkingMessage.tsx	`1.88% <50.00%> (+1.88%)`	⬆️
src/pages/inbox/AgentZeroStatusContext.tsx	`97.50% <97.50%> (ø)`
...report/ReportActionCompose/ReportActionCompose.tsx	`69.32% <75.00%> (+0.42%)`	⬆️
src/pages/inbox/ReportScreen.tsx	`70.95% <77.77%> (-0.24%)`	⬇️
... and 189 files with indirect coverage changes

The new eslint-config-expensify@2.0.107 enforces context-provider-split-values: contexts must not mix data and functions in a single provider. Split AgentZeroStatusContext into: - AgentZeroStatusStateContext: {isProcessing, reasoningHistory, statusLabel} - AgentZeroStatusActionsContext: {kickoffWaitingIndicator} Export useAgentZeroStatus() for state and useAgentZeroStatusActions() for actions. Update ReportActionCompose to use the actions hook. Update tests to use the appropriate hook per test case — state-only tests use useAgentZeroStatus(), tests needing both spread inline. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…atus-context # Conflicts: # src/hooks/useAgentZeroStatusIndicator.ts # src/pages/inbox/ReportScreen.tsx

melvin-bot · 2026-03-18T13:24:11Z

@DylanDylann Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

src/pages/home/report/ConciergeThinkingMessage.tsx

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7c1c53a639

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

src/pages/inbox/AgentZeroStatusContext.tsx

src/pages/inbox/report/ReportActionsList.tsx

src/pages/inbox/report/ReportActionCompose/ReportActionCompose.tsx

adhorodyski · 2026-03-18T16:11:49Z

Marked as HOLD, SQ fixes that this PR needs will likely get reverted. I'll keep monitoring with @szymonzalarski98.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

trjExpensify · 2026-03-18T16:28:17Z

PR doesn’t need product input as a performance PR. Unassigning and unsubscribing myself.

…me state Self-derive shouldSuppressIndicators inside AgentZeroStatusGate using side-panel context and report actions, then expose it via useAgentZeroStatus(). ConciergeThinkingMessage and a new AgentZeroAwareTypingIndicator wrapper consume the flag to hide indicators until the user sends a message. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

src/pages/inbox/AgentZeroStatusContext.tsx

src/pages/home/report/ConciergeThinkingMessage.tsx

src/pages/inbox/AgentZeroStatusContext.tsx

DylanDylann · 2026-03-23T09:29:45Z

Open Concierge in both main view and side panel simultaneously → send a message → verify both show the indicator in sync

@adhorodyski I’m curious about how to simulate this test case. Could you help me?

DylanDylann · 2026-03-24T07:11:59Z

Open Concierge → send a message → verify typing indicator still shows below the composer

@adhorodyski It still doesn’t work on my side.

DylanDylann · 2026-03-24T07:12:25Z

@adhorodyski Could you please add video evidence?

adhorodyski · 2026-03-24T13:07:51Z

~~Looks like this does not show up in production either, my bad. Updating the description now.~~

edit: validating this now with Rodrigo.

adhorodyski · 2026-03-24T14:43:46Z

@rlinoz will be posting a video recording from his repro, this works as expected. The LLM-oriented workflows do not trigger pusher's typing indicator payloads.

github-actions · 2026-03-24T15:22:06Z

🚧 @rlinoz has triggered a test Expensify/App build. You can view the workflow run here.

rlinoz · 2026-03-24T15:33:15Z

I think this is working as intended, the typing shows when someone is actually typing.

Screen.Recording.2026-03-24.at.12.28.33.mov

Regarding the RHP, it doesn't show the typing in prod either so all good I think

DylanDylann · 2026-03-25T07:27:29Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Screen.Recording.2026-03-25.at.15.41.20.mov

Android: mWeb Chrome

Screen.Recording.2026-03-25.at.15.12.34.mov

iOS: HybridApp

Screen.Recording.2026-03-25.at.15.39.34.mov

iOS: mWeb Safari

Screen.Recording.2026-03-25.at.15.04.32.mov

MacOS: Chrome / Safari

Screen.Recording.2026-03-25.at.15.01.05.mov

DylanDylann · 2026-03-25T07:30:52Z

src/hooks/useShouldSuppressConciergeIndicators.ts

+        }
+        return Object.values(actions).some((action) => !isCreatedAction(action) && action.actorAccountID === currentUserAccountID && action.created >= sessionStartTime);
+    };
+    // eslint-disable-next-line rulesdir/no-inline-useOnyx-selector -- React Compiler handles memoization


Could we remove this disabled line?

I think so, looks like an artifact from Opus. Doing this now.

pushing a fix, thanks

DylanDylann · 2026-03-25T07:51:10Z

@rlinoz I discovered a BE bug (also happens on main):

Steps to reproduce: Send a message to Concierge → navigate away before the response arrives → navigate back → the old ConciergeThinkingMessage briefly appears, disappears, and then immediately appears again.

RCA: When returning to Concierge, the old reportNameValuePairs?.agentZeroProcessingRequestIndicator is still present. Then the openApp API resets it to empty, and shortly after, Pusher updates it again with a new value.

Screen.Recording.2026-03-25.at.14.41.03.mov

DylanDylann

LGTM

adhorodyski · 2026-03-25T09:20:06Z

@rlinoz still working on the last comment from @DylanDylann, please HOLD with a merge in case you wanted to.

DylanDylann · 2026-03-25T09:21:44Z

@adhorodyski I think this is a minor issue and can be handled quickly 😄, so I’ve approved it in advance.

- key={reportID} resets all state on report change (PERF-7), deletes reset effect - Render-time derivations replace effects for clearing optimistic/reasoning state - displayedLabelRef mirrors state so label effect drops displayedLabel dep - addReasoning in Pusher deps, compiler auto-memoizes it Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

adhorodyski · 2026-03-25T11:02:39Z

@DylanDylann updated to make everything pass the compiler check, I believe it's way more correct now at the same time. Tests fine manually as well.

github-actions · 2026-03-25T11:23:00Z

🚧 @rlinoz has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-03-25T11:27:18Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #85535.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-ad37d54-15c7bec-c0f3778a6e11091a6078c0520850e6c1cc57d644/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-ad37d54-15c7bec-a67cd263d6411fd7f41c8501ffed5f096f7bfffb/index.html

Web 🕸️
https://85535.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-25T11:30:13Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-03-25T16:40:00Z

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.3.44-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

OSBotify · 2026-03-25T18:52:15Z

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.3.47-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

OSBotify · 2026-03-26T14:17:36Z

🚀 Deployed to production by https://github.com/grgia in version: 9.3.48-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

melvin-bot bot assigned adhorodyski Mar 17, 2026

adhorodyski force-pushed the decompose/agent-zero-status-context branch from 964e83a to bbc1155 Compare March 17, 2026 13:31

adhorodyski changed the title ~~[No QA] Consolidate AgentZero status into a shared context provider~~ Consolidate AgentZero status into a shared context provider Mar 17, 2026

adhorodyski and others added 3 commits March 17, 2026 15:20

Merge remote-tracking branch 'exfy/main' into decompose/agent-zero-st…

e152383

…atus-context # Conflicts: # src/hooks/useAgentZeroStatusIndicator.ts # src/pages/inbox/ReportScreen.tsx

chore: trigger CI re-run after upstream merge

7c1c53a

adhorodyski marked this pull request as ready for review March 18, 2026 13:24

adhorodyski requested review from a team as code owners March 18, 2026 13:24

melvin-bot bot requested a review from DylanDylann March 18, 2026 13:24

melvin-bot bot requested review from trjExpensify and removed request for a team March 18, 2026 13:24

github-actions bot reviewed Mar 18, 2026

View reviewed changes

src/pages/home/report/ConciergeThinkingMessage.tsx Show resolved Hide resolved

chatgpt-codex-connector bot reviewed Mar 18, 2026

View reviewed changes

src/pages/inbox/AgentZeroStatusContext.tsx Show resolved Hide resolved

src/pages/inbox/report/ReportActionsList.tsx Show resolved Hide resolved

src/pages/inbox/report/ReportActionCompose/ReportActionCompose.tsx Outdated Show resolved Hide resolved

rlinoz self-requested a review March 18, 2026 14:16

adhorodyski changed the title ~~Consolidate AgentZero status into a shared context provider~~ [HOLD] Consolidate AgentZero status into a Context Mar 18, 2026

Use imported ReasoningEntry type instead of inline duplication

498a5bd

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

trjExpensify removed their request for review March 18, 2026 16:28

adhorodyski and others added 2 commits March 18, 2026 18:28

Merge branch 'Expensify:main' into decompose/agent-zero-status-context

ff6322c

adhorodyski changed the title ~~[HOLD] Consolidate AgentZero status into a Context~~ Consolidate AgentZero status into a Context Mar 19, 2026

DylanDylann reviewed Mar 23, 2026

View reviewed changes

src/pages/inbox/AgentZeroStatusContext.tsx Show resolved Hide resolved

src/pages/home/report/ConciergeThinkingMessage.tsx Outdated Show resolved Hide resolved

DylanDylann reviewed Mar 23, 2026

View reviewed changes

src/pages/inbox/AgentZeroStatusContext.tsx Outdated Show resolved Hide resolved

src/pages/inbox/AgentZeroStatusContext.tsx Show resolved Hide resolved

Merge branch 'Expensify:main' into decompose/agent-zero-status-context

b93412a

This comment has been minimized.

Sign in to view

DylanDylann reviewed Mar 25, 2026

View reviewed changes

DylanDylann approved these changes Mar 25, 2026

View reviewed changes

remove eslint disable from useShouldSuppressConciergeIndicators

72d3c69

adhorodyski changed the title ~~Consolidate AgentZero status into a Context~~ HOLD Consolidate AgentZero status into a Context Mar 25, 2026

adhorodyski changed the title ~~HOLD Consolidate AgentZero status into a Context~~ Consolidate AgentZero status into a Context Mar 25, 2026

rlinoz approved these changes Mar 25, 2026

View reviewed changes

rlinoz merged commit ad37d54 into Expensify:main Mar 25, 2026
34 checks passed

OSBotify mentioned this pull request Mar 25, 2026

Deploy Checklist: New Expensify 2026-03-25 #86329

Closed

71 tasks

melvin-bot bot mentioned this pull request Mar 26, 2026

Decompose ReportScreen #84895

Open

adhorodyski mentioned this pull request Mar 28, 2026

[No QA] Add CLEAN-REACT-PATTERNS-6: guard wrappers for conditional subtrees #86610

Draft

52 tasks

Conversation

adhorodyski commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov bot commented Mar 17, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot bot commented Mar 18, 2026

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

adhorodyski commented Mar 18, 2026

Uh oh!

trjExpensify commented Mar 18, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

DylanDylann commented Mar 23, 2026

Uh oh!

DylanDylann commented Mar 24, 2026

Uh oh!

DylanDylann commented Mar 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adhorodyski commented Mar 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adhorodyski commented Mar 24, 2026

Uh oh!

github-actions bot commented Mar 24, 2026

Uh oh!

This comment has been minimized.

rlinoz commented Mar 24, 2026

Uh oh!

DylanDylann commented Mar 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

DylanDylann Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

adhorodyski Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

adhorodyski Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann commented Mar 25, 2026

Uh oh!

DylanDylann left a comment

Choose a reason for hiding this comment

Uh oh!

adhorodyski commented Mar 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DylanDylann commented Mar 25, 2026

Uh oh!

adhorodyski commented Mar 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Mar 25, 2026

Uh oh!

adhorodyski commented Mar 17, 2026 •

edited

Loading

codecov bot commented Mar 17, 2026 •

edited by github-actions bot

Loading

DylanDylann commented Mar 24, 2026 •

edited

Loading

adhorodyski commented Mar 24, 2026 •

edited

Loading

DylanDylann commented Mar 25, 2026 •

edited

Loading

adhorodyski commented Mar 25, 2026 •

edited

Loading

adhorodyski commented Mar 25, 2026 •

edited

Loading