@geoly-ai/social-hub-cli 0.3.2 → 0.3.4

package/skills/reddit-strategy-shared/references/handoff-schemas.md

@@ -69,8 +69,8 @@ Required:
 - `memory/phase4-内容排期表.md`
 - `memory/phase4-brand-risk-review.md` for any batch with brand-word rows, PGC rows, comparison/review language, external links, product claims, prior negative signals, or subreddit sensitivity; otherwise an explicit low-risk waiver from `reddit-brand-risk-response`
 - `memory/phase4-叙事指纹索引.md` exists as a fixed table with the schema header (`WindowCount`, `WindowDays`, `WindowScope`, `WindowSort`, `BaselineMaxAgeDays`, `HashSchemaVersion`, `IndexRevision`), and has exactly one active `Planned` row for every briefed post Key
-- a valid `SampleSetID` (subreddit baseline, 5–10 recent real posts, word-count median + IQR, with `AcquiredAt` / `ValidUntil`) for every target subreddit in the batch; missing or expired baseline is a `BlockingGap`
-- every post Brief row carries the nine `LockedFingerprintFields` (`ContentFunction`, `StructureFamily`, `OpeningMove`, `EvidenceShape`, `BrandEntryMode`, `CaveatMode`, `EndingMode`, `LengthBand`, `AnchorSlot`) and the four `TraceFields` (`SampleSetID`, `RecentCollisionCheck`, `MappingRuleID`, `MappingVersion`)
+- a valid `SampleSetID` (flair-level subreddit baseline, 5–10 recent real posts, word-count median + IQR, with `AcquiredAt` / `ValidUntil`) for every target subreddit in the batch, recording flair coverage (`BaselineScope` / `BaselineFlair` / `FlairCoverageStatus`); missing or expired baseline, or `FlairCoverageStatus: Insufficient`, is a `BlockingGap`
+- every post Brief row carries the nine `LockedFingerprintFields` (`ContentFunction`, `StructureFamily`, `OpeningMove`, `EvidenceShape`, `BrandEntryMode`, `CaveatMode`, `EndingMode`, `LengthBand`, `AnchorSlot`), the two `PrewritingControlFields` (`AssignedFlair` non-empty; `PostingTrigger` from the controlled five values satisfying the `PostingTrigger × BrandEntryMode` cross-constraint), and the four `TraceFields` (`SampleSetID`, `RecentCollisionCheck`, `MappingRuleID`, `MappingVersion`)
 - every post Brief row carries a `Routing Decision` block with the five candidate-narrowing steps, `MatchedPredicate`, `SelectedStructureFamily`, and `CollisionRepairPath`
 - `RecentCollisionCheck` is `Pass` (or `Exception` with an approved `ExceptionRef`) for every row
 - `brief_approval_mode`
@@ -118,6 +118,8 @@ ForbiddenStructuralChanges:
 PrimaryPostType:              # one of the authoritative 9
 MappingRuleID:                # when a client prototype applies
 StructureFamily:
+AssignedFlair:                # PrewritingControlField; non-empty; NoFlairAvailable/NoFlairRequired for flairless boards
+PostingTrigger:               # PrewritingControlField; controlled 5 values; not in the collision triple
 OpeningMove:
 EvidenceShape:
 BrandEntryMode:
@@ -125,6 +127,7 @@ CaveatMode:
 EndingMode:
 LengthBand:
 SampleSetID:
+FlairCoverageStatus:          # Exact | ApprovedFallback (Insufficient is a BlockingGap upstream)
 AnchorSlot:                   # single value, never an "A + B" composite
 SecondaryAnchorSlot:          # only for >350-word posts with two ABUs; "—" otherwise
 RecentCollisionCheck:
@@ -148,6 +151,7 @@ Rules:
   in the source, do not guess one and do not load `推荐转化叙事`.
 - Rewrite may only fix factual expression, marketing tone, readability, and explicitly flagged problems.
 - Rewrite may not reorder sections, add a failed attempt, add a question ending, add a caveat, add a community-observation line, move the brand mention, change `AnchorSlot`, or change any of the nine `LockedFingerprintFields`.
+- Rewrite must **preserve `PostingTrigger`** for `ArtifactType: Post`: a body edit that changes the post's real-world trigger (or that breaks the `PostingTrigger × BrandEntryMode` cross-constraint) is out of allowance — flag it instead of applying, so the finished body still re-derives to the `Planned` `PostingTrigger`.
 - Hub `optimized` output that changes a protected structure field may not be adopted wholesale; record `HubStructureConflictStatus: None | Escalated` (see `content-review-gate.md` §3.1). `Escalated` holds the draft and routes to `reddit-phase-brief`.
 - `reddit-content-rewrite` does **not** own `memory/phase4-叙事指纹索引.md`. When its edits change the body, it returns `FingerprintSyncRequired: Yes` / `FingerprintSyncStatus: PendingWritingOwner`; `reddit-content-writing` (the index owner) performs the re-review and hash write-back.
 
@@ -179,7 +183,7 @@ Required:
 - `memory/content-review-log.md`
 - `memory/phase4-叙事指纹索引.md` has exactly one active `Final` row for every delivered **main-post** Key (`WindowScope: PostOnly`; comments and external comments need no fingerprint row, only Hub `FinalDraftSha256`)
 - each `Final` row's `DraftHash` equals the `FinalDraftSha256` in `memory/content-review-log.md` and a recomputation from the delivered text using `HashSchemaVersion: reddit-final-draft-sha256-v1`
