@hraness/message-like-me 0.8.20 → 0.8.22

package/CHANGELOG.md

@@ -1,23 +1,47 @@
 # Changelog
 
-## 0.8.20 (2026-09-24)
+Each version's section is copied onto its GitHub Release page: a summary
+paragraph, then one bullet per change. Write the section in the version bump
+pull request.
+
+## 0.8.22 - 2026-09-28
+
+The Textbutler menu companion is rebuilt around one status line and ten top-level rows, the terminal gains a guided macOS access step, and the `messagelikeme` history CLI drops its banner and names the app in access errors.
+
+- Bind legacy installation to the exact public `@hraness/message-like-me@0.8.22` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
+- Rebuild the menu companion around a status line and ten top-level rows: failed actions surface as a ⚠︎ row that clears, Quit actually ends the menu process, and the menu can launch through the locally built TextButler.app (behind `HRANESS_LOCAL_APP`).
+- Add a guided "Give Textbutler access" step to the terminal walkthrough and detect existing Ghostget and Bun installs in the connect step, using the shared desktop-foundation 0.8 permission copy, audience detection, and symbols.
+- Add owner-set contact labels: `textbutler contacts label <contact> <name>` renames a chat for commands instead of a raw number; labels are display metadata only and never touch routing, grants, or reply settings.
+- Adopt support-foundation 0.6.0: agent support verbs move to `textbutler help advanced` and every root help keeps one support line.
+- Reply loop: the acknowledgement now overlaps composition, polls yield to sends, due runs start at debounce expiry, drain replays deduplicate, and self-chat acks correlate by relatedMessageId; Ghostget pins 0.18.43 for the native iMessage setup.
+- `messagelikeme` CLI: root help no longer prints the banner, and Messages/Contacts permission failures name the app and deep-link the Full Disk Access pane.
+- Refresh the Textbutler site: quiet landing with real terminal proof, design-kit v0.23.0, and copy checked against source.
+
+## 0.8.21 - 2026-09-24
+
+A LaunchAgent service installed by 0.8.19 now verifies and uninstalls under this release. In 0.8.20 it failed verification, because 0.8.19 had changed the service template without changing the receipt schema.
+
+- Bind legacy installation to the exact public `@hraness/message-like-me@0.8.21` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
+- Complete the LaunchAgent contract fix: receipts written before schema 4 recorded an artifact now verify the installed service definition against every exact render a shipped template produced (the template changed `ProcessType` within the same receipt schema), so a service installed by the previous release verifies and uninstalls under this binary. When advancing an absent service's older receipt, the rewritten plist lands before the receipt so an interruption still verifies against the older contract's historical renders.
+
+## 0.8.20 - 2026-09-24
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.20` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Make the LaunchAgent receipt record the exact rendered plist it installed (schema version 4): installation verification now compares the on-disk service definition with the recorded artifact instead of re-rendering it under the current binary, so a launch-template change can no longer make a newer `textbutler` unable to verify or uninstall a service an older binary installed. Older receipts keep verifying against their historical template bytes, `daemon install` refuses to mutate an owned service on an earlier contract until it is removed and reinstalled, and an absent service's older receipt advances to the recorded-artifact contract in place.
 
-## 0.8.19 (2026-09-23)
+## 0.8.19 - 2026-09-23
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.19` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Run the Textbutler daemon at standard launchd priority instead of `Background`: on a loaded host the previous setting starved the messaging child's spawn-synchronous startup, so automation initialization could outlast its request deadline and cycle through recovery without ever answering inbound messages.
 - Make the automation child's initialize watchdog progress-aware: it re-arms only while the recorded process group proves CPU progress, so a slowly starting child is adopted instead of orphaned while a genuinely frozen child still dies on the original deadline under the same hard cap.
 - Escalate failed-child cleanup to the recorded process group whenever that group may be alive rather than only while the direct child process entry is absent, so same-group helpers left behind by a closed child meet SIGKILL instead of surviving as orphans.
 
