@sushanglewis/lincoln 1.8.2 → 1.8.4

package/framework/.claude/skills/lc-workflow/validators/validate.py

@@ -640,33 +640,75 @@ def check_tdd_plan_complete(design_id: str):
 # PRD checks
 # ---------------------------------------------------------------------------
 
+# 递进骨架（issue-129）：版本说明 → 修订记录 → 功能列表 → 需求展开。
+# 章节编号不参与匹配，PM 可按需求类型在骨架内增插业务章节。
 REQUIRED_PRD_SECTIONS = [
-    "## 1. 需求背景",
-    "## 2. 用户故事",
-    "## 3. 功能拆解",
-    "## 4. 业务流程图",
-    "## 5. 验收标准",
-    "## 6. 业务规则",
-    "## 7. 非功能需求",
-    "## 8. 关联系统/接口",
-    "## 9. 相关产物链接",
-    "## 10. 风险与开放问题",
+    "版本说明",
+    "修订记录",
+    "功能列表",
+    "需求背景",
+    "用户故事",
+    "功能拆解",
+    "业务流程图",
+    "验收标准",
+    "业务规则",
+    "非功能需求",
+    "关联系统/接口",
+    "相关产物链接",
+    "风险与开放问题",
 ]
 
+PRD_SECTION_PATTERNS = [
+    (name, re.compile(rf"^##\s*(?:\d+\s*[.、．]?\s*)?{re.escape(name)}\s*$", re.MULTILINE))
+    for name in REQUIRED_PRD_SECTIONS
+]
+
+# PRD 正文禁则：过程性疑问在对话中解决，技术内容归归档页（issue-129 第 4/6 条）。
+PRD_FORBIDDEN_PROCESS_RE = re.compile(r"待确认|待人类|待补充|待\s*PM|TODO|FIXME", re.IGNORECASE)
+PRD_FORBIDDEN_TECH_HEADING_RE = re.compile(
+    r"^##+\s*.*(技术调研|技术方案|可行性研究|架构设计|接口设计|数据库设计)",
+    re.MULTILINE,
+)
+
+CROSS_VALIDATION_PASS_RE = re.compile(
+    r"<!--\s*cross-validation:\s*pass\s+prd-version:\s*(v\d+\.\d+)\s*-->"
+)
+
+
+def _prd_hygiene_violations(content: str) -> list[str]:
+    violations = sorted(set(PRD_FORBIDDEN_PROCESS_RE.findall(content)))
+    violations.extend(sorted(set(PRD_FORBIDDEN_TECH_HEADING_RE.findall(content))))
+    return violations
+
 
 def check_prd_has_required_sections(path: str):
     target = PROJECT_ROOT / path
     if not target.exists():
         fail(f"PRD missing: {target}")
 
-    text = read_document_file(target)
-    missing = [section for section in REQUIRED_PRD_SECTIONS if section not in text]
+    content = read_document_file(target)
+    missing = [name for name, pattern in PRD_SECTION_PATTERNS if not pattern.search(content)]
     if missing:
         fail(f"PRD missing required sections: {', '.join(missing)}")
 
     pass_check("PRD has all required sections")
 
 
+def check_prd_content_hygiene(path: str):
+    target = PROJECT_ROOT / path
+    if not target.exists():
+        fail(f"PRD missing: {target}")
+
+    violations = _prd_hygiene_violations(read_document_file(target))
+    if violations:
+        fail(
+            "PRD contains content that belongs in conversation or archived pages, "
+            f"not the PRD: {', '.join(violations)}"
+        )
+
+    pass_check("PRD content hygiene OK")
+
+
 def check_prd_snapshot_present(path: str):
     target = PROJECT_ROOT / path
     if not target.exists():
@@ -692,6 +734,43 @@ def check_prd_snapshot_present(path: str):
     pass_check(f"PRD snapshot present: {snapshot_path}")
 
 
