docs: correct 5.4.4 positioning and public demo privacy

Why:
The published README narrowed AI Delivery Spec into an artifact-to-PRD utility, weakened the problem-first value proposition, and used a review-handoff demo that exposed a recognizable project combination.

What changed:
- restore a problem-first, full-lifecycle story from discovery and clarification through implementation handoff, change control, traceability, and acceptance
- explain concrete value for junior/senior PMs, product leaders, business roles, frontend, backend, QA, technical leads, and architects
- clarify the current boundary with Spec Kit and OpenSpec without outdated comparisons
- remove the project-derived demo asset and add a durable privacy rule for public examples
- align skill metadata, lifecycle visual, changelog, runtime package contract, and regression expectations

Scope:
This is a same-version 5.4.4 documentation and positioning patch. Runtime routing, delivery levels, gates, schemas, CLI behavior, and required artifact contracts are unchanged.

Validation:
- full release profile: PASS
- Skill Creator quick validation: PASS
- product-experience regression suite: 8/8 PASS
- runtime package: 111 source files; removed demo excluded
- maintainer budget: 449935/450000 bytes
- git diff check: PASS

Author: franklinxkk

.github/CONTRIBUTING.md

@@ -60,6 +60,9 @@ independent audit evidence.
 
 - Never submit secrets, credentials, personal data, private customer documents,
   or insufficiently anonymized screenshots/data.
+- Public README demos and assets must be synthetic and domain-neutral: do not
+  reuse customer nouns, workflows, metrics, screenshots, or recognizable project
+  combinations, and do not let one brownfield scenario define the whole Skill.
 - Do not copy protected standards or paid research in full. Store citation,
   applicability, version, and the minimal product implication.
 - Generated or inferred professional claims must be marked as such.

.github/assets/demo-review-handoff.svg

@@ -1,15 +1,15 @@
 # Changelog
 
 
-## 5.4.4 正式候选 - 2026-08-08
+## 5.4.4 - 2026-08-08
 
-- README 首屏改为真实存量原型交接 Demo、需求生命周期图和 60 秒开始，并明确与 Spec Kit/OpenSpec
-  的互补边界；两个自包含 SVG 随运行包分发，文件预算由 110 精确调整为 112，不增加维护实验室文件。
+- README 恢复问题导向首屏，按初中高级产品、产品负责人、前后端、测试和技术/架构角色说明价值，
+  覆盖从零发现到验收的完整需求生命周期；删除带项目指纹的单场景 Demo，仅保留通用生命周期图。
 - 发版前修复 Windows 旧代码页下澄清编译输出、稳定 ID 内 `TODO` 误判、`${act}` 模板引用污染、
   高不确定性分诊空依据、运行包 dirty 来源标记和失效回归样例；动态 `act/add/confirmAction` 的字面量
   入口不再被重复判为孤儿处理器，真实无入口处理器与动态锚点拼接仍独立阻断。
-- 实施步骤合同补齐企业/人员/车辆/证件等计数单位、日志行粒度、成功/失败/部分成功归集、
-  差异确认后的权威源回写、选中/未选提交边界及生成对象后的下一可达入口。
+- 实施步骤合同补齐对象计数单位、记录粒度、成功/失败/部分成功归集、权威源更新、
+  提交集合边界及处理完成后的下一可达入口。
 - 为实施可见性合同增加确定性守门：handoff 中的 `implementation_step_refs` 必须解析到 PRD 的完整
   `STEP-*` 实施卡，开发就绪清单不得漏包；幽灵 STEP、工作包漏引和八类核心实施语义缺失均阻断。
 - 明确交互账本是派生覆盖清单而非需求权威源：纯界面动作使用 `UIACT-*`，业务 `ACT-*` 与 `AC-*`