Support the claim chat Information step (RND-2030)#3017
Open
hugokallstrom wants to merge 1 commit into
Open
Conversation
The agent-driven claim flow can return a ClaimIntentStepContentInformation step (a read-and-acknowledge notice, e.g. emergency accommodation guidance when the home is uninhabitable). The app had no fragment or renderer for it, so the union member fell into the NeedsUpdate branch: SubmitTaskUseCase treated the successful response as a failure, retried 6 times and surfaced an error, dead-ending the claim. Renders the notice as a HedvigNotificationCard (Info/Error styling for the INFO/CRITICAL severities) with the server-driven button title, acknowledged via the claimIntentSubmitInformation mutation. The severity mapping and the rendered step are covered by jvm tests; the render test writes reference PNGs via ImageComposeScene since the AGP screenshot plugin does not support KMP android library targets. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Why
The agent-driven claim flow can return a ClaimIntentStepContentInformation step - a read-and-acknowledge notice, e.g. emergency-accommodation guidance when the member says their home is uninhabitable. The app has no fragment or renderer for that union member, so it falls into the NeedsUpdate branch: SubmitTaskUseCase treats the otherwise-successful response as a failure, retries six times (each retry re-submitting an already-completed step and getting an INTERNAL_ERROR back) and dead-ends the claim with an error. First hit by a real fire-claim test on staging 2026-07-10.
What
🤖 Generated with Claude Code