@iamdevlinph/codex-kit 1.1.3 → 1.1.4

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.
@@ -141,16 +141,20 @@ conditional procedures into validated project skills.
141
141
  - Avoid broad commands. After changes, run the smallest targeted verification
142
142
  that meaningfully validates them when practical, then report the command and
143
143
  result. Use the repository's documented package manager and scripts.
144
- - For behavior changes and bug fixes, add or update the smallest focused
145
- automated tests that meaningfully prevent regression when the repository has
146
- an established test setup.
144
+ - Select tests for regression value rather than exhaustive coverage. When the
145
+ repository has an established test setup, cover changed observable contracts,
146
+ reported regressions, meaningful boundaries, and plausible costly failures,
147
+ especially security, trust-boundary, or data-loss risks.
148
+ - Use one representative case per equivalent behavior class. Skip redundant
149
+ permutations, implementation-detail assertions, and contrived or unreachable
150
+ states unless a requirement or past defect justifies them.
147
151
  - Treat existing tests as regression contracts. Preserve their assertions unless
148
152
  the requested behavior intentionally changes. When behavior changes, update
149
153
  only the affected tests and add coverage for the new contract; never weaken or
150
154
  delete tests merely to make the suite pass.
151
- - Do not introduce a test framework or create low-value tests solely to satisfy
152
- this rule. If automated coverage is impractical, explain why and perform the
153
- strongest targeted verification available.
155
+ - Do not introduce a test framework solely to satisfy this rule. If automated
156
+ coverage is impractical, explain why and perform the strongest targeted
157
+ verification available.
154
158
  - Run the relevant focused tests after changing tested behavior.
155
159
  - When adding or updating dependencies, pin exact versions rather than ranges.
156
160
  With pnpm, use `pnpm add -E` (`--save-exact`).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@iamdevlinph/codex-kit",
3
- "version": "1.1.3",
3
+ "version": "1.1.4",
4
4
  "description": "Portable Codex subagents and project AGENTS.md defaults.",
5
5
  "type": "module",
6
6
  "bin": {