Can AI replace Yaps?

Build the closest honest single-platform subset of Yaps in an empty repository; do not claim it replaces the full product.
Use Swift 6, SwiftUI with AppKit, AVFoundation, and a locally installed whisper.cpp CLI; do not offer alternative stacks.
Target macOS 14 or later and make it a menu-bar accessory app with no Dock icon.
State in the app and README that this subset covers dictation, Markdown notes, and read-aloud only.
Provide one documented command that builds and launches a debug build from a clean clone.
The core loop is: hold a global shortcut, record the microphone, transcribe locally, and insert clean text at the active cursor.
Default to Control-Space, allow remapping, and do not claim to replace or reliably intercept the Fn key.
Capture 16 kHz mono WAV with AVAudioEngine and show a compact recording and transcribing status pill.
On release, invoke whisper.cpp with a configurable model path and no network request.
Insert with the pasteboard plus Cmd-V, restore the previous clipboard, and leave the text copied when direct insertion cannot be verified.
Keep the last 20 transcripts locally with timestamps, copy, retry, delete, and save-as-note actions.
Save notes as plain Markdown under ~/Documents/YapsDIY and never hide content in an opaque database.
Add a small notes window with create, edit, full-text filename/body search, and a recent-notes list.
Add read-aloud for the current note using NSSpeechSynthesizer with voice, rate, pause, resume, and stop controls.
Add a custom vocabulary text file whose terms are passed to whisper.cpp as an initial prompt.
Keep raw audio only when the user enables it; otherwise delete it after a successful transcript.
Store settings in Application Support and make the Markdown vault easy to relocate and back up.
Handle denied microphone or Accessibility permission with clear instructions and a retry button.
Include visible idle, recording, transcribing, success, and recoverable error states.
Add focused tests for settings, history limits, vault file safety, clipboard restoration, and transcription command construction.
Add one smoke test that injects a fixture WAV and proves a transcript becomes a Markdown note.
Create a README covering setup, model download, permissions, data locations, privacy, backup, and limitations.
Do not add accounts, billing, telemetry, analytics, cloud sync, or hidden network calls.
Deliberately leave out Windows, Linux, Android, iOS, mobile keyboards, meetings, diarization, captions, voice cloning, media tools, browser capture, and sync.
Finish by running the tests and build, fixing failures, and listing the exact commands used.