tech-lead-skill 5.5.1 → 5.5.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/README.zh-CN.md +1 -1
- package/docs/AUDIT_REPORT.md +1 -1
- package/docs/TECHNICAL_GUIDE.md +4 -0
- package/package.json +1 -1
- package/skill/SKILL.md +1 -1
package/README.md
CHANGED
|
@@ -148,6 +148,6 @@ The executable skill body (`SKILL.md`) is authored in Simplified Chinese; coding
|
|
|
148
148
|
|
|
149
149
|
## Version
|
|
150
150
|
|
|
151
|
-
Current version: `v5.5.
|
|
151
|
+
Current version: `v5.5.3`.
|
|
152
152
|
|
|
153
153
|
See [`docs/TECHNICAL_GUIDE.md`](docs/TECHNICAL_GUIDE.md) for the full operating model and [`docs/AUDIT_REPORT.md`](docs/AUDIT_REPORT.md) for the publication audit.
|
package/README.zh-CN.md
CHANGED
package/docs/AUDIT_REPORT.md
CHANGED
|
@@ -35,7 +35,7 @@ The source set was scanned for local absolute paths, passwords, API-key prefixes
|
|
|
35
35
|
### Structural scan
|
|
36
36
|
|
|
37
37
|
- YAML frontmatter has `name: tech-lead` and a trigger description.
|
|
38
|
-
- The skill version is `v5.5.1
|
|
38
|
+
- The skill version is `v5.5.3`. R8.1 (2026-08-26) completes the R8 public contract: protocolJson declared on all 22 tool schemas; all nine legacy bare tools negotiate with bare defaults and fail-closed envelope passthrough; inputCompatibility=compat migrates unknown context keys instead of rejecting; context_validate dispatches canonical v2 documents to validateContextV2; v2 envelopes carry findings/guidance/meta.complete plus meta.outputProtocol stamped by negotiation. one-way state→context-v2 projection (identity options mandatory), result-protocol negotiation on every tool, and the v2 wire label for strengthened envelopes; reverse projection is deferred as non-lossless (evidence/2026-08-26-r8-projection.md).
|
|
39
39
|
- The eight templates referenced by the skill exist.
|
|
40
40
|
- The installer validates options, requires a marker before removing any target, and records the managed package/version after installation.
|
|
41
41
|
- The release-check template covers allowlist inventory, sensitive-content scanning, reference checks, scope checks, publication results, and remote verification.
|
package/docs/TECHNICAL_GUIDE.md
CHANGED
|
@@ -135,3 +135,7 @@ Use the smallest applicable artifact set, but do not omit a required record mere
|
|
|
135
135
|
## Lifecycle results (R6)
|
|
136
136
|
|
|
137
137
|
PAUSE/PIVOT/SCOPE-DOWN/STOP and gate non-pass states are valid `ok:true` analyses; `ok:false` is reserved for malformed input, budget overruns and incomplete scans (`SCAN_INCOMPLETE`). Guidance actions always carry `doneWhen` predicates.
|
|
138
|
+
|
|
139
|
+
## Result protocol negotiation (R8)
|
|
140
|
+
|
|
141
|
+
Every tool accepts `protocolJson`: `{"outputProtocol":"legacy|tech-lead.result.v1|tech-lead.result.v2","inputCompatibility":"strict|compat"}`. Strengthened tools default to the v2 envelope; all nine legacy bare-shape tools stay bare by default and negotiate on explicit request; fail-closed SCAN_INCOMPLETE envelopes always pass through untouched. `inputCompatibility:"compat"` migrates unknown top-level context keys into namespaced extensions (EXTENSION_MIGRATED warning) instead of rejecting them; strict rejects. Declared on every tool schema. Unsupported selections return `UNSUPPORTED_SCHEMA_VERSION`. Canonical v2 documents are routed through validateContextV2 by tech_lead_context_validate; gate_precheck is envelope-only since R6. Canonical context: `projectStateToContextV2` performs a one-way v1→v2 projection; identity/fingerprint options are mandatory (`NON_CONVERTIBLE_STATE` otherwise); reverse conversion is deferred (see docs/superpowers/evidence/2026-08-26-r8-projection.md).
|
package/package.json
CHANGED
package/skill/SKILL.md
CHANGED
|
@@ -3,7 +3,7 @@ name: tech-lead
|
|
|
3
3
|
description: 用于软件、基础设施、研究和运维中的多步、跨边界或有状态工程交付:项目规划、架构选择、跨模块实现、部署、迁移、发布、恢复、重构、长期运行与跨会话续跑。涉及不可逆/生产变更、回滚验证、真实环境对账、发布安全或项目级交付治理时优先加载,即使用户没有说“项目”或“Tech Lead”。不要仅因一次性小修复、单文件编辑、普通解释、单次测试或只读代码审查而自动加载,除非用户明确要求项目级计划或本规范。
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
# Tech Lead · 自主演进规划与交付规范 v5.5.
|
|
6
|
+
# Tech Lead · 自主演进规划与交付规范 v5.5.3
|
|
7
7
|
|
|
8
8
|
> 双层架构声明:本文件是**判断层**(自由裁量域)。其中可机械判定的不变量(Gate 前置校验、
|
|
9
9
|
> 证据锚点存在性、分级判定器、状态机转换有效性)为未来 **MCP 工具化候选**——
|