[WimvandenHeijkant]

Stacked on #1183 (dor/issue-937). Retarget to main once that merges.

What this is

The business-role row view built for #370 — roles as parent rows, their resources drawn and folded underneath, the BR chips, the deviation markers — becomes the opt-in half of #937's wizard checkbox, now called "Show business roles as foldable rows".

• Unticked (the default): the matrix that was there before, minus the business-role rows [FEATURE] Don't who Business Roles as a row in the matrix #937 removed. No fold buttons, no chips, no new markers, plain row order in the Excel export.
• Ticked: each business role gets its own row with the resources it grants underneath it, foldable into it, plus everything [Feature] Collapse managed resources under business roles in the matrix #370 built around that.

This replaces PR #933, which was written against a main that has since extracted accessPackageModel.js, MatrixCell.helpers.js and the row-cell components. The fold, the staircase promotion and the marker strip land in those instead of in the monolith they were written against. #933's implementation stays in the history of dor/issue-370 as the reference.

How the option is enforced

The gate is the data, not a pile of UI conditionals. With no business-role rows on the resource axis, analyseRoleRows finds nothing foldable, no row carries a roleParentId, and every affordance disappears on its own — fold chevrons, toolbar buttons, chips, "held outside" counts, the under-role export layout.

Two things could have been drawn from the SOLL columns alone, so they take an explicit showBusinessRoles:

• the red + "more than the role assigns" mark, and
• the legend entries for markers a default grid can never draw.

That makes "the default matrix is the old matrix" a property tests pin rather than an emergent one — see the new describe blocks in MatrixView.mount.test.jsx, MatrixGroupRow.mount.test.jsx, MatrixLegend.test.js and matrix-business-role-rows.spec.js.

Reconciling migration 061 with #937's decision 5

Per the scope amendment on #370. No flag of its own was needed: the coverage view's self arm stays unconditional (holding a business role is governed access), and the scope/governed counts follow the flag because the resource axis does — #937's choke point already excludes business-role resources from the pair counts. Pinned in scopeHistory.test.js from both directions.

Fix at the source, not the surface

Two things stayed unconditional on purpose, because they are not about business roles:

• the resizable grid (useViewportFitHeight / useResizableGridHeight / GridResizeHandle) — it also fixes a page-overflow the current measurement still has;
• the cell marker strip geometry, which stops markers overlapping their neighbours' badges.

One behaviour change reaches the default matrix: the Gaps row filter now uses the same comparison as the amber ! marker, so the Gaps view and the marker can no longer disagree. Previously the filter flagged rows the marker did not.

Tests

• UI 1498 passed, API 2735 passed; both coverage suites green against their thresholds.
• New mutation scope app/ui/stryker.roles.config.json for coverageDeviation.js + useBusinessRoleFold.js — measured 93.54% (333 killed / 21 survived / 2 unkillable-by-construction), floor 90, registered in the weekly workflow. The five presentational/measurement files that landed with the feature are excluded with written reasons.
• The two ratchets written in Python (file length, complexity) could not be run locally — no working interpreter on this box — so CI is the first check on those.

🤖 Generated with Claude Code

[WimvandenHeijkant]

Folded into #933, which is now the single PR for this work — #937 and #370 were merged into one item at the requestor's request. Same tree, rebased onto current main; this branch is no longer needed.