scene-capability-engine 3.3.11 → 3.3.12
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/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [3.3.12] - 2026-02-25
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
- Strengthened steering baseline for root-cause defect handling:
|
|
14
|
+
- Added explicit rule: bug fixing must prioritize root-cause remediation, not workaround-style bypass.
|
|
15
|
+
- Added explicit complex-issue debugging method: prefer debug logs and observability signals (inputs/outputs/branches/stack/context) to reconstruct execution path before conclusion.
|
|
16
|
+
- Standardized ontology analysis baseline in steering as a unified "four layers + one chain" model:
|
|
17
|
+
- Entity model
|
|
18
|
+
- Relation graph
|
|
19
|
+
- Business rule
|
|
20
|
+
- Decision logic
|
|
21
|
+
- Action/lineage execution chain
|
|
22
|
+
- Synced the same steering enhancements to both runtime project steering and template steering:
|
|
23
|
+
- `.sce/steering/CORE_PRINCIPLES.md`
|
|
24
|
+
- `template/.sce/steering/CORE_PRINCIPLES.md`
|
|
25
|
+
|
|
10
26
|
## [3.3.11] - 2026-02-24
|
|
11
27
|
|
|
12
28
|
### Added
|
package/package.json
CHANGED
|
@@ -128,6 +128,31 @@
|
|
|
128
128
|
|
|
129
129
|
**目标**: AI 像人类开发者自由使用开发环境资源，专注解决问题而非权限申请
|
|
130
130
|
|
|
131
|
+
### 11. 缺陷修复优先根因原则 🛠️
|
|
132
|
+
|
|
133
|
+
**核心**: 定位问题时，第一要务是修复根因，不是绕过问题
|
|
134
|
+
|
|
135
|
+
**硬规则**: ❌ 禁止通过关闭校验、跳过测试、降级关键路径、屏蔽异常等方式“假修复”
|
|
136
|
+
|
|
137
|
+
**复杂问题定位方法**: 优先使用 debug 日志与可观测信号定位（输入、输出、关键分支、异常栈、上下文参数），先还原执行路径再下结论
|
|
138
|
+
|
|
139
|
+
**允许的临时措施**: 仅在生产止血场景可临时绕行，但必须同时给出根因修复任务、回滚条件和截止时间
|
|
140
|
+
|
|
141
|
+
**验收标准**: 必须有可复现用例、修复后回归通过、明确根因记录（不是仅现象描述）
|
|
142
|
+
|
|
143
|
+
### 12. Ontology 四层一链分析原则 🧭
|
|
144
|
+
|
|
145
|
+
**核心**: 梳理项目必须按统一语义框架推进，避免只看页面或只看接口
|
|
146
|
+
|
|
147
|
+
**标准口径（修正）**:
|
|
148
|
+
1) 实体模型（Entity）
|
|
149
|
+
2) 关系图谱（Relation）
|
|
150
|
+
3) 业务规则（Business Rule）
|
|
151
|
+
4) 决策逻辑（Decision）
|
|
152
|
+
5) 执行链路（Action/Lineage，体现“决策如何被执行与影响到哪里”）
|
|
153
|
+
|
|
154
|
+
**要求**: 需求分析、问题定位、模板沉淀、发布门禁均按该口径检查完整性与一致性
|
|
155
|
+
|
|
131
156
|
---
|
|
132
157
|
|
|
133
|
-
|
|
158
|
+
v15.0 | 2026-02-25 | 新增根因修复原则与 Ontology 四层一链分析原则
|