Seth R. Johnson

I really appreciate this fix! Grepping my sphinx html output for `&#` I see this in about 7 places in [my project's user manual](https://celeritas-project.github.io/celeritas/user/implementation/core-physics/limits.html#_CPPv4N9celeritas6detail12MscStepToGeoE). Could one of the maintainers (@michaeljones...

Perhaps we just need to make sure that HTML escapes (into XML) are converted into unicode characters?

@mrguilima Where will this be by the end of today? If necessary we can still leave the 2.0/surface tests disabled but we can't keep wasting time resolving conflicts every week....

@mrguilima Thanks for continuing on this. You're right that there are a lot of combinations. What about we just try to simply fix the [celeritas/field/FieldPropagator:Cmse* test for vecgeom 2 solid](https://github.com/celeritas-project/celeritas/actions/runs/18888421629/job/53909745245?pr=1720),...

@pcanal do we need to add a "surface" vecgeom to codecov as well? 😅 now that it's clear we can build against both surface and solid in a single installation,...

@mrguilima I'm running before-and-after comparisons on GPU for select problems in the benchmark suite; if there are no substantial changes for the vg1 (and if the vg2 cases don't crash)...

Results coming in now. Good news: 1. VecGeom 1.x performance is unaffected by the changes. 2. Some previously hanging vecgeom2 problems now finish in a reasonable number of step iterations....

@lebuller If this is ready to review, could you please merge upstream/develop (there's a few conflicts), mark as "ready", and then @stognini can start reviewing? Thanks!

@lebuller If this is ready for review (it sounded like it was based on your coments?) please merge in the latest upstream, fix the failing CI tests, and mark as...

Tagging https://github.com/celeritas-project/celeritas/issues/1397 : also @lebuller can you sketch out on that page the execution plan we discussed? (Or maybe we need to sit down and write one out if we...