fix(frontend): close the advanced-settings bypass while the policy is unknown

Create was gated on knowing whether the instance derives usernames, and
the link beside it went to a form with no such gate — so the way around
the block sat next to it. It is disabled until the policy is known, with
a title saying why.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012fRjnaHLwjpHN84gNNxah9
This commit is contained in:
Guilhem Lemouel
2026-09-07 13:09:44 +02:00
co-authored by Claude Opus 5
parent 4303538686
commit 58c9073656
@@ -191,8 +191,13 @@
{@render leading?.()}
<!-- A bare <button> as a quiet text link, signed off by design: a second <Button> here
would compete with Create workspace for the eye. -->
<!-- Closed while the policy is unknown, or it would be a way around the gate beside
it: the full form asks the same question of the same setting and submits on
its own optimistic default, so with no policy neither route creates. -->
<button
class="text-xs text-secondary hover:text-emphasis"
class="text-xs text-secondary hover:text-emphasis disabled:opacity-50 disabled:hover:text-secondary"
disabled={!policyLoaded}
title={policyLoaded ? undefined : "This instance's settings could not be read"}
onclick={() => (advanced = true)}
>
Advanced settings