Platform capability flags for adapters #663
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#663
Reference in new issue
Block a user
A capability-flag mechanism so callers can ask an adapter which optional features it supports (typing indicator, edit, delete, media send, clarify/approval/picker UI) instead of discovering support by a failed type assertion or a runtime error.
Context for implementers
This depends on the optional-method interfaces this issue is meant to describe:
archie-core-1786637493329-136-49b39c78(typing/edit/delete/media) andarchie-core-1786637493357-137-35af7083(clarify/approval/pickers). Implement after (or in close coordination with) those two, since the flag set should mirror whatever optional interfaces they land — don't invent a flag taxonomy ahead of the methods it describes.Acceptance Criteria
BasePlatformAdapter(internal/gateway/adapter.go) or a wrapping type exposes a capability query (e.g.Capabilities() AdapterCapabilities) that reports which optional methods an adapter implements. Every existing adapter's reported capabilities match its actual method set (a regression test should fail if an adapter claims a capability it doesn't implement, or vice versa).Notes
Partial: the mechanism itself (gateway.CapabilityReporter, CapabilitiesOf, AdapterCapabilities) is built and covered by a regression test, scoped to Media only -- see archie-core-1786637493329-136-49b39c78 (closed, media portion). Still blocked on archie-core-1786637493357-137-35af7083 (clarify/approval/pickers) since AdapterCapabilities needs those flags added too before this is fully done.
Close reason
Closed on GitHub with verification evidence; confirmed against the tree.
Imported from beads
archie-core-1786637493387-138-cad8e7a7· GitHub #159 · type task · priority P2 · created 2026-08-08 · closed 2026-10-05