-- all nine `LockedFingerprintFields` of a delivered post match the Brief's `Planned` values
+- all nine `LockedFingerprintFields` of a delivered post match the Brief's `Planned` values, and the two `PrewritingControlFields` match too: `AssignedFlair` equals the Brief value (and the baseline flair coverage it was written against), and the delivered body's re-derived `PostingTrigger` equals the `Planned` value while satisfying the `PostingTrigger × BrandEntryMode` cross-constraint
 - no delivered post Key collides with any other Key in the rolling window unless an approved `ExceptionRef` exists
 - every post/comment to be delivered has Hub `executionStatus=completed` and `verdict=pass`
 - final delivery rows have `ReviewMode: AccountBound` and a real `accountId`

package/skills/social-hub-cli/SKILL.md

@@ -54,6 +54,8 @@ social-hub version --json
 
 命中上表场景时，**打开对应领域 skill**；不要在总路由里重复展开领域命令细节。
 
+> **深度历史（绝对日期 / 往年 / 跨年 / 长期趋势）不是 Hub 能力。** `social-hub intelligence hot-posts` 只读 Hub 近实时缓存（当下热帖，且仅覆盖已入库 watchlist 板块），**不持有深度归档**。凡「历史帖 / 往年数据 / 某年某月 / 绝对日期区间 / 长期趋势演变 / 建 baseline 需历史样本」或用户明确「只用 Arctic」，改用 `reddit-voc-volume` 的 `history` 模式（Arctic Shift 权威源），**不要**用 `intelligence hot-posts` 顶替。注意「最近一天 / 周 / 月」仍是当下声量，走 `reddit-voc-volume` 的 `keyword` / `subreddit`（Hub-First），也不是 hot-posts。详见 `social-hub-intelligence` 的「热帖」三态路由。
+
 ## CLI 新版本提醒
 
 运行任意子命令时（`version`/`help` 除外），CLI 会检测 npm 上的最新版并在 stderr 提示升级；**Agent 应转告用户** 并执行 `npm install -g @geoly-ai/social-hub-cli@latest`。CLI 升级后，新发布的 skill 会在后续运行时同步到已托管目录（含本次新增的 skill）——开启 `SOCIAL_HUB_SKILLS_AUTO_UPDATE=1` 时自动完成，未开启则在 stderr 提示你补齐；无论哪种，手动补齐一律用 `social-hub skills install`（**不是** `update` —— `update` 只刷新已安装的 skill，不会装上新增的）。详见 `social-hub-shared` 的「CLI 新版本检测」。

package/skills/social-hub-intelligence/SKILL.md

@@ -185,6 +185,39 @@ social-hub intelligence hot-posts-create -j '{ ... }'
 social-hub intelligence hot-posts-export --subreddit technology > hot-posts.csv
 ```
 
+**口径（`hot-posts` = Hub 近实时缓存，不是历史/归档源）**：`hot-posts` /
+`hot-posts-export` 只返回 Hub **当下/近期**已缓存的热帖快照，且**仅覆盖已入库
+watchlist 的 subreddit**（未监控的板块查不到）。它读的是 Hub 缓存，**不是深度归档**，
+不持有往年数据、不支持时间窗回溯。
+
+**负路由（何时 _不_ 用 hot-posts，改用 `reddit-voc-volume` 的 `history` 深归档模式）**：凡下列
+**深度历史**意图**一律不要用 `hot-posts`**，必须改用 **`reddit-voc-volume` 的 `history` 模式**
+（Arctic Shift 深度归档，2005 至今权威源，正文不截断）：
+
+- 历史帖 / 往年数据 / 某年某月的帖子 / 回溯到 20xx 年 / 截至某日
+- 任意**绝对日期区间**回溯、早于 Hub 覆盖窗口的样本
+- 过去 N 年、跨年 / 同比、按季度、**长期趋势 / 趋势演变**、逐年 / 逐月抽样、历史基准 / 回测
+- 建 subreddit baseline 卡需要历史正文样本 / 长度分布语料
+- 未入库 watchlist 的 subreddit 的历史内容（hot-posts 根本查不到）
+
+**用户明确要「只用 Arctic」/「不要用 Hub 数据」时**：固定走 `reddit-voc-volume history`
+（脚本层恒 `arctic_search_posts`、**不接受** `--acquisition-policy`、provenance 恒
+`arctic_shift`），**绝不**用 `hot-posts` 顶替——hot-posts 拿到的是 Hub 缓存，不是 Arctic。
+
+**近期窗口 carve-out（别把「最近」误判成深归档）**：「最近一天 / 一周 / 一月、本周、本月、
+当前热度」仍是**当下声量**，**不进 `history`**；但它也不等于 `hot-posts`——按关键词 / 板块
+的近期声量查询应走 **`reddit-voc-volume` 的 `keyword` / `subreddit` 模式（Hub-First，
+`--hub-time-window day|week|month`）**。`hot-posts` 只负责 Hub 已缓存的 watchlist 当前热榜快照。
+
+**三态路由判据**：
+
+1. 要「**Hub watchlist 现在的热榜 / 缓存快照**」（现在热什么、导出近期热帖 CSV）→ `hot-posts`（本命令，照常用）。
+2. 要「**最近一天 / 周 / 月的关键词或板块当下声量**」→ `reddit-voc-volume` 的 `keyword` / `subreddit`（Hub-First）。
+3. 要「**绝对历史日期 / 跨年 / 早于 Hub 覆盖 / 历史 baseline / 长期趋势演变**」→ `reddit-voc-volume` 的 `history`（Arctic 权威源）。
+
+**hot-posts 的合法用途（照常用，别误伤）**：查「当下 watchlist 热榜」、消费 Hub 已缓存的热帖
+快照、按 watchlist 板块看当前热度榜、导出近期热帖 CSV。
+
 ## KOL
 
 ```bash