@vyriy/handler 0.9.0 → 0.9.2

package/AGENTS.md

@@ -14,6 +14,7 @@ Always read the root `AGENTS.md` first for current project direction, then use t
 - Avoid hidden framework, CMS, browser, filesystem, network, or cloud assumptions unless they are the package contract.
 - Add packages only when they reduce real complexity, clarify boundaries, or improve reuse.
 - Prefer the option that is simpler to explain, easier to evolve, and calmer to maintain.
+- Grow package functionality in small, calm, reviewable steps that are easy to test and continue.
 
 ## Standard Package Shape
 
@@ -84,6 +85,8 @@ Documentation must move with code. Do not finish a package change while docs des
 - Keep `doc.mdx` aligned with the README and package title when packages are added, renamed, or reorganized.
 - Add or update JSDoc for public exports when behavior, parameters, return values, errors, side effects, or usage expectations need explanation.
 - For component packages, include visual documentation, stories, or examples for supported states, variants, and interaction states.
+- Keep reusable components as dumb as practical: push data shaping, stateful orchestration, and demo-specific logic into the entry point or owning composition layer.
+- Store demo data in stories instead of embedding it in reusable component source.
 - Avoid broad architecture essays in package READMEs; keep architectural direction in root-level docs unless it is necessary to use the package.
 
 ## Tests Are Required
@@ -94,9 +97,11 @@ Tests should protect public behavior and meaningful regression risk.
 - Add a real test immediately for new packages. If behavior is not finalized, add a valid placeholder test with a clear public API expectation.
 - Prefer behavior-focused tests over private implementation lock-in.
 - Keep tests deterministic and avoid real network, timers, browser, filesystem, or cloud dependencies unless that dependency is the behavior under test.
+- Mock external dependencies from `node_modules` in unit tests so package behavior stays deterministic and local.
 - When mocking modules, install mocks before loading the module under test.
 - Use `@jest/globals` in Jest tests.
-- Use `--coverage=false` for focused behavioral regression runs when global coverage thresholds would obscure the result.
+- Keep coverage enabled for normal validation. The shared Jest config in `packages/jest/index.ts` requires 100% global coverage for branches, functions, lines, and statements.
+- For small changes, run Jest against the changed tests or changed package with coverage enabled. For larger package changes, public API changes, or cross-package changes, run the full Jest suite with coverage.
 
 Typical package test naming:
 
@@ -127,10 +132,12 @@ Preferred validation commands:
 yarn tsc --pretty false
 yarn eslint <changed files or package>
 yarn prettier --check <changed files or package>
-yarn jest <changed tests or package> --runInBand --coverage=false
+yarn jest <changed tests or package> --runInBand
 ```
 
-Also run `yarn build:dist` for package export, manifest, build-shape, or generated-dist behavior changes. After larger package or library changes, prefer building the affected library/package as an additional confidence check.
+Run ESLint after YAML/YML changes too, for example `yarn eslint <changed.yml>`, because the repo ESLint setup validates YAML files as well.
+
+Also run `yarn build:dist` for package export, manifest, build-shape, or generated-dist behavior changes. After larger package or library changes, run the full Jest suite with coverage and prefer building the affected library/package as an additional confidence check.
 
 If a required validation command cannot be run, state why and report the remaining risk.
 

package/package.json

@@ -1,16 +1,16 @@
 {
   "name": "@vyriy/handler",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "description": "Composable AWS Lambda handler chains and wrappers for Vyriy projects",
   "homepage": "https://vyriy.dev/docs/handler/",
   "type": "module",
   "dependencies": {
     "@types/aws-lambda": "^8.10.162",
-    "@vyriy/chaos": "0.9.0",
-    "@vyriy/config": "0.9.0",
-    "@vyriy/logger": "0.9.0",
-    "@vyriy/smoke": "0.9.0",
-    "@vyriy/timeout": "0.9.0"
+    "@vyriy/chaos": "0.9.2",
+    "@vyriy/config": "0.9.2",
+    "@vyriy/logger": "0.9.2",
+    "@vyriy/smoke": "0.9.2",
+    "@vyriy/timeout": "0.9.2"
   },
   "agents": "./AGENTS.md",
   "license": "MIT",