+def check_prd_cross_validated(path: str):
+    target = PROJECT_ROOT / path
+    if not target.exists():
+        fail(f"Cross-validation report missing: {target}")
+
+    match = CROSS_VALIDATION_PASS_RE.search(read_document_file(target))
+    if not match:
+        fail(
+            "Cross-validation report has no pass marker. Every gap must be closed by a "
+            "human-PM decision (PRD fix with re-freeze, or accepted with recorded "
+            "rationale) before adding '<!-- cross-validation: pass prd-version: vX.Y -->'."
+        )
+
+    prd_path = target.parent / "prd.html"
+    if not prd_path.exists():
+        fail(f"PRD missing next to cross-validation report: {prd_path}")
+
+    if extract_markdown_version is None:
+        fail("markdown version extraction is not available")
+
+    prd_version = extract_markdown_version(prd_path)
+    if prd_version != match.group(1):
+        fail(
+            f"Cross-validation pass marker is for PRD {match.group(1)}, but the PRD is now "
+            f"{prd_version or 'unversioned'}. Re-run cross-validation against the current PRD."
+        )
+
+    violations = _prd_hygiene_violations(read_document_file(prd_path))
+    if violations:
+        fail(
+            f"PRD regressed after cross-validation pass: {', '.join(violations)}. "
+            "Fix the PRD, bump its version, re-freeze, and re-run cross-validation."
+        )
+
+    pass_check(f"PRD cross-validation pass marker matches PRD {prd_version}")
+
+
 # ---------------------------------------------------------------------------
 # Registry
 # ---------------------------------------------------------------------------
@@ -729,6 +808,8 @@ EXIT_CHECKS = {
     "tdd_plan_complete": check_tdd_plan_complete,
     "prd_has_required_sections": check_prd_has_required_sections,
     "prd_snapshot_present": check_prd_snapshot_present,
+    "prd_content_hygiene": check_prd_content_hygiene,
+    "prd_cross_validated": check_prd_cross_validated,
 }
 
 

package/framework/.claude/skills/plan-tdd-development/SKILL.md

@@ -13,6 +13,7 @@ inputs:
     required: true
 outputs:
   - "{process_slug}/pages/docs/tdd-plan.html"
+  - "{process_slug}/pages/docs/prd-cross-validation.html"
 required_tools:
   - Read
   - Bash

package/framework/.claude/skills/plan-tdd-development/prompts/main.md

@@ -1,10 +1,10 @@
 # plan-tdd-development
 
-You are executing the Lincoln workflow step `tdd-development-plan`: turn the confirmed product design and prototype into a TDD development plan.
+You are executing the Lincoln workflow step `tdd-development-plan`: turn the confirmed product design and prototype into a TDD development plan, then reverse-drive the PRD with test scenarios so gaps close before development.
 
 ## Goal
 
-Create `{process_slug}/pages/docs/tdd-plan.html` as the bridge from product design to OpenSpec and GitHub Issues.
+Create `{process_slug}/pages/docs/tdd-plan.html` as the bridge from product design to OpenSpec and GitHub Issues, and produce `{process_slug}/pages/docs/prd-cross-validation.html` so every test scenario (正常/边界/异常) challenges the PRD — SDD tests reverse-drive PRD completeness.
 
 ## Input
 
@@ -16,11 +16,13 @@ Create `{process_slug}/pages/docs/tdd-plan.html` as the bridge from product desi
 在执行本 prompt 前：
 1. 调用 `superpowers:writing-plans` 规划 `tdd-plan.html` 结构。
 2. 遵循 `superpowers:test-driven-development` 方法论：确保每个任务切片都是“先写失败测试 → 最小实现 → 重构”序列。
-3. 在 `tdd-plan.html` 的 Markdown source 头部加入：  
+3. 在 `tdd-plan.html` 的 Markdown source 头部加入：
    `> **Required sub-skill:** Use superpowers:test-driven-development for all implementation`
 
 ## Steps
 
