feat(workspace): sealed-area names are confidential by default
Some checks failed
Security / Security check (push) Failing after 2s

The switcher listed sealed areas by name ('lbs', 'stromnetz') on
any glance or screenshot — but the names themselves often carry
client/mandate identity (usertest security finding). The sealed
section now renders one aggregated row ('2 sealed areas') with a
deliberate 'Show names' reveal per menu opening; selection still
pops the regular s:<slug> value. Settings -> Security gains 'list
sealed areas with their names right away' (WorkspacePrefs,
SidebarPrefs pattern, default off).

The aggregate row wraps to two lines — popup menus cap their
width and action texts must never be truncated (the first cut
showed '1 abgeschotte…' in the proof shot). Guard: switcher tests
cover aggregated-until-reveal and the Settings toggle; the old
direct-listing test now asserts the reveal contract. DE+EN.

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
This commit is contained in:
flemming-it 2026-07-19 03:34:05 +02:00
parent ed680c507a
commit 588f437395
11 changed files with 370 additions and 41 deletions

View file

@ -1799,6 +1799,11 @@
"runsPhaseUnknown": "Unbekannt",
"navRuns": "Läufe",
"workspaceSealedHeader": "ABGESCHOTTETE BEREICHE",
"workspaceSealedAggregate": "{n, plural, =1{1 abgeschotteter Bereich} other{{n} abgeschottete Bereiche}}",
"@workspaceSealedAggregate": {"placeholders": {"n": {"type": "int"}}},
"workspaceSealedRevealAction": "Namen einblenden",
"settingsSealedNamesTitle": "Abgeschottete Bereiche direkt mit Namen anzeigen",
"settingsSealedNamesBody": "Bereichsnamen können schutzwürdig sein (Kunden-/Mandantenbezug). Standardmäßig zeigt der Projekt-Umschalter sie nur zusammengefasst; die Namen erscheinen erst nach einem Klick.",
"workspaceSealedRunning": "läuft",
"workspaceSealedStopped": "gestoppt",
"workspaceSealedRunningHint": "Der abgeschottete Bereich läuft als eigener Hub-Prozess. Auswählen wechselt hinein.",