@sylphx/flow 3.26.0 → 3.27.0
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 +6 -0
- package/assets/agents/builder.md +7 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @sylphx/flow
|
|
2
2
|
|
|
3
|
+
## 3.27.0 (2026-04-04)
|
|
4
|
+
|
|
5
|
+
### ✨ Features
|
|
6
|
+
|
|
7
|
+
- **agent:** enforce root cause analysis and rigorous testing standards (#146) ([68df2bf](https://github.com/SylphxAI/flow/commit/68df2bf4b66288a770e11d95c185f1cf5386a1ef))
|
|
8
|
+
|
|
3
9
|
## 3.26.0 (2026-04-04)
|
|
4
10
|
|
|
5
11
|
### ✨ Features
|
package/assets/agents/builder.md
CHANGED
|
@@ -142,6 +142,8 @@ Two-layer durable memory:
|
|
|
142
142
|
|
|
143
143
|
## Quality
|
|
144
144
|
|
|
145
|
+
**Root cause or nothing.** Every bug, every failure, every unexpected behavior — trace it to the root cause. Fixing symptoms is not fixing. If you can't explain WHY it happened, you haven't found the cause yet. Keep digging until you reach the architectural, logical, or data-level origin of the problem.
|
|
146
|
+
|
|
145
147
|
- Every fix must address the root cause, not the symptom
|
|
146
148
|
- Write tests that prevent regressions
|
|
147
149
|
- After fixing a bug, scan the entire project for similar issues — proactive, not reactive
|
|
@@ -195,10 +197,15 @@ Errors should be:
|
|
|
195
197
|
|
|
196
198
|
## Testing
|
|
197
199
|
|
|
200
|
+
**Rigorous verification, reliable checks.** Tests are not ceremony — they are proof that the system works. Every test must make a meaningful assertion that would catch a real regression. Flaky tests are bugs. Missing tests are liabilities.
|
|
201
|
+
|
|
198
202
|
- Unit tests for pure functions and utilities
|
|
199
203
|
- Integration tests for API routes and database operations
|
|
200
204
|
- E2E tests for critical user flows
|
|
201
205
|
- Test the behavior, not the implementation
|
|
206
|
+
- Every assertion must be deterministic — no timing-dependent, order-dependent, or environment-dependent tests
|
|
207
|
+
- Test edge cases and failure paths, not just the happy path
|
|
208
|
+
- If a bug was found, a test must be written that would have caught it before the fix is applied
|
|
202
209
|
|
|
203
210
|
## Database (Atlas)
|
|
204
211
|
|
package/package.json
CHANGED