+### Phase 1 — TDD 计划
+
 1. Verify that `{process_slug}/pages/docs/ui-spec.html` contains `<!-- prototype-status: approved -->` or `[x] PM 已确认原型`.
 2. Confirm `{process_slug}/designs/<design_id>/prototype.pen`, `{process_slug}/pages/docs/fields.html`, and the design review package exist.
 3. Read the confirmed design docs and inspect the `.pen` through Pencil tools if visual structure is needed.
@@ -34,11 +36,39 @@ Create `{process_slug}/pages/docs/tdd-plan.html` as the bridge from product desi
    - Task slices suitable for OpenSpec tasks and GitHub Issues
    - Risks, dependencies, and out-of-scope items
 5. Add `<!-- status: ready-for-openspec -->` when the plan is complete.
-6. Run `python scripts/stage_loader.py --stage tdd-development-plan --action record-artifacts`.
+
+### Phase 2 — PRD 交叉验证（测试反向驱动 PRD）
+
+6. **场景回问**：从 tdd-plan 的测试场景（正常、边界、异常）逐一回问 `{process_slug}/pages/docs/prd.html`：该场景涉及的业务规则与验收标准在 PRD 中是否有明确答案？逐项记录「场景 → PRD 答案（章节 + 条文）」，PRD 无答案者标记为缺口。
+7. **对齐闭环**：建立业务流程步骤 ↔ 原型页面双向对齐矩阵——PRD 业务流程图中的每个步骤至少有 1 个原型页面承载；每个原型页面归属于某流程步骤或用户故事。任一侧对不上即为缺口（流程中断或原型多余）。
+8. **渲染报告**：写 `{process_slug}/pages/docs/prd-cross-validation.md`（顶部含 `<!-- version: v1.0 -->`），用 `lincoln_render.py` 渲染为 `{process_slug}/pages/docs/prd-cross-validation.html`：
+
+   ```bash
+   python scripts/lincoln_render.py \
+     --stage tdd-development-plan \
+     --target {process_slug}/pages/docs/prd-cross-validation.html \
+     --title "PRD 交叉验证报告" \
+     --markdown {process_slug}/pages/docs/prd-cross-validation.md
+   ```
+
+   报告必须含：场景 → PRD 答案映射表、缺口清单、决策记录表（缺口 / 闭环方式 / PM 决策 / 理由）、PRD 修订回执。
+9. **闭环缺口**：每个缺口由人类 PM 决策二选一——
+   - **修复**：修订 `prd.md`，bump `<!-- version: vX.Y -->`，运行 `python scripts/lincoln_prd.py freeze` 重新冻结，然后重跑 Phase 2；
+   - **接受**：在决策记录表中记录理由与影响，经人类 PM 明确认可。
+
+   全部缺口闭环后，在报告 markdown 末尾追加 `<!-- cross-validation: pass prd-version: vX.Y -->`（vX.Y = 当前 PRD 版本）并重新渲染。未闭环前禁止写入该标记。
+10. Run `python scripts/stage_loader.py --stage tdd-development-plan --action record-artifacts`.
+
+## Output Artifacts
+
+- `{process_slug}/pages/docs/tdd-plan.html`
+- `{process_slug}/pages/docs/prd-cross-validation.html`（含场景→PRD 答案映射、缺口清单、决策记录、闭环标记）
 
 ## Rules
 
 - Keep the plan executable by an engineer without requiring extra product decisions.
 - Every task slice must map back to a design artifact and acceptance criterion.
 - Do not generate OpenSpec artifacts in this step.
+- 交叉验证发现的 PRD 缺口不得自行编造业务答案，必须交回人类 PM 决策（修复或接受）。
+- pass 标记中的版本必须与当前 PRD 版本一致；PRD 后续任何改动都会使标记失效，须重跑 Phase 2。
 - After completion, tell the user to run: `claude propose-with-openspec <session_id> <design_id> <change_name>`.

package/framework/.claude/stages/clarify.yaml

@@ -61,6 +61,9 @@ gates:
   - check: prd_has_required_sections
     args:
     - '{process_slug}/pages/docs/prd.html'
