Prove the migration against live directories and fix what that surfaced

Finishes the unproven half of gap G04. Running the harness against real LLDAP,
OpenLDAP and Keycloak found four defects that the full unit suite passed over.

Every LLDAP user search pointed at a branch that does not exist. Config.userOU()
defaulted to ou=users while LLDAP stores users under ou=people, and nothing set
UserOU. LookupUser, ListUsers and ValidatePassword all derive from it, so all
three silently found nothing against a stock LLDAP -- human login included, not
only the export. Exposed by an export returning zero users while still emitting a
membership referencing uid=admin, a snapshot the repo's own validator rejects.

raw_attributes_well_formed, added one workplan earlier, rejected the LLDAP
adapter's own _validation_warning annotation, so the exporter's output failed its
own validation. Tooling annotations are exempt now, and a test proves the
exemption does not weaken the rule.

Migrated group memberships were dangling: resolveMemberDN passed a source DN
through unchanged while entries were written to the target branch, so groups
named entries the migrated directory does not contain. And empty groups could
not load at all, since groupOfNames makes member a MUST -- they reference a
placeholder entry the LDIF creates, an organizationalRole rather than a person,
emitted only when some group needs it.

The scenario-c compose file could not start: bitnami/openldap:2.6 does not
exist, though it passed docker compose config. Pinned to the image the scenario
was proved against.

Proof: LLDAP -> export -> validate -> LDIF -> ldapadd into OpenLDAP 1.5.0, every
entry added and every member resolving; a realm from the same export imports into
Keycloak and serves discovery. KeyCape passes 5/5 conformance checks, a migrated
Keycloak 4/5.

Relying-party behaviour and MFA against a migrated realm remain unexercised, and
credential/MFA migration is not supplied at all, so no harness can establish it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NV9oijZukGyGbRQGGKnK4P

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 713576@bnt-lap001
Assistant-Session: 384c511d-9bce-4cb8-a676-2aef6c0c8df6

SCOPE.md

@@ -83,9 +83,13 @@ Keycloak interchangeability are not established.
   (KEY-WP-0022). Run against Keycloak 26.0 it verified discovery, the
   authorization surface, the published keys and a real token exchange — and
   showed that stock Keycloak advertises the excluded `implicit` and `password`
-  grants, so it is not a drop-in for this profile. Directory migration,
-  credential and MFA preservation and relying-party behaviour remain unexercised;
-  Scenario C has not been run end to end.
+  grants, so it is not a drop-in for this profile. Directory migration is proved
+  end to end into a real OpenLDAP, with every migrated membership resolving, and a
+  realm built from a live export imports into Keycloak and serves discovery
+  (KEY-WP-0023). Relying-party behaviour and MFA against a migrated realm remain
+  unexercised, and credential/MFA migration is not supplied at all, so no harness
+  can establish it. Subject continuity is explicitly not preserved: the canonical
+  ID survives as an attribute while Keycloak mints its own `sub`.
 - The server listens on HTTP; HTTPS termination is deployment-owned.
   `/healthz` reports process status without probing dependencies. Development
   Compose needs configuration/key material absent from the checkout. Production