Besidka changelog

version

3.1.0 → 3.2.0

https://raw.githubusercontent.com/besidka/besidka/HEAD/AGENTS.md

−   parent/top, unverified stack-event behavior, migrations in children)−   32 per-user tools behind OAuth; `@nuxtjs/mcp-toolkit` on Workers): UI parity−   API Keys); add to it only when the owner asks.+ `user_roles` and the `feature_*` tables (`server/db/schemas/features.ts`) have no FK to `users` and no cascade: `purgeUserData` deletes them explicitly and anonymises `feature_audit_log` (see `docs/feature-flags.md`).+ `documents` (`server/db/schemas/documents.ts`) has no FK and no cascade: `purgeUserData` deletes its rows and the spec objects under `documents/<userId>/`, and the deletion hooks in `server/utils/documents/cleanup.ts` remove the rest (see `docs/d1-restore-reconciliation.md`).+ The skills tables (`skills`, `skill_versions`, `skill_files`, `skill_chat_settings`, `server/db/schemas/skills.ts`) have no FK and no cascade: `purgeUserSkills` deletes their rows and the objects under `user-skills/u<userId>/` and `skills-staging/u<userId>/`, and `cleanupSkillsForDeletedChats` removes the per-chat rows (see `docs/d1-restore-reconciliation.md`).+ - `packages/` - Workspace packages shared by the app and satellite Workers+   (`artifacts-protocol`)+ - `workers/` - Satellite Workers deployed by `deploy-satellites`+   (`artifacts-runtime`, see `docs/artifacts-runtime.md`)+ - `docs/mail-alerts.md` - Phone push for mail to `privacy@`, `abuse@`,+   `security@` and `contact@` (TCO one-hour rule, 72-hour breach clock): the+   `besidka-mail-alerts` Email Worker (`workers/mail-alerts/`) forwards first,+   exactly like the old Email Routing rule, then calls the HMAC-signed internal+   route `/api/v1/internal/mail-alert` over a service binding, which pushes to+   every admin; urgency rules (keywords, DMARC-checked authority domains), the+   KV collapse (2 min, urgent 60 s), what is logged (mailbox, urgent, outcome+   only), the legal note (no Privacy Policy change, no new Art. 30 row), the+   `MAIL_ALERTS_DEPLOY_ENABLED` CI gate, and the owner runbook (secrets, test+   rule, `cf email-routing rules update` per mailbox, restore to forward), and+   why there is no cover person (owner works alone, the push is the only+   safeguard)+ - `docs/chats/chat-input-markdown.md` - The Markdown-aware chat textarea+   (`useMarkdownTextarea`, also on the project instructions card): HTML paste+   conversion from Apple Mail, Gmail and web pages (the `shouldConvertHtml` gate+   that lets VS Code span soup fall through, `htmlToChatMarkdown`, bullet glyph+   normalisation for `text/plain`), long paste (over 1200 characters or 40+   lines) becoming a visual-only "Pasted text" chip (edit, Insert as text, max+   10) that is appended to the message as plain text on send, and why it is+   neither an uploaded file nor a message part, the keyboard rules (Enter+   inside an open fence does not send, Shift+Enter list continuation, Tab+   indent, IME guard), the single insertion helper that keeps native undo, and+   why a TipTap/ProseMirror editor was deferred+ - `docs/chats/context-panel.md` - The chat context panel: the contextual+   fifth pill slot (Chat button with an outputs badge on owned and shared chat+   pages, ⋯ More elsewhere), Pin sidebar and Cookie settings moving into the+   User menu on chat pages, Branch, Share and memory exclusion in the panel+   header, the Outputs, Inputs and Used sections, the+   `GET /api/v1/chats/[slug]/context` and shared aggregates, the section+   registry later features add to, and the `get_chat` context summary+ - `docs/chats/code-execution.md` - Provider-native "Run code" (Anthropic,+   OpenAI, Gemini sandboxes on the user's key): which models, the Labs opt-in+   gate and the silent drop when off, the stream transform that compacts runs

Showing the first 40 of each.

version

3.0.1 → 3.1.0

• + create_artifact
• + delete_artifacts
• + get_artifact
• + list_artifact_shares
• + list_artifacts
• + list_feature_access
• + list_feature_flags
• + list_my_features
• + revoke_artifact_shares
• + set_feature_access
• + share_artifact
• + update_artifact

version

2.1.0 → 3.0.1

version

1.1.0 → 2.1.0