Add /me and enrollment with the identity-provider key binding (M1)

The last backend piece of M1. A client can now log in, discover it must
enroll, publish its identity key, and get a usable personal vault.

Enrollment is one indivisible act. One transaction writes the key, its
wraps, the device, the key log entry, the vault and the vault key grant,
because none of them is useful alone: a key with no vault leaves a user
unable to store anything, and a vault with no grant is a container nobody
can ever open -- including its owner, since only the client can wrap the
key and it has already moved on.

Two independent checks run, and neither substitutes for the other. The
Ed25519 self-signature proves possession of the private key. The
identity-provider binding proves whose key it is: the client hashed its
statement, used the hash as an OIDC nonce, and the resulting ID token is
the provider's signature over exactly those public keys. This server
cannot mint that signature, so it cannot invent a key for a user who never
enrolled -- which is the attack that would otherwise let an operator read
every vault by publishing its own key as yours.

The binding token is stored verbatim, not just summarised. Clients must
repeat the check against the provider's JWKS fetched directly, and storing
only our conclusion would ask them to trust the server about the one
question the design exists to avoid trusting it about.

Key log appends take a deployment-wide advisory lock. The falsification
matters more than the passing test: with the lock removed,
Enroll_ConcurrentEnrollmentsByDifferentUsers_LeaveAnUnbrokenChain fails
with entry 11 linked to the wrong predecessor. Different users trip no
unique index, so without serialising they all read the same head and the
chain forks -- indistinguishable from the key substitution the log exists
to make detectable, and permanent, because the log is append-only.

Enrollment is idempotent. Vault ids and keys are client-chosen, so a
client whose response was lost re-sends the identical body and gets the
identical result. Without that, a lost response leaves a user enrolled
against a vault they never learned the id of.

Contract change, breaking the v0.1 freeze deliberately. EnrollmentRequest
had DevicePublicKey but no wrap to go with it, which is unsatisfiable:
only the holder of the secret bundle can seal it, so the server could
never fill the gap. Added DeviceWrappedPrivateKey, and PersonalVault so
enrollment can be atomic rather than leaving an unopenable vault behind
two endpoints that do not exist yet. No client exists and no package is
published, which is exactly when PublicAPI.Unshipped.txt expects this.

Sync now requires the Enrolled policy, which until now was a stub whose
name promised a check it never made. The sync denial tests use enrolled
intruders instead of unenrolled ones -- an unenrolled caller is stopped
before the vault check runs, which would have left those tests passing
without exercising the thing they exist to prove.

Also fixed: omitting kdfParameters from the JSON body was a 500. A
record's non-nullable parameters are a compile-time promise, not a runtime
one.

268 tests pass, zero warnings on a clean rebuild, format clean.

src/DodoSSH.Api/Setup/Auth.cs

@@ -58,10 +58,15 @@ internal static class Auth
         {
             options.AddPolicy(AuthenticatedPolicy, policy => policy.RequireAuthenticatedUser());
 
-            // Enrollment state lives in the database, so the real handler arrives with the
-            // enrollment feature. Registered now so endpoint groups can reference the policy name
-            // and the endpoint-inventory test has something to assert against.
-            options.AddPolicy(EnrolledPolicy, policy => policy.RequireAuthenticatedUser());
+            // Enrollment state lives in the database, so this is satisfied by EnrolledHandler.
+            // An unmet EnrolledRequirement is rewritten into a ProblemDetails carrying
+            // "enrollment-required" by DodoAuthorizationResultHandler, because an empty 403 cannot
+            // tell a client whether the problem is theirs to fix.
+            options.AddPolicy(
+                EnrolledPolicy,
+                policy => policy
+                    .RequireAuthenticatedUser()
+                    .AddRequirements(new Authorization.EnrolledRequirement()));
 
             // Deny by default: an endpoint without an explicit policy still requires a caller.
             options.FallbackPolicy = options.GetPolicy(AuthenticatedPolicy);

src/DodoSSH.Api/Setup/EndpointRegistration.cs

@@ -1,3 +1,4 @@
+using DodoSSH.Api.Features.Identity;
 using DodoSSH.Api.Features.Meta;
 using DodoSSH.Api.Features.Sync;
 
@@ -17,10 +18,11 @@ internal static class EndpointRegistration
     internal static WebApplication MapDodoEndpoints(this WebApplication app)
     {
         app.MapMetaEndpoints();
+        app.MapIdentityEndpoints();
         app.MapSyncEndpoints();
 
         // Registered as each feature lands:
-        //   Identity   — /me, enrollment, key rotation, devices
+        //   Identity   — key rotation, devices, passphrase change
         //   Directory  — public-key lookup
         //   Vaults     — grants, rekey, ACL
         //   Relay      — tickets and the WebSocket