@oj-module/cli 0.2.66 → 0.2.67

package/templates/src/app/api/auth/_shared/wecom/client.ts

@@ -15,6 +15,8 @@
 
 const API_BASE = "https://qyapi.weixin.qq.com";
 const TIMEOUT_MS = 5000;
+/** 软超时的检查步长：主链路一结束，最坏再挂一个步长就收尾 */
+const TIMEOUT_STEP_MS = 50;
 const TOKEN_SKEW_SECS = 300;
 
 export interface WecomHttp {
@@ -37,6 +39,14 @@ export interface WecomClientDeps {
  * 软超时：服务端 isolate 无 `setTimeout` / `AbortSignal` 全局，不能用 `AbortSignal.timeout`。
  * 这里用运行时注入的 `tasks.sleep(ms)` 起一个「到点就 reject」的竞态；fetch 不被真正 abort，
  * 只是不再等它（后台连接最终由 OS/池回收）。`tasks` 不可用时降级为原 promise（无超时）。
+ *
+ * **必须短步长**：oj 运行时要等请求上下文里所有未完成的异步任务（含 `tasks.sleep`）
+ * 结束才 flush 响应。早期实现挂一条 `sleep(5000)` 做竞态，上游 100ms 就返回时那条
+ * sleep 仍在飞，于是每个调企微接口的请求都被白拖到 5s 才发得出响应——登录回调
+ * `/api/auth/wecom/callback` 实测恒定 5011ms，正是企微工作台进入 5-6s 白屏的来源。
+ * 改成按 `TIMEOUT_STEP_MS` 逐段 sleep 并检查 settled 后，主链路一结束、最多再挂
+ * 一个步长即收尾（<=50ms），超时语义不变。
+ *
  * 输家 promise 在 race 结束后仍可能 reject，挂 `.catch` 防 unhandled rejection。
  */
 function withSoftTimeout<T>(p: Promise<T>, ms: number): Promise<T> {
@@ -44,11 +54,21 @@ function withSoftTimeout<T>(p: Promise<T>, ms: number): Promise<T> {
 	const sleep = g.tasks?.sleep;
 	if (typeof sleep !== "function")
 		return p;
-	const timeout = sleep(ms).then(
-		() => { throw new Error(`超时 ${ms}ms`); },
-		() => undefined as never, // sleep 自身异常不中断主链路（返回 never 以免 race 结果退化为 void | T）
-	);
+	let settled = false;
+	const deadline = Date.now() + ms;
+	const timeout = (async () => {
+		for (;;) {
+			const left = deadline - Date.now();
+			if (settled || left <= 0)
+				break;
+			await sleep(Math.min(left, TIMEOUT_STEP_MS));
+		}
+		if (!settled)
+			throw new Error(`超时 ${ms}ms`);
+		return undefined as never;
+	})();
 	return Promise.race([p, timeout]).finally(() => {
+		settled = true;
 		// 输家 promise 在 race 结束后仍可能 reject，挂 catch 防 unhandled rejection
 		timeout.catch(() => {});
 	});

package/templates/src/app/api/home/migrations/0001__create_home_tables.mysql.sql

@@ -0,0 +1,14 @@
+-- 0001（mysql 方言）：home 两表建表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGINT AUTO_INCREMENT；TEXT 不能带字面默认值 → 收窄 VARCHAR(255)。
+CREATE TABLE IF NOT EXISTS home_pie (
+  id BIGINT AUTO_INCREMENT PRIMARY KEY,
+  category VARCHAR(255) NOT NULL DEFAULT '',
+  value INTEGER NOT NULL DEFAULT 0
+);
+
+CREATE TABLE IF NOT EXISTS home_line (
+  id BIGINT AUTO_INCREMENT PRIMARY KEY,
+  day INTEGER NOT NULL DEFAULT 0,
+  value INTEGER NOT NULL DEFAULT 0
+);
+

package/templates/src/app/api/home/migrations/0001__create_home_tables.pg.sql

@@ -0,0 +1,14 @@
+-- 0001（postgres 方言）：home 两表建表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGSERIAL（SERIAL 系允许 seed 显式写 id）；TEXT 在 pg 合法且可带默认值。
+CREATE TABLE IF NOT EXISTS home_pie (
+  id BIGSERIAL PRIMARY KEY,
+  category TEXT NOT NULL DEFAULT '',
+  value INTEGER NOT NULL DEFAULT 0
+);
+
+CREATE TABLE IF NOT EXISTS home_line (
+  id BIGSERIAL PRIMARY KEY,
+  day INTEGER NOT NULL DEFAULT 0,
+  value INTEGER NOT NULL DEFAULT 0
+);
+

package/templates/src/app/api/home/migrations/0002__tenant.pg.sql

@@ -0,0 +1,4 @@
+-- 0002__tenant（postgres 方言）：首页图表两表租户化。TEXT 在 pg 合法，与基础件同语法。
+ALTER TABLE home_pie ADD COLUMN tenant_id TEXT NOT NULL DEFAULT 'default';
+ALTER TABLE home_line ADD COLUMN tenant_id TEXT NOT NULL DEFAULT 'default';
+

package/templates/src/app/api/home/seed.mysql.sql

@@ -0,0 +1,71 @@
+-- 方言覆盖（mysql）：INSERT OR IGNORE → INSERT IGNORE，语句与基础件逐条对应。
+-- home 模块种子（P4-1）。按分号朴素切分（S006）。
+-- home_pie：五分类（code 对齐前端 DATA_KEY），幂等 INSERT OR IGNORE。
+INSERT IGNORE INTO home_pie (category, value) VALUES ('electronics', 320);
+INSERT IGNORE INTO home_pie (category, value) VALUES ('home_goods', 210);
+INSERT IGNORE INTO home_pie (category, value) VALUES ('apparel_accessories', 180);
+INSERT IGNORE INTO home_pie (category, value) VALUES ('food_beverages', 150);
+INSERT IGNORE INTO home_pie (category, value) VALUES ('beauty_skincare', 95);
+
+-- home_line：日窗口序列（day = epoch-day，种子围绕"当前日期"生成，约 60 天窗口）。
+-- 刻意缺 today-30 / today-12 两天，演示"缺哪天补哪天"——handler 在窗口内对缺失日补 0；
+-- 若整个窗口无 seed（seed 随时间变旧），handler 回落确定式趋势兜底（懒补数）。
+INSERT IGNORE INTO home_line (day, value) VALUES (20640, 181);
+INSERT IGNORE INTO home_line (day, value) VALUES (20641, 190);
+INSERT IGNORE INTO home_line (day, value) VALUES (20642, 199);
+INSERT IGNORE INTO home_line (day, value) VALUES (20643, 208);
+INSERT IGNORE INTO home_line (day, value) VALUES (20644, 217);
+INSERT IGNORE INTO home_line (day, value) VALUES (20645, 226);
+INSERT IGNORE INTO home_line (day, value) VALUES (20646, 235);
+INSERT IGNORE INTO home_line (day, value) VALUES (20647, 244);
+INSERT IGNORE INTO home_line (day, value) VALUES (20648, 253);
+INSERT IGNORE INTO home_line (day, value) VALUES (20649, 262);
+INSERT IGNORE INTO home_line (day, value) VALUES (20650, 271);
+INSERT IGNORE INTO home_line (day, value) VALUES (20651, 280);
+INSERT IGNORE INTO home_line (day, value) VALUES (20652, 289);
+INSERT IGNORE INTO home_line (day, value) VALUES (20653, 298);
+INSERT IGNORE INTO home_line (day, value) VALUES (20654, 100);
+INSERT IGNORE INTO home_line (day, value) VALUES (20655, 109);
+INSERT IGNORE INTO home_line (day, value) VALUES (20656, 118);
+INSERT IGNORE INTO home_line (day, value) VALUES (20657, 127);
+INSERT IGNORE INTO home_line (day, value) VALUES (20658, 136);
+INSERT IGNORE INTO home_line (day, value) VALUES (20659, 145);
+INSERT IGNORE INTO home_line (day, value) VALUES (20660, 154);
+INSERT IGNORE INTO home_line (day, value) VALUES (20661, 163);
+INSERT IGNORE INTO home_line (day, value) VALUES (20662, 172);
+INSERT IGNORE INTO home_line (day, value) VALUES (20663, 181);
+INSERT IGNORE INTO home_line (day, value) VALUES (20664, 190);
+INSERT IGNORE INTO home_line (day, value) VALUES (20665, 199);
+INSERT IGNORE INTO home_line (day, value) VALUES (20666, 208);
+INSERT IGNORE INTO home_line (day, value) VALUES (20667, 217);
+INSERT IGNORE INTO home_line (day, value) VALUES (20668, 226);
+INSERT IGNORE INTO home_line (day, value) VALUES (20669, 235);
+INSERT IGNORE INTO home_line (day, value) VALUES (20671, 253);
+INSERT IGNORE INTO home_line (day, value) VALUES (20672, 262);
+INSERT IGNORE INTO home_line (day, value) VALUES (20673, 271);
+INSERT IGNORE INTO home_line (day, value) VALUES (20674, 280);
+INSERT IGNORE INTO home_line (day, value) VALUES (20675, 289);
+INSERT IGNORE INTO home_line (day, value) VALUES (20676, 298);
+INSERT IGNORE INTO home_line (day, value) VALUES (20677, 100);
+INSERT IGNORE INTO home_line (day, value) VALUES (20678, 109);
+INSERT IGNORE INTO home_line (day, value) VALUES (20679, 118);
+INSERT IGNORE INTO home_line (day, value) VALUES (20680, 127);
+INSERT IGNORE INTO home_line (day, value) VALUES (20681, 136);
+INSERT IGNORE INTO home_line (day, value) VALUES (20682, 145);
+INSERT IGNORE INTO home_line (day, value) VALUES (20683, 154);
+INSERT IGNORE INTO home_line (day, value) VALUES (20684, 163);
+INSERT IGNORE INTO home_line (day, value) VALUES (20685, 172);
+INSERT IGNORE INTO home_line (day, value) VALUES (20686, 181);
+INSERT IGNORE INTO home_line (day, value) VALUES (20687, 190);
+INSERT IGNORE INTO home_line (day, value) VALUES (20689, 208);
+INSERT IGNORE INTO home_line (day, value) VALUES (20690, 217);
+INSERT IGNORE INTO home_line (day, value) VALUES (20691, 226);
+INSERT IGNORE INTO home_line (day, value) VALUES (20692, 235);
+INSERT IGNORE INTO home_line (day, value) VALUES (20693, 244);
+INSERT IGNORE INTO home_line (day, value) VALUES (20694, 253);
+INSERT IGNORE INTO home_line (day, value) VALUES (20695, 262);
+INSERT IGNORE INTO home_line (day, value) VALUES (20696, 271);
+INSERT IGNORE INTO home_line (day, value) VALUES (20697, 280);
+INSERT IGNORE INTO home_line (day, value) VALUES (20698, 289);
+INSERT IGNORE INTO home_line (day, value) VALUES (20699, 298);
+INSERT IGNORE INTO home_line (day, value) VALUES (20700, 100);

package/templates/src/app/api/home/seed.pg.sql

@@ -0,0 +1,71 @@
+-- 方言覆盖（postgres）：INSERT OR IGNORE → ON CONFLICT DO NOTHING，语句与基础件逐条对应。
+-- home 模块种子（P4-1）。按分号朴素切分（S006）。
+-- home_pie：五分类（code 对齐前端 DATA_KEY），幂等 INSERT OR IGNORE。
+INSERT INTO home_pie (category, value) VALUES ('electronics', 320) ON CONFLICT DO NOTHING;
+INSERT INTO home_pie (category, value) VALUES ('home_goods', 210) ON CONFLICT DO NOTHING;
+INSERT INTO home_pie (category, value) VALUES ('apparel_accessories', 180) ON CONFLICT DO NOTHING;
+INSERT INTO home_pie (category, value) VALUES ('food_beverages', 150) ON CONFLICT DO NOTHING;
+INSERT INTO home_pie (category, value) VALUES ('beauty_skincare', 95) ON CONFLICT DO NOTHING;
+
+-- home_line：日窗口序列（day = epoch-day，种子围绕"当前日期"生成，约 60 天窗口）。
+-- 刻意缺 today-30 / today-12 两天，演示"缺哪天补哪天"——handler 在窗口内对缺失日补 0；
+-- 若整个窗口无 seed（seed 随时间变旧），handler 回落确定式趋势兜底（懒补数）。
+INSERT INTO home_line (day, value) VALUES (20640, 181) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20641, 190) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20642, 199) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20643, 208) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20644, 217) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20645, 226) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20646, 235) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20647, 244) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20648, 253) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20649, 262) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20650, 271) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20651, 280) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20652, 289) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20653, 298) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20654, 100) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20655, 109) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20656, 118) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20657, 127) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20658, 136) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20659, 145) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20660, 154) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20661, 163) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20662, 172) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20663, 181) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20664, 190) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20665, 199) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20666, 208) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20667, 217) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20668, 226) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20669, 235) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20671, 253) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20672, 262) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20673, 271) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20674, 280) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20675, 289) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20676, 298) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20677, 100) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20678, 109) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20679, 118) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20680, 127) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20681, 136) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20682, 145) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20683, 154) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20684, 163) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20685, 172) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20686, 181) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20687, 190) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20689, 208) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20690, 217) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20691, 226) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20692, 235) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20693, 244) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20694, 253) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20695, 262) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20696, 271) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20697, 280) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20698, 289) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20699, 298) ON CONFLICT DO NOTHING;
+INSERT INTO home_line (day, value) VALUES (20700, 100) ON CONFLICT DO NOTHING;

