Chore/npm release changeset

.changeset/release-4-0-4.md

@@ -0,0 +1,8 @@
+---
+'hookform-action': patch
+'hookform-action-core': patch
+'hookform-action-standalone': patch
+'hookform-action-devtools': patch
+---
+
+Publish a patch release with the latest docs, examples, lint/format alignment, and core adapter consistency updates.

.gitignore

@@ -6,3 +6,4 @@ coverage
 *.tsbuildinfo
 .env
 .env.local
+.claude/

MESSAGING.md

@@ -0,0 +1,102 @@
+# hookform-action Messaging Pack
+
+## Core Positioning
+- The missing layer between React Hook Form and your server.
+- Typed submit flows with Zod mapping, optimistic UI, persistence, and DevTools.
+- Keep RHF ergonomics. Remove repeated integration wiring.
+
+## 1) One-Liners (15)
+1. Typed submit flows for React Hook Form.
+2. The missing layer between RHF and your server.
+3. Write the schema. Write the action. Skip the wiring.
+4. React Hook Form meets typed server submits.
+5. Keep RHF. Add reliable server submit flows.
+6. One hook for validation, pending state, and submit errors.
+7. Zod errors mapped to RHF fields automatically.
+8. Optimistic UI with rollback, built in.
+9. Persistence for multi-step forms, without storage glue code.
+10. Server actions without repetitive form plumbing.
+11. End-to-end type safety from input to action result.
+12. Predictable RHF submit pipelines for production apps.
+13. Same API for Next.js and standalone React apps.
+14. Less per-form code between data entry and mutation.
+15. Form-server integration you configure, not rewrite.
+
+## 2) Short Descriptions (10)
+1. hookform-action bridges React Hook Form and server submits with typed data flow and automatic field error mapping.
+2. It removes repetitive submit plumbing: FormData parsing, transition wiring, and server error propagation.
+3. Define your Zod schema once and keep types consistent across validation, submission, and response handling.
+4. Enable optimistic updates with rollback through options, not custom state machines.
+5. Persist multi-step values with debounced sessionStorage restore behavior.
+6. Keep the RHF API you already use while adding server-aware pending and result state.
+7. Use the same mental model in Next.js Server Actions and standalone React apps.
+8. Add DevTools to inspect form state, submit history, and debug actions during development.
+9. Built for teams that need predictable server-backed forms without replacing RHF.
+10. A practical typed layer for RHF submit flows with Zod and server feedback.
+
+## 3) Medium Descriptions (5)
+1. hookform-action is the integration layer between React Hook Form and your server. It standardizes typed submission, Zod validation mapping, pending state, and field-level server errors in one pipeline. You keep RHF ergonomics and remove repeated boilerplate.
+2. RHF, Zod, and Server Actions are strong primitives, but the space between them is where most form bugs appear. hookform-action closes that gap with typed submit flow control, automatic error mapping, optimistic updates, and optional persistence.
+3. Use `withZod` as a single source of truth for validation and types. hookform-action carries those types through the submit lifecycle and keeps form state behavior consistent across client and server boundaries.
+4. In Next.js, it plugs into Server Actions directly. In standalone React apps, the same API works with a `submit` function, which keeps form architecture consistent across frameworks.
+5. The library is designed for production submit behavior: predictable pending state, rollback-safe optimistic UI, debounced persistence, and DevTools visibility. It reduces per-form complexity while keeping behavior explicit.
+
+## 4) GitHub Repo Description Options (5)
+1. Typed submit flows for React Hook Form: Zod mapping, optimistic UI, persistence, and DevTools.
+2. The missing layer between RHF and server submits, with typed actions and automatic field error mapping.
+3. Connect RHF to Next.js Server Actions or standalone submits with one consistent API.
+4. Server-backed React forms without glue code: typed flow, error mapping, optimistic rollback, persistence.
+5. Monorepo for hookform-action core, Next.js/standalone adapters, and DevTools.
+
+## 5) Headline Variations (5)
+1. React Hook Form Meets Typed Server Submits
+2. Write the Schema. Write the Action. Skip the Wiring.
+3. Typed Submit Flows for Real RHF Apps
+4. One Hook Between RHF and Server Mutations
+5. Keep React Hook Form. Remove Submit Plumbing.
+
+## 6) Release Announcement Variations (5)
+1. `hookform-action v4.0.3` is live: typed RHF submit flows with Zod mapping, optimistic UI, persistence, and DevTools.
+2. Released: `hookform-action v4.0.3`. Same RHF-first API, better server submit consistency.
+3. `hookform-action v4.0.3` ships typed form-server wiring so you can stop rewriting the same submit glue code.
+4. New release: `hookform-action v4.0.3` for predictable RHF submit pipelines across Next.js and standalone React apps.
+5. `hookform-action v4.0.3` is out. If you manually wire RHF + Zod + server submits, this package standardizes that flow.
+
+## 7) "What This Replaces" Messaging (5)
+1. Replaces manual `FormData` parsing and hand-written type casting.
+2. Replaces custom `fieldErrors -> setError` mapping code per form.
+3. Replaces per-form `useTransition` submit pending wiring.
+4. Replaces ad-hoc optimistic update and rollback logic.
+5. Replaces custom sessionStorage persistence code for wizard flows.
+
+## X / Twitter Post Templates (5)
+1. React Hook Form + server submits usually means repeated glue code. `hookform-action` gives typed submit flows, Zod error mapping, optimistic UI, persistence, and DevTools. `npm i hookform-action`
+2. We built `hookform-action` to remove repetitive RHF submit plumbing: FormData parsing, transition wiring, and field error mapping. Keep RHF, standardize the server flow.
+3. `hookform-action v4.0.3` is live. Typed RHF submit flows for Next.js Server Actions and standalone React apps. One API, less boilerplate, clearer behavior.
+4. If your RHF forms submit to a server, this is the integration layer: typed actions, Zod mapping, pending state, optimistic rollback, and persistence.
+5. `withZod` + `useActionForm`: schema once, typed flow through validation, submit, and response handling. That is the core idea behind `hookform-action`.
+
+## LinkedIn Post Template (1)
+Today we are shipping `hookform-action v4.0.3`.
+
+React Hook Form, Zod, and Server Actions are solid primitives. The repeated work is in the integration layer between them: submit wiring, error mapping, pending state, and recovery behavior.
+
+`hookform-action` standardizes that layer with typed submit flows, automatic Zod -> RHF field mapping, optimistic UI with rollback, multi-step persistence, and DevTools.
+
+It works with Next.js Server Actions and also with standalone React apps through the same API shape.
+
+If your team is rewriting form-server glue code in every feature, this release is for you.
+
+## Release Notes Snippets (5)
+1. This release strengthens the project positioning around typed submit flows for React Hook Form and server integrations.
+2. Messaging now emphasizes practical outcomes: less submit boilerplate, predictable pending state, and consistent field error mapping.
+3. Documentation copy is now aligned across README, docs home, and package descriptions for clearer onboarding.
+4. NPM metadata has been updated to surface Zod mapping, optimistic UI, persistence, and DevTools in a consistent way.
+5. A centralized messaging pack has been added to support launch posts, release notes, and changelog summaries.
+
+## Changelog Highlights (5)
+1. Refined core tagline to "typed submit flows for React Hook Form".
+2. Updated docs home messaging to match the current product scope and tone.
+3. Aligned package descriptions across `hookform-action`, `-standalone`, `-core`, and `-devtools`.
+4. Improved README wording to reinforce technical clarity over marketing phrasing.
+5. Added reusable copy blocks for GitHub, npm, X/Twitter, LinkedIn, release notes, and changelog highlights.