-## 0.8.18 (2026-09-23)
+## 0.8.18 - 2026-09-23
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.18` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Let the local TextButler app build against a persistent owner signing identity with `--signing-identity`, so macOS permission grants such as Full Disk Access and Apple Events bind to a stable certificate instead of each ad-hoc rebuild's changing code hash. The managed app receipt records the signing class explicitly (`ad-hoc` or `certificate`), treats a signing-class change as a new permission target that requires reinstall, and rejects unreviewed signing classes at startup. Ad-hoc signing remains the default for development builds.
 
-## 0.8.17 (2026-09-23)
+## 0.8.17 - 2026-09-23
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.17` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Add isolated per-contact habitats: each enrolled contact gets a private workspace whose bounded evolution loop proposes, evaluates and promotes reply-guidance updates through the admitted subscription driver, with journaled budgets and reservations.
@@ -26,28 +50,28 @@
 - Keep the automatic loop honest under load: inbound events drain in batches, a degraded transport keeps pending work and only reports attention after repeated failures, reactions and echoes can no longer erase or trigger pending replies, and a continuous inbound stream is answered within a bounded debounce instead of starving.
 - Accept bare-object driver output, map silent suggestions to an explicit outcome, supervise the messaging transport child with custody-verified recovery, keep injected contact-workspace guidance out of trusted policy, and reseal the reviewed XCB composition receipt over the current sources.
 
-## 0.8.16 (2026-09-22)
+## 0.8.16 - 2026-09-22
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.16` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Treat an owner text naming the butler in an enrolled contact conversation as a deliberate invocation: it now queues a disclosed reply through the same grant, rate-limit, capability, and freshness checks instead of marking the thread answered. Only a strictly newer owner message suppresses it as a takeover, and invocations no longer count as owner presence, so they cannot cool the butler down or swallow the next inbound. `inbox` and `replies suggest` report the same owner run the loop sees.
 
-## 0.8.15 (2026-09-21)
+## 0.8.15 - 2026-09-21
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.15` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Keep an admitted automatic reply alive while it is drafted: the post-composition recheck measures event age from admission instead of the live clock, so a slow provider call can no longer cancel a live reply as stale, while owner activity, superseded events, sync, and settings still cancel it.
 - Treat the butler's own echoed messages as loop traffic only: they no longer cancel an in-flight reply or clear a newer pending inbound, and echo-only traffic cannot supersede a live reply.
 
-## 0.8.14 (2026-09-21)
+## 0.8.14 - 2026-09-21
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.14` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Let the owner mark a conversation as their own address with `contacts self CONTACT on|off`. iMessage self chats deliver each owner text as an inbound copy plus an outgoing echo; the echo is no longer mistaken for the owner's answer, and the butler's own wrapped sends echoing back inbound cannot trigger another reply. Marking requires a visible butler wrap so the echo signal cannot be cleared away, and stored contacts default off.
 
-## 0.8.13 (2026-09-21)
+## 0.8.13 - 2026-09-21
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.13` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Accept the renamed XCB account identity fields (`name` plus optional `email`, with `label` retained as an alias) in subscription capability discovery, so a verified Textbutler bundle works against both pre- and post-rename XCB runtimes.
 
