@hraness/message-like-me 0.8.0 → 0.8.1

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## 0.8.1
+
+- Verify the Beeper bundle boundary at Wrench v0.16.5 and adapter
+  `beeper-local@2.3.0`: 32 reviewed operations comprise 27 through the pinned
+  CLI 0.6.2 executable and five fixed Desktop reads. The tagged source package
+  declaration of 0.6.1 is provenance only; export remains internal and bounded,
+  and Message Like Me owns no Beeper operation, credential, or live session.
+- Make the exact public `@hraness/message-like-me@0.8.1` npm package the
+  supported default install, with the same reviewed bytes mirrored in the
+  immutable GitHub Release.
+- Document that the Wrench v0.16.5 and official Wacli v0.15.0 WhatsApp
+  producer omits reaction-shaped rows and reports `reaction-state-unproven`
+  when current active or removed state cannot be established.
+- Keep the v2 reaction artifact and strict parser for proven records while
+  treating an empty artifact from this producer as unobservable reaction
+  behavior, not evidence that no reactions occurred. Native WhatsApp overlap
+  therefore cannot reconcile reaction state from this producer.
+- Give each supported source a distinct decorative SVG mark, preserve those
+  marks in forced-colors mode, and point the Beeper MCP note to Beeper's
+  official built-in server documentation.
+
 ## 0.8.0
 
 - Add `ensoul prepare` as an offline, bounded source adapter for the owner or

package/README.md

@@ -1,46 +1,43 @@
 # Message Like Me
 
