Lohnt sich dein eigenes TextExpander?

Build a personal replacement for TextExpander in an empty repository.
Use Swift 6, SwiftUI, AppKit where necessary, SQLite, and the macOS Keychain; do not offer alternative stacks.
The core loop is: build one focused macOS utility that expands local text snippets from abbreviations with forms and simple variables, exposes keyboard-first controls, and stores settings locally.
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 menu-bar app with a searchable command window and global hotkey.
Implement only the primary feature and one settings screen instead of a plugin platform.
Request permissions just in time and explain why each is needed before opening System Settings.
Store configuration locally, support export or import, and never capture unrelated user content.
Add launch-at-login, update-check opt-in, diagnostics export, and a complete uninstall note.
Write unit tests for transformation logic and one UI test for the core keyboard workflow.
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 third-party extension marketplace.
Deliberately leave out cloud accounts and cross-device sync.
Deliberately leave out broad automation that executes untrusted scripts.
Finish by running the tests and listing the exact commands used.