+  - check: prd_content_hygiene
+    args:
+    - '{process_slug}/pages/docs/prd.html'
   - check: human_approved
   - check: prd_snapshot_present
     args:

package/framework/.claude/stages/tdd-development-plan.yaml

@@ -18,6 +18,7 @@ variables:
 - process_slug
 artifact_templates:
   '{process_slug}/pages/docs/tdd-plan.html': .claude/templates/issue-package/page-doc.html.tpl
+  '{process_slug}/pages/docs/prd-cross-validation.html': .claude/templates/issue-package/page-doc.html.tpl
 agent:
   primary: lc-engineer
   reviewers:
@@ -36,11 +37,12 @@ skills:
 artifacts:
   required:
   - '{process_slug}/pages/docs/tdd-plan.html'
+  - '{process_slug}/pages/docs/prd-cross-validation.html'
 references:
   skill_prompt: .claude/skills/plan-tdd-development/SKILL.md
   agent_guide: .claude/agents/engineer.md
 context:
-  goal: 基于已确认的产品设计文档、字段规格、UI 规格和 Pencil 原型，生成可执行的测试驱动研发计划（`tdd-plan.html`），作为从产品设计到 OpenSpec 变更提案的桥梁。所有产物通过 {process_slug}/index.html 门户访问。
+  goal: 基于已确认的产品设计文档、字段规格、UI 规格和 Pencil 原型，生成可执行的测试驱动研发计划（`tdd-plan.html`），作为从产品设计到 OpenSpec 变更提案的桥梁；随后执行 PRD 交叉验证——用测试场景反向挑战 PRD（业务规则、验收标准、流程与原型对齐），全部缺口经人类 PM 决策闭环后方可离开本阶段。所有产物通过 {process_slug}/index.html 门户访问。
   execution: "调用 plan-tdd-development skill 基于已确认的产品设计文档、字段规格、UI 规格和 Pencil 原型，生成包含验收映射、测试场景与任务切片的 tdd-plan.html，作为 OpenSpec 提案的输入。"
 gates:
   entry:
@@ -49,3 +51,6 @@ gates:
     - product-prototype
   exit:
   - check: artifacts_present
+  - check: prd_cross_validated
+    args:
+    - '{process_slug}/pages/docs/prd-cross-validation.html'

package/framework/.claude/workflows/interview-to-knowledge.yaml

@@ -54,6 +54,8 @@ workflow:
       exit_checks:
         - check: prd_has_required_sections
           args: ["{process_slug}/pages/docs/prd.html"]
+        - check: prd_content_hygiene
+          args: ["{process_slug}/pages/docs/prd.html"]
         - check: human_approved
           args: ["{session_id}"]
         - check: prd_snapshot_present
@@ -114,9 +116,12 @@ workflow:
       action: plan-tdd-development
       artifacts:
         - "{process_slug}/pages/docs/tdd-plan.html"
+        - "{process_slug}/pages/docs/prd-cross-validation.html"
       exit_checks:
         - check: tdd_plan_complete
           args: ["{design_id}"]
+        - check: prd_cross_validated
+          args: ["{process_slug}/pages/docs/prd-cross-validation.html"]
 
     - id: propose
       name: OpenSpec 提案

package/framework/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "lincoln",
       "description": "AI-Native product R&D collaboration system for Conductor + Claude Code. Orchestrates stages, gates, artifacts, skills, and roles across product, design, and engineering into a repeatable workflow from recordings to GitHub Issues to Obsidian knowledge base.",
-      "version": "1.8.2",
+      "version": "1.8.4",
       "author": {
         "name": "Lincoln contributors"
       },
@@ -28,5 +28,5 @@
       ]
     }
   ],
-  "version": "1.8.2"
+  "version": "1.8.4"
 }

