Split address connector portfolio into work packages

docs/ADDRESS_MODULE_ARCHITECTURE.md

@@ -208,13 +208,26 @@ Implement connectors in this order:
 
 1. vCard import/export and batch import.
 2. CardDAV address books.
-3. LDAP/Active Directory read-only directories.
-4. Exchange/Microsoft 365 and Google Contacts.
-5. CSV/XLSX/LDIF import mapping profiles.
+3. [LDAP/Active Directory read-only directories](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/15)
+   and [reusable CSV/XLSX mapping profiles](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/19).
+4. [Microsoft Graph for Microsoft 365](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/16),
+   [explicit on-premises Exchange profiles](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/17),
+   and [Google People](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/18).
+5. [LDIF import](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/20)
+   and [selective/large-batch vCard workflows](https://git.add-ideas.de/GovOPlaN/govoplan-addresses/issues/21).
+
+The live connectors use the existing sync-source model. LDAP starts read-only;
+Microsoft Graph and Google start with read-only/import and gate two-way mode on
+conditional-write and outcome-reconciliation tests. On-premises Exchange first
+probes and records an explicit supported server/API profile. CSV/XLSX, LDIF,
+and uploaded vCard are static one-way imports, not writable remote sources.
 
 Connector runtime behavior should reuse shared connector concepts where useful:
 configured endpoints, credentials, dry-run, diagnostics, rate limits, and audit
-events.
+events. The shared contract work is tracked in
+[`govoplan-connectors#8`](https://git.add-ideas.de/GovOPlaN/govoplan-connectors/issues/8);
+Addresses remains the owner of contact mapping, provenance, quality, and sync
+state.
 
 ## Cross-Module Integration
 

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