Split address connector portfolio into work packages

docs/IMPLEMENTATION_PLAN.md

@@ -219,10 +219,13 @@ Primary issues: `govoplan-addresses#8`, `govoplan-addresses#9`,
 
 Tasks:
 
-- [ ] LDAP/Active Directory read-only directory connector
-- [ ] Exchange/Microsoft 365 contacts connector
-- [ ] Google Contacts connector
-- [ ] CSV/XLSX/LDIF import mapping profiles
+- [ ] [LDAP/Active Directory read-only directory connector](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/15)
+- [ ] [Microsoft Graph contacts connector for Microsoft 365](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/16)
+- [ ] [On-premises Exchange connector profile](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/17)
+- [ ] [Google People contacts connector](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/18)
+- [ ] [Reusable CSV/XLSX import mapping profiles](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/19)
+- [ ] [Bounded LDIF import profile](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/20)
+- [ ] [Selective and large-batch vCard workflows](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/21)
 - [x] classical address-list UI; reusable static/dynamic operational segments move
   to `govoplan-dist-lists`
 - [x] operational distribution lists move to `govoplan-dist-lists`
@@ -239,9 +242,10 @@ Exit criteria:
 - users can understand where data came from and whether they may edit it
 - downstream modules can safely use contacts without owning them
 
-Issues #9 and #10 are implemented. Issue #8 tracks the connector portfolio and
-is split into independently deliverable connector/import follow-ups rather than
-keeping one cross-protocol implementation ticket open.
+Issues #9 and #10 are implemented. Issue #8 is complete as a portfolio split:
+issues #15-#21 independently track each connector/import profile with explicit
+direction, dry-run, diagnostics, provenance, recovery, and module-independence
+requirements.
 
 ## First Implementation Recommendation