Local Campaign/Files WIP is only a partial precursor: it discovers rule-matching file assets that are not yet Campaign-shared and can link them. It does not surface unmatched watched-folder files,…
CardDAV is owned by Addresses #7, with shared connector diagnostics in Connectors #8; Campaign consumption was handled by Campaign #55. Closing this duplicate as superseded.
Address-book ownership is now govoplan-addresses. Addresses #3 delivered scoped local books/CRUD, Addresses #11 delivered management UI and Campaign picker integration, and Campaign #55…
Retained as the canonical Cases MVP issue. The concept already exists; the title and acceptance criteria now describe the remaining runtime slice. Scheduling is deferred while interface and…
govoplan-cases concept and MVP
govoplan-cases concept and MVP
Duplicate of #1. Both issues were imported from the same source line and carry the identical backlog fingerprint 94dd33aef34d8eefdb50847e. Continuing the Cases concept/MVP work in #1.
Retest update, 2026-07-20: the Files-only/combined production WebUI build and affected diff checks pass. Static inspection confirms direct target handoff, DataTransfer.files/items/handle…
Implemented on origin/main: users can create, edit, archive, and restore address lists and add/remove contacts or specific contact methods. Address books and lists are exposed through the…
Implemented on origin/main at f19350e: CardDAV discovery and connection, full and sync-token refresh, ETag-aware inbound/outbound synchronization, deletes, conflicts, diagnostics, preview/run…
Tracker reconciliation: the completed portion is present on origin/main; the title and acceptance criteria now describe only the remaining work. This issue is ready as narrowed.
Tracker reconciliation: the completed portion is present on origin/main; the title and acceptance criteria now describe only the remaining work. This issue is ready as narrowed.
Tracker reconciliation: the completed portion is present on origin/main; the title and acceptance criteria now describe only the remaining work. This issue is ready as narrowed.
Implemented on origin/main. /api/v1/docs/context classifies documentation into always, configured, available, and evidence layers and reports module, capability, and scope blockers. Focused…
docs backend manifest, permissions, module metadata, and route contribution
Implemented on origin/main. The Docs manifest defines module metadata, authentication capability requirements, documentation permission and role template, backend route factory, /docs…