webmail-client

152 Commits 1 Branch 0 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
lukasandClaude Opus 5	6414504f6e	Settings: a section per plugin, and call the folder Spam Plugin settings pages were stacked at the bottom of Settings -> Accounts, which put antispam's thresholds and lists under a heading about mail accounts. Each `settings.page` now gets its own entry in the Settings nav: "Antispam filtering" and "Mail filters". Slot gains an optional `title` for this — the host needs a label when it gives a slot an area of its own, and falls back to the plugin name. PluginSlot gains an optional `plugin` filter so a host can render one plugin's bundle rather than every binding for a slot name. Wording: the app calls that folder Spam (i18n `nav.spam`), so the plugin's copy now does too — "filed into Spam", "Move to Spam", "marked as spam". The IMAP special-use stays `junk`, which is what the protocol calls it; only what the user reads changed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018SqJYt7jD7oUEkoY68sBZo	2026-09-17 08:19:11 +02:00
lukasandClaude Opus 4.8	4e077f1a37	M3 plugin platform: SDK + loader, RLS-isolated tables, migrations, jobs Backend foundation for the plugin platform (SPEC §11), Phases 1-3. Phase 1 — SDK + loader: - app/plugins/types.py: frozen Plugin/UiManifest/Slot/Page/JobSpec contract. - app/plugins/sdk.py: sdk(name) facade — the only app.* import allowed for plugins (scoped session, plugin.{name}.* publish, blob, outbox, settings, SSRF http_get, KV, enqueue). - app/plugins/loader.py: entry-point discovery (webmail.plugins), hook forwarding (API + worker), router mounting at /api/plugins/{name}, ui-manifest aggregation. - plugin_kv core table (migration 0013) + GET /api/plugins/ui-manifest. Phase 2 — non-removable core plugins + DB-enforced privacy: - builtin flag (calendar/contacts will be builtin=True; uninstall refuses them). - RLS per-user isolation on plg_* tables: least-privilege webmail_plugin role (migration 0014), plugin_session(user_id) sets LOCAL ROLE + app.current_user_id, rls.enable_rls() (ENABLE+FORCE RLS + USING/WITH CHECK policy). Mail untouched. - Per-plugin Alembic runner (shared env, dedicated version table) + install/uninstall --drop-data CLI; skeleton fixture proves install -> run -> uninstall --drop-data leaves zero residue (§12 M3 acceptance). Phase 3 — plugin jobs (§11.2): - JobSpec registered as arq function plg.{plugin}.{func} + cron (5-field parser); singleton=True guarded by a per-(plugin,user) Redis lock; wired onto the shared interactive worker. Gates: ruff, mypy --strict (94 files + tests), full suite 326 passed. RLS isolation, migration round-trip, and singleton lock covered by tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rcj3TpydMTzTSmU7kunzf8	2026-07-26 21:42:35 +02:00

Author

SHA1

Message

Date

lukasandClaude Opus 5

6414504f6e

Settings: a section per plugin, and call the folder Spam

Plugin settings pages were stacked at the bottom of Settings -> Accounts, which
put antispam's thresholds and lists under a heading about mail accounts. Each
`settings.page` now gets its own entry in the Settings nav: "Antispam filtering"
and "Mail filters".

Slot gains an optional `title` for this — the host needs a label when it gives a
slot an area of its own, and falls back to the plugin name. PluginSlot gains an
optional `plugin` filter so a host can render one plugin's bundle rather than
every binding for a slot name.

Wording: the app calls that folder Spam (i18n `nav.spam`), so the plugin's copy
now does too — "filed into Spam", "Move to Spam", "marked as spam". The IMAP
special-use stays `junk`, which is what the protocol calls it; only what the
user reads changed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018SqJYt7jD7oUEkoY68sBZo

2026-09-17 08:19:11 +02:00

lukasandClaude Opus 4.8

4e077f1a37

M3 plugin platform: SDK + loader, RLS-isolated tables, migrations, jobs

Backend foundation for the plugin platform (SPEC §11), Phases 1-3.

Phase 1 — SDK + loader:
- app/plugins/types.py: frozen Plugin/UiManifest/Slot/Page/JobSpec contract.
- app/plugins/sdk.py: sdk(name) facade — the only app.* import allowed for plugins
  (scoped session, plugin.{name}.* publish, blob, outbox, settings, SSRF http_get, KV, enqueue).
- app/plugins/loader.py: entry-point discovery (webmail.plugins), hook forwarding
  (API + worker), router mounting at /api/plugins/{name}, ui-manifest aggregation.
- plugin_kv core table (migration 0013) + GET /api/plugins/ui-manifest.

Phase 2 — non-removable core plugins + DB-enforced privacy:
- builtin flag (calendar/contacts will be builtin=True; uninstall refuses them).
- RLS per-user isolation on plg_* tables: least-privilege webmail_plugin role
  (migration 0014), plugin_session(user_id) sets LOCAL ROLE + app.current_user_id,
  rls.enable_rls() (ENABLE+FORCE RLS + USING/WITH CHECK policy). Mail untouched.
- Per-plugin Alembic runner (shared env, dedicated version table) + install/uninstall
  --drop-data CLI; skeleton fixture proves install -> run -> uninstall --drop-data
  leaves zero residue (§12 M3 acceptance).

Phase 3 — plugin jobs (§11.2):
- JobSpec registered as arq function plg.{plugin}.{func} + cron (5-field parser);
  singleton=True guarded by a per-(plugin,user) Redis lock; wired onto the shared
  interactive worker.

Gates: ruff, mypy --strict (94 files + tests), full suite 326 passed. RLS isolation,
migration round-trip, and singleton lock covered by tests.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rcj3TpydMTzTSmU7kunzf8

2026-07-26 21:42:35 +02:00