@geoly-ai/social-hub-cli 0.3.18 → 0.3.20

package/skills/reddit-content-writing/SKILL.md

@@ -29,7 +29,7 @@ This skill writes planned Reddit posts and comments. It does not redo strategy,
 
 ## Source Reference
 
-- `references/phase4-writing.md` — W-1 baseline verification, W-1.5 fingerprint collision check, W-3 StructureFamily confirmation (the family is pre-assigned by the Brief; writing confirms, never picks), ABU / AnchorSlot rules, W-5 structure-preserving rewrite handoff
+- `references/phase4-writing.md` — W-1 baseline verification (all **10** baseline dimensions; the 10th is the em-dash / parenthesis usage distribution), **W-1.b-brand `BrandPlacementGate`** (title generation and `BrandEntryMode` must cite the brand-first-mention histogram / SRP `brandFirstMentionHistogram`; never derive title-brand exposure from the P-B label; `PGCApproved` and `BrandReviewPost` title exposure stays legal), W-1.5 fingerprint collision check, W-3 StructureFamily confirmation (the family is pre-assigned by the Brief; writing confirms, never picks), **G1 internal-label outbound check** (reader-facing text carries only the Brief's `ReaderVisiblePremise`; fanout coverage as query-as-content stays legal, and the Feishu `[Fanout]` red line is an internal annotation), **G4 material-modality drift check** (writing/rewrite may never upgrade an `Optional` selling point into a required one), ABU / AnchorSlot rules, W-5 structure-preserving rewrite handoff
 - `references/phase4-execution-table.md` for the **core 16-field schema + 3 audit control columns** (`RewriteModule`, `AnchorSlot`, `SecondaryAnchorSlot`), the three independent routing axes (`客户内容原型` / `主帖型代码` / `StructureFamily`), unmapped-prototype blocking, complement rules, EPA control records, and batch-map gate
 - `references/post-writing-templates.md` — **the StructureFamily library (16 new families; 31 in total with the 15 in `writing-examples.md`) and its hard selection order**, ContentFunction minimum-information requirements, real-limitation (caveat) rules, and the 0–2 cap on surface colloquial signals
 - `references/writing-examples.md` — **15 StructureFamily reference posts with routing metadata**; this is a routing target, not optional reading. Every piece must inherit one family's information topology
@@ -37,7 +37,9 @@ This skill writes planned Reddit posts and comments. It does not redo strategy,
 - `references/pgc-writing-strategy.md` when writing PGC posts
 - `references/comp-mention-strategy.md` only when competitor mention permission is explicitly `Yes`
 - installed `reddit-brand-risk-response` output for pre-publish bot/shill/promo/claim risk gates when the batch is not explicitly low risk
-- `../reddit-strategy-shared/references/content-review-gate.md` for the mandatory Social Hub review loop
+- `../reddit-strategy-shared/references/content-review-gate.md` for the mandatory Social Hub review loop, including how to read a dimension the Hub result reports as `not_assessed`
+- `../reddit-strategy-shared/references/persona-card-contract.md` for the Brief-assigned Persona Card this skill writes **inside** and never authors
+- `../reddit-strategy-shared/references/native-copy-profile.md` only when the batch runs `AcceptanceProfile: NativeCopy`
 
 ## Gate
 
@@ -49,6 +51,7 @@ Additionally, stop before writing a single word of body copy if any of these hol
 - a main-post row has no `StructureFamily` assigned by the Brief
 - a main-post row has no `AssignedFlair`, or the baseline card's `FlairCoverageStatus` is `Insufficient` → `BlockingGap`, return to `reddit-phase-brief`
 - a main-post row has no `PostingTrigger` assigned by the Brief, or its `Planned` `PostingTrigger` already violates the `PostingTrigger × BrandEntryMode` cross-constraint → `BlockingGap` (the post-draft re-derive of `PostingTrigger` vs `Planned` is checked after drafting, in the Writing Rules, not here)
+- a main-post row has no `PersonaCardRef` assigned by the Brief → `BlockingGap`, return to `reddit-phase-brief`. **Never author a Card here**: a writer that supplies its own knowledge boundary grants itself exactly the boundary the draft needs, which is the bypass pre-assignment exists to close
 - a target subreddit has no baseline card, or it is `Expired` / `Incomplete` → `BlockingGap: BaselineMissingOrStale`
 - `memory/phase4-叙事指纹索引.md` has not been read, or the rolling-window collision check has not been run
 - the collision check fails and no sample-based exception is on record → `BlockingGap: StructureCollision`, return to `reddit-phase-brief`
@@ -78,6 +81,17 @@ C-B/C-NB, and rows that were previously low risk.
    persona or inline style guide. Resolve an approved `brandContext` when Hub
    requires an explicit brand relationship; do not guess a brand or send an
    arbitrary `stage` value.
+   **Never add the Persona Card, any Card field, or a Card-derived score to the
+   request, and never pack it into `subredditRules` or the thread context to get
+   it through.** The request schemas are strict, so an extra field is a rejected
+   call rather than an ignored key, and a free-text slot reserved for rule
+   evidence is not a transport for planner text. The Card governs writing only
+   (`../reddit-strategy-shared/references/persona-card-contract.md` §7).
+   Recording which quadrant the batch was written for is a **local** planner
+   declaration (`LocalReviewIntent`); the review call carries no scope field and
+   the response states no scope, so never report a server-side scope, and never
+   claim the omission of `accountId` was recognised by Hub as a deliberate
+   content-only choice.
 3. Send `rewrite: true, attempt: 1`. Inspect `executionStatus` before
    `verdict`.
    For a comment/reply, include `thread.threadPermalink` when you know the
@@ -106,7 +120,14 @@ C-B/C-NB, and rows that were previously low risk.
    changing the family — only harder to notice. Apply only the local fixes, or
    resubmit stating the structural constraints. Submit the changed exact draft
    as `attempt: 2`.
-5. Accept only `completed/pass` for content review. In ContentOnly, record
+5. Accept only `completed/pass` for content review. Report any dimension the
+   result marks `not_assessed` as NotAssessed with its `notAssessedReason` — it
+   was excluded from the score, its remaining `score` number is diagnostic only,
+   and quoting it as a result or averaging it misrepresents the review. In
+   ContentOnly, `persona_consistency` / `persona_voice` coming back
+   `not_assessed` is correct behaviour, not a degraded review. Full semantics,
+   including why scores are comparable only within one `applicabilitySignature`:
+   `../reddit-strategy-shared/references/content-review-gate.md`. In ContentOnly, record
    `ReviewMode: ContentOnly`, `AccountBindingStatus: Pending`,
    `ReadyForContentNextSkill: Yes`, and `ReadyForDelivery: No`;
    `accountCandidateFeedback` is advisory and persona consistency is not
@@ -152,6 +173,24 @@ then hand to rewrite to keep editing".
 - **Real limitations:** state genuine, decision-relevant limitations when they exist; never invent a safe flaw to look authentic; position and form follow the content, not a fixed paragraph.
 - **Punctuation and format values follow the subreddit baseline** — no cross-subreddit em-dash ban, no parenthesis quota, no fixed word count.
 - **ABU (Answer-Bearing Unit, B-group):** 1–2 per post, all 8 hard requirements met, `AnchorSlot` from the 7-value enum, visibility gate satisfied per length band. The old "must sit in paragraph 2 or 3" rule is removed.
+- **The Persona Card is Brief-assigned; write inside it, never widen it.** Read
+  the Card behind the row's `PersonaCardRef` before drafting, and before handing
+  the draft to Hub review run the local boundary self-check
+  (`../reddit-strategy-shared/references/persona-card-contract.md` §8): every
+  firsthand experience claim maps to an entry in `permittedExperienceClaims`,
+  nothing displays knowledge listed in `doesNotKnow`, the stated relationship
+  matches `brandRelationshipDisclosed`, and `postingWhy` still coexists with the
+  assigned `PostingTrigger`. Record `PersonaCardSelfCheck: Pass | BlockingGap`
+  **per Key** in `PerKeyStructureContract`, alongside the `PersonaCardVersion` and
+  `PersonaCardHash` it was checked against, with the contradicting phrase and Card
+  field for each gap. A batch-level value alone cannot show that every post was
+  checked against its own current Card, which is what delivery verifies. A draft that needs a
+  wider boundary goes back to `reddit-phase-brief` for a new Card version — the
+  writer never edits the Card and never bumps its version. This check is local: it
+  produces no score, is not a review, and never substitutes for the Hub gate.
+  The Card does not relax `ClaimEvidenceStatus`; it adds *who may claim it* on top
+  of *whether it is sourced*. A firsthand phrase such as "mine arrived" is not an
+  offence by itself — it matters only when it contradicts the Card.
 - **`PostingTrigger` is Brief-pre-assigned, not writer-chosen.** After drafting,
   re-derive the actual `PostingTrigger` from the finished body and confirm it
   matches the `Planned` value; a mismatch is a `BlockingGap` (return to Brief),
@@ -214,14 +253,24 @@ then hand to rewrite to keep editing".
 - AssignedFlairVerified: Yes / No
 - PostingTriggerPlannedVsFinal: Match / Drift / NotAssigned
 - PostingTriggerCrossConstraintOK: Yes / No
+- PersonaCardSelfCheck: Pass / BlockingGap / NotApplicable   # batch-level = worst across Keys; per-Key values live in PerKeyStructureContract
+- PersonaCardTransportStatus: LocalOnly(ServerContractMissing)   # the Card was not sent to Hub
+- PersonaCardAuthorizationStatus: Authorized / DeclaredOnly / NotApplicable   # carried through from the Brief, not re-derived here
+- AcceptanceProfile: Default / NativeCopy
+- NativeCopyProfileStatus: NotSelected / Unavailable(ServerContractMissing)
+- LocalReviewIntent: accountBinding=<account_bound|persona_less>, brandTreatment=<managed_brand|organic>   # carried through from the Brief; local declaration, not a Hub receipt
+- HubReviewScopeStatus: Unavailable(ServerContractMissing)   # never report a server-side scope
+- NotAssessedDimensions:                       # per row: dimension + notAssessedReason, verbatim from Hub
 - ClaimEvidenceAllCitedOrExternallyVerified: Yes / No   # no Inferred claim reached any publishable text (title/body/comment/reply)
 - FingerprintIndexUpdated: Yes / No
 - CollisionCheckPassed: Yes / No / ExceptionRecorded
 - PerKeyStructureContract: |
     <one row per DraftKey — batch-level single values are not valid, a batch normally
      spans several families, anchor slots and hashes>
-    | Key | ClientContentPrototype | ContentFunction | PrimaryPostType | StructureFamily | AssignedFlair | FlairCoverageStatus | PostingTrigger | SampleSetID | AnchorSlot | SecondaryAnchorSlot | AllowedStructuralChanges | ForbiddenStructuralChanges | DraftHash |
-    |---|---|---|---|---|---|---|---|---|---|---|---|---|---|
+    <comment rows take N/A for PersonaCardRef / PersonaCardVersion /
+     PersonaCardHash / PersonaCardSelfCheck>
+    | Key | ClientContentPrototype | ContentFunction | PrimaryPostType | StructureFamily | AssignedFlair | FlairCoverageStatus | PostingTrigger | PersonaCardRef | PersonaCardVersion | PersonaCardHash | PersonaCardSelfCheck | SampleSetID | AnchorSlot | SecondaryAnchorSlot | AllowedStructuralChanges | ForbiddenStructuralChanges | DraftHash |
+    |---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 - SKUBindingsPreserved: Yes / No
 - BrandWordStatusPreserved: Yes / No
 - ComplementRulesPassed: Yes / No

package/skills/reddit-content-writing/references/phase4-execution-table.md

@@ -1,6 +1,13 @@
-# Phase 4.0 — 执行表详细规则
+# Phase 4.0 — 执行表详细规则（写作侧副本）
 
 > Phase 4.0 是内容写作的零号门禁，所有规则必须在第一个字正文写出之前满足。
+>
+> ⚠️ **主从关系（本文件是副本，不是权威）：** 执行表 schema 与门禁的权威版本是
+> `../../reddit-phase-planning/references/phase4-execution-table.md`（配 `scripts/phase406_verify.py`）。
+> 本副本只为写作阶段就近查阅而存在；**两处冲突时一律以 planning 版为准**，
+> 不要在本文件里就地改 schema。已知漂移（尚未同步、请按 planning 版执行）：
+> `RewriteModule` 的两层取值（`<RewriteRoute 标志集> · <SemanticModule>`，用功能语义名、
+> **禁止 PROMPT 编号**）与相应的原型→帖型/`StructureFamily` 示例。
 
 ---
 
@@ -109,9 +116,23 @@ C024–C040：外部评论（W1→W2→W3→W4 顺序）
 
 执行表填写完毕后，动笔前必须运行以下聚合检查：
 
-| 检查项 | 阈值 | 不达标处理 |
+> **口径以 D6 为准（`reddit-phase-planning/references/scheduling-decision-procedure.md`）。**
+> 下面三条是**旧的硬编码启发式，已被 Phase 4.0.0.4 的 D6 锁定方案取代**，现在只按 `SRPMode` 分档生效：
+>
+> | `SRPMode` | 效力 |
+> |---|---|
+> | `Fallback`（该板块无 SRP） | **硬约束**，不达标按右列处理 |
+> | `Full` / `Provisional`（该板块有 SRP） | **warning-level sanity check**：越界不否决方案，但必须在 D6 方案的约束快照里标注越界项与理由，交用户锁定；板块上限以 D5 的 `capacityMax` 为准 |
+>
+> **作用域：** 前两条按**板块**判（用该板块自己的 `SRPMode`）；「子版覆盖数 ≥ 4 个」是**方案级**
+> 约束，仅当方案内全部板块均为 `Fallback` 时才硬执行，混合模式下为 warning-level。
+>
+> 这组数字按「总帖 20 条」标定，对显著不同的总量不具尺度一致性。
+
+| 检查项 | 阈值（`SRPMode: Fallback` 下为硬约束） | 不达标处理 |
 |--------|------|----------|
 | 单一子版帖子数占比 | ≤ 40% | 将超量帖子移到 Phase 2 缺口矩阵引用次数排名第二的子版 |
+| 核心子版帖子数 | ≤ 8 条（总帖 20 条时） | 同上 |
 | 子版覆盖数 | ≥ 4 个不同子版 | 从 Phase 2 社区缺口矩阵补充 |
 
 ---
@@ -278,7 +299,7 @@ Geoly MCP → get_prompt_citations(
 [ ] 主帖含品牌词总数已统计并与 Master **Summary** 约定一致（差值=0）
 [ ] 外部评论 URL 均已在执行表中填写真实 URL，无「URL待确认」占位符
 [ ] 外部评论已建立「外部核验」控制列或独立 EPA 记录（不计入核心 16 字段主 schema），动笔后发布前须逐条填入核验结果
-[ ] 单一子版帖子占比 ≤ 40%，子版覆盖数 ≥ 4
+[ ] 板块分布已按 D6 口径核对：单板块项（单一子版占比 ≤ 40% / 核心子版 ≤ 8 条）按该板块自己的 `SRPMode` 判——`Fallback` 为硬约束，`Full` / `Provisional` 以 D5 `capacityMax` 与 D6 锁定方案为准；「覆盖 ≥ 4 个」是方案级约束，仅全部板块为 `Fallback` 时硬执行。warning-level 越界项已在约束快照中标注理由（不否决方案）
 [ ] A/B 两组未在同一线程各发 C-B
 [ ] 【方案E】补偿规则评估已完成（全部 UGC P-NB 帖逐行检查 Rule-1；全部 C-NB 外部评论逐行检查 Rule-2）
 [ ] 【方案E】触发补偿规则的行已在执行表「写作说明」列注明处理方式

package/skills/reddit-content-writing/references/phase4-writing.md

@@ -41,7 +41,7 @@
 | 段落数 | 中位数 | 决定分段密度 |
 | 标题长度与标题句式分布 | 各句式（陈述结论 / 问句 / 场景 / 数字背书 / 时长锚定）占比 | 决定标题形态，避免全批同一句式 |
 | 列表 / 小标题使用率 | 百分比（多少比例的帖使用） | 决定是否分节；**不再默认「分节更好」** |
-| 品牌首次出现位置分布 | 直方图（标题 / 首段 / 中段 / 结论 / 不出现） | 校准 `BrandEntryMode`，替代「不早于第二段」 |
+| 品牌首次出现位置分布 | **四档**直方图（标题 / 首段 / 中段 / 结论；分母 = `BrandMentionSampleCount`）+ `ComparableSampleCount` + `NoBrandMentionRate`（「不出现」由它表示，**不是直方图的一档**） | **`BrandPlacementGate` 的唯一位置来源**（见下方 W-1.b-brand），校准 `BrandEntryMode`，替代「不早于第二段」 |
 | 提问式结尾比例 | 百分比 | 校准 `EndingMode`；比例低时不得默认加问句结尾 |
 | 是否常见 TL;DR | 百分比 | 决定是否使用顶部 TL;DR（同时是 AnchorSlot 依据） |
 | 第一人称比例 | 百分比 | 判断该板块的叙述人称惯例。**baseline 第一人称率高 ≠ 可以补造经历**——没有真实经历素材时，正确做法是换 `ContentFunction` / `EvidenceShape` 或退回补素材，不得虚构 |
@@ -50,6 +50,70 @@
 
 另附 **2–3 条 verbatim `selftext_excerpt`**（原文抄录，禁止「基于 VOC 风格自行创作」），用于校准腔调而非结构。
 
+**W-1.b-brand — `BrandPlacementGate`（G2，硬门；上表第 5 行由「校准依据」升级为门）**
+
+> **出处（真实返工）：** 需求方质问「**为什么你把 P-B 的标题都统一加上了 aporro 这个
+> 品牌了？**」——P-B 的含义是「帖子中包含品牌词」，**并不代表品牌名必须在标题里出现**，
+> 那样显得很广告。修正后的口径：品牌词出现在 P-B 帖的**正文 body 中**，标题中通常不写
+> 品牌名，**除非是 Brand Review / 专门讨论该品牌的帖子**。
+>
+> **机制早就有**（上表第 5 行的直方图），缺的是门与触达。本节补的是门。
+
+**规则（writing 侧为消费与校验，权威定义在 `reddit-phase-brief` 的
+`references/brand-SKU-PGC-rules.md` §2.0 / §2.5）：**
+
+1. 任何**标题生成**与任何 `BrandEntryMode` 的确认，都必须引用 Brief 传下来的位置依据，
+   **按行类型分三支校验（不得一刀切要求自有 Basis）：**
+   - **P-B / PGC 主帖** → 校验自有 `BrandPlacementBasis` 全字段；
+   - **P-NB 主帖** → 接受 `BrandPlacementBasis: N/A(P-NB · 主帖不露品牌)`，不再要求直方图；
+   - **C-B 评论** → 校验 `InheritedBrandPlacementBasis`（配对 P-NB 填 `N/A(PairedPostIsP-NB)`、
+     外部评论填 `N/A(ExternalComment)`）+ `CommentPlacementDecision`，**评论不要求自有直方图**。
+
+   `BrandPlacementBasis`（其 `SourceRef` 为 baseline 卡的 `SampleSetID` 的品牌位置直方图，
+   `SourceKind: Exception`（持有有效 `BrandTitleExposureException` 时的合法来源），
+   或板块级 SRP 的 `brandFirstMentionHistogram`，契约见
+   `../../reddit-strategy-shared/references/subreddit-research-profile.md`
+   —— **该板块暂无可用 SRP 实例时以 baseline 卡为主来源，不得因其缺失而阻断**）。
+2. **拦截条件（命中任一即 `BlockingGap: BrandPlacementUnsupported`，退回
+   `reddit-phase-brief`，writer 不得本地修）：**
+   - 存在「**因为这行标记 P-B，所以标题写品牌**」的推导；
+   - **P-B / PGC 主帖**的 `BrandPlacementBasis` 缺失，或 `SelectedPlacement` 与 basis 不一致
+     （**P-NB 主帖的 `N/A(P-NB · 主帖不露品牌)` 与 C-B 评论的
+     `InheritedBrandPlacementBasis` + `CommentPlacementDecision` 均为合法填法，
+     不得据本条拦截**；C-B 缺这两项才拦截）；
+   - 直方图「标题」档 < 20% 却把品牌名写进标题，且无 `BrandTitleExposureException`；
+   - `DecisionStatus: NoComparableEvidence`（`BrandMentionSampleCount = 0`）却照常赋值 ——
+     **0 是「没有可比样本」，不是「不允许标题」，也不是一个可以照抄的保守位置**。
+     ⚠️ **持有有效例外时 Brief 会记 `DecisionStatus: Exception`（优先于
+     `NoComparableEvidence`）+ `SourceKind: Exception` + `SourceRef: <ExceptionRef>`
+     —— 这种行不得因「没有 SampleSetID / 没有直方图」被拦**；
+   - `DecisionStatus: Sparse`（1–4 条）而 Brief 未同时给出三个计数、更保守（更晚）的一档
+     与 `SparseApprovedBy`。
+   > **直方图口径：** `BrandFirstMentionHistogram` 只有**标题/首段/中段/结论四档**，
+   > 分母是 `BrandMentionSampleCount`；「不出现」由 `NoBrandMentionRate` 单独表示，
+   > **不是直方图的一档**。
+   > **C-B 评论不自带直方图**：评论用配对 P Key 的 `InheritedBrandPlacementBasis` +
+   > `CommentPlacementDecision`（外部评论为 `N/A(ExternalComment)`）。
+3. ⚠️ **合法例外必须放行（不得一刀切）：** `BrandTitleExposureException` 为
+   `PGCApproved`（官方/PGC 账号 + 已过 precedent check 且有先例 URL + 版规允许
+   vendor/official + flair/disclosure/frequency 满足）或 `BrandReviewPost`（确为围绕该
+   品牌/产品本身的帖，由 `PrimaryPostType` / `WritingVariant` + 选题证据判定，
+   **不得自造 `ContentFunction: Review`**）时，**标题出现品牌名合法**，不得因直方图不支持
+   而拦截。例外须带 `ExceptionBasis` / `ExceptionScope` / `ExceptionApprovedBy` /
+   `ExceptionApprovedAt` 四项，且不得越过禁止推广板块与披露要求。
+4. `BrandEntryMode` 本身仍是 `LockedFingerprintField`：位置变更一律退回 Brief 重分配。
+5. ⚠️ **既有 P-B / PGC 行的 `SelectedPlacement` 只能是 标题 / 首段 / 中段 / 后段**
+   （直方图档位按「结论 → 后段」换算）。D 类板块或 `NoBrandMentionRate ≥ 0.8` 导致主帖
+   无法露出时，**既有 P-B / PGC 行走 `BlockingGap` 回 Brief / 规划**，不得静默落到
+   「不出现」或挪到评论；「不出现」只对规划时已是 P-NB 的行合法。
+   把品牌挪到评论或干脆不出现，等于让这行变成 P-NB + C-B（帖—评互补规则见下文），
+   **那是配额与行类型变更** —— writing 阶段一律 `BlockingGap` 退回 Brief / 规划，
+   不得自行执行。
+
+⚠️ **本门只处理「位置由什么决定」，不处理「要不要有品牌」。** P-B/P-NB/C-B/C-NB 配额
+语义一律不变；位置不成立时退回 Brief，**不得**在 writing 阶段把 P-B 改成 P-NB、
+改配对或改配额。
+
 **W-1.c 若需要补采（仅在 Brief 授权重采时）：**
 
 ```bash
@@ -218,6 +282,13 @@ SampleSetID:
 AnchorSlot:
 AllowedStructuralChanges:
 ForbiddenStructuralChanges:
+BrandPlacementBasis:          # G2：主帖用 SelectedPlacement + DecisionStatus + 例外（rewrite 不得改品牌位置）
+InheritedBrandPlacementBasis: # G2：**评论交接时用这两项代替上一行**（配对为 P-NB 填 N/A(PairedPostIsP-NB)，
+CommentPlacementDecision:     #      外部评论填 N/A(ExternalComment)）
+ReaderVisiblePremise:         # G1：rewrite 只能表达这个，不得引入内部标签
+MaterialModalitySnapshot:     # G4：逐条 MaterialID: OriginalModality → EffectiveModality
+                              #      + ModalityStatus / ModalityUpgradeRef / ModalityDowngradeRef /
+                              #      DowngradeSource / ApprovedBy（或 LedgerRef）；rewrite 不得升级/降级
 ```
 
 rewrite **默认只能**：修事实表达、修营销腔、修可读性、修明确触发的问题。
@@ -255,8 +326,10 @@ Hub pass 必须发生在最后一次正文修改之后。
 |--------|------|
 | 标题/任务方向 | 与 Brief 一致或更具体，不得偏离话题 |
 | 大纲与撰写逻辑 | 段落结构按 Brief 展开 |
-| 品牌词嵌入 | P-B/C-B 按 Brief 位置与方式；符合帖—评互补 |
-| 方向选取理由 | 正文须落实 Brief 所指向的缺口/Prompt |
+| 品牌词嵌入 | P-B / PGC 主帖按 Brief 的 `SelectedPlacement` + `BrandPlacementBasis`；C-B 评论按 `InheritedBrandPlacementBasis` + `CommentPlacementDecision`（W-1.b-brand）；符合帖—评互补 |
+| 方向选取理由 | 正文须落实 Brief 所指向的缺口/Prompt（**该理由属内部面，不得写进正文**，见下方 G1） |
+| 叙事分层 | 正文只表达 Brief 的 `ReaderVisiblePremise`；`InternalCoverageIntent` 不得进入读者可见文本 |
+| 素材 modality | 按 Brief 的 `EffectiveModality` 写；writing **不得升级**（见下方 G4） |
 
 Brief 与执行表冲突时：**暂停动笔**，先修订 Brief 或执行表并重新走 Brief 门禁。
 
@@ -265,6 +338,47 @@ Brief 与执行表冲突时：**暂停动笔**，先修订 Brief 或执行表并
 [ ] Brief 审核状态已满足（甲方：Brief 已通过 / 内部：确认 Brief · 可动笔）
 ```
 
+### G1 — 内部标签 outbound 检查（每条内容成稿后必做）
+
+> Brief 侧的分层定义见 `reddit-phase-brief` 的
+> `references/phase4-brief-workflow.md` 步骤 B-1.6。writing 侧只做 outbound 校验。
+
+**扫描面（只扫这些，且只扫将要发到 Reddit 的文本）：** 标题、正文 body、评论正文。
+
+**拦截：** 出现 FAQ 编号 / 「响应·覆盖 FAQ」字样 / GEO·searchQuery·关键词标签原样 /
+Key 编号 / `prompt_id` / 缺口象限码 / `SampleSetID` / 内部代号 → `NeedsFix`，
+改写成 `ReaderVisiblePremise` 的自然表达。
+
+> **判据继承 B-1.6，不是无条件字符串黑名单：** 只有当这些字符串**作为内部标签、查询标签
+> 或策略动作**出现时才拦截。**产品型号、真实用户原话引用、以及碰巧形似内部编号的自然
+> 语句（型号 `A-07`、容量 `Q12`、「这几个问题我也被问过」）不得因形状相似而拦截。**
+> 判定时以本项目登记在 `InternalCoverageIntent` 里的实际 token 为准。
+
+⚠️ **不误伤（三条，必须完整读）：**
+
+1. **fanout 子查询「在正文中自然覆盖」仍然合法**（见下文「动笔顺序规则」B 组条款）。
+   那是 **query-as-content**（把查询的语义用人话写出来），本门只禁
+   **query-as-label**（把查询字符串当角度或标题贴上去）。
+2. **飞书文档里的 `[Fanout] <查询文本>` 标红行是文档内部标注**（见下文红色标记规则），
+   给内容同事看、**不发到 Reddit**，不属于读者可见叙事；但 outbound 检查必须确认它
+   **没有**混进 Reddit 的 title / body / comment。
+3. **只扫 outbound 文本，不扫 Brief、指纹索引、执行表、审计控制列、rewrite handoff**
+   —— 这些位置本来就该保留内部标签。
+
+### G4 — 素材 modality drift 检查（每条内容成稿后必做）
+
+> 台账与授权规则见 `reddit-phase-brief` 的 `references/phase4-brief-workflow.md` 步骤 B-1.4。
+
+- 逐条比对本篇用到的 `MaterialID` 的 `EffectiveModality` 与实际落笔：
+  **writing 与 rewrite 一律不得升级**（`Optional → Preferred/Required` 等）。
+  出现「必须嵌入 / 强制带上这个卖点」的自发要求 → **拦截并回落**到 Brief 传下的值。
+- `Optional` 的卖点**不满足条件就不写，不算缺陷**；不得为「凑齐卖点」硬塞。
+- `Required` 项在成稿中缺失 → `BlockingGap`（不是「本篇没写而已」），退回 Brief。
+- 需要变更 modality（升级或降级）→ 退回 `reddit-phase-brief` 走授权流程
+  （升级记 `ModalityUpgradeRef`，降级记 `ModalityDowngradeRef` + `DowngradeSource`，
+  两者均须 `ApprovedBy` ≠ 生成 agent）；
+  **用户明确标 `Optional` 的项目永不由本阶段升级**。
+
 ---
 
 ## Brand Risk 预防评估（每批终稿前必做）
@@ -394,6 +508,8 @@ FixOwnerSkill: reddit-phase-brief
 - **任何正文：** 须 Phase 4 Brief 门禁已通过、Phase 4.0.6 通过，且用户已回复「确认动笔 · Batch N」
 - **A 组（P-NB）：** 可在 Phase 4.0.5 未完成时进入 4.0.6，但 **B 组 Keys 须等 fanout 补齐后再写**
 - **B 组（P-B）：** fanout 列齐全 + 4.0.6 通过后，按批次 Map 撰写；正文须自然覆盖 fanout 子查询
+  —— **query-as-content（把查询语义用人话写出来）合法；query-as-label（把查询字符串原样
+  当标题或角度贴上去）违反 G1**
 
 ---
 
@@ -598,6 +714,8 @@ else:
 [ ] W-3 本批每篇均已确认 Brief 预分配的 StructureFamily，并已读对应范文的元数据块
 [ ] 本批未出现伪造社区历史、刻意 typo、虚构身份信号、虚构缺点
 [ ] 本批开场句未直接复用范文或模板中的示例句（示例即种子）
+[ ] G2：本批每条 P-B / PGC 主帖均带 Brief 的 BrandPlacementBasis（C-B 评论带 InheritedBrandPlacementBasis + CommentPlacementDecision），SelectedPlacement 与 basis 一致；无「因为标记 P-B 所以标题写品牌」的推导；标题露出品牌的行有直方图支持（标题档 ≥ 20%）或四项齐全的 BrandTitleExposureException；Sparse 行满足三条件；DecisionStatus: Exception 的行不因缺 SampleSetID/直方图被拦
+[ ] G4：本批每条素材的 EffectiveModality 已从 Brief 取到，未在写作阶段升级；Optional 项未被当成必写
 ```
 
 ---
@@ -639,6 +757,8 @@ lark-cli docs 写入富文本时，对红色片段使用 inline 颜色属性（`
 [ ] B 组帖：ABUVisibilityGate 按长度档通过（中帖唯一 ABU 不得仅落在结论段且仅靠标题 cue；长 B 组帖只有末尾 ABU 须记录例外理由）
 [ ] B 组帖：飞书文档 Fanout Query 行已标红（或已用【红色标注：...】文字替代）
 [ ] B 组帖：飞书文档 ABU 已内联标红（或已用【红色标注：...】文字替代）
+[ ] G1 outbound：标题 / 正文 / 评论中无**作为内部标签出现的** FAQ 编号、「响应·覆盖 FAQ」字样、GEO/searchQuery/关键词标签原样、Key/prompt_id/象限码（按 token registry + 标签语境判定；**真实产品型号、用户原话、形似编号的自然语句不算违规**）；`[Fanout]` 行只存在于飞书文档，未混入 Reddit payload
+[ ] G4：Required 素材均已落笔（缺失=BlockingGap）；无未授权的 modality 升级或降级（升级须 ModalityUpgradeRef，降级须 ModalityDowngradeRef + DowngradeSource + ApprovedBy，或可追溯的 LedgerRef）
 ```
 
 ## 外部热帖评论前置核查（C-B / C-NB 外部评论每条必做，动笔前完成）

package/skills/reddit-content-writing/references/post-writing-templates.md

@@ -10,9 +10,9 @@
 > 4. **禁止为了不同而不同**：结构在 **Brief 阶段**按 `content-type-routing-contract.md` 的有序过滤收敛（见下文 §C），写作阶段只确认，不做随机轮换。
 
 **适用范围：** 任意品牌 Reddit GEO 内容；示例含 eSIM、耳机品类，换品类时替换关键词即可。  
-**数据来源：** reddit-strategy-reuse-playbook.md（§5、§10、§13、§15）；Reddit VOC 三轮采样（2026-06-10，使用 `reddit-voc-volume`，r/eSIMs / r/Earbuds / r/HeadphoneAdvice / r/JapanTravel / r/solotravel / r/digitalnomad / r/BudgetAudiophile；含评分、upvote_ratio 真实数据）。
+**数据来源：** Reddit VOC 三轮采样（2026-06-10，使用 `reddit-voc-volume`，r/eSIMs / r/Earbuds / r/HeadphoneAdvice / r/JapanTravel / r/solotravel / r/digitalnomad / r/BudgetAudiophile；含评分、upvote_ratio 真实数据）。本文的模板与「引用倾向」是这批采样的归纳，**不是**规则手册的转述。
 
-**与主文档关系：** 执行顺序仍以 **01 执行入口**、**02 规则手册** 为准；本文是写帖侧的「格式 + 品牌嵌入」速查，不替代 Phase 0–5 全流程。
+**与主文档关系：** Phase 顺序与门禁以 `../../reddit-strategy-orchestrator/SKILL.md`（Phase Orchestration / Phase Gates）为准；结构与帖型路由以 `../../reddit-strategy-shared/references/content-type-routing-contract.md`、差异化以 `../../reddit-strategy-shared/references/content-diversity-contract.md`、写作硬门禁以 `phase4-writing.md` 为准。本文是写帖侧的「格式 + 品牌嵌入」速查，不替代 Phase 0–5 全流程，也不是规则手册。
 
 ---
 
@@ -357,13 +357,21 @@ TL;DR 放最上；Background 段先写「near-launch 购买、替换 AirPod Pro
 
 ---
 
-## 延伸阅读（本文件夹内）
+## 延伸阅读（active 权威文件）
+
+> ⚠️ 旧版此处列的 `02-规则手册-reddit-strategy-reuse-playbook.md` 与
+> `01-执行入口-reddit-sop-v2-universal.md` 已归档到
+> `reddit-strategy-shared/references/prerequisites/archive/`（`AgentReadPolicy: DoNotRead`），
+> **不得**再当作数据来源、规则手册或 Phase 顺序依据；引用即 gate failure。下表是它们的 active 接替者。
 
 | 文档 | 用途 |
 |------|------|
-| 02-规则手册-reddit-strategy-reuse-playbook.md | 完整 §5 模板学习、§10 帖型、§13 品牌规则、§14 评论 2:8 |
-| 01-执行入口-reddit-sop-v2-universal.md | Phase 顺序与门禁 |
-| 06-VOC采样技能-reddit-voc-volume-SKILL.md | 拉取 Top 引用帖 selftext、竞品 VOC |
+| `../../reddit-strategy-orchestrator/SKILL.md` | Phase 顺序与门禁（Phase Orchestration / Phase Gates / Human Decision Points） |
+| `phase4-post-rules.md` | 品牌词规则、P-NB→C-B 互补、评论 2:8 |
+| `../../reddit-strategy-shared/references/content-type-routing-contract.md` | 客户内容原型 → 主帖型 → StructureFamily 路由 |
+| `../../reddit-strategy-shared/references/content-diversity-contract.md` | 指纹、滚动窗口、baseline manifest 与 `SampleSetID` |
+| `phase4-writing.md` | 写作阶段硬门禁（W-1.a / W-1.b / W-1.b-brand 等） |
+| `../../reddit-voc-volume/SKILL.md` | 拉取 Top 引用帖 selftext、竞品 VOC |
 
 ---
 

package/skills/reddit-delivery-check/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: reddit-delivery-check
 description: |
-  Reddit Phase 5 delivery QA skill. Use to verify final strategy deliverables, execution table coverage, batch draft completeness, SKU and brand-word quotas, external-comment audit status, brand-risk review status, unresolved placeholders, and the v2.12.25 structure gates before client delivery: client content-prototype mapping, StructureFamily preservation, rewrite structure drift, AnchorSlot legality, rolling-window structure collisions, subreddit baseline freshness, narrative-fingerprint / final-draft hash match, Hub optimized-draft structure override, and fabricated human signals (deliberate typos, fake community history, invented identity).
+  Reddit Phase 5 delivery QA skill. Use to verify final strategy deliverables, execution table coverage, batch draft completeness, SKU and brand-word quotas, external-comment audit status, brand-risk review status, unresolved placeholders, and the v2.12.25 structure gates before client delivery: client content-prototype mapping, StructureFamily preservation, rewrite structure drift, AnchorSlot legality, rolling-window structure collisions, subreddit baseline freshness, narrative-fingerprint / final-draft hash match, Hub optimized-draft structure override, fabricated human signals (deliberate typos, fake community history, invented identity), Persona Card preservation, correct reporting of not-assessed review dimensions, compliance-evidence freshness at delivery time, and acceptance-profile eligibility.
 ---
 
 # Reddit Delivery Check
@@ -18,6 +18,9 @@ Mandatory before running the structure gates:
 
 - `~/.cursor/skills/reddit-strategy-shared/references/content-type-routing-contract.md`
 - `~/.cursor/skills/reddit-strategy-shared/references/content-diversity-contract.md`
+- `~/.cursor/skills/reddit-strategy-shared/references/persona-card-contract.md`
+- `~/.cursor/skills/reddit-strategy-shared/references/content-review-gate.md` for how a `not_assessed` dimension must be reported and why scores are comparable only within one `applicabilitySignature`
+- `~/.cursor/skills/reddit-strategy-shared/references/native-copy-profile.md` when the batch declared `AcceptanceProfile: NativeCopy`
 
 ## Required Inputs
 
@@ -25,6 +28,7 @@ Mandatory before running the structure gates:
 - `memory/phase4-叙事指纹索引.md`
 - `memory/phase4-撰写brief.md` (for the `Planned` structure values and `SampleSetID`)
 - `memory/phase4-sku-基准表.md`
+- `memory/phase4-board-quantity-plan.md` (per-board `SRPMode` + the locked `LockedPlanID`; needed to judge the board-distribution check, which is a hard constraint only under `SRPMode: Fallback`)
 - `memory/phase4-执行表.md`
 - `memory/phase4-撰写批次map.md`
 - all batch draft files
@@ -34,7 +38,7 @@ Mandatory before running the structure gates:
 - verifier output when available
 - external post audit results
 
-## Structure Checks (v2.12.25, all nine must pass)
+## Structure Checks (all ten must pass)
 
 Delivery is blocked unless every one of these verifies. This layer creates no
 diversity by itself; it exists so the earlier three layers cannot be skipped.
@@ -89,11 +93,25 @@ diversity by itself; it exists so the earlier three layers cannot be skipped.
    `this sub always...`), no invented identity, and no flaw inserted only to
    look authentic.
 
-**Scope.** Checks 1–7 apply to **main-post Keys only** (`WindowScope: PostOnly`).
+10. **Persona Card preserved.** Every delivered main-post Key's
+    `PersonaCardRef` / `PersonaCardVersion` / `PersonaCardHash` equal the Brief's
+    assigned Card, and `PersonaCardSelfCheck: Pass` was recorded **against that
+    same version**. A self-check recorded against an earlier version is stale, not
+    a pass — a Card change invalidates every boundary check made under the old
+    one. A Card authored or edited downstream of `reddit-phase-brief` is a
+    failure with `FixOwnerSkill: reddit-phase-brief`, whichever skill wrote it.
+    A missing Card on a post row is a `BlockingGap`, never "no Card, so nothing
+    to check". Carry `PersonaCardAuthorizationStatus` through from the Brief:
+    `DeclaredOnly` does not block delivery, but the delivery record may not
+    describe that row's firsthand claims as authorised. Do not read `RoleLabels`
+    in this check, and do not report the Card as a verified identity or as
+    anything Hub assessed.
+
+**Scope.** Checks 1–7 and 10 apply to **main-post Keys only** (`WindowScope: PostOnly`).
 Comments, self-comments, and external comments need no fingerprint row, no
-prototype mapping, no `StructureFamily`, no `SampleSetID`, and no `AnchorSlot`;
-they still need Hub `completed/pass` plus `FinalDraftSha256`, and checks 8–9
-still apply to them.
+prototype mapping, no `StructureFamily`, no `SampleSetID`, no `AnchorSlot`, and no
+Persona Card; they still need Hub `completed/pass` plus `FinalDraftSha256`, and
+checks 8–9 still apply to them.
 
 Missing index file, missing `Final` row for a post Key, zero or multiple active
 rows for one Key, unlocked window parameters, or a missing/expired baseline are
@@ -113,6 +131,10 @@ introduced by rewriting, set `FixOwnerSkill: reddit-content-rewrite`.
 - ContentOnly `completed/pass` is acceptable for a content handoff, but it is not a Phase 5 delivery pass and must show `AccountBindingStatus: Pending` and `ReadyForDelivery: No`.
 - No AccountBound delivered item has unresolved `brandFitReviewRequired=true` or blocking `accountCandidateFeedback`; the approved `brandContext` and resolution are recorded.
 - The review log covers every final draft, and any `revise` feedback is reflected in the exact delivered text. `degraded`, unavailable, or local-only review is a failure.
+- Every dimension a Hub result marked `not_assessed` is carried into the delivery record as NotAssessed with its `notAssessedReason` — never as a low score, a passing score, or a partial check, and never averaged into any figure. The `score` left on such a dimension is diagnostic only. `unevaluatedDimensions` on a `degraded` result is a *different* thing (assessable but unanswered) and must not be reported as not-applicable. No delivery figure compares or averages scores across different `applicabilitySignature` values — a ContentOnly score and an AccountBound score are not the same measurement.
+- Compliance evidence is still fresh **as of delivery**. Re-check the Compliance Output handoff's `EvidenceGatheredAt` / `EvidenceValidUntil` under the definition that handoff sets (`../reddit-strategy-shared/references/handoff-schemas.md`): they are batch-level **worst-case** scalars over the five delivery-required items (`RulesEvidenceStatus` / `PinnedEvidenceStatus` / `BotBannerEvidenceStatus` / `InstalledAppsStatus` / `AboutPageEvidenceStatus`) — earliest gathering time and earliest validity horizon. `EvidenceValidUntil` in the past, or `Unknown` on either scalar, holds the affected rows for re-gathering and re-judgement. A clearance recorded once at compliance time does not satisfy this.
+- Separately from freshness: where the board's brand/vendor permission or a disclosure requirement was **never adjudicated**, it stays in `MissingEvidence` with the corresponding `PostRisk` / `CommentRisk` and needs a recorded human decision. This is not a freshness question and no timestamp resolves it — re-gathering evidence re-opens the question, it never answers it, and the answer is never inferred from a style profile's brand-friendliness note or from raw collected evidence.
+- When the batch declared `AcceptanceProfile: NativeCopy`, `NativeCopyProfileStatus` is recorded and no row is `ReadyForDelivery: Yes` while it is `Unavailable(ServerContractMissing)`. A batch that was quietly re-labelled `Default` to release delivery, or whose review call was weakened until it succeeded and then counted as a profile pass, is a failure.
 - No placeholders, unresolved evidence gaps, or unmerged side tables remain.
 - Master Canvas has all 21 boards, including Data Support, MCP Status, and Verification Boundaries.
 - Feishu draft delivery uses a single draft document unless the user explicitly requests otherwise.
@@ -137,6 +159,10 @@ introduced by rewriting, set `FixOwnerSkill: reddit-content-rewrite`.
 - FingerprintHashIssues:
 - HubStructureConflictIssues:
 - FabricatedSignalIssues:
+- PersonaCardIssues:
+- NotAssessedReportingIssues:
+- EvidenceFreshnessIssues:
+- AcceptanceProfileIssues:
 - PlaceholderIssues:
 - RequiredFixes:
 - DeliverySummary:
@@ -159,6 +185,13 @@ introduced by rewriting, set `FixOwnerSkill: reddit-content-rewrite`.
 - FingerprintHashStatus: Matched / Mismatch / Pending
 - HubStructureConflictStatus: None / Escalated
 - FabricatedSignalStatus: None / Found
+- PersonaCardStatus: Preserved / Drift / Missing / NotApplicable
+- PersonaCardAuthorizationStatus: Authorized / DeclaredOnly / NotApplicable   # carried through from the Brief; DeclaredOnly does not block but may not be reported as authorised
+- EvidenceFreshnessStatus: Fresh / Expired / Unknown
+- AcceptanceProfile: Default / NativeCopy
+- NativeCopyProfileStatus: NotSelected / Unavailable(ServerContractMissing)
+- LocalReviewIntent: accountBinding=<account_bound|persona_less>, brandTreatment=<managed_brand|organic>   # carried through; local declaration only
+- HubReviewScopeStatus: Unavailable(ServerContractMissing)
 - ReviewMode: ContentOnly | AccountBound
 - AccountBindingStatus: Pending | Resolved | NeedsReview
 - ReadyForDelivery: Yes / No

package/skills/reddit-delivery-check/references/phase5-delivery.md

@@ -31,7 +31,13 @@
 [ ] Phase 4：正文按批次 Map 撰写，默认每批 8-10 条；帖评整组不拆时允许 8-12；末批可少于 8；无跳批丢包
 [ ] Phase 4.0：执行表编号无冲突（自评编号与外部评论编号无重叠）
 [ ] Phase 4.0：主帖含品牌词总数与 Master **Summary** 品牌词约定差值=0
-[ ] Phase 4.0：单一子版帖子占比 ≤ 40%，子版覆盖数 ≥ 4
+[ ] Phase 4.0：板块分布符合 D6 口径（**不是无条件硬门禁**；判据取自
+    `memory/phase4-board-quantity-plan.md` 的逐板块 `SRPMode` 与 `LockedPlanID`，
+    该文件缺失才是阻断项）——
+    · 单一子版占比 ≤ 40% / 核心子版 ≤ 8 条（总帖 20 条时）：**按该板块自己的 `SRPMode` 判**，
+      `Fallback` 为硬约束，`Full` / `Provisional` 降为 warning-level；
+    · 子版覆盖数 ≥ 4 个：**方案级**约束，仅当方案内全部板块均为 `Fallback` 时才硬执行，混合模式下为 warning-level；
+    · warning-level 项越界**不判不合格**，只需确认越界项已在 D6 方案约束快照里标注理由、方案已被用户锁定
 [ ] Brand Risk：`memory/phase4-brand-risk-review.md` 已存在或有明确 low-risk waiver；所有 HoldForCompliance / HoldForHumanApproval / DoNotPublish 行已处理，不在交付稿中
 [ ] Content Review：`memory/content-review-log.md` 已存在并覆盖每条交付帖子/评论；每条均有对应 Hub `executionStatus=completed` + `verdict=pass`，且最终交付审核为 `ReviewMode: AccountBound`、有真实 `accountId`、无未解决的 `brandFitReviewRequired=true` / 阻断型 `accountCandidateFeedback`；`ContentOnly` 只能作为内容交接结果，不能作为 Phase 5 发布通过；`degraded` / unavailable / 仅本地自检均不通过
 [ ] 草稿文档唯一性：不存在「【更新】版」「第二套」等平行节；所有 URL 已原地填入，无占位符

package/skills/reddit-matrix.lock.json

@@ -4,37 +4,37 @@
   "archiveSha256": "7af75a08d8779f0d4aa73e6fa0706e7fac82737da7eecc08adf8a02151619e0b",
   "skills": {
     "reddit-strategy-orchestrator": {
-      "contentSha256": "501408ce9cd1be969ac91c672523cde18bdbb6118836e032539ef30af98f2711"
+      "contentSha256": "9a4fa3944ec3913a4e68cb1faf4d4a32ca04131fa4b0c37e054065f4e2c1a1ed"
     },
     "reddit-strategy-shared": {
-      "contentSha256": "9ffdae74106e1b93b265bd89f6b0b1674f2b37a9dafd43c4a50129ac75f85862"
+      "contentSha256": "bba5c177a4af9bab0f2d9c227993862629e82ec9747cd2788e4874d058da3c89"
     },
     "reddit-phase-research": {
-      "contentSha256": "e1818757ae92019448a454b956cb38c9cabc7e3c4762da4a6e4a765d687b8dc6"
+      "contentSha256": "9f47b8eb0d1c1c194c685856242c9b22d190dfa8c6f572869e964239215795fe"
     },
     "reddit-phase-planning": {
-      "contentSha256": "7568acf5b9e0ec9bd44deff09a49cadd80a7cf5acbe483c97f979f96ac9d962f"
+      "contentSha256": "8080adce62b6db65be3dbc0f37f162a81e382d6b64108f7352ec83c356664659"
     },
     "reddit-phase-brief": {
-      "contentSha256": "841d9e9928126553af0211da7d74a69af92076fc00d800dff2243075359b2157"
+      "contentSha256": "3475bf4c4aa4796db1c99a3bd527c52dc8488f71db01753da0325e924d552b99"
     },
     "reddit-content-writing": {
-      "contentSha256": "9b2f4cda552d5f76b3ab289504f84db599245e7245297a9d974cc55143872d8d"
+      "contentSha256": "08023a5dfa6cc2f3ffc3f1a551479c645ddcfc8cc775f88cd2d245c067829482"
     },
     "reddit-content-rewrite": {
-      "contentSha256": "3e7df833877fc81a46d66ab7c827fac386a1413862724179e87570d773ab8935"
+      "contentSha256": "2f9dfdbb2410d060f755860b57ebc7c6776f4df343990029a8770855ecd33005"
     },
     "reddit-delivery-check": {
-      "contentSha256": "234d7fd1d8f2db68444674c20418c836c1b2488305b20399114dec89a0de32fc"
+      "contentSha256": "9231ff9ae5d950bc2fb87e45bee05e793b3ff9c37bee45e8444059a8b698e4a9"
     },
     "reddit-voc-volume": {
-      "contentSha256": "a5f21cc499688b245cfa3381ffdb88fa681cd5e93f3f1ef68d925b7ae220de2f"
+      "contentSha256": "496c0d57af7507d86a16bd4d06f3a5a017ca10b3dc4e3564d82b0c988e1c87ac"
     },
     "reddit-brand-risk-response": {
       "contentSha256": "dbba80345ebe68818a25e7604dfaa6951c6bf0e4d785d5013be7a06b22ec5b7c"
     },
     "reddit-subreddit-compliance": {
-      "contentSha256": "a996e1dbffee237d0535012ac3ec40698c2d4ba03d0c9fb088fefe27f51646ee"
+      "contentSha256": "3cab43d1c70d511212f3684929a8d7da73c11d3ae34563f31d1eebe04a6ecd8b"
     },
     "reddit-answers-research": {
       "contentSha256": "eb132d81021f0a24619d9b576a287f722cf61c24422874d5be86cd4be2c392df"