@murphai/murph 0.1.1 → 0.1.14

package/CHANGELOG.md

@@ -2,6 +2,180 @@
 
 All notable changes to `@murphai/murph` will be documented in this file.
 
+## [0.1.14] - 2026-04-04
+
+### Added
+- add best-effort assistant typing indicators across supported messaging channels
+- add hosted per-user root-key envelopes and browser-compatible user-key helpers for future unlock flows
+
+### Fixed
+- harden hosted execution control with signed control routes, per-run runner tokens, and safer per-user key handling
+- keep hosted user-envelope reads greenfield-safe while preserving the new hosted key model
+- restore hosted verification stability by fixing Cloudflare control-path regressions and stale hosted-web smoke-process cleanup
+- align hosted Linq integrations with the current v3 API, canonical snapshots, and v3 media payloads
+- harden the hosted install script for stock macOS Bash
+- tighten assistant onboarding so first-contact guidance runs once, uses clearer copy, and keeps knowledge tools available on provider turns
+- support Venice defaults in hosted assistant configuration
+
+### Changed
+- move knowledge runtime ownership into `assistant-core` and tighten knowledge validation
+- centralize first-contact finalization in the assistant runtime
+- refactor the hosted homepage into composable sections and refresh the landing-page copy
+
+## [0.1.13] - 2026-04-04
+
+### Changed
+- No user-facing changes recorded.
+
+## [0.1.12] - 2026-04-04
+
+### Changed
+- No user-facing changes recorded.
+
+## [0.1.11] - 2026-04-04
+
+### Fixed
+- harden hosted storage confidentiality
+- restore knowledge metadata fallback
+- align refresh semantics and guidance
+
+### Changed
+- set npm scope for publish
+- use latest node and npm
+- make knowledge compile assistant-authored
+- bootstrap package trust bindings
+- finish knowledge helper extraction
+
+## [0.1.10] - 2026-04-04
+
+### Changed
+- restore trusted publishing flow
+- speed up release checks
+- share canonical knowledge model
+
+## [0.1.9] - 2026-04-04
+
+### Fixed
+- clear empty npm auth fallback
+
+## [0.1.8] - 2026-04-03
+
+### Fixed
+- drop npm self-update from publish workflow
+
+## [0.1.7] - 2026-04-03
+
+### Fixed
+- restore npm token fallback
+
+## [0.1.6] - 2026-04-03
+
+### Added
+- harden wiki runtime
+- add wiki search surface
+- add derived knowledge wiki
+- add calm device sync sources
+- add wearables query surfaces
+- add workout measurements media and units
+- add web pdf read tool
+- add guarded web fetch tool
+- land data model cutover
+- add web search tool
+- land Garmin provider and green checks
+- move hosted auth to privy request tokens
+
+### Fixed
+- expose time helpers for package verification
+- harden public sender ingress
+- tighten hosted callback/runtime guards
+- encrypt hosted gateway durable state
+- land pro cleanup patch
+- simplify hosted email routes
+- land crypto hardening patch
+- add hosted email public sender routing
+- keep next config self-contained
+- allow Privy custom auth domains in csp
+- wire hosted brave web search
+- default hosted web reads on
+- pin vetted web fetch destinations
+- defer node require helpers
+- prebuild workspace before rollout
+- inherit canonical script path aliases
+- keep web fetch tools always on
+- align inbox subpath ts paths
+- narrow inbox runtime bundle surface
+- harden web fetch and pdf tools
+- stabilize repo green checks
+- remove hosted agentmail env
+- bake whisper into hosted runner
+- wire hosted email deploy config
+
+### Changed
+- split query search helpers
+- hard cut over ingress routes
+- land queued web and runtime updates
+- update review-gpt to 0.5.30
+- record wearables semantic correctness completion
+- unify descriptor and wearables policy seams
+- remove transcript distillation
+- remove docs drift from default test lane
+- add contribution kit
+- unify shared descriptors
+- hard-cut hosted web control host allowlist
+- remove stale paddleocr deploy residue
+- align deploy workflow default
+- raise hosted runner baseline
+- remove hosted assistant automation opt-out
+- clear stale coordination ledger
+- clear completed ledger row
+- remove doc inventory
+- remove legacy fallback paths
+- split web search module
+- normalize runner bundle slot storage
+- bump review-gpt to v0.5.24
+- remove npm token fallback
+- remove hosted session helpers
+- narrow shared export surfaces
+- clear completed review-gpt row
+- land pro audit patch set
+
+## [0.1.5] - 2026-04-02
+
+### Fixed
+- unblock hosted web and package publish
+
+### Changed
+- disable dependabot
+
+## [0.1.4] - 2026-04-02
+
+### Fixed
+- tune first-turn onboarding prompt
+- default codex reasoning to medium
+- omit empty npm tag in publish workflow
+- drop onboarding tone prompt
+
+### Changed
+- clear finished boundary-cleanup ledger row
+- clean parser and gateway boundaries
+
+## [0.1.3] - 2026-04-02
+
+### Fixed
+- soften first-turn and memory prompt guidance
+- support hosted inbound attachments
+
+### Changed
+- move gateway and assistant schemas to zod
+- centralize system prompt
+- clarify npm package messaging
+
+## [0.1.2] - 2026-04-02
+
+### Changed
+- stop tracking generated doc inventory
+- add patch rc shortcut
+
 ## [0.1.1] - 2026-04-02
 
 ### Added

