chore: prepare v3.0.0 release and update dev toolchain

- Migrate dev toolchain from webpack/karma/eslint to vite/vitest/Biome
- Update htmlparser2 to ^12.0.0 and React peer dep to ^19.0.0
- Remove deprecated prop-types from test dependencies
- Enhance npm package contents by excluding dev tool files
- Add exports config to vite build configs
- Update git-commit skill metadata and formatting rules

Author: orrisroot

.agents/skills/git-commit/SKILL.md

@@ -4,7 +4,7 @@ metadata:
     github-path: skills/git-commit
     github-ref: refs/heads/main
     github-repo: https://github.com/orrisroot/agent-skills
-    github-tree-sha: 55f44eb2a8ac455b0953b2fb6399f5a628066b51
+    github-tree-sha: e578a03c4a4295e65d0b0ef737d9ee979fbf08a0
 name: git-commit
 ---
 # Git Commit Operator

.agents/skills/git-commit/references/conventional_commits.md

@@ -35,12 +35,13 @@ When drafting, validating, or executing Git commits, you must strictly adhere to
    * The subject line (first line) must not exceed 72 characters, ideally 50 characters or less.
    * **Every single line within the commit message body must also be wrapped at 72 characters or less.** If an explanation runs longer, you must manually insert line breaks to keep each line under the 72-character threshold.
 
-3. **Paragraph Separation via Multiple `-m` Flags**:
-   * When providing or executing the final `git commit` command, **you must use a separate `-m` option for each distinct paragraph** (e.g., the subject line, body paragraphs, and footers). Do not use a single multi-line string.
+3. **Part Separation via Multiple `-m` Flags**:
+   * Use one `-m` flag per structural part: the subject line, the body, and the footer. Use at most three `-m` flags in total.
+   * All body content — including bullet lists and multi-sentence explanations — must be placed in a single `-m` value. Do not split body content across multiple `-m` flags; doing so inserts unwanted blank lines between items.
    * *Example:*
 
      ```bash
-     git commit -m "feat(auth): add jwt authentication" -m "Validate tokens on every incoming request. Secure endpoints by rejecting expired credentials." -m "BREAKING CHANGE: The old session-based cookie auth is deprecated."
+     git commit -m "feat(auth): add jwt authentication" -m $'Validate tokens on every incoming request.\nSecure endpoints by rejecting expired credentials.\n- Added middleware for token validation\n- Removed legacy session handling' -m "BREAKING CHANGE: The old session-based cookie auth is deprecated."
      ```
 
 4. **Co-authored-by Restriction**:

.npmignore

@@ -1,6 +1,11 @@
+.agents/
+.cspell.json
+biome.json
 tsconfig.json
 tsconfig.*.json
 node_modules
 /coverage/
 /test/
-/demo/dist/
+/demo/
+vite.*.ts
+vitest.config.ts

CHANGELOG.md

@@ -1,5 +1,20 @@
 # Change Log
 
+## v3.0.0
+
+### Breaking Changes
+
+- Migrated development toolchain from webpack/karma/eslint to vite/vitest/Biome
+- Removed ESLint, Prettier, and Karma configurations
+- Restructured demo application with TypeScript and modern Vite setup
+
+### Updates
+
+- Updated the depending `htmlparser2` library version to `^12.0.0`
+- Updated peer dependency React version to `^19.0.0`
+- Updated all development dependencies to latest versions
+- Enhanced package contents — removed development tool files from npm package
+
 ## v2.1.2
 
 ### Updates