+[![skills.sh](https://skills.sh/b/hraness/message-like-me)](https://skills.sh/hraness/message-like-me)
+
 **A local-first CLI and Agent Skill for studying private messaging history and
 drafting messages that sound like you.**
 
-Message Like Me turns private local messaging history into deterministic
-conversation metrics, bounded study packets, reusable style profiles, and
-privacy-bounded evidence packets for the Ensoul person-model workflow. It
-reads native iMessage history, caller-owned X data archives, and strict local
-source bundles, including multi-account Beeper and native WhatsApp exports
-produced through Wrench. Its copied Message Like Me and Ensoul Agent Skills
-teach Codex, Claude, and other coding agents how to interpret those local
-artifacts, build revisable evidence-led person models, and draft unsent replies
-in your voice.
-
-The CLI has no model integration. It does not authenticate with a product
-account, invoke Wrench, Beeper, Wacli, or WhatsApp, send messages, or operate
-Messages. An agent you already run may use the installed skill for semantic
-analysis and drafting; opening a study or Ensoul packet exposes its bounded
-excerpts to that agent environment.
-
-This is an evidence layer for relationship-aware drafting. It does not train a
-model, represent your identity, infer your beliefs, or claim that a draft is
-what you would have written. Your current meaning, facts, and intent outrank
+Message Like Me turns caller-owned messaging history into deterministic local
+metrics, bounded evidence packets, reusable style profiles, and unsent drafts.
+The CLI owns ingestion, storage, measurement, and export. Its copied Message
+Like Me and Ensoul Agent Skills teach Codex, Claude, and other coding agents how
+to interpret those artifacts through the agent environment you already use.
+
+The result is an inspectable evidence layer for relationship-aware drafting,
+not a model of your identity. Your current meaning, facts, and intent outrank
 historical style.
 
-## Supported sources
+## Why Message Like Me
 
-| Source | What Message Like Me reads | Boundary |
-| --- | --- | --- |
-| Apple Messages | The current macOS user's native `chat.db` history | Read-only ingestion from an ownership-checked stable local copy; Messages is never operated or changed. |
-| X data archive | Direct-message history in a caller-owned archive ZIP | X Chat is not included; the importer does not contact X, extract the archive, or download media. |
-| Beeper via Wrench | A bounded local bundle produced by verified Wrench v0.16.1 with Beeper CLI 0.6.2 | Message Like Me reads the finished bundle; it receives no Beeper credential, invokes no Wrench or Beeper operation, and sends nothing. |
-| WhatsApp via Wrench | A one-account native bundle produced by Wrench v0.16.3 with official Wacli 0.15.0 | Message Like Me verifies the finished bundle; Wrench alone owns Wacli, linked-device authentication, synchronization, and provider operations. |
-| macOS Contacts | Optional names and exact email or phone handles from AddressBook | Label enrichment only; Contacts is not a messaging-history source and is never changed. |
+- **Separate evidence from interpretation.** The CLI produces deterministic
+  metrics and versioned packets without a model integration. Semantic analysis
+  happens only when you deliberately open an artifact in your own agent
+  environment.
+- **Study each relationship in context.** Outgoing messages supply style
+  evidence; incoming messages supply the response context. Tempo, sessions,
+  bubble shape, replies, and prose remain attributable to their source.
+- **Keep private history bounded.** Read-only import uses stable local copies,
+  ordinary views omit bodies and private labels, and body-bearing exports go
+  only to explicit owner-selected paths.
+- **Stop at an inspectable draft.** The installed skill can help draft text,
+  but Message Like Me never authenticates with a messaging provider, operates a
+  messaging app, or sends, reacts to, or schedules a message.
 
-## Install
+## Install and first run
 
-Message Like Me requires Bun 1.3.14 or newer. Install the immutable public
-release from GitHub, then install both bundled Agent Skills:
+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 github:hraness/message-like-me#v0.8.0
+bun add --global @hraness/message-like-me@0.8.1
 messagelikeme skill install
 ```
 
@@ -56,18 +53,60 @@ messagelikeme skill install --target agents --scope project
 messagelikeme skill path
 ```
 
-Message Like Me is distributed directly through GitHub and is not published to
-npm.
+The npm tarball and the immutable GitHub Release artifact are the same reviewed
+bytes. Neither distribution includes private messages, contacts, profiles,
+packets, drafts, or a network-backed runtime.
 
-## Start with private local history
-
-Initialize the private data store and inspect its location:
+Initialize an empty private store, then inspect it without reading any messaging
+source:
 
 ```sh
 messagelikeme init
 messagelikeme doctor --json
 ```
 
+The JSON response reports the initialized state, exact local paths, and store
+integrity checks. This is the shortest complete product check; no message body,
+contact, account, or provider credential is involved.
+
+The first proof is intentionally data-free. It shows where Message Like Me will
+work and whether its private store is healthy before you choose a source or
+open evidence in an agent environment.
+
+## Three deliberate interfaces
+
+| Surface | What it owns | First useful action |
+| --- | --- | --- |
+| CLI | Read-only ingestion, deterministic measurement, private artifacts, validation, and redacted machine-readable output | `messagelikeme doctor --json` |
+| Agent Skill | Evidence-calibrated interpretation and unsent drafting inside the agent environment you already chose | Invoke `$message-like-me` after preparing an explicit bounded packet |
+| TypeScript library | Versioned public types, strict bundle parsers, canonical JSON, digest helpers, and pure packet builders | Import from `@hraness/message-like-me` or a versioned subpath |
+
+The artifact is the seam between these surfaces. Deterministic code produces
+and validates it; an authorized agent may interpret it; typed consumers can
+verify it. Importing the library does not inspect a source, open a private
+packet, access a network, or start the CLI.
+
+## What becomes observable
+
+After you add a source, ordinary commands expose pseudonymous contacts, source
+health, conversation counts, sessions, response tempo, bubble sequences,
+reactions, and explicit-reply coverage. Study and Ensoul commands can then write
+bounded, body-bearing packets to paths you name. Profiles retain the exact
+corpus revision and packet digest they came from, so stale evidence fails
+visibly instead of being treated as current.
+
+## Supported sources
+
+| Source | What Message Like Me reads | Boundary |
+| --- | --- | --- |
+| Apple Messages | The current macOS user's native `chat.db` history | Read-only ingestion from an ownership-checked stable local copy; Messages is never operated or changed. |
+| X data archive | Direct-message history in a caller-owned archive ZIP | X Chat is not included; the importer does not contact X, extract the archive, or download media. |
+| Beeper via Wrench | A bounded local bundle produced by verified Wrench v0.16.5 with Beeper adapter 2.3.0 and executable runtime 0.6.2 | Message Like Me owns zero Beeper operations, credentials, or live sessions; it reads the finished bundle, never sends, and does not claim complete history. |
+| WhatsApp via Wrench | A one-account native bundle produced by Wrench v0.16.5 with official Wacli 0.15.0 | Reaction-shaped rows are omitted with `reaction-state-unproven` when current state cannot be proved. Message Like Me verifies the finished bundle and never operates WhatsApp. |
+| macOS Contacts | Optional names and exact email or phone handles from AddressBook | Label enrichment only; Contacts is not a messaging-history source and is never changed. |
+
+## Add private local history
+
 On macOS, the default store is:
 
 ```text
@@ -142,12 +181,12 @@ same or a later archive preserves proven deduplication; archive absence does not
 delete retained history.
 
 To study accounts connected through Beeper, install the currently verified
-[`@hraness/wrench@0.16.1`](https://www.npmjs.com/package/@hraness/wrench/v/0.16.1)
+[`@hraness/wrench@0.16.5`](https://www.npmjs.com/package/@hraness/wrench/v/0.16.5)
 package from npm, then use Wrench to create a new private Message Like Me
 bundle:
 
 ```sh
-bun add --global @hraness/wrench@0.16.1
+bun add --global @hraness/wrench@0.16.5
 wrench beeper export-message-like-me \
   --auth <beeper-auth-id> \
   --output /absolute/private/path/beeper-bundle \
@@ -156,22 +195,32 @@ wrench beeper export-message-like-me \
 
 The optional `--limit-chats`, `--limit-messages`, and `--max-participants`
 flags lower the export bounds. The output path must be a normalized absolute
-path to a directory that does not already exist. Wrench v0.16.1 calls the
-pinned [official Beeper CLI 0.6.2 release](https://github.com/beeper/cli/releases/tag/v0%2E6%2E2)
-directly. It enumerates
+path to a directory that does not already exist. Wrench v0.16.5 adapter
+`beeper-local@2.3.0` exposes 32 reviewed Beeper operations: 27 use the pinned
+CLI and 5 use fixed Desktop loopback reads. Message Like Me owns none of
+those operations. The bundle command enters Wrench's separate internal bounded
+export, which fixes the raw export arguments, excludes attachments, and
+preserves explicit incomplete-coverage evidence instead of claiming full
+history.
+
+Wrench calls the pinned
+[official Beeper CLI 0.6.2 release](https://github.com/beeper/cli/releases/tag/v0%2E6%2E2)
+directly. The exact executable reports version `0.6.2`; the tagged source file
+`packages/cli/package.json` declares `0.6.1`. That source value is provenance
+only and never overrides the executable runtime identity. Wrench enumerates
 the connected account realm, invokes `export --no-attachments` once per
 account in deterministic order, and reports the account ordinal, elapsed-time
 heartbeats, and cumulative validated chat and message counts on stderr. It
 retains each private raw shard until it can atomically publish the complete
 mode-`0700` seven-file bundle with mode-`0600` files.
 
-The export does not use the separate
-[Beeper Desktop API MCP project](https://github.com/beeper/desktop-api-mcp).
-The CLI path supplies the bounded account snapshots and local files needed for
-hash validation, deterministic conversion, crash recovery, and atomic
-publication. Provider URLs and credentials are excluded. Message Like Me does
-not receive the Beeper credential, start Wrench, invoke a Beeper operation, or
-send a message.
+Beeper Desktop also includes a
+[built-in MCP server](https://developers.beeper.com/desktop-api/mcp/), but this
+export path does not use it. The pinned CLI path supplies the bounded account
+snapshots and local files needed for hash validation, deterministic conversion,
+crash recovery, and atomic publication. Provider URLs and credentials are
+excluded. Message Like Me does not receive the Beeper credential or live
+session, start Wrench, invoke a Beeper operation, or send a message.
 
 Ingest the finished directory, then inspect its redacted source health:
 
@@ -190,7 +239,7 @@ iMessage and prior bundle sources remain alongside it.
 The interchange, integrity, identity, and reimport laws are in the
 [version-one local message bundle contract](docs/local-message-bundle-v1.md).
 Message Like Me accepts bundle schema `1` with source ID `beeper-local` and
-source-transform version `1.1.0`. Wrench v0.16.1 is the currently verified
+source-transform version `1.1.0`. Wrench v0.16.5 is the currently verified
 producer. Compatibility is determined by those exact manifest coordinates,
 not by an open-ended Wrench package range.
 
@@ -201,11 +250,11 @@ reappearance restores it. Older snapshots cannot overwrite newer state. Use
 `sources show <source-id> --private --json` only when you deliberately need the
 private provider account and source metadata.
 
-For native WhatsApp evidence, install Wrench v0.16.3 and let its official
+For native WhatsApp evidence, install Wrench v0.16.5 and let its official
 Wacli 0.15.0 adapter create the one-account v2 bundle:
 
 ```sh
-bun add --global @hraness/wrench@0.16.3
+bun add --global @hraness/wrench@0.16.5
 wrench whatsapp export-message-like-me \
   --auth <whatsapp-auth-id> \
   --output /absolute/private/path/whatsapp-bundle \
@@ -224,6 +273,14 @@ broadcast, newsletter, credential, session-database, provider-URL, and media-byt
 surfaces are excluded. The complete contract is in
 [local message bundle v2](docs/local-message-bundle-v2.md).
 
+Wacli v0.15.0 may retain an earlier emoji after a reaction is removed, so its
+local rows cannot prove current active reaction state. Wrench v0.16.5 omits
+every reaction-shaped row and adds `reaction-state-unproven` when it observes
+one. An empty `reactions.ndjson` from this producer means reaction behavior was
+unobservable, not that the account had no reactions. The v2 wire contract keeps
+its fixed reaction artifact and strict parser for proven records; Message Like
+Me imports only the records the producer can establish.
+
 If a Beeper WhatsApp source already represents the same exact account, inspect
 the redacted source inventory and name it explicitly:
 
@@ -239,7 +296,8 @@ unambiguous shared text-message fingerprint. Groups, bodyless messages, names,
 phone suffixes, and approximate timestamps cannot prove equivalence. Both
 provenances and source-unique history remain. Native Wacli evidence becomes the
 preferred `whatsappJid` route; its proven Beeper duplicate remains
-`evidence-only` with reason `superseded-route`.
+`evidence-only` with reason `superseded-route`. This producer supplies no native
+reaction records, so overlap cannot reconcile reaction state.
 
 Optionally enrich and join direct conversations with private identities from
 macOS Contacts:
@@ -548,6 +606,22 @@ context support them.
 Drafting ends with text in the agent task. Message Like Me has no send, react,
 schedule, or messaging-application command.
 
+## Find the right documentation
+
+- **Install and prove the local boundary:** use [Install and first run](#install-and-first-run).
+- **Add evidence:** choose a path under [Supported sources](#supported-sources),
+  then follow [Add private local history](#add-private-local-history).
+- **Study or draft:** inspect behavior, prepare a study packet, build a profile,
+  audit it against later conversations, then draft an unsent reply using the
+  task sections above.
+- **Review evidence and safety claims:** read the
+  [methodology](docs/methodology.md), [research review](docs/research.md), and
+  [security policy](SECURITY.md).
+- **Integrate a producer:** use the versioned
+  [Beeper bundle](docs/local-message-bundle-v1.md),
+  [WhatsApp bundle](docs/local-message-bundle-v2.md), and public JSON Schemas
+  instead of inferring a wire format from examples.
+
 ## Command reference
 
 Run `messagelikeme --help` for the checked grammar. The public surfaces are:
@@ -594,7 +668,7 @@ messagelikeme doctor [--json]
 
 Place global `--data-dir PATH` before the command.
 
-## Privacy model
+## Privacy, security, and limitations
 
 - The original `chat.db` and AddressBook databases remain authoritative.
   SQLite opens only stable private copies, never the source files or sidecars.
@@ -617,6 +691,9 @@ Place global `--data-dir PATH` before the command.
   data handling you accept; the CLI cannot make a hosted agent local.
 - Public fixtures are synthetic. Private corpora, profiles, packets, and drafts
   do not belong in Git, issues, logs, packages, or examples.
+- Message Like Me does not train a model, represent your identity, infer your
+  beliefs, or claim that a draft is what you would have written. Current facts,
+  meaning, and intent remain the user's responsibility.
 - A draft is never sent.
 
 Read [SECURITY.md](SECURITY.md) before integrating the library into another
@@ -675,18 +752,26 @@ import type {
 The library does not start the CLI, inspect Messages, Contacts, or an X archive,
 connect to a network, or send a draft merely because it is imported.
 
-## Development
+## Verify a checkout
 
 ```sh
 bun install --frozen-lockfile --ignore-scripts
 bun run check
 ```
 
+The complete gate type-checks the project, runs the synthetic test suite,
+validates both bundled Agent Skills and the standalone public boundary,
+rebuilds `dist/`, checks the committed build, and exercises a packed consumer.
+
+## Develop and contribute
+
 Tests use synthetic Messages and AddressBook databases, synthetic X archive
 ZIPs, and synthetic source bundles and conversations. Never add a real message,
 handle, group title, attachment, contact record, private path, or derived
 profile to a fixture.
 
+Read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a change.
+
 The canonical repository is
 [`hraness/message-like-me`](https://github.com/hraness/message-like-me).
 The informational project page is

package/dist/cli.js

@@ -6214,7 +6214,7 @@ class LocalStore {
 }
 
 // src/version.ts
-var MESSAGE_LIKE_ME_VERSION = "0.8.0";
+var MESSAGE_LIKE_ME_VERSION = "0.8.1";
 
 // src/x-archive.ts
 import { createHash as createHash4 } from "crypto";

package/docs/local-message-bundle-v1.md

@@ -8,11 +8,11 @@ importer never receives provider credentials, starts Wrench, invokes a Beeper
 operation, or sends a message.
 
 The currently verified producer is the local Beeper export in the
-[`@hraness/wrench@0.16.1`](https://www.npmjs.com/package/@hraness/wrench/v/0.16.1)
+[`@hraness/wrench@0.16.5`](https://www.npmjs.com/package/@hraness/wrench/v/0.16.5)
 npm package:
 
 ```sh
-bun add --global @hraness/wrench@0.16.1
+bun add --global @hraness/wrench@0.16.5
 wrench beeper export-message-like-me \
   --auth <beeper-auth-id> \
   --output <normalized-absolute-new-directory> \
@@ -31,13 +31,26 @@ express.
 ## Compatibility coordinates
 
 Message Like Me accepts schema version `1` with source ID `beeper-local` and
-source-transform version `1.1.0`. Wrench v0.16.1 emits those coordinates with
-the pinned Beeper CLI version `0.6.2`. A later Wrench package release remains
-compatible only while its manifest still declares that schema, source ID, and
-`source.version: "1.1.0"`; package age or a permissive version range never
-overrides the manifest coordinates. The provider version records the pinned
-Beeper CLI used for capture and may change without changing the bundle
-contract.
+source-transform version `1.1.0`. Wrench v0.16.5 emits those coordinates through
+adapter `beeper-local@2.3.0`. That adapter has 32 reviewed Beeper operations:
+27 use the pinned CLI and 5 use fixed Desktop loopback reads. The Message
+Like Me bundle is made by Wrench's separate internal bounded export, not by a
+Message Like Me provider operation. It fixes the raw export arguments, excludes
+attachments, and preserves incomplete-coverage evidence. It does not claim a
+complete Beeper history.
+
+The pinned Beeper CLI executable reports version `0.6.2`. At the corresponding
+source tag, `packages/cli/package.json` declares `0.6.1`; that source value is
+provenance only and never overrides executable runtime identity. A later Wrench
+package release remains compatible only while its manifest still declares the
+same bundle schema, source ID, and `source.version: "1.1.0"`. Package age,
+adapter version, or a permissive package range never overrides those manifest
+coordinates. The provider version records the pinned Beeper CLI used for
+capture and may change without changing the bundle contract.
+
+Message Like Me owns zero Beeper operations, credentials, or live sessions. It
+does not start Wrench, call the provider, or support sending. Its authority
+begins at strict verification of the already finished private directory.
 
 The dependency-free package subpath is the executable contract authority for
 producers and consumers:

package/docs/local-message-bundle-v2.md

@@ -10,7 +10,7 @@ network, or sends a message.
 The intended producer flow is:
 
 ```sh
-bun add --global @hraness/wrench@0.16.3
+bun add --global @hraness/wrench@0.16.5
 wrench whatsapp export-message-like-me \
   --auth <whatsapp-auth-id> \
   --output /absolute/private/path/whatsapp-bundle
@@ -20,10 +20,16 @@ messagelikeme ingest bundle \
   --json
 ```
 
-The checked compatibility coordinates are Wrench v0.16.3 and official Wacli
+The checked compatibility coordinates are Wrench v0.16.5 and official Wacli
 v0.15.0. Wrench owns that executable dependency and its authentication state;
 neither enters Message Like Me.
 
+That exact producer excludes every reaction-shaped Wacli row. Wacli v0.15.0
+may retain an earlier emoji after a removal, so the local projection cannot
+durably establish current active reaction state. A bundle that encountered any
+such row carries the categorical `reaction-state-unproven` warning. This is an
+observability limit, not evidence that no reactions occurred.
+
 The normative object schema is
 [`schema/local-message-bundle-v2.schema.json`](../schema/local-message-bundle-v2.schema.json).
 The runtime parser is stricter than JSON Schema where byte length, canonical
@@ -82,6 +88,11 @@ changes, invalid UTF-8, blank or oversized records, noncanonical JSON, count or
 byte disagreement, and SHA-256 disagreement. The same public bounds as v1
 apply, except v2 admits exactly one account.
 
+The v2 wire contract retains the fixed `reactions.ndjson` artifact and strict
+reaction parser for proven records. The checked Wrench v0.16.5/Wacli v0.15.0
+producer leaves that artifact empty because it cannot prove current reaction
+state.
+
 `manifest.json` is canonical JSON followed by one newline. Every NDJSON record
 is one canonical JSON object followed by one newline. The manifest integrity
 digest covers its canonical projection without the `integrity` member;
@@ -112,8 +123,10 @@ matches.
 Every message has a proven incoming or outgoing direction. Direct-message
 senders are proven. A group or system row may retain a null sender when the
 bounded local observation cannot prove one, and it cannot establish overlap.
-Reply, edit, deletion, reaction, attachment, and tombstone fields retain the
-same strict meanings as v1. Attachment bytes, provider URLs, credentials, Wacli
+Reply, edit, deletion, attachment, and tombstone fields retain the same strict
+meanings as v1. The contract also defines reaction records, but the checked
+producer emits none and reports `reaction-state-unproven` when it encounters a
+reaction-shaped row. Attachment bytes, provider URLs, credentials, Wacli
 session state, database paths, and unmodeled provider payloads are excluded.
 Unsupported status, broadcast, and newsletter records are not represented as
 ordinary conversations.
@@ -148,11 +161,13 @@ messages, groups, names, phone suffixes, approximate timestamps, and ambiguous
 duplicates cannot prove equivalence.
 
 Both source provenances and all source-unique history remain stored. Proven
-message and reaction duplicates contribute once. The native Wacli conversation
-is the preferred action route and carries the exact private `whatsappJid`
-coordinate. Its proven Beeper duplicate remains evidence with reason
-`superseded-route`. Reimport rechecks the named proof atomically and fails
-closed on disagreement.
+message duplicates contribute once. A reaction can deduplicate only when a
+conforming producer supplies a proven reaction record; Wrench v0.16.5 supplies
+none, so this overlap path does not reconcile reaction state. The native Wacli
+conversation is the preferred action route and carries the exact private
+`whatsappJid` coordinate. Its proven Beeper duplicate remains evidence with
+reason `superseded-route`. Reimport rechecks the named proof atomically and
+fails closed on disagreement.
 
 ## Privacy and action boundary