-## 0.8.12 (2026-09-21)
+## 0.8.12 - 2026-09-21
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.12` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Add the native TextButler desktop app with scoped guided setup, a menu bar companion, and per-contact review-first controls. New installations start paused and automatic replies stay off per contact.
@@ -56,13 +80,13 @@
 - Restore native iMessage discovery and history through the reviewed Ghostget connector, including literal modern coordinates, and provision the pinned private transport during setup so a reviewed connector upgrade cannot leave a stale helper.
 - Refresh the informational site's identity and keep it informational only; it receives no messages or contact data.
 
-## 0.8.11 (2026-09-16)
+## 0.8.11 - 2026-09-16
 
 - Bind legacy installation to the exact public `@hraness/message-like-me@0.8.11` npm package, with the same reviewed bytes mirrored in the immutable GitHub Release. This does not install the Textbutler menu companion or enable automatic replies.
 - Add optional development support to CLI discovery, the Message Like Me skill, the Textbutler menu, and the public website. Task output and private message boundaries stay unchanged.
 - Bundle the shared local support protocol separately from all public SDK graphs. Paid support remains a human choice; no newsletter is offered for this product.
 
-## 0.8.10 (2026-09-13)
+## 0.8.10 - 2026-09-13
 
 - Show a compact ASCII robot before interactive root help. Piped output,
   machine-readable commands, version output, and command help stay unchanged.
@@ -70,20 +94,20 @@
   Textbutler app remains in development; this package does not enable replies.
 - Route legacy installation to the exact public `@hraness/message-like-me@0.8.10` npm package after release admission, with the same reviewed bytes mirrored in the immutable GitHub Release.
 
-## 0.8.9 (2026-09-10)
+## 0.8.9 - 2026-09-10
 
 - Use the shared Paper theme on the informational website, with warm neutral surfaces, compact Nebula Sans headings, and a blue action color in light and dark appearances.
 - Verify the theme snapshot's immutable source and file digests independently of the existing component package versions.
 - Route installation to the exact public `@hraness/message-like-me@0.8.9` npm package after release admission, with the same reviewed bytes mirrored in the immutable GitHub Release. CLI behavior and private data boundaries remain unchanged.
 
-## 0.8.8 (2026-09-09)
+## 0.8.8 - 2026-09-09
 
 - Route installation to the exact public `@hraness/message-like-me@0.8.8` npm package after release admission, with the same reviewed bytes in the immutable GitHub Release.
 - Use Ghostget in current CLI options, SDK names, source guidance, and the public site. Keep the original Wrench options and exports as compatibility aliases.
 - Accept `ghostgetContext` when preparing a handoff while preserving the existing serialized handoff, receipt, contract hashes, and local history. Reject simultaneous context aliases.
 - Point Ghostget setup to its exact canonical GitHub Release archive.
 
-## 0.8.7 (2026-09-09)
+## 0.8.7 - 2026-09-09
 
 - Make the exact public `@hraness/message-like-me@0.8.7` npm package the
   supported default install, with the same reviewed bytes mirrored in the
@@ -97,7 +121,7 @@
 - Strengthen the development Effect architecture checker. Public protocols,
   the source readers, and command behavior are unchanged.
 
-## 0.8.6 (2026-09-07)
+## 0.8.6 - 2026-09-07
 
 - Make the exact public `@hraness/message-like-me@0.8.6` npm package the
   supported default install, with the same reviewed bytes mirrored in the
@@ -113,7 +137,7 @@
 - Strengthen the development Effect checker with generator alias and wrapper
   regressions. Public protocol graphs and local-only behavior remain unchanged.
 
-## 0.8.5 (2026-09-06)
+## 0.8.5 - 2026-09-06
 
 - Make the exact public `@hraness/message-like-me@0.8.5` npm package the
   supported default install, with the same reviewed bytes mirrored in the
@@ -130,7 +154,7 @@
 - Bound private JSON read allocation to the admitted file size, including
   short reads and files that grow during inspection.
 
-## 0.8.4 (2026-09-06)
+## 0.8.4 - 2026-09-06
 
 - Make the exact public `@hraness/message-like-me@0.8.4` npm package the
   supported default install, with the same reviewed bytes mirrored in the
@@ -145,7 +169,7 @@
   skip-aware condition, and a terminal admission fails unless verification and
   provider admission both succeeded.
 
-## 0.8.3 (2026-09-06)
+## 0.8.3 - 2026-09-06
 
 - Let Beeper users bring a finished private Wrench bundle into the same local
   evidence corpus as Apple Messages and the other supported sources. The exact

package/README.md

@@ -2,31 +2,38 @@
 
 [![skills.sh](https://skills.sh/b/hraness/message-like-me)](https://skills.sh/hraness/message-like-me)
 
-Textbutler is a local message assistant for macOS. Its guided terminal and menu
-bar help you connect selected iMessage, WhatsApp and Beeper conversations, see
-what needs an answer, and review replies before sending them.
-
-**Current status: source pilot.** Messaging setup, conversation selection,
-private contact memory, inbox review and replies you write yourself are
-implemented. AI replies require a verified Textbutler bundle with reviewed
-composition admission and connect to a separately installed
-[xcb](https://github.com/hraness/xcb) native runtime with an explicit subscription
-account and model. Textbutler is an MIT-licensed reference application for xcb's
-zero-tool generation API; xcb keeps provider credentials and custody. Account
-setup, current runtime admission and live verification on your chosen messaging
-account and recipient are required before relying on automatic replies. See the
-[subscription guide](docs/textbutler/native-subscription.md).
+Textbutler is an AI butler for the iMessage, WhatsApp, and Beeper chats you
+choose on your Mac. Turn it on for one person, and it replies as a clearly
+marked assistant that knows your history with them.
+
+**Status:** In development. Textbutler runs from source on a Mac; there is no
+app to download and no published Textbutler package. Without an AI account you
+can connect iMessage, WhatsApp, and Beeper through Ghostget, check your inbox,
+and send replies you write yourself. AI replies also need a local build of
+Textbutler and a Claude Code, Codex, or Devin subscription connected through
+[xcb](https://github.com/hraness/xcb). Automatic replies have worked end to end
+over iMessage in our testing. Try them on your own account,
+especially over WhatsApp or Beeper, before you rely on them.
 
 Start with the [guided setup](docs/textbutler/getting-started.md) and
 [messaging app support](docs/textbutler/messaging-apps.md). Beeper can connect
-apps such as Signal, Telegram and Instagram through Ghostget's current text
-automation adapter. Its linked apps and account permissions determine what is
-available. The [architecture](docs/textbutler/architecture.md) records the
-runtime boundaries and remaining qualification work.
-
-Agents can use the [JSON CLI](docs/textbutler/agent-cli.md) to read and summarize
-one conversation, prepare text or media drafts, and send an explicitly
-authorized message. Each connection reports its available actions.
+apps such as Signal, Telegram, and Instagram through Ghostget, for text only;
+its linked apps and account permissions decide what is available. The
+[subscription guide](docs/textbutler/native-subscription.md) covers AI replies,
+and the [architecture](docs/textbutler/architecture.md) describes how the parts
+fit together and what still needs live testing.
+
+Agents can use the [JSON CLI](docs/textbutler/agent-cli.md) to list
+conversations, read and summarize history, prepare text or media drafts, and
+send an explicitly authorized message, using the same staged actions the butler
+uses on its own. Each connection reports its available actions.
+
+Textbutler keeps each contact's context in files you can read and edit, marks
+its own replies by default, and answers only after you turn a contact on and
+resume the butler: the design every Hraness project shares. [The thread through
+hraness](https://hraness.com/writing/the-thread-through-hraness) follows that
+design across the projects, and the [ALGAL
+vision](https://algal.computer/docs/vision/) states the bet behind it.
 
 ## Open the guided terminal
 
@@ -45,12 +52,16 @@ contacts have automatic replies off. Setup and conversation selection never
 send a message.
 
 For AI replies, build and install with `bun run textbutler:install`, then run
-`~/.local/bin/textbutler`. The builder requires the reviewed composition receipt
-to match current source bytes and both contact capability profiles. A source
-daemon has no embedded composition admission and cannot enable subscription
-inference. Source commands remain useful for setup and manual reply controls.
-
-Textbutler's source is MIT licensed and its new packages remain unpublished.
+`~/.local/bin/textbutler`. The installer refuses to build unless the source
+files it checks and both contact permission profiles match the reviewed record
+in `qualification/`. Running from source never writes AI replies; source
+commands handle setup and the replies you write yourself. xcb keeps your AI
+sign-in, and the model gets no tools of its own. Before you rely on automatic
+replies, finish account setup and test with a recipient you trust on the
+messaging account you'll use.
+
+Textbutler's source is MIT licensed, and it also serves as an example app for
+developers building on xcb's generation API. Its new packages are unpublished.
 The published Message Like Me package documented below installs the legacy
 history tools, not Textbutler. The website at
 [textbutler.app](https://textbutler.app) is informational and receives no private
@@ -58,9 +69,9 @@ messages or contact folders.
 
 ## Run the Textbutler menu companion
 
-The native companion downloads and verifies a pinned prebuilt
-desktop-foundation runner on first start. No local Rust build is needed. Start
-it from the terminal's **Menu bar companion** action or run:
+On first start, the menu bar companion downloads a prebuilt desktop-foundation
+runner and checks it against a pinned hash, so you don't need a local Rust
+build. Start it from the terminal's **Menu bar companion** action or run:
 
 ```sh
 bun run textbutler menubar start