package/framework/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lincoln",
-  "version": "1.8.2",
+  "version": "1.8.4",
   "description": "AI-Native product R&D collaboration system for Conductor + Claude Code + OpenSpec + GitHub + Obsidian",
   "author": {
     "name": "Lincoln contributors"

package/framework/.version-bump.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.8.2",
+  "version": "1.8.4",
   "manifests": [
     {
       "path": ".claude-plugin/plugin.json",

package/framework/README.en.md

@@ -12,9 +12,9 @@ Lincoln is an AI-Native R&D workflow system spanning **IDEs, agent harnesses, co
 
 ## Latest Release
 
-[![Release](https://img.shields.io/badge/release-v1.8.2-blue)](RELEASE.md)
+[![Release](https://img.shields.io/badge/release-v1.8.4-blue)](RELEASE.md)
 
-**v1.8.2** is released: SecurityAnalyzer pre-tool-use gating, Trace 2.0 event log, session friction scoring and knowledge recall, plus multi-dimensional stakeholder analysis in the clarify stage.
+**v1.8.4** is released: hook-injected less-is-more artifact discipline, plus a fix syncing the `policies` directory into vendored projects.
 
 See the full release notes in [RELEASE.md](RELEASE.md).
 
@@ -101,6 +101,12 @@ lincoln update            # upgrade to the latest release and re-sync
 lincoln update --check    # check for a newer version without installing
 ```
 
+Or upgrade the package directly via npm and then re-sync:
+
+```bash
+npm install -g @sushanglewis/lincoln@latest && lincoln update
+```
+
 On an older install (e.g. from the `lincoln-install` era), or if npm reports `EEXIST: file already exists`, a leftover bin from an old package is blocking the install — clean up first, then reinstall:
 
 ```bash
@@ -152,6 +158,12 @@ Lincoln assigns stable IDs such as `feature/*`, `page/*`, `field/*`, and `doc/*`
 
 See [`.claude/workflows/README.md`](.claude/workflows/README.md) for the full template catalog.
 
+### Less-is-More Artifact Discipline
+
+AI-generated handoff artifacts tend to bury key information under bulk. Lincoln enforces a "less is more" discipline that applies **only when generating deliverables** ([`.claude/policies/less-is-more.md`](.claude/policies/less-is-more.md)): before writing, identify the reader, the purpose, and the decision the reader must make; then write conclusion-first, one artifact per question, pass a deletion test, prefer tables/diagrams over prose, link instead of duplicating, and keep the main reading path under three minutes. Research and deep-exploration stages are exempt and encouraged to expand fully.
+
+The discipline is injected automatically by the session hook whenever an active issue package is detected — no manual step required.
+
 ### Markdown-First Issue Work Packages
 
 Every requirement maps to one GitHub issue and one Lincoln feature branch. The `issue-<N>/` work package contains:
@@ -230,6 +242,8 @@ Before submitting a PR, please read:
 
 | Version | Date | Key capabilities |
 |---|---|---|
+| v1.8.4 | 2026-10-08 | PM-stage PRD quality gates: six-question clarity check, 13-section progressive PRD skeleton, content-hygiene and cross-validation checks, final-system-only prototype discipline (#129) |
+| v1.8.3 | 2026-10-08 | Less-is-more artifact discipline (hook-injected); platform-aware install hints for non-npm CLIs; `lincoln update` refreshes external skill libraries |
 | v1.7.0 | 2026-09-05 | SecurityAnalyzer gating; Trace 2.0 event log; friction scoring/knowledge recall/trace condensation/MR mining; parallel specialist delegation; stakeholder analysis model |
 | v1.6.3 | 2026-08-15 | Markdown-first issue-package documents; `--render-stage` batch rendering; local `mermaid.min.js` runtime |
 | v1.6.2 | 2026-08-12 | `lc-init-branch` reads global Lincoln templates |

package/framework/README.md

@@ -12,9 +12,9 @@ Lincoln 是一个贯穿 **IDE、Agent Harness、代码托管、知识管理、
 
 ## 最新版本
 
-[![Release](https://img.shields.io/badge/release-v1.8.2-blue)](RELEASE.md)
+[![Release](https://img.shields.io/badge/release-v1.8.4-blue)](RELEASE.md)
 
-**v1.8.2** 已发布：新增 SecurityAnalyzer 安全门控、Trace 2.0 事件日志与会话摩擦学习/知识召回能力，clarify 阶段支持多维度相关者分析。
+**v1.8.4** 已发布：新增少即是多制品生成纪律（hook 注入），修复 policies 目录未同步进 vendored 项目的问题。
 
 查看完整发布说明：[RELEASE.md](RELEASE.md)
 
@@ -101,6 +101,12 @@ lincoln update            # 升级本体 + 同步框架 + 刷新外部技能库
 lincoln update --check    # 只检查是否有新版本，不安装
 ```
 
+也可以直接用 npm 把本体升到最新再同步框架：
+
+```bash
+npm install -g @sushanglewis/lincoln@latest && lincoln update
+```
+
 技能库同步遵循 dependencies.yaml 的 pin 策略：本地有未提交修改的仓库会被跳过并警告（不会被强制覆盖），非 npm 管理的 CLI（如 gh）缺失时只提示安装命令。同步失败降级为警告，不会阻断升级。
 
 如果还是旧版安装（例如 bin 名是 `lincoln-install` 的时代），或更新时 npm 报 `EEXIST: file already exists`，说明有旧包残留的 bin 文件挡住了安装，先清理再重装：
@@ -154,6 +160,12 @@ Lincoln 为需求、页面、字段、文档等产物分配 `feature/*`、`page/
 
 完整模板说明见 [`.claude/workflows/README.md`](.claude/workflows/README.md)。
 
+### 少即是多的制品生成纪律
+
+AI 生成的交接产物容易内容堆积、重点淹没。Lincoln 把「少即是多」固化为一条只在**制品生成**时生效的纪律（[`.claude/policies/less-is-more.md`](.claude/policies/less-is-more.md)）：生成前先明确读者、用途与读者要做的决定；写作遵循结论先行、一件制品回答一个问题、删除测试、结构优于段落、链接优于复制、三分钟可读六条原则。调研与深度研究阶段不受其约束，鼓励充分展开。
+
+该纪律由 session hook 在检测到活跃 issue 工作包时自动注入，无需任何手动操作。
+
 ### Markdown-first Issue 工作包
 
 每个需求对应一个 GitHub issue 和一个 Lincoln feature 分支。工作包目录 `issue-<N>/` 包含：
@@ -232,6 +244,8 @@ Lincoln 的 `.claude/` 是开放的系统提示层，欢迎基于同一套元模
 
 | 版本 | 日期 | 关键能力 |
 |---|---|---|
+| v1.8.4 | 2026-10-08 | PM 阶段 PRD 质量门控：需求六问自检、13 章递进骨架、PRD 内容卫生与交叉验证校验、原型最终样貌纪律（#129） |
+| v1.8.3 | 2026-10-08 | 少即是多制品生成纪律（hook 注入）；非 npm CLI 平台化安装提示；`lincoln update` 同步刷新外部技能库 |
 | v1.7.0 | 2026-09-05 | SecurityAnalyzer 安全门控；Trace 2.0 事件日志；摩擦学习/知识召回/Trace 浓缩/MR 挖掘；并行专家子代理委托；相关者分析模型 |
 | v1.6.3 | 2026-08-15 | Markdown-first issue-package 文档；`--render-stage` 批量渲染；Mermaid 图表本地渲染 |
 | v1.6.2 | 2026-08-12 | `lc-init-branch` 改读全局 Lincoln 模板 |

package/framework/RELEASE.md

@@ -1,3 +1,40 @@
+# Lincoln v1.8.4 Release Notes
+
+**Release date:** 2026-10-08
+
+## Highlights
+
+- **PM 阶段 PRD 质量整治 (#129)** — 把「PM 产出的 PRD 必须经得起研发团队与测试挑战」从 prompt 建议升级为可执行的门控：
+  - **需求清晰度六问自检** — clarify-requirements 起草原稿前必须逐项回答：用户有哪些、场景是什么、边界在哪里、如何管异常、如何体验好、最终谁决策；答不出先问人类 PM，禁止带未决问题落笔。
+  - **13 章递进骨架** — PRD 固定为「版本说明 → 修订记录 → 功能列表 → 需求背景 → … → 风险与开放问题」的渐进结构，章节按名字匹配、编号只是装饰，PM 可按需求形态在骨架内增插业务章节。
+  - **双注册表内容卫生校验** — 两份校验器（stage gates 与 workflow exit_checks）同步新增 `prd_content_hygiene`：PRD 正文禁止过程性短语（待确认/待 PM/TODO 等）与技术性章节（技术调研/架构设计/数据库设计等），技术内容只进 design 阶段的归档页 feasibility.html。
+  - **SDD 测试反向驱动交叉验证** — plan-tdd-development 新增 Phase 2：从测试场景（正常/边界/异常）逐一回问 PRD 业务规则与验收标准，并建立业务流程步骤 ↔ 原型页面双向对齐矩阵；缺口必须由人类 PM 决策闭环（修复 = PRD 升版重冻结，或接受 = 记录理由与影响），全部闭环后交叉验证报告才能写入 pass 标记，`prd_cross_validated` 校验器强制 pass 标记版本与当前 PRD 版本严格相等并对 PRD 复检卫生，防止后续阶段编辑回潮。
+  - **原型只画最终样貌** — build-product-prototype 明确禁止仅用于演示的模拟按钮、屏内说明文字与演示跳转，解释一律走 `doc-*` 注释由门户右侧面板呈现；每个原型页面标注所属用户故事与业务流程步骤，与 PRD 文字双向对齐。
+  - **PM 角色质量职责** — lc-pm 新增三条专属职责：输出 PRD 前完成六问自检、PRD 只承载业务内容、交叉验证缺口必须经人类 PM 决策才允许闭环。
+
+## Migration Notes
+
+- 无破坏性变更：新校验只在 `clarify` 与 `tdd-development-plan` 阶段出口执行，既有已审批产物不受影响；重跑这两个阶段时需满足新版骨架与卫生规则。
+- 升级后执行 `lincoln update` 即把新 prompt、校验器与门控接线同步进各 harness；进行中的 issue 工作包从下一阶段起自动适用新规则。
+
+---
+
+# Lincoln v1.8.3 Release Notes
+
+**Release date:** 2026-10-08
+
+## Highlights
+
+- **少即是多制品生成纪律 (#126 / #128)** — 新增 `.claude/policies/less-is-more.md`，把「少即是多」固化为一条只在生成制品时生效的写作纪律：生成前先明确读者、用途与读者要做的决定；写作遵循结论先行、一件制品回答一个问题、删除测试、结构优于段落、链接优于复制、三分钟可读六条原则。调研与深度研究阶段不受其约束。该纪律由 session hook 在检测到活跃 issue 工作包（`current_stage != not_started`）时自动注入全文——单一注入点，skill prompt、stage YAML 与通用 Agent 契约均不重复携带，零额外上下文压力。
+- **修复 policies 目录未同步进项目的问题** — `syncClaudeCode` 的 `COPY_SUBDIRS` 新增 `policies`：此前 vendored 项目中 `.claude/policies/` 缺失，导致 `pre-tool-use.sh` 的 security.yaml 安全门控与本次新增的 less-is-more.md 在项目内静默跳过。修复后两类政策文件都会随 `lincoln install` / `lincoln update` 同步进项目。
+
+## Migration Notes
+
+- 无破坏性变更。升级到本版本后，下一次 issue 会话启动即自动获得少即是多纪律注入，无需手动操作。
+- 注意：npm 上 1.8.1 与 1.8.2 因发布令牌问题未曾发布（见 v1.8.2 说明），从 1.8.0 直接升级到 1.8.3 会一并获得这两个版本的能力（外部技能库自动刷新、非 npm CLI 平台化安装提示），升级后建议执行一次 `lincoln update`。
+
+---
+
 # Lincoln v1.8.2 Release Notes
 
 **Release date:** 2026-10-07