Cakemix feature parity

Popii 1.0 Cakemix uses v0.7.6 as its stable dashboard baseline. It restores useful bot-management workflows inside typed services, scoped repositories, and permission-aware pages. It does not restore the browser terminal, database explorer, public API keys, filesystem editor, runtime plugin reload, or secret inspection.

Data boundaries

Web sessions, OAuth credentials, audit metadata, delegated roles, and task overrides live in the Web plugin’s private SQLite database. Plugin-owned content uses the bot’s active sqlitePlugin or mongoosePlugin. Both implementations follow the same version-conflict and guild-isolation contract.

If neither persistence plugin is enabled, the dashboard renders an unavailable state. It does not silently create a second source of truth.

Delegated access

Discord administrators and members with Manage Guild retain full guild administration. Managers may delegate narrowly scoped capabilities to Discord roles:

• Guild viewing
• Guild configuration
• Member moderation
• Content management
• Audit viewing
• Music management

Role membership is fetched from Discord when access is checked. Popii owners do not implicitly bypass guild privacy.

Safe editors

Embed, RSS, locale, and UI-preset editors use versioned records and optimistic concurrency. Locale and presentation changes are runtime overlays: the dashboard never edits project files. UI presets accept data descriptors only, not CSS, HTML, JavaScript, fonts, or arbitrary components.

RSS and external media inputs require public HTTPS URLs. Production integrations must additionally resolve every redirect and reject private, loopback, link-local, multicast, and cloud-metadata addresses.

Migration

The machine-readable inventory is maintained in docs/parity-v0.7.6.json. Database migration creates a pre-1.0 backup, applies changes transactionally, removes legacy Web sessions and API keys, and retains plugin-owned records. Users must sign in again after upgrading.