package/README.md

@@ -1,31 +1,89 @@
-# `@murphai/murph` (`packages/cli`)
-
-Owns the `vault-cli` command surface. The CLI may validate inputs and format outputs, but it must delegate all canonical writes to core.
-
-## Status
-
-- Package-local Incur command structure is present under `src/`.
-- Command handlers are thin and dependency-injected through `createVaultCli()`.
-- Machine-facing callers should rely on Incur's native envelope via `--verbose --format json` instead of a Murph-specific wrapper contract.
-- Built-in Incur surfaces such as `--help`, `--schema`, `--llms`, `completions bash`, and the root `--config` / `--no-config` flags are part of the package verification surface and should remain truthful as command metadata evolves.
-- Library exports and the executable bin are now split: `src/index.ts` is the package entrypoint, and `src/bin.ts` is the CLI launcher.
-- Default runtime services now lazy-load the workspace `@murphai/core`, `@murphai/importers`, and `@murphai/query` package boundaries instead of reaching into sibling `src/` trees.
-- `packages/cli` now extends the shared `../../tsconfig.base.json`; `tsconfig.json` is the buildable package project, `tsconfig.build.json` stays as the local build alias, and `tsconfig.typecheck.json` covers package-local scripts and tests.
-- Package-local verification scripts and runtime tests now live in TypeScript under `scripts/` and `test/`.
-- Local build now runs in this workspace, and the built binary can be exercised with `node dist/bin.js ...` after `pnpm --dir packages/cli build`.
-- Top-level retrieval commands now include `search` for lexical read-model search, `search index status` / `search index rebuild` for the optional SQLite FTS index stored in `.runtime/search.sqlite`, with CLI code importing the headless query helpers from `@murphai/assistant-core` instead of keeping a local compatibility layer.
-- The inbox CLI runtime now resolves `.runtime` paths through `@murphai/runtime-state`, so inbox config/state/promotions JSON and `inboxd.sqlite` stay aligned with inboxd itself.
-- The CLI now also owns an `inbox` command group for local runtime init/source management, diagnostics, backfill, foreground daemon control, and inbox capture review/promotion while importing the underlying headless inbox services from `@murphai/assistant-core`.
-- The CLI now also owns an `assistant` command group for provider-backed local chat turns, Ink-backed local chat UI fallback, assistant-session metadata plus local transcripts outside the vault, outbound channel delivery, and an always-on inbox triage loop via `src/assistant-runtime.ts`.
-- The dedicated `@murphai/assistant-core` package owns the headless assistant/inbox/vault/operator-config modules plus the shared inbox-app, usecase, and setup/runtime helper layers directly; the CLI now imports that package in place and keeps only command/setup orchestration plus the daemon-aware wrappers that genuinely belong at the CLI transport boundary.
-- iMessage-backed inbox and assistant delivery flows now depend directly on `@photon-ai/imessage-kit` instead of late-loading that package at call time, while Telegram delivery and ingestion share the same assistant channel binding abstraction.
-- The published CLI package is `@murphai/murph`, and it exposes both `vault-cli` and an onboarding-focused `murph` alias from the same entrypoint; `murph`, `murph --help`, and `murph onboard ...` land on the setup surface, while other operator/data-plane commands stay under `vault-cli`.
+# Murph - Personal Health Assistant
+
+Murph is your personal health assistant.
+
+Install this package to get the main `murph` command and the full local Murph experience: onboarding, vault setup, local assistant chat, inbox capture, parser tooling, and the always-on assistant loop.
+
+The repo implementation happens to live in `packages/cli`, but that is a maintainer detail. For users, `@murphai/murph` is the installable Murph package.
+
+[Repository](https://github.com/cobuildwithus/murph) · [Architecture](https://github.com/cobuildwithus/murph/blob/main/ARCHITECTURE.md) · [Hosted control plane](https://github.com/cobuildwithus/murph/blob/main/apps/web/README.md) · [Hosted execution](https://github.com/cobuildwithus/murph/blob/main/apps/cloudflare/README.md)
+
+If you want a local, inspectable assistant that keeps durable truth in normal files you can read, this is the package you install.
+
+Runtime: Node `>= 22.16.0`.
+
+Supported host setup path: macOS and Linux. iMessage remains macOS-only.
+
+## Install
+
+```bash
+npm install -g @murphai/murph@latest
+# or
+pnpm add -g @murphai/murph@latest
+```
+
+## Quick start
+
+```bash
+murph onboard
+```
+
+`murph onboard` installs or reuses the local parser dependencies, initializes a vault, saves that vault as the default Murph vault for later commands, and walks through assistant, channel, and optional wearable setup.
+
+Once setup is complete, the main commands are:
+
+```bash
+murph chat
+murph run
+murph status
+vault-cli inbox doctor
+```
+
+`vault-cli` is still available as a secondary alias for the operator surface, but `murph` is the primary command this package installs.
+
+For durable local synthesis that should keep adding up inside the vault, use the derived knowledge wiki commands:
+
+```bash
+vault-cli knowledge upsert --title "Sleep notes" --body "# Sleep notes\n\nMagnesium looked helpful for sleep continuity.\n" --source-path research/2026/04/sleep-note.md
+vault-cli knowledge search "sleep magnesium"
+vault-cli knowledge list
+vault-cli knowledge lint
+```
+
+## What you get
+
+- a file-native health vault with canonical writes owned by `@murphai/core`
+- local assistant chat, automation, status, cron, and outbox commands
+- a non-canonical derived knowledge wiki you can upsert and inspect under `derived/knowledge/**`
+- inbox capture, review, backfill, and parser-driven attachment extraction
+- optional local device sync through `@murphai/device-syncd`
+- optional local assistant daemon support through `@murphai/assistantd`
+
+`@murphai/murph` is the installable local Murph product entrypoint. The wider monorepo also contains hosted control and execution apps, but those are repo internals rather than something npm users need to install directly.
+
+## From source
+
+If you are developing from a checkout instead of installing the published package:
+
+```bash
+pnpm install --frozen-lockfile
+pnpm onboard --vault ./vault
+```
+
+If `pnpm` is not available yet, use:
+
+```bash
+./scripts/setup-host.sh --vault ./vault
+```
 
 ## Config defaults
 
-The root CLI now supports incur's built-in config loading for command option defaults. By default it searches `~/.config/murph/config.json` and then `~/.config/vault-cli/config.json`; `vault-cli --config <path> ...` selects an explicit file, including a repo-local JSON file, and `vault-cli --no-config ...` disables config loading for a single run.
+The CLI supports incur's built-in config loading for command option defaults. By default it searches `~/.config/murph/config.json` and then `~/.config/vault-cli/config.json`.
+
+- `murph --config <path> ...` selects an explicit config file
+- `murph --no-config ...` disables config loading for a single run
 
-Config files only supply command `options`, following incur's nested `commands` shape. For example, this file makes `vault-cli init` default to a chosen vault path:
+Config files only supply command `options`, following incur's nested `commands` shape. For example:
 
 ```json
 {
@@ -39,29 +97,26 @@ Config files only supply command `options`, following incur's nested `commands`
 }
 ```
 
-## Host setup (macOS and Linux)
-
-Once `@murphai/murph` is published, the installed-package onboarding path will be:
-
-```bash
-murph onboard
-```
+## Maintainer notes
 
-That command installs or reuses the local parser dependencies (`ffmpeg`, `poppler`/`pdftotext`, `whisper-cpp`), downloads a Whisper model into `~/.murph/toolchain/models/whisper/`, initializes the default `./vault` target unless you override it, saves that vault as the default Murph CLI vault for later commands, runs inbox bootstrap, and then launches `assistant run` automatically when at least one selected channel is fully configured for auto-reply, falling back to `assistant chat` otherwise.
+The package exports the CLI runtime plus assistant helper subpaths from `dist/**`, exposes both `murph` and `vault-cli` bins from the same built entrypoint, and keeps `src/index.ts` as the package entrypoint with `src/bin.ts` as the launcher.
 
-Setup also installs user-level `murph` and `vault-cli` shims into `~/.local/bin`. If that directory is not already on `PATH`, setup appends a managed PATH block to the active shell profile and tells the operator to reload the shell. Once setup has run, the main CLI can omit `--vault` when the saved default is the intended target.
+Machine-facing callers should rely on incur's native envelope via `--verbose --format json` instead of a Murph-specific wrapper contract.
 
-Useful flags include `--dry-run` and `--whisperModel small.en`.
+Current repo-local package responsibilities include:
 
-From a checkout, the supported onboarding path is the repo-local `scripts/setup-host.sh` wrapper. On macOS it delegates to the existing Homebrew-based bootstrap path; on Linux it can reuse or download Node locally, activate pnpm through corepack, install dependencies with the frozen lockfile, build the workspace, and then run the same CLI setup flow. `./scripts/setup-host.sh --dry-run ...` now prints the wrapper bootstrap plan without mutating Homebrew, Node, pnpm, dependencies, or the workspace build. A successful non-dry-run setup now leaves behind working `murph` and `vault-cli` commands for future shells via those user-level shims. iMessage remains macOS-only even though the rest of the host setup now supports Linux.
+- the command graph and onboarding flow
+- local assistant command orchestration and Ink chat UI
+- inbox and device command surfaces that delegate to headless owner packages
+- CLI-only wrappers around shared packages such as `@murphai/assistant-core`, `@murphai/query`, `@murphai/inboxd`, and `@murphai/runtime-state`
 
-## Release Flow
+## Release flow
 
-Release/version/publish actions remain user-operated. The monorepo release source of truth is `scripts/release-manifest.json`, and the normal entrypoints are root commands:
+Release and publish actions remain user-operated. The monorepo release source of truth is `scripts/release-manifest.json`, and the normal entrypoints are:
 
 ```bash
 pnpm release:check
-pnpm release:patch   # or: pnpm release:minor / pnpm release:major
+pnpm release:patch
 ```
 
 Pre-release and exact-version flows use the same root script:
@@ -73,25 +128,13 @@ bash scripts/release.sh 0.1.0-rc.1 --dry-run
 
 The release flow bumps every publishable package in the manifest to one shared version, updates `packages/cli/CHANGELOG.md`, writes `packages/cli/release-notes/v<version>.md`, and then creates a repository tag so `.github/workflows/release.yml` can pack and publish all tarballs in dependency order.
 
-The first publish set is:
-
-- `@murphai/contracts`
-- `@murphai/hosted-execution`
-- `@murphai/messaging-ingress`
-- `@murphai/runtime-state`
-- `@murphai/assistant-core`
-- `@murphai/gateway-core`
-- `@murphai/gateway-local`
-- `@murphai/core`
-- `@murphai/query`
-- `@murphai/importers`
-- `@murphai/device-syncd`
-- `@murphai/inboxd`
-- `@murphai/parsers`
-- `@murphai/assistant-runtime`
-- `@murphai/assistantd`
-- `@murphai/murph`
-
-`pnpm release:check` now installs with the frozen lockfile, builds the workspace, runs the repo checks, verifies that every workspace dependency in the publish set stays inside the publish set, and packs every publishable package with `pnpm pack`.
-
-Trusted publishing still has to be configured on npm for each published package entry that this workflow will publish.
+npm trusted publishing is configured per package on npm, not once per repository. Because this monorepo publishes multiple `@murphai/*` packages, maintainers should bootstrap those package-level trust bindings before relying on tag-driven release publication:
+
+```bash
+pnpm release:trust:github -- --dry-run
+pnpm release:trust:github -- --yes
+```
+
+Those commands target the current publishable package set in `scripts/release-manifest.json` and bind each package to `cobuildwithus/murph` via `.github/workflows/release.yml`.
+
+If a package is already bound to the wrong workflow or repository in npm, revoke that package's existing trust entry with `npm trust list` and `npm trust revoke`, then rerun `pnpm release:trust:github -- --yes`.