delivery: hand reports and schedule drafts to the host (callback and webhook)

未关闭
#517 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, react, web-dev

调研方向

Read PRODUCT.md and the related issues #163, #513, and #267 to understand existing reporting, draft quotas, and host hooks. Trace how the MCP draft_schedule result and front end request are handled, then identify the library and server entry points for the handoff. Done means both callback and signed webhook handoffs are covered, with documentation explaining the host's responsibilities and what pivotkit never does.

由索引模型根据 Issue 内容生成。

描述

area:server enhancement

Step 5 of #165: hand a report and its schedule draft to the host, so the host can schedule, approve and send it. pivotkit has no scheduler or mail sender (PRODUCT.md).

  • A host callback in the library and the server: called with the report document (file or HTML) and the draft (view, format, recipients as the user asked, cadence).
  • A webhook: an HTTP call with the same document, signed, with the operator's target and limits.
  • The MCP draft_schedule result and the front end's request go through the same handoff.
  • Docs: what the host must do (approve, resolve recipients, send, keep copies) and what pivotkit never does.

Related: #163 (deterministic workbooks for repeated reports), #513 (drafts quota), #267 (host hooks).

主要语言
JavaScript
星标
1
派生
1
平均合并
3 小时 34 分钟
30 天内合并 PR
213

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

eizedev/pivotkit 的其他 Issue

查看 eizedev/pivotkit 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。