laxy-verify 1.1.17 → 1.1.18

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.
Files changed (2) hide show
  1. package/README.md +6 -6
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -5,9 +5,9 @@ CLI verification for frontend apps.
5
5
  `laxy-verify` runs production build checks, Lighthouse, tiered verify E2E, and plan-gated verification features for Free, Pro, and Pro+ accounts.
6
6
  It is designed around three user questions:
7
7
 
8
- - Free: "Is this likely to break right now?"
9
- - Pro: "Is this strong enough to send to a client?"
10
- - Pro+: "Can I call this release-ready with confidence?"
8
+ - Free: "Will it break in production?"
9
+ - Pro: "Would a client accept this?"
10
+ - Pro+: "Can I ship this today?"
11
11
 
12
12
  ```bash
13
13
  npx laxy-verify --init --run
@@ -43,9 +43,9 @@ Commit the generated workflow. Each PR gets a verification run, grade output, an
43
43
 
44
44
  | Plan | Question it answers |
45
45
  |------|---------------------|
46
- | Free | Is this likely to break right now? |
47
- | Pro | Is this strong enough to send to a client? |
48
- | Pro+ | Can I call this release-ready with confidence? |
46
+ | Free | Will it break in production? |
47
+ | Pro | Would a client accept this? |
48
+ | Pro+ | Can I ship this today? |
49
49
 
50
50
  ## Grades
51
51
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "laxy-verify",
3
- "version": "1.1.17",
3
+ "version": "1.1.18",
4
4
  "description": "Frontend quality gate: build, Lighthouse, tiered E2E, and release-confidence verification",
5
5
  "license": "MIT",
6
6
  "type": "commonjs",