Add the member the directory cannot see, rather than inviting them

ADD MEMBER quietly issued an invitation instead of adding anybody, for everyone
who had signed in here and not yet enrolled. The screen told them that address
had no account, the members list did not change, and the person only actually
joined on the next hourly sweep.

The client decided whether an address had an account by asking the public-key
directory, and the directory answers a narrower question than that. It drops
every account with no current key — deliberately, because an entry exists to be
wrapped to and one carrying no key is a check a caller forgets exactly once. An
account exists from its owner's first authenticated request and publishes
nothing until they choose a passphrase on their own machine, so every account is
missing from the directory for that whole window and some indefinitely. A miss
there is not an absent account, and reading it as one was the bug.

The server would have taken the add. TeamService.AddMemberAsync only requires
the account row, and TeamMemberSummary.IsEnrolled exists precisely so a member
with no key can be listed — added on Monday, enrolled on Tuesday. The client
never asked.

So the directory is still asked first and the miss is retried as an add by
address, and only a server saying there is no such account reaches the
invitation. AddTeamMemberRequest gained an Email used when UserId is empty. The
lookup-first ordering is kept because it is load-bearing for sharing and not for
this: the key verified before a vault key is wrapped is the one the lookup
returned, and nothing is wrapped by adding somebody. That is why resolving the
address server-side is safe here and would not be there.

NoSuchAccount is its own code rather than folded into InvalidTeam, because it is
the one add failure the caller can act on unprompted — there is nobody to add,
so invite them — and a code shared with a rejected role would leave them
guessing which had happened. It does answer whether an address has an account
here, which CreateTeamInvitationRequest deliberately does not. That is the
property traded for the fix; the exposure is bounded by the admin check the add
already needed, and it is the same fact the member list shows a moment later.
Adding by a user id that does not exist now answers 404 no-such-account rather
than 400 invalid-team, and nothing depended on the old pairing.

The two silent returns are gone. Offline and no-team-selected set nothing and
returned, so those failures were visible only as a flicker of the busy flag —
which reads as a button that does nothing at all. The success line reads the
enrollment flag too, because pointing an unenrolled member at SHARE KEY is
pointing at a button that will refuse; their row already says it holds no key.

Why nothing caught it. FakeVaultServer had one list, so it could not tell an
account that does not exist from one that exists and has not enrolled — the
distinction this whole path turns on — and every account it knew was enrolled by
construction. It grows an accounts list beside the directory and reports
IsEnrolled from whether the directory has them, rather than hardcoding true. The
regression test asserts Invitations is empty, which is what fails against the
old behaviour. Four tests: that pair in the shell suite, and in the API suite an
unenrolled account added by address after its own directory lookup comes back
empty, and an unknown address refused under the new code. 1495 tests pass.

tests/DodoSSH.Api.Tests/TeamEndpointTests.cs

@@ -450,6 +450,69 @@ public sealed class TeamEndpointTests(ApiFixture fixture)
         vault.TeamId.ShouldBe(team.TeamId);
     }
 
+    /// <remarks>
+    /// <para>
+    /// An account exists from its owner's first authenticated request and publishes no key until they
+    /// enroll, and the directory omits it for that whole window — deliberately, because an entry exists
+    /// to be wrapped to. So the lookup is asserted empty first: that is not a missing account, and a
+    /// caller that read it as one would invite an address that already has one.
+    /// </para>
+    /// <para>
+    /// Adding by address is what covers the gap, and the member it produces says <c>IsEnrolled</c>
+    /// false. Membership is authorization and grants nothing readable, so there is nothing inconsistent
+    /// about a member with no key — it is the state everybody passes through.
+    /// </para>
+    /// </remarks>
+    [Fact]
+    public async Task AnAccountThatHasNotEnrolled_CanBeAddedByAddressThoughTheDirectoryOmitsIt()
+    {
+        var owner = await EnrolledClientAsync("unenrolled-owner", "uowner@example.com");
+
+        var address = NewAddress();
+        var (_, userId) = await SignInAsync(address);
+
+        var team = await CreateTeamAsync(owner, "Newcomers");
+
+        var found = await ReadAsync<IReadOnlyList<DirectoryEntry>>(
+            owner, $"/api/v1/directory?email={Uri.EscapeDataString(address)}");
+
+        found.ShouldBeEmpty("they have published no key, so there is nothing to wrap to");
+
+        var member = await PostAsync<AddTeamMemberRequest, TeamMemberSummary>(
+            owner,
+            MembersUrl(team.TeamId),
+            new AddTeamMemberRequest(Guid.Empty, TeamMemberRole.Member, address));
+
+        member.UserId.ShouldBe(userId);
+        member.IsEnrolled.ShouldBeFalse();
+        member.Role.ShouldBe(TeamMemberRole.Member);
+
+        var listed = await ReadAsync<IReadOnlyList<TeamMemberSummary>>(
+            owner, MembersUrl(team.TeamId));
+
+        listed.ShouldContain(row => row.UserId == userId && !row.IsEnrolled);
+    }
+
+    /// <remarks>
+    /// The other side of it. An address with no account is refused under its own code rather than the
+    /// general one, because the caller can act on it unprompted — there is nobody to add, so invite
+    /// them — and a code shared with a rejected role would leave them guessing which had happened.
+    /// </remarks>
+    [Fact]
+    public async Task AddingAnAddressWithNoAccount_IsRefusedWithItsOwnCode()
+    {
+        var owner = await EnrolledClientAsync("no-account-owner", "naowner@example.com");
+
+        var team = await CreateTeamAsync(owner, "Nobody");
+
+        var response = await owner.PostContractAsync(
+            MembersUrl(team.TeamId),
+            new AddTeamMemberRequest(Guid.Empty, TeamMemberRole.Member, NewAddress()));
+
+        await ShouldBeProblemAsync(
+            response, HttpStatusCode.NotFound, ProblemCodes.NoSuchAccount);
+    }
+
     /// <remarks>
     /// A viewer may read the vault and may not write to it. The failure this guards is the quiet one: a
     /// role that resolved to the wrong flags would let somebody who was added to look at a vault change