Robert Lupton, this is the issue we discussed earlier this week in which the Detector obtained from the Camera has amplifer bboxes that all start at (0, 0) (i.e. they're appropriate for per-HDU images, not full-detector images).  I got the impression you were planning to fix that, so here's a ticket.

I'm adding this as a blocker on DM-16297, just because I want to be able to test there that I'm not breaking the current assembly logic while refactoring it, and I want to make sure the assembly logic is correct before I add that regression test.  That's not a super high priority for me now that we're no longer targeting Gen3 for Camera Bootcamp, but it does mean that if you can verify this works via a one-off test, you can rely on DM-16297 landing soon after for a regression test.