feat(server): createRosterAccountStore — Shape C explicit AccountStore for publisher-curated rosters

[bokelley]

Parent: #452
Depends on: #456

JS source

6.7 commit eda2648f feat(adapters): createRosterAccountStore.

Use case

For publisher-curated rosters where the adopter has a fixed list of allowed accounts (not OAuth, not multi-tenant). Currently adopters write ExplicitAccounts(loader=...) from scratch and re-implement the same lookup-by-id logic.

Proposed API

from adcp.decisioning import create_roster_account_store

store = create_roster_account_store(
    roster={
        "acct_alpha": Account(account_id="acct_alpha", ...),
        "acct_beta":  Account(account_id="acct_beta", ...),
    },
)

Returns an AccountStore whose resolve does the dict lookup, whose list returns the roster, and whose upsert / sync_governance are no-ops or raise (TBD on shape).

Acceptance criteria

• create_roster_account_store exported from adcp.decisioning.
• Tests: resolve hit / miss; list returns full roster; upsert behavior documented and tested.

[bokelley]

Triage

Classification: Feature request
Bucket(s): client
Status: deferred

What the experts said:

• Pre-classification gate: issue body declares Depends on: #456, which is open — routed to Defer rather than Execute; no expert panel needed.

My take: create_roster_account_store is a clean, well-scoped addition to adcp.decisioning with clear acceptance criteria — good candidate for Execute once unblocked. It depends on the updated AccountStore contract (upsert(ctx) / sync_governance(ctx) signatures) that #456 introduces; implementing it against the current surface would require an immediate follow-up rewrite.

Blocked-on: #456 — resurfaces on merge.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_014RJHgoctZLrYCtbdyUg1DF

---

Generated by Claude Code