Add governed contact point snapshots

docs/ADDRESS_MODULE_ARCHITECTURE.md

@@ -87,6 +87,8 @@ The first stable capabilities are:
   campaign, scheduling, postbox, portal, and case workflows.
 - `addresses.contact_writer`: provide address-book-scoped write target decisions
   and contact creation for local or otherwise writable sources.
+- `addresses.contact_point_resolution` version 1.x: resolve channel-neutral
+  contact points and freeze immutable recipient evidence.
 
 Capabilities use DTOs and source IDs. Consumers must not receive ORM objects or
 write address tables directly. Consumers that need historical evidence must
@@ -96,10 +98,24 @@ provenance; they must not treat live address records as historical evidence.
 `addresses.recipient_source` exposes both complete address books and classical
 address lists. Address-book sources use `addresses:address_book:<id>`.
 Address-list sources use `addresses:address_list:<id>` and include the
-address-list entry ID in each recipient's provenance. The current snapshot DTO
-is email-recipient oriented; postal-only list entries are valid address-list
-members but are skipped by the email recipient-source path until postal
-recipient DTOs are added.
+address-list entry ID in each recipient's provenance. The legacy snapshot DTO
+remains email-oriented for compatible campaign consumers.
+
+Channel-neutral consumers use `addresses.contact_point_resolution`, which
+supports email, postal, internal-mail, and portal targets, including postal-only
+address-list entries. Requests make effective date, communication purpose,
+address purpose, fallback behavior, locale, and domestic/international postal
+formatting explicit. Results retain stable subject/contact/contact-point IDs,
+source, preference and consent revisions, provenance, and reasons for excluded
+or unresolved candidates.
+
+Live previews are bounded to 500 rows per page and 20,000 source members per
+request. Frozen snapshots persist resolved values and exclusions with a
+deterministic hash; reading a snapshot never resolves the live contact again.
+Mixed-audience expansion and final cross-provider Policy/channel decisions
+remain owned by Distribution Lists and Policy. The contract is defined in Core,
+and Addresses does not import IDM, Organizations, or Distribution Lists
+implementations.
 
 The writer capability is intentionally address-book specific. It answers
 whether the current principal may perform an operation such as `create_contact`,

docs/IMPLEMENTATION_PLAN.md

@@ -73,6 +73,11 @@ Tasks:
 - [x] define immutable recipient snapshot DTOs
 - [x] expose source provenance in capability responses
 - [x] expose classical address lists as `addresses.recipient_source` sources
+- [x] expose versioned channel-neutral contact-point resolution for local and
+      stable provider subject references
+- [x] support purpose/address-purpose selection, deterministic fallback,
+      locale, and domestic/international postal rendering
+- [x] add bounded source previews and immutable postal/email snapshots
 - [x] add module presence/capability tests
 - [x] document consumer rules for campaign, mail, scheduling, portal, postbox, and
   reporting
@@ -82,6 +87,8 @@ Exit criteria:
 - [x] campaign can request a recipient source via core-mediated capability
 - [x] mail/scheduling can request autocomplete candidates via core-mediated lookup
 - [x] consumers do not import `govoplan_addresses`
+- [x] postal-only contacts/list entries can be resolved without changing the
+      legacy email recipient-source contract
 
 ## Milestone 4: Campaign Integration