v1.5.1

fix(registry): re-list under io.github.unsoldgroup — v1.5.1 (#30)

The old MCP Registry namespace was unreachable, not just misconfigured.
`io.github.alunsoldantarctica/*` derives from a GitHub username that no
longer exists (the account was renamed, the org rename followed), and the
registry grants a namespace only to a live identity — so nobody could
authenticate to it: not CI's OIDC identity, not a browser login, not the
original owner. Both attempts 403'd during the v1.5.0 release.

- server.json `name` and package.json `mcpName` -> io.github.unsoldgroup/
  mail-index. mcpName is the registry's npm ownership check, so the rename
  only takes effect via a published version: 1.5.1 in all four version
  fields.
- registry-publish.yml: the `release: [published]` trigger NEVER fires for a
  Release created by release.yml — GitHub refuses to start a workflow from an
  event another workflow raised with the default GITHUB_TOKEN. Documented in
  the workflow and in PUBLISHING.md; the step is a manual dispatch.
- PUBLISHING.md prerequisites, verification URLs, and the 403 troubleshooting
  note rewritten for the org namespace.

The npm package is still `mail-index`; installs, MCP configs, and the tool
surface are unchanged. Only the registry listing's identifier moved. The old
entry stays frozen at 1.0.0 permanently.

Co-authored-by: al-unsoldgroup <al-unsoldgroup@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

v1.5.0

chore(release): v1.5.0 — the remote Deployment release (#29)

Ship the Cloudflare Worker work (PRs #12-#28) as a published version.

- CHANGELOG.md: new, Keep-a-Changelog format. Thorough v1.5.0 entry
  (remote Deployment, D1 driver, gmail-rest adapter, OAuth, Job engine,
  Trigger rules + signed webhooks, A2A, seed path, freshness/auto-refresh,
  fixes, security posture, upgrade notes) plus back-filled 1.0.0-1.4.0.
- README: v1.5 status + feature TIP, v1.4 TIP demoted to historical, and
  the Documentation index now lists INSTALL-worker, WORKER-SEED,
  PLAN-worker, and the changelog.
- docs/PUBLISHING.md: the release is now one pushed tag end to end
  (release.yml -> npm + .mcpb + GitHub Release -> registry-publish.yml via
  OIDC). Documents the four-version-fields/three-files trap that left the
  registry entry pinned at 1.0.0 through v1.4.0, and adds post-release
  verification.
- Bump package.json, manifest.json, and BOTH server.json version fields to
  1.5.0.

427 tests, lint, and typecheck green.

Co-authored-by: al-unsoldgroup <al-unsoldgroup@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

v1.4.0

v1.4.0 — opt-in mailbox writes + human-readable labels

v1.3.0

chore(release): v1.3.0 — Gmail label indexing + refresh_inbox MCP tool

Query labels (CLI inbox/labeled, MCP list_labeled), per-sync INBOX membership
reconcile, and refresh_inbox MCP tool for live-accurate "what's in my inbox".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v1.2.2

v1.2.2 — self-contained Windows .mcpb + XDG-over-worktree db fix

v1.2.1

chore(release): v1.2.1 — auto-isolate linked-worktree DBs

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v1.2.0

feat(index): mirror m008 (topic tables) + MAIL_INDEX_DB isolation — v…

v1.1.0

mail-index v1.1.0

First feature release since 1.0.0. All changes are additive and backward-compatible — the local index auto-migrates on next open (schema v6 → v7).

✨ Auto-update (new)

From this version on, mail-index keeps itself up to date. On launch, the CLI/MCP fire a background check against the npm registry; when a newer version is published, the install updates itself and the new build is picked up on the next launch.

• Non-blocking & safe: the check runs detached and never delays startup. An update is never hot-swapped into a running process — a long-lived MCP server keeps serving its loaded build until it next restarts, so the CLI and MCP always stay in lockstep on one install.
• Throttled: at most once per 24h.
• Opt-out: set MAIL_INDEX_NO_AUTOUPDATE=1 to disable entirely.
• Install-aware: an npm-global install updates with npm i -g mail-index@latest; a git checkout fast-forwards main and rebuilds (only when the checkout is clean — your work is never clobbered).
• Privacy preserved: the updater is quarantined in bin/ (the one network seam besides the provider adapter) so the core (src/) stays provably egress-free — enforced by the same CI egress guard, which now audits bin/ too. See THREAT-MODEL / SECURITY.

🧭 Deterministic correspondent cadence (new)

mail-index cadence --account <a> [--category <c>] [--since <30d|1mo>] and a matching cadence MCP tool: how often each sender brand emails you (volume, distinct senders, first/last, per-month), groupable by an agent-assigned entity category. Brands are keyed by a new registrable-domain (eTLD+1) normalization (domains.registrable_domain, migration m006).

🔎 FTS improvements

• m005: repaired FTS schema drift (rebuilds messages_fts to the canonical 4-column, rowid-aligned shape) — fixes wrong-result rows on indexes created by the pre-v1 prototype.
• m007: porter-stemmed FTS contract with bm25 weighting + query expansion for better recall.

Upgrade

npm i -g mail-index@1.1.0 (or just let auto-update handle it), or download the attached .mcpb.

v1.0.0

mail-index v1.0.0 — first public release (gog adapter, MCP, homepage)