Admin Settings IA stage D part 1: split Governance and Scale, move Front Door to Security

[Paul Lizer (paullizer)]

First part of stage D — the stage that actually moves cards. Targets the feature/admin-settings-ia staging branch.

Two groups are re-homed here, deliberately chosen because both split within a single source pane. That proves the mechanics before the harder cross-pane moves.

What moved

Governance held five cards doing three different jobs → Feature Governance (what is governed) · Policies (the policies themselves) · MCP Governance.

Scale mixed cache config with Cosmos capacity → Redis & Caching · Cosmos.

Azure Front Door left Scale entirely for Security, under a new Network tab. It configures auth and redirect flows, not throughput — it never belonged next to RU autoscaling.

Old #governance and #scale links still resolve, via a new LEGACY_TAB_REDIRECTS map.

The safety mechanism

The split is done by a tool that works line by line and refuses to write unless every source line lands in exactly one output. That's not ceremony — it caught a real bug immediately.

It found a duplicate-ID bug before I could ship it

governance-status sat after the last card in the pane. My tool copies the pane trailer (the closing </div>s) into each new pane — so that div would have been duplicated into three panes with the same id.

The tool refused:

governance.html has content after its last card:
    line 249: <div id="governance-status" class="alert d-none" role="alert"></div>
  Copying it into every new pane would duplicate element ids.

Fixing it properly turned out to also fix a latent UX bug: governance-status is an inline status target written by admin_governance.js. Inside a pane, a message raised while working in Policies could render on a tab you weren't looking at. It now lives outside the tabs and is visible wherever you are in Governance.

Interleaved modals (complication I1)

Scale was the real test: five modals sit between cards, not collected at the end, and each must travel with the tab owning its trigger.

The tool assigns the gap after a card to that card. Verified by listing modals per output pane:

New pane	Modals it took
redis-caching	redisExplorerModal
cosmos	cosmosIndexingPolicyApplyModal, staleCacheCleanupApplyModal, documentAccessIndexResetModal, cosmosThroughputSetupModal, cosmosThroughputContainerModal
network	—

Every one landed with its trigger.

A useful property fell out

Moving a whole tab between groups needs no markup change at all. Panes are independent files; groups are entries in the nav map. So Front Door moving from Scale to Security was a one-line map edit.

Only moving a card between tabs requires markup surgery. That distinction shapes the rest of stage D.

Verification

• Field names and card ids unchanged: 462 names, 110 card ids — saving untouched
• Regression set: 32 pre-existing failures, identical set
• 24/24 admin templates parse under Jinja
• check_xss_sinks.py full-file scan of all 7 touched files
• node --check on modified JS

Where stage D goes next

The remaining groups pull cards from multiple source panes — Data Lifecycle wants Retention and Classification out of Workspaces and Archiving out of Safety. The split tool only handles one pane at a time, so the next step is a move-card-between-panes operation carrying the same every-line-accounted-for guarantee.

I stopped here rather than hand-editing those moves. Hand-moving markup across files is exactly where a name= attribute goes missing silently, and the whole point of the tooling is that it can't.

Current structure: 12 groups, 22 tabs. Version 0.260.011. Status doc updated with the proven pattern.