[Feature] Integrate addresses.lookup for recipient autocomplete and add-contact flows #13

New Issue

zemion · 2026-07-13T00:53:58+02:00

zemion commented

2026-07-13 00:53:58 +02:00

Goal

Use contacts naturally in mail without making mail depend on the addresses package.

Scope

detect addresses.lookup through core/module capabilities
autocomplete recipients from visible address books
optionally add sender/recipient as contact when addresses.contactWriter exists
hide or explain write actions for read-only sources

Acceptance Criteria

Mail works unchanged without addresses installed.
Mail + addresses improves recipient entry through lookup.
Add-contact actions respect source scope, policy, and read-only connector state.

Related address-module plan: govoplan-addresses/docs/IMPLEMENTATION_PLAN.md.

## Goal Use contacts naturally in mail without making mail depend on the addresses package. ## Scope - detect `addresses.lookup` through core/module capabilities - autocomplete recipients from visible address books - optionally add sender/recipient as contact when `addresses.contactWriter` exists - hide or explain write actions for read-only sources ## Acceptance Criteria - Mail works unchanged without addresses installed. - Mail + addresses improves recipient entry through lookup. - Add-contact actions respect source scope, policy, and read-only connector state. Related address-module plan: `govoplan-addresses/docs/IMPLEMENTATION_PLAN.md`.

zemion added the

labels 2026-07-13 00:53:58 +02:00

zemion commented

2026-07-13 12:58:40 +02:00

Codex State: started

Summary

Starting Milestone 5 mail/address integration: optional address lookup only; no hard addresses dependency and no write/contact action until addresses exposes a writer capability.

Suggested status label: status/in-progress

## Codex State: started ### Summary - Starting Milestone 5 mail/address integration: optional address lookup only; no hard addresses dependency and no write/contact action until addresses exposes a writer capability. Suggested status label: `status/in-progress`

zemion commented

2026-07-13 13:05:39 +02:00

Codex State: progress

Summary

Added optional addresses.lookup support at the mail backend/API boundary: manifest metadata, /api/v1/mail/address-lookup, runtime registry access, and typed WebUI API helper.

Changed Files

src/govoplan_mail/backend/router.py
webui/src/api/mail.ts

Verification

unittest tests.test_manifest: OK
mail helper/parser tests: OK
core webui npm run build: OK

Next / Blocked

Visible mail recipient autocomplete should attach to the future compose/send UI; the current mail module has mailbox/settings UI but no compose recipient field.
Add sender/contact write actions need an explicit addresses writer capability and policy/read-only contract before UI actions are safe.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Added optional addresses.lookup support at the mail backend/API boundary: manifest metadata, /api/v1/mail/address-lookup, runtime registry access, and typed WebUI API helper. ### Changed Files - `src/govoplan_mail/backend/router.py` - `webui/src/api/mail.ts` ### Verification - `unittest tests.test_manifest: OK` - `mail helper/parser tests: OK` - `core webui npm run build: OK` ### Next / Blocked - Visible mail recipient autocomplete should attach to the future compose/send UI; the current mail module has mailbox/settings UI but no compose recipient field. - Add sender/contact write actions need an explicit addresses writer capability and policy/read-only contract before UI actions are safe. Suggested status label: `status/in-progress`

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: add-ideas/govoplan-mail#13