refactor(recovery-step2): mirror InquiryStep2's spatial-context layout#253
Merged
Conversation
Brings RecoveryStep2 in line with InquiryStep2 (#246 / #247 / #249): - 3-col grid at xl+ (addresses list / form / map), single-column stack below xl so the form doesn't get squeezed at midsized viewports. - Map column with the same sticky positioning and explicit height so Mapbox renders against a real container. - Pin click syncs the selected sample so clicking a marker focuses the matching row in the addresses list and form. Recovery samples key on the BAG PAND id rather than a gfm- address id, but the geocoder /address/:id route already accepts PAND and returns a representative address with the building centroid, so pin derivation is the same shape — samples whose building lacks geometry simply don't render a pin. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Summary
Brings
RecoveryStep2in line with the spatial-context layout shipped onInquiryStep2in #246 / #247 / #249.xl+(addresses list / form / map), stacks belowxlso the form isn't squeezed at midsized viewports.Note on PAND keying
Recovery samples store a BAG PAND id (not a gfm- address id). The geocoder's `/api/geocoder/address/:id` route already handles PAND input and returns a representative address with the building centroid, so pin derivation is the same shape as inquiry. Samples whose building lacks geometry simply don't render a pin — same behavior as on the inquiry side.
Test plan
🤖 Generated with Claude Code