package/templates/src/app/api/notification/_shared/notify.ts

@@ -69,11 +69,9 @@ function splitId(id: string): [scope: "u" | "b", raw: string] {
 function mapItem(r: Row): NoticeItem {
 	const scope = String(r.scope);
 	const isBroadcast = scope === "broadcast";
-	// UNION 结果列名取首分支（userQ）=> 位置 4 名为 is_read。按人项此处即存储整数列；
-	// 广播项此处实际承载回执 read_time（非空即已读，与原始 SQL 的 (read_time IS NOT NULL AND <> '') 等价）。
-	const isRead = isBroadcast
-		? (r.is_read != null && String(r.is_read) !== "")
-		: Number(r.is_read) === 1;
+	// UNION 结果列名取首分支（userQ）=> 位置 4 名为 is_read，两分支都输出整数 0/1
+	// （按人项取存储列，广播项由回执 EXISTS 推导），故统一按整数判已读。
+	const isRead = Number(r.is_read) === 1;
 	return {
 		id: (isBroadcast ? "b:" : "u:") + String(r.id),
 		scope: isBroadcast ? "broadcast" : "user",
@@ -172,7 +170,9 @@ export async function noticesFor(
 		"b.id",
 		"b.avatar",
 		"b.date",
-		"r.read_time",
+		// 第 4 列与首分支 is_read 同型（整数）：pg 的 UNION 不允许 integer/text 混排，
+		// sqlite/mysql 会隐式放宽；回执存在即已读 → 0/1，mapItem 统一按 Number(...) === 1 判定。
+		{ case: { when: [{ cond: { field: "r.read_time", op: "isnull" }, then: 0 }], else: 1 }, as: "is_read" },
 		"b.message",
 		"b.title",
 		"b.link",

package/templates/src/app/api/notification/migrations/0001__create_notifications.mysql.sql

@@ -0,0 +1,11 @@
+-- 0001（mysql 方言）：通知表建表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGINT AUTO_INCREMENT；TEXT 不能带字面默认值 → 短文本收窄 VARCHAR，长文本用括号默认值。
+CREATE TABLE IF NOT EXISTS notifications (
+  id BIGINT AUTO_INCREMENT PRIMARY KEY,
+  avatar VARCHAR(255) NOT NULL DEFAULT '',
+  `date` VARCHAR(64) NOT NULL DEFAULT '',
+  is_read INTEGER NOT NULL DEFAULT 0,
+  message TEXT NOT NULL DEFAULT (''),
+  title VARCHAR(255) NOT NULL DEFAULT ''
+);
+

package/templates/src/app/api/notification/migrations/0001__create_notifications.pg.sql

@@ -0,0 +1,11 @@
+-- 0001（postgres 方言）：通知表建表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGSERIAL（SERIAL 系允许 seed 显式写 id）；TEXT 在 pg 合法且可带默认值。
+CREATE TABLE IF NOT EXISTS notifications (
+  id BIGSERIAL PRIMARY KEY,
+  avatar TEXT NOT NULL DEFAULT '',
+  date TEXT NOT NULL DEFAULT '',
+  is_read INTEGER NOT NULL DEFAULT 0,
+  message TEXT NOT NULL DEFAULT '',
+  title TEXT NOT NULL DEFAULT ''
+);
+

package/templates/src/app/api/notification/migrations/0002__notifications_user.mysql.sql

@@ -0,0 +1,8 @@
+-- 0002（mysql 方言）：按人真实通知表演进。
+-- 方言差异：TEXT 不能带字面默认值 → category 收窄 VARCHAR(255)；MySQL 不支持 CREATE INDEX IF NOT EXISTS，直接建索引。
+ALTER TABLE notifications ADD COLUMN user_id INTEGER;
+ALTER TABLE notifications ADD COLUMN link TEXT;
+ALTER TABLE notifications ADD COLUMN category VARCHAR(255) NOT NULL DEFAULT 'notice';
+CREATE INDEX idx_notifications_user ON notifications (user_id, is_read);
+UPDATE notifications SET user_id = 1, category = 'notice' WHERE user_id IS NULL;
+

package/templates/src/app/api/notification/migrations/0003__notifications_broadcast.mysql.sql

@@ -0,0 +1,21 @@
+-- 0003（mysql 方言）：广播表 + 已读回执表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGINT AUTO_INCREMENT；CREATE INDEX IF NOT EXISTS 不被 MySQL 支持，索引写进建表语句。
+CREATE TABLE IF NOT EXISTS notifications_broadcast (
+  id BIGINT AUTO_INCREMENT PRIMARY KEY,
+  avatar VARCHAR(255) NOT NULL DEFAULT '',
+  `date` VARCHAR(64) NOT NULL DEFAULT '',
+  message TEXT NOT NULL DEFAULT (''),
+  title VARCHAR(255) NOT NULL DEFAULT '',
+  link TEXT,
+  category VARCHAR(255) NOT NULL DEFAULT 'notice',
+  create_time VARCHAR(64) NOT NULL DEFAULT ''
+);
+
+CREATE TABLE IF NOT EXISTS notifications_broadcast_read (
+  id BIGINT AUTO_INCREMENT PRIMARY KEY,
+  broadcast_id BIGINT NOT NULL,
+  user_id BIGINT NOT NULL,
+  read_time VARCHAR(64) NOT NULL DEFAULT '',
+  KEY idx_broadcast_read (user_id, broadcast_id)
+);
+

package/templates/src/app/api/notification/migrations/0003__notifications_broadcast.pg.sql

@@ -0,0 +1,22 @@
+-- 0003（postgres 方言）：广播表 + 已读回执表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGSERIAL（SERIAL 系允许 seed 显式写 id）；其余 DDL 与基础件同语法。
+CREATE TABLE IF NOT EXISTS notifications_broadcast (
+  id BIGSERIAL PRIMARY KEY,
+  avatar TEXT NOT NULL DEFAULT '',
+  date TEXT NOT NULL DEFAULT '',
+  message TEXT NOT NULL DEFAULT '',
+  title TEXT NOT NULL DEFAULT '',
+  link TEXT,
+  category TEXT NOT NULL DEFAULT 'notice',
+  create_time TEXT NOT NULL DEFAULT ''
+);
+
+CREATE TABLE IF NOT EXISTS notifications_broadcast_read (
+  id BIGSERIAL PRIMARY KEY,
+  broadcast_id BIGINT NOT NULL,
+  user_id BIGINT NOT NULL,
+  read_time TEXT NOT NULL DEFAULT ''
+);
+
+CREATE INDEX IF NOT EXISTS idx_broadcast_read ON notifications_broadcast_read (user_id, broadcast_id);
+

package/templates/src/app/api/notification/migrations/0004__notifications_broadcast_hidden.mysql.sql

@@ -0,0 +1,10 @@
+-- 0004（mysql 方言）：广播隐藏标记表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGINT AUTO_INCREMENT；CREATE INDEX IF NOT EXISTS 不被 MySQL 支持，索引写进建表语句。
+CREATE TABLE IF NOT EXISTS notifications_broadcast_hidden (
+  id BIGINT AUTO_INCREMENT PRIMARY KEY,
+  broadcast_id BIGINT NOT NULL,
+  user_id BIGINT NOT NULL,
+  create_time VARCHAR(64) NOT NULL DEFAULT '',
+  KEY idx_broadcast_hidden (user_id, broadcast_id)
+);
+

package/templates/src/app/api/notification/migrations/0004__notifications_broadcast_hidden.pg.sql

@@ -0,0 +1,11 @@
+-- 0004（postgres 方言）：广播隐藏标记表。口径同基础件。
+-- 方言差异：AUTOINCREMENT → BIGSERIAL（SERIAL 系允许 seed 显式写 id）；其余 DDL 与基础件同语法。
+CREATE TABLE IF NOT EXISTS notifications_broadcast_hidden (
+  id BIGSERIAL PRIMARY KEY,
+  broadcast_id BIGINT NOT NULL,
+  user_id BIGINT NOT NULL,
+  create_time TEXT NOT NULL DEFAULT ''
+);
+
+CREATE INDEX IF NOT EXISTS idx_broadcast_hidden ON notifications_broadcast_hidden (user_id, broadcast_id);
+

package/templates/src/app/api/notification/migrations/0005__tenant.pg.sql

@@ -0,0 +1,6 @@
+-- 0005__tenant（postgres 方言）：通知四表租户化。TEXT 在 pg 合法，与基础件同语法。
+ALTER TABLE notifications ADD COLUMN tenant_id TEXT NOT NULL DEFAULT 'default';
+ALTER TABLE notifications_broadcast ADD COLUMN tenant_id TEXT NOT NULL DEFAULT 'default';
+ALTER TABLE notifications_broadcast_read ADD COLUMN tenant_id TEXT NOT NULL DEFAULT 'default';
+ALTER TABLE notifications_broadcast_hidden ADD COLUMN tenant_id TEXT NOT NULL DEFAULT 'default';
+

package/templates/src/app/api/notification/seed.mysql.sql

@@ -0,0 +1,8 @@
+-- 方言覆盖（mysql）：INSERT OR IGNORE → INSERT IGNORE，语句与基础件逐条对应。
+-- notification 模块种子（按人真实通知）。user_id=1（admin），link/category 幂等可空/默认。
+-- avatar 给真实 URL：铃铛按 avatar 渲染头像，空串会破图（空串仅作为运行时兜底，不作为种子值）。
+-- 按分号朴素切分（S006）：语句内不得含分号字面量。
+INSERT IGNORE INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (1, 1, 'https://avatar.vercel.sh/seed-welcome.svg?text=W', '2026-09-01 09:12', 0, '脚手架已就绪，用 admin / aA123456 登录开始', '欢迎', NULL, 'notice');
+INSERT IGNORE INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (2, 1, 'https://avatar.vercel.sh/seed-bell.svg?text=B', '2026-09-02 14:30', 0, '通知铃支持单条已读、全部已读与清空；广播经 push-broadcast 入 b: 命名空间', '通知铃', NULL, 'notice');
+INSERT IGNORE INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (3, 1, 'https://avatar.vercel.sh/seed-contract.svg?text=C', '2026-09-03 18:45', 1, '契约改动后重跑 ojm api 生成前端 client 与文档', '契约', NULL, 'notice');
+INSERT IGNORE INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (4, 1, 'https://avatar.vercel.sh/seed-dev.svg?text=D', '2026-09-04 08:00', 0, '编辑 api/src 下的 api.ts 保存即热更；handler 组支持四层嵌套（oj v0.1.64）', '开发提示', NULL, 'notice');

package/templates/src/app/api/notification/seed.pg.sql

@@ -0,0 +1,11 @@
+-- 方言覆盖（postgres）：INSERT OR IGNORE → ON CONFLICT DO NOTHING，语句与基础件逐条对应。
+-- notification 模块种子（按人真实通知）。user_id=1（admin），link/category 幂等可空/默认。
+-- avatar 给真实 URL：铃铛按 avatar 渲染头像，空串会破图（空串仅作为运行时兜底，不作为种子值）。
+-- 按分号朴素切分（S006）：语句内不得含分号字面量。
+INSERT INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (1, 1, 'https://avatar.vercel.sh/seed-welcome.svg?text=W', '2026-09-01 09:12', 0, '脚手架已就绪，用 admin / aA123456 登录开始', '欢迎', NULL, 'notice') ON CONFLICT DO NOTHING;
+INSERT INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (2, 1, 'https://avatar.vercel.sh/seed-bell.svg?text=B', '2026-09-02 14:30', 0, '通知铃支持单条已读、全部已读与清空；广播经 push-broadcast 入 b: 命名空间', '通知铃', NULL, 'notice') ON CONFLICT DO NOTHING;
+INSERT INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (3, 1, 'https://avatar.vercel.sh/seed-contract.svg?text=C', '2026-09-03 18:45', 1, '契约改动后重跑 ojm api 生成前端 client 与文档', '契约', NULL, 'notice') ON CONFLICT DO NOTHING;
+INSERT INTO notifications (id, user_id, avatar, date, is_read, message, title, link, category) VALUES (4, 1, 'https://avatar.vercel.sh/seed-dev.svg?text=D', '2026-09-04 08:00', 0, '编辑 api/src 下的 api.ts 保存即热更；handler 组支持四层嵌套（oj v0.1.64）', '开发提示', NULL, 'notice') ON CONFLICT DO NOTHING;
+
+-- 显式写 id 不会推进 BIGSERIAL 序列，补一次 setval 免新增行撞主键（幂等，每次启动按当前最大 id 校正）。
+SELECT setval(pg_get_serial_sequence('notifications', 'id'), GREATEST((SELECT MAX(id) FROM notifications), 1));

package/templates/src/app/api/publish/_shared/identity.ts

@@ -0,0 +1,69 @@
+// 发布身份的推导规则 —— **唯一真源**。
+//
+// 为什么只在服务端算：`key_id` 直接决定 `~/.ojm/keys/<id>/` 的目录名与签名身份，
+// 同一规则若在 `packages/cli` 与模板工程（互不可 import 的两棵树）各写一份，必然漂移，
+// 表现为「CLI 建了 demo-solution.wecom-everpan，服务端记录成 demo-solution.wecom-everpan-x」。
+// 故 key_id 在**申请时**由本文件算好落库，兑换接口原样下发，CLI 零推导。
+//
+// 规则与约束：
+//   · 产品名 = 解决方案名，遵循 NAME_RE（小写字母开头，仅 [a-z0-9-]，≤64）
+//   · 人名段 = username 归一化：小写 → 非 [a-z0-9-] 一律替换为 '-' → 折叠连续 '-' → 去首尾 '-'
+//     （`wecom:everpan` → `wecom-everpan`，目录名不出现冒号；比对也无需回到裸人名）
+//   · key_id = `<product>.<person>`，必须满足 C2-37 的 key_id 形状
+//   · 归一化后为空（例如纯中文用户名）→ 退化为 `u<uid>`，保证仍满足 key_id 形状
+
+/** C2-37 key_id 形状：小写、≥2 段、仅 [a-z0-9-]（与 packages/cli/src/keygen.ts 的 isValidKeyId 同规则） */
+export const KEY_ID_RE = /^[a-z][a-z0-9-]*(?:\.[a-z0-9-]+)+$/;
+
+/** 解决方案名规则（与 packages/cli/src/manifest-contract.ts 的 NAME_RE 同规则） */
+export const PRODUCT_RE = /^[a-z][a-z0-9-]{0,63}$/;
+
+/**
+ * 保留名：产品名占用它们会让人误以为是框架/平台自身发布的包。
+ * 与 manifest-contract 的 RESERVED_NAMES 取交集（`_platform` / `_system` 等带下划线的
+ * 本就过不了 PRODUCT_RE，不必重复列）。
+ */
+export const RESERVED_PRODUCTS = new Set(["oj", "ojm", "system", "auth", "market", "framework", "health", "plugins", "registry"]);
+
+/** 凭证有效期：7 天（一次性令牌的暴露窗口） */
+export const CREDENTIAL_TTL_SECS = 7 * 24 * 3600;
+
+export interface IdentityInput {
+	product: string
+	username: string
+	uid: number
+}
+
+/** username → key_id 的人名段 */
+export function encodePerson(username: string, uid: number): string {
+	const normalized = username
+		.toLowerCase()
+		.replace(/[^a-z0-9-]/g, "-")
+		.replace(/-+/g, "-")
+		.replace(/^-|-$/g, "");
+	return normalized === "" ? `u${uid}` : normalized;
+}
+
+/** 产品名 + 用户名 → key_id（不做校验，调用方先用 assertProduct 收口） */
+export function deriveKeyId(input: IdentityInput): string {
+	return `${input.product}.${encodePerson(input.username, input.uid)}`;
+}
+
+/** 产品名校验：形状 + 保留名。错误信息给可用示例，避免用户反复试错 */
+export function assertProduct(value: unknown): string {
+	const product = typeof value === "string" ? value.trim() : "";
+	if (product === "")
+		throw Object.assign(new Error("产品名不能为空：填你要发布的解决方案名，例如 demo-solution"), { status: 400 });
+	if (!PRODUCT_RE.test(product))
+		throw Object.assign(new Error("产品名只能是小写字母开头的 [a-z0-9-]，最长 64 个字符，例如 demo-solution"), { status: 400 });
+	if (RESERVED_PRODUCTS.has(product))
+		throw Object.assign(new Error(`产品名 ${product} 是框架保留名，请换成你的解决方案名`), { status: 400 });
+	return product;
+}
+
+/** 派生结果自检：理论上必然成立，不成立说明归一化有 bug，宁可 500 也不发一个畸形身份 */
+export function assertKeyId(keyId: string): string {
+	if (!KEY_ID_RE.test(keyId))
+		throw new Error(`内部错误：推导出的发布身份 ${keyId} 不符合 key_id 规则，请联系管理员`);
+	return keyId;
+}