One PR, one mark. Reusing the section grammar means the UI change is reviewable in one PR. The risk is all in the backend.
Two callers, one bug. Reuse cuts both ways: every project-section bug now has two callers, and the two surfaces render from different caches.
Yes exactly