The workflow list scrolled sideways off a phone screen and the history grid
pushed the diff off it. Below lg the list becomes a header select with the
draft badge; below md the revision list becomes a select above a full-width
diff, with the two canvases stacked.
The gutter printed one number per source line while the text layer wrapped,
so every line after a long one was numbered wrong. The textarea no longer
wraps: the gutter, the highlight layer and the textarea share one row per
line and scroll together on both axes.
Below md the section tabs that do not fit collapse into one menu that sets
the same tab, and the actions share one right-aligned row. The canvas is
sized to the viewport left on a phone, frames a graph or card wider than the
canvas instead of clipping its edges, and clears the chat launcher.
A coarse-pointer-only floor keeps switches, tab triggers and scrolled nav
strips from being deformed on a phone, and the topbar reveals the current
section after a route change.
The Access area mixed organisation, instance and personal settings under
one name. Split them: /org is the organisation's own area (members,
identities, connections, models, schedules, playbooks), /settings is
instance administration only, and personal security stays in the account
menu. Setup checklist steps now link to the page that fixes them.
Drop the sentence explaining that the credential is a reference and that an
identity with no entry is not granted: both lectured at the operator instead of
labelling the field. The external account needs no hint, the forge type keeps
one line saying where the value comes from, and the identity button reads the
way the credential-grants control already does.
A Connections page under Settings lists the organisation's forge connections:
host, forge type, the reference to the credential (never its value), the
external account it belongs to, and the operations each execution identity may
perform through it. The chat agent's page registry names the page too.
Personal API tokens are the signed-in operator's, and the instance URL and
OIDC providers are the instance's, so neither belongs under the organisation
Access area. Tokens render in the account page and Authentication moves to
Settings; the old paths redirect.