content-publish-lifecycle
把技术方案 / 设计从「设计 → 落地 → 检查 → 验证 → 发布 → 沉淀」串成一条可复用发布流水线，用于回答「方案做完了怎么变成能发的东西」「发出去之前该查什么」这类问题
as observed 2026-09-29T04:47:03.526Z- Identifier
content-publish-lifecycle- Source
- ClawHub
- Version observed
- 1.0.3
- Source repository
- not published
- Repository observation
- No source repository listed
- First observed here
- 2026-08-31T05:56:02.339Z
- Observations recorded
- 2
- Installs (reported upstream)
- 1
- Weekly downloads (upstream)
- 264
- Declared license
- MIT-0
Observation history
2026-09-29T04:47:03.526Z
Fields that differed: license changelog description displayName latestVersion
| Field | Before | After |
|---|---|---|
license |
null | "MIT-0" |
changelog |
"v1.0.0 首次发布：六阶段发布流水线，含本地零网络权属证明与安全实测雷达图。" | "权利层第 3 轮：① §3.2 权属宣告统一块归一——清除块内他资产事实（此前误填 uibc-core 的 DOI / commit cb6f11b / Sigstore Rekor 锚），改按本资产真值填写；② 技能件许可口径过授权清除——理论文本由 CC BY 4.0 改为「保留所有权利」，.py 依 §3.2 标 MIT；③ 保留分层许可：代码 MI |
description |
"把技术方案 / 设计从「设计 → 落地 → 检查 → 验证 → 发布 → 沉淀」串成一条可复用发布流水线，用于回答「方案做完了怎么变成能发的东西」「发出去之前该查什么」这类问题" | null |
displayName |
"内容发布全流程（设计→落地→检查→验证→发布→沉淀）" | "content-publish-lifecycle" |
latestVersion |
"1.0.0" | "1.0.3" |
Correction
If you maintain this extension and believe anything above is inaccurate, request a correction. Corrections are published, and disputed entries are marked as disputed while under review.