circuitjson-toolkit 1.0.16 → 1.0.17
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/AGENTS.md +15 -0
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -47,6 +47,21 @@
|
|
|
47
47
|
- Keep tests focused on observable CircuitJSON utility behavior.
|
|
48
48
|
- Tests must use small fake CircuitJSON samples only.
|
|
49
49
|
|
|
50
|
+
## Fix Quality Rules
|
|
51
|
+
|
|
52
|
+
- Fixes must always address the general behavior, not a specific example,
|
|
53
|
+
fixture, file, project, or test case.
|
|
54
|
+
- Do not implement workarounds, cheats, allowlists, hard-coded example handling,
|
|
55
|
+
or special-case logic to make one sample pass.
|
|
56
|
+
- When you encounter existing workaround code, cheating behavior, or
|
|
57
|
+
example-specific handling, rewrite it into general-purpose behavior
|
|
58
|
+
immediately when it is in scope for the change.
|
|
59
|
+
- Keep fixes universal and structural: derive behavior from the underlying data
|
|
60
|
+
model, format, protocol, or UI contract instead of matching known sample text,
|
|
61
|
+
filenames, labels, or project identifiers.
|
|
62
|
+
- After fixing code, run the appropriate repo-owned tests and do not modify tests
|
|
63
|
+
just to make a workaround pass.
|
|
64
|
+
|
|
50
65
|
## Security & Configuration Tips
|
|
51
66
|
|
|
52
67
|
- Treat CircuitJSON files as untrusted input.
|