Should you build your own ProWritingAid?

Build a personal replacement for ProWritingAid in an empty repository.
Use Tauri 2, React, TypeScript, SQLite, and a small Rust filesystem layer; do not offer alternative stacks.
The core loop is: open local text or Markdown, run deep style reports, manuscript checks, and guided rewrite passes for long-form prose, show a diff, and save or export without uploading the document.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create a three-pane editor with source text, suggestion list, and accepted-result preview.
Implement deterministic checks for repeated words, sentence length, passive constructions, and typography.
Add an optional API-backed rewrite action that sends only the selected passage.
Show every change as an accept-or-reject diff and support undo.
Import and export .txt and .md while preserving headings and lists.
Persist user rules, ignored terms, and recent documents in SQLite.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a browser extension.
Deliberately leave out Office or Google Docs plugins.
Deliberately leave out collaborative editing and cloud sync.
Finish by running the tests and listing the exact commands used.