Add Profile B broader read-only client capabilities #10

New issue

Open

opened 2026-08-03 07:48:15 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-03 07:48:15 +00:00

(Migrated from github.com)

Depends on

Goal

Extend the independently usable library beyond the StarIntel collection kernel while preserving a read-only public surface.

Scope

guild and channel traversal
member chunking and bounded member search
read-state and relationship events
audit-log retrieval when the account can access it
invite and directory metadata
richer thread, forum, stage, and scheduled-event models
optional bounded local cache queries
capability discovery for each optional subsystem

Constraints

read-only behavior only
no command framework
no message sending convenience API
no application-command invocation or interaction automation
no billing, store, promotion, payment, or subscription helpers
no requirement that callers use StarIntel
all calls remain bounded, cancellable, and observable

Exit gate

a standalone Common Lisp application can discover and use Profile B capabilities
every added endpoint/event has deterministic fixtures
unsupported capabilities fail explicitly
Profile A users do not pull unnecessary Profile B dependencies into their closure

## Depends on - #8 ## Goal Extend the independently usable library beyond the StarIntel collection kernel while preserving a read-only public surface. ## Scope - guild and channel traversal - member chunking and bounded member search - read-state and relationship events - audit-log retrieval when the account can access it - invite and directory metadata - richer thread, forum, stage, and scheduled-event models - optional bounded local cache queries - capability discovery for each optional subsystem ## Constraints - read-only behavior only - no command framework - no message sending convenience API - no application-command invocation or interaction automation - no billing, store, promotion, payment, or subscription helpers - no requirement that callers use StarIntel - all calls remain bounded, cancellable, and observable ## Exit gate - a standalone Common Lisp application can discover and use Profile B capabilities - every added endpoint/event has deterministic fixtures - unsupported capabilities fail explicitly - Profile A users do not pull unnecessary Profile B dependencies into their closure