@@ -120,9 +131,10 @@ sends plain text. The review shows the actual outgoing text. The send journal
 retains provider acceptance IDs when available; see the messaging guide for
 connection-specific attribution and delivery limits.
 
-Automatic replies remain a separate choice: they require a qualified agent,
-a ready messaging connection, explicit contact activation and global resume.
-Keep them paused until those requirements and the relevant live checks pass.
+Automatic replies are a separate step. They need an AI account that passes
+`providers check`, a working messaging connection, the contact turned on with
+`contacts enable`, and the butler resumed with `resume`. Leave them paused until
+all of that works and you've tested with a real recipient.
 
 ## Legacy Message Like Me history tools
 
@@ -167,7 +179,7 @@ Message Like Me requires Bun 1.3.14 or newer. Install the exact public npm
 package, then install both bundled Agent Skills:
 
 ```sh
-bun add --global @hraness/message-like-me@0.8.20
+bun add --global @hraness/message-like-me@0.8.22
 messagelikeme skill install
 ```
 
@@ -909,8 +921,8 @@ Read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a change.
 The canonical repository is
 [`hraness/textbutler`](https://github.com/hraness/textbutler).
 The informational project page is
-[`messagelikeme.com`](https://messagelikeme.com). The CLI does not connect to
-the site, and the site never receives message or contact data.
+[textbutler.app](https://textbutler.app). The CLI does not connect to the site,
+and the site never receives message or contact data.
 
 ## License
 

package/SECURITY.md

@@ -1,7 +1,7 @@
 # Security
 
 Report suspected vulnerabilities privately through
-[GitHub Security Advisories](https://github.com/hraness/message-like-me/security/advisories/new).
+[GitHub Security Advisories](https://github.com/hraness/textbutler/security/advisories/new).
 Do not open a public issue containing a message, handle, contact name, group
 title, attachment, local path, profile, study or Ensoul packet, installation key, or
 database detail that could identify a person.

package/dist/cli.js

@@ -15453,7 +15453,7 @@ function commandFailure(cause3) {
 function translateIMessageError(error) {
   const code = error.code;
   if (code === "EACCES" || code === "EPERM" || code === "permission") {
-    throw new CliError("permission", "Messages data is not readable. Grant Full Disk Access to this terminal or agent host, then retry.", { cause: error });
+    throw new CliError("permission", "Message Like Me can't read your Messages data: macOS access is off for the app running this command. Turn on your terminal or agent app in System Settings \u203A Privacy & Security \u203A Full Disk Access (x-apple.systempreferences:com.apple.preference.security?Privacy_AllFiles), then retry.", { cause: error });
   }
   if (code === "ENOENT") {
     throw new CliError("not-found", "The selected Messages database does not exist", { cause: error });
@@ -15463,7 +15463,7 @@ function translateIMessageError(error) {
 function translateContactsError(error) {
   const code = error.code;
   if (code === "EACCES" || code === "EPERM") {
-    throw new CliError("permission", "Contacts data is not readable. Grant Full Disk Access to this terminal or agent host, then retry.", { cause: error });
+    throw new CliError("permission", "Message Like Me can't read your Contacts data: macOS access is off for the app running this command. Turn on your terminal or agent app in System Settings \u203A Privacy & Security \u203A Full Disk Access (x-apple.systempreferences:com.apple.preference.security?Privacy_AllFiles), then retry.", { cause: error });
   }
   if (code === "ENOENT") {
     throw new CliError("not-found", "The selected AddressBook source does not exist", { cause: error });
@@ -25088,14 +25088,14 @@ function commandPlatformLive(io, cleanupFailure) {
 import { isAbsolute as isAbsolute7, resolve as resolve8 } from "path";
 
 // src/version.ts
-var MESSAGE_LIKE_ME_VERSION = "0.8.20";
+var MESSAGE_LIKE_ME_VERSION = "0.8.22";
 
 // src/command-input.ts
 var HELP = `Message Like Me ${MESSAGE_LIKE_ME_VERSION}
 
 Usage:
-  messagelikeme support [protocol --json|offer --json|shown ID|release ID|dismiss|snooze|enable|status --json]
-    Optional support; agents use support protocol --json at closeout.
+  messagelikeme support [--json]
+    Optional ways to support Message Like Me.
   messagelikeme [--data-dir PATH] init [--json]
   messagelikeme [--data-dir PATH] ingest imessage [--database PATH] [--json]
   messagelikeme [--data-dir PATH] ingest bundle --input ABS_PATH
@@ -25139,6 +25139,8 @@ Message Like Me reads caller-owned macOS Messages, official X archives,
 optional Contacts data, and strict private local message bundles, then stores
 private analysis locally. It has no network, account, AI-provider, or
 message-sending surface.
+
+Optional support: messagelikeme support \xB7 Turn off: HRANESS_SUPPORT=off
 `;
 function metricOptions(parsed) {
   return {
@@ -27844,19 +27846,6 @@ function runClosed(effect2) {
   return exports_Effect.runPromise(effect2);
 }
 
-// src/cli-intro.ts
-function terminalIntro(terminal) {
-  if (terminal.isTTY !== true || terminal.term === "dumb" || (terminal.columns ?? 80) < 48)
-    return "";
-  return `   _|_
- .----- .   textbutler
- | o o |   A little help in your conversations.
- | === |
- '-----'
-
-`;
-}
-
 // src/io.ts
 var processIo = {
   stdout: (text3) => process.stdout.write(text3),
@@ -27880,12 +27869,7 @@ async function main(argv, io = processIo, supportEnv) {
   try {
     if (argv[0] === "support")
       return await runProductSupportCommand(argv.slice(1), io, supportEnv === undefined ? {} : { env: supportEnv });
-    const rootHelp = argv.length === 0 || argv.length === 1 && argv[0] === "--help";
-    const output = rootHelp && io === processIo ? {
-      ...io,
-      stdout: (text3) => io.stdout((text3 === HELP ? terminalIntro({ isTTY: process.stdout.isTTY, columns: process.stdout.columns, term: process.env.TERM }) : "") + text3)
-    } : io;
-    await runCommand(argv, output);
+    await runCommand(argv, io);
     return 0;
   } catch (error) {
     io.stderr(`${errorMessage(error)}