Keysat
5faa5ae4d6
The email-capture "proposed grid notes" gain two review surfaces:
1. Inline source email — each proposed-note card on the Email Capture page
gets a "View email" toggle that lazily fetches the existing
GET /api/email/detail and shows from/to/cc/date/subject + scrollable body,
so a reviewer can judge the note against the email it was drafted from.
2. CRM->Matrix review bridge — the CRM (box, stdlib, no matrix-nio) can't post
to Matrix, so the intake bot (Spark) PULLS: GET /api/intake/email-proposals
returns to_post/open/to_close work-lists; the bot posts a review card
(metadata + snippet + draft note) to a dedicated review room
(MATRIX_EMAIL_REVIEW_ROOM) and relays in-thread yes / no / NL-edit
(POST .../{id}/decide, note revised via local Qwen). Decisions sync both
ways: web decide -> bot announces + closes the thread; Matrix decide -> the
web panel's ~25s poll clears the card. State lives CRM-side in the new
email_proposal_matrix side row (email-integration migration 0003, additive
+ idempotent CREATE TABLE IF NOT EXISTS), so it survives a bot restart.
Adds a 'bot' role (authenticated, never admin; require_bot_or_admin) to gate
the email-proposal endpoints rather than handing the bot full admin — the
principled base for the coming agentic capabilities. Role controls reach;
the draft->approve gate still controls autonomy (a human approves every write).
Deploy split: endpoints + migration + role + frontend ship in the s9pk; the
bot poll loop + review-room handling ship on the Spark. The bot's CRM user
must be flipped member->bot and joined to the review room (one-time).
Tests: backend/test_email_proposal_matrix.py + matrix_intake/test_email_proposals.py
(30/30 suite green, render-smoke green, migration verified twice on a DB copy).
25 lines
1.5 KiB
TypeScript
25 lines
1.5 KiB
TypeScript
import { VersionInfo } from '@start9labs/start-sdk'
|
|
|
|
// Email-proposal review over Matrix + a dedicated agent role. The CRM-drafted "proposed grid
|
|
// notes" (Email Capture panel) gain (1) a click-to-view inline popup of the source email
|
|
// (from/to/cc/date/subject/scrollable body, via the existing /api/email/detail) so a reviewer
|
|
// can judge the note against the email, and (2) a CRM→Matrix review bridge: the intake bot
|
|
// (Spark) pulls pending proposals, posts a review card to a dedicated review room, and relays
|
|
// the human's in-thread yes/no/edit back to the CRM — with the web panel and Matrix kept in
|
|
// sync (decide on either; the other surface reflects it). New side table email_proposal_matrix
|
|
// (email-integration migration 0003, additive + idempotent — CREATE TABLE IF NOT EXISTS) holds
|
|
// the per-proposal Matrix thread state. New bot-or-admin endpoints under /api/intake/
|
|
// email-proposals (list/mark/decide), gated by a new 'bot' role (authenticated, never admin).
|
|
// The bot's poll loop + review-room handling ship on the Spark (git pull + restart), not here.
|
|
export const v_0_1_0_89 = VersionInfo.of({
|
|
version: '0.1.0:89',
|
|
releaseNotes: {
|
|
en_US: [
|
|
'Email Capture: click a proposed grid note to see the source email inline',
|
|
'(from/to/cc/date/subject + body) before approving, and review/approve/dismiss/edit',
|
|
'proposals from a dedicated Matrix room on mobile — decisions sync both ways.',
|
|
].join(' '),
|
|
},
|
|
migrations: { up: async () => {}, down: async () => {} },
|
|
})
|