Record verified 0.2.1 publication and sync Homebrew formula

docs/PACKAGING.md

@@ -14,7 +14,7 @@ The Go version is declared in `go.mod`; CI uses that file. The release workflow
 
 For a released archive, download it and the matching `checksums.txt` from the same [GitHub release](https://github.com/KingPsychopath/raindrop-cli/releases). On Linux run `sha256sum --check checksums.txt --ignore-missing`; on macOS compare `shasum -a 256 YOUR_ARCHIVE` to that archive's entry before extracting it. Do not reuse another release's checksums.
 
-The [Homebrew formula](../packaging/homebrew/rdrop.rb) and `KingPsychopath/tap` use a tagged source archive and its verified SHA-256 checksum. The `head` option tracks main. Update the source URL and checksum together after each release tag exists; source archive checksums differ from native release archive checksums.
+The [published Homebrew formula](https://github.com/KingPsychopath/homebrew-tap/blob/main/Formula/rdrop.rb), mirrored in [packaging/homebrew/rdrop.rb](../packaging/homebrew/rdrop.rb), uses a tagged source archive and its verified SHA-256 checksum. The `head` option tracks main. Update the source URL and checksum together after each release tag exists; source archive checksums differ from native release archive checksums.
 
 ## npm packages
 

docs/VERIFICATION.md

@@ -4,7 +4,13 @@ The 2026-10-10 check used macOS arm64, Python 3.12.13, Ollama 0.40.2, `qwen3:4b`
 
 ## Released executables
 
-The v0.2.0 release is tagged at `c4c997e748655bfa9b615b3d3eb17ea9952cff40`. All 14 native/npm/plugin artifacts were downloaded and checked against the release's `checksums.txt`. All seven published npm versions have registry SHA-512 integrity matching the exact release tarballs. A fresh registry installation reported the release commit and 26 read-only tools. The exact tarballs also installed offline and completed a real MCP stdio handshake. The downloaded native executable also passed the complete three-step Qwen/Laya loop, dry-run and one fixture update described below. This checks package bootstrap and transport independently of model prose. The source archive has its own Homebrew checksum. The tap's source build and formula tests passed in CI and on the tested macOS arm64 host; the installed version is `0.2.0`.
+The v0.2.1 release is tagged at `eaf8d33fe88374c2a266291def3096737edc18a7`. All 14 native/npm/plugin artifacts passed their release SHA-256 checks. The downloaded macOS arm64 executable completed a real MCP stdio handshake with 26 read-only tools, then passed the three-step Qwen/Laya loop with two successful tool calls, dry-run and one fixture update. Existing tags and notes survived; no real Raindrop writes occurred. Homebrew source upgrade, strict formula audit and version/help tests passed locally, and the tap's source build/tests passed in CI. Its source archive SHA-256 is `dff61f02b2750565fc7b0092bbb1e6c58e142b51f6793574fbefe3e881d09fee`; the installed Homebrew version is `0.2.1`.
+
+All seven npm 0.2.1 versions have registry SHA-512 integrity matching the exact GitHub release tarballs. A fresh registry install reports the release commit and 26 read-only tools. The published `npx` command also completed a real stdio handshake with protocol version `2025-03-26`. These checks verify installation, package identity and transport; they do not test every client UI or evaluate model accuracy.
+
+The [MCP Registry publication](https://github.com/KingPsychopath/raindrop-cli/actions/runs/38056208690) succeeded using short-lived GitHub OIDC. Independent registry API readback confirmed active `io.github.KingPsychopath/raindrop-cli` version `0.2.1`, public title **rdrop for Raindrop.io**, npm package/version and local stdio transport. Downstream directories control their own indexing; this is a registry listing, not a hosted endpoint or client-directory approval. [Listing](https://registry.modelcontextprotocol.io/?q=io.github.KingPsychopath%2Fraindrop-cli).
+
+The earlier v0.2.0 release is tagged at `c4c997e748655bfa9b615b3d3eb17ea9952cff40`. All 14 native/npm/plugin artifacts were downloaded and checked against the release's `checksums.txt`. All seven published npm versions have registry SHA-512 integrity matching the exact release tarballs. A fresh registry installation reported the release commit and 26 read-only tools. The exact tarballs also installed offline and completed a real MCP stdio handshake. The downloaded native executable also passed the complete three-step Qwen/Laya loop, dry-run and one fixture update described below. This checks package bootstrap and transport independently of model prose. The source archive has its own Homebrew checksum. The tap's source build and formula tests passed in CI and on the tested macOS arm64 host; the installed version at that check was `0.2.0`.
 
 To repeat with the released macOS arm64 executable instead of a development build:
 

packaging/homebrew/rdrop.rb

@@ -1,8 +1,8 @@
 class Rdrop < Formula
-  desc "Find, review and organize Raindrop bookmarks from a shell or agent"
+  desc "Find and organize Raindrop.io bookmarks with reviewed plans"
   homepage "https://github.com/KingPsychopath/raindrop-cli"
-  url "https://github.com/KingPsychopath/raindrop-cli/archive/refs/tags/v0.2.0.tar.gz"
-  sha256 "2be3fe887073288141ddc185fa7f639bea143b2275d5f1650c10b0f164130818"
+  url "https://github.com/KingPsychopath/raindrop-cli/archive/refs/tags/v0.2.1.tar.gz"
+  sha256 "dff61f02b2750565fc7b0092bbb1e6c58e142b51f6793574fbefe3e881d09fee"
   license "MIT"
   head "https://github.com/KingPsychopath/raindrop-cli.git", branch: "main"