Send invite ends in silence
_{/ · Invite member}

The card closes and clears. Nothing says the invitation went, the People table gains no Invited row, and Activity, where the description says it shows up, is unchanged. An invite that vanishes without a word has not been sent as far as the admin can tell.

Keep the card open until the email passes, then say what happened: an Invited row in the table, or a line in Activity. If Activity is not wired yet, say so on the card.

Role and permissions ask the same question twice
_{/ · Invite member}

The role decides what a person can do, and three checkboxes under it let the admin contradict it: a Member with the directory unchecked, a Workspace admin who cannot invite. The invite should ask who and what role, and show what the role allows as a sentence; permissions belong on the person’s page, after they exist.

Drop the checkboxes from the invite. Under the role, one line: what a Member can do. Edit permissions on the member’s page.

Send invite is blue in a green app
_{styles.css:388}

The button hardcodes #3b82f6. Every other primary, the Invite member trigger included, is the forest green --accent token. White on that blue is 3.7:1.

Drop the colour rules and let .btn-primary style the button.

The close button has no name
_{index.html:184}

A bare × with no aria-label: a screen reader announces “button” and nothing else.

Give it aria-label="Close".

The dialog is on its own spacing rhythm
_{styles.css:304}

22 px between fields where the rest of the stylesheet moves on the 8 px scale.

Replace the literal with --space-lg.

Delete show is dressed as the happy path
_{/settings.html · Danger zone}

The same fill and weight as Save changes, a few lines below it, and one click is the whole flow: no confirmation between the click and 48 episodes gone. The note above it says what deletion removes, which makes the button more dangerous, not less.

Give Delete show a destructive treatment, an outlined --danger button, and a confirmation that names the show and what goes with it, with Cancel as the default.

The page invents its own navigation
_{/settings.html · sidebar}

A sidebar of four section links while every other page navigates from the masthead. Nothing updates its current state, and on a phone it wraps into two rows of links between the heading and the first field. Four sections on one short page do not need a second navigation.

Cut the sidebar and its column. The section headings already do the job.

Connected services is a heading over nothing
_{/settings.html · Connected services}

An empty list under a heading. A host cannot tell whether they have no connected services or the feature is not built yet, and the PR body knows the answer.

Write the empty state: one sentence saying the Spotify and Apple sync is coming and nothing needs doing now. If that cannot be written yet, leave the section out until it can.

The title field is one line for a title that is not
_{settings.html:38}

Show title is a single-line input, and the 105-character title runs off its right edge. The hint says apps show only the first two lines of the description; nothing says where the title is cut. The one field a host comes here to fix hides the part that matters.

Make it a textarea sized to the title, with the directory’s limit beside it as a count.

Two field names reach no control
_{settings.html:49}

The Category label points at an id the select does not have, and Description is a heading above a textarea with no label. Both look labelled and neither is.

Point the label at category, and turn the Description heading into <label for="show-description">.

Spacing in the new sections is off the app’s scale
_{styles.css:194}

28 px gaps, 18 px section padding and a 10 px rhythm where the rest of the app moves in 12, 16 and 24.

Replace the literals with the steps the stylesheet already names.