chore: release v1.24.2 with ESLint import/order rule, PostToolUse hook for Prettier formatting, updated assertions documentation, and dependency updates

Author: vasu31dev

CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## [1.24.2] - 2026-03-18
+
+### Added
+
+- **ESLint import/order:** `import/order` rule in `eslint.config.base.mjs` for consistent import declaration order (builtin → external → internal → parent → sibling → index) with alphabetize and path groups for `@/**`; auto-fix via `eslint --fix`. `sort-imports` kept with `ignoreDeclarationSort: true` for member order within named imports only.
+- **PostToolUse hook (Claude/Cursor):** `.claude/settings.json` config to run Prettier on edited `.ts`/`.tsx` files after Edit/Write tool use.
+
+### Changed
+
+- **Import order:** Sorted imports across source, tests, and config with `npm run lint:fix` to satisfy the new import/order rule.
+- **Assertions skill (references/assertions.md):** Do not use assertions in spec files—only in page `verify*` methods. Added good spec examples for readable tests.
+- **Tests:** Removed redundant add-to-cart test case.
+
+### Fixed
+
+- **lint-staged:** For staged `*.ts` files, lint-staged now runs `eslint --fix` then `eslint` so auto-fixable issues are applied in the index and remaining errors are reported (commit blocked until lint passes).
+
 ## [1.24.1] - 2026-03-17
 
 ### Added

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "vasu-playwright-utils",
-  "version": "1.24.1",
+  "version": "1.24.2",
   "description": "Playwright Typescript Library with reusable utilities",
   "main": "./dist/src/vasu-playwright-lib/index.js",
   "types": "./dist/src/vasu-playwright-lib/index.d.ts",
@@ -68,7 +68,7 @@
     "eslint-import-resolver-typescript": "^4.4.4",
     "eslint-plugin-import": "^2.32.0",
     "eslint-plugin-jsdoc": "^62.8.0",
-    "eslint-plugin-playwright": "^2.10.0",
+    "eslint-plugin-playwright": "^2.10.1",
     "eslint-plugin-prettier": "^5.5.5",
     "husky": "^9.1.7",
     "lint-staged": "^16.4.0",

package.json

@@ -2,13 +2,15 @@
 
 Source: `src/vasu-playwright-lib/utils/assert-utils.ts`
 
-## Key Principle
+## Using Assertions in Spec Files
 
-**Use assertions in page files, NOT in spec files.** Spec files should read like plain English — all assertion logic lives inside page-object `verify*` methods.
+**Do not use assertions in spec files.** Assertions are for building and verifying behaviour inside page objects (e.g. `verify*` methods). Spec files should only orchestrate steps and call those methods so the test reads like a clear, readable scenario.
 
-### Good Example
+### Good Example — Readable Spec (No Assertions in Spec)
 
-**Spec file** — reads like a test plan, no assertions:
+The spec reads like a test plan; all assertions live in page files.
+
+**Spec file** — plain English, no assertion utils:
 
 ```typescript
 test('Complete checkout flow', async () => {