agents-pod 0.0.0-stage → 0.2.0

package/CHANGELOG.md

@@ -0,0 +1,83 @@
+# Changelog
+
+All notable changes to agents-pod. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project
+adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.2.0] — 2026-11-04
+
+Work that arrives in a chat can now be picked up there, and answered there,
+without a resident process holding a socket: a **Source** drains a conversation
+into a pod once per pass, a **Deliverer** posts a pod's **Outbox** back, and a
+**Delivery Address** rides the Goal so a Worker can reply without asking anyone.
+
+### Added
+
+- **IM intake and outbound — Source, Deliverer, Outbox, and Delivery Address** —
+  a pull-based intake and file-based reply path, with platform credentials and
+  API behavior kept in operator commands.
+- **Sources and drains** — `source add|list|rm`, cursor-based JSONL drains with
+  platform ids and routing fields, bounded execution, claim-before-cursor
+  commits, and two-generation claim retention.
+- **Source Listeners and standing Pod intake** — `listener add --source`, batched
+  `TASKS.md` Inbox delivery with Waiting state, the `{{reply_to}}` template
+  placeholder, and `--project` for template-materialized Pods.
+- **Outbox delivery** — `deliver add|list|rm`, one operator deliverer, named
+  per-wake-up entry files carrying `{to, text}`, stable delivery uuids, bounded
+  wrapper and reconcile flushes, same-uuid retries, one-hour dead-lettering,
+  and retained `*.dead` entries for expired or invalid input.
+
+### Fixed
+
+- Wake-up outcomes are recorded under the registry lock, so concurrent passes
+  and wrappers no longer overwrite each other's registry updates.
+
+## [0.1.0] — 2026-11-03
+
+First release: one pod, many wake-ups, and the machinery that keeps a standing
+unit alive across them. Published under the AGPL-3.0-or-later.
+
+### Added
+
+- **CLI** — `spawn`, `status`, `list`, `logs [--follow]`, `wake [--warm]`,
+  `cancel`, `reconcile`, `agent add|edit|rm|list`, `listener add|rm|list`,
+  `project cap`. Exit codes: `0` success or nothing to do, `1` at least one pod
+  failed, `2` configuration or storage error.
+- **Wrapper per wake-up** (`bin/wrapper.mjs`) — a detached session and
+  process-group leader that spawns the agent CLI, streams stdout/stderr to the
+  pod log, touches a heartbeat, and adjudicates the outcome in three layers
+  (fresh handoff declaration over observed events over exit facts). A clean
+  exit with no fresh handoff is `failed`.
+- **Document store** — `docs/HANDOFF.md` (rolling, `status: rotating | done`
+  first line), `docs/DECISIONS.md` (append-only), `docs/TASKS.md` (plan
+  checkboxes plus the `## Inbox` section reconcile appends to).
+- **Reconcile** — idempotent cron entry point: ghost records marked lost,
+  orphans reaped, reboot detection, idle pods woken per policy (backoff after
+  `failed`/`lost`, 1m ×2 capped at 15m, three consecutive failures park the
+  pod), listener inboxes scanned and claimed, one lock so overlapping passes
+  cannot double-wake.
+- **Wake admission** — `--after <podId>` dependencies and the per-project live
+  wake-up cap; a manual `wake` overrides park and backoff, never a dependency
+  or the cap.
+- **Listeners** — standing intake without a daemon: an inbox directory or
+  JSONL file, a pod template or a bound standing pod, routing by substring.
+- **Progress signals** — document and log growth per wake-up, so a live but
+  progressless wake-up is killed and re-woken rather than left to burn.
+- **Notifications** — system, webhook and email channels adapted from
+  agents-cron, on the two events a human must hear: a pod reached `done`, and a
+  pod parked after three consecutive failures (with its failure trail).
+- **Pi extension** — two planes gated by wrapper-injected env: the management
+  plane (`/pod …` commands and the `spawn_pod` tool) registers only in an
+  interactive session, and the self plane (`pod_handoff`) only inside a pod, so
+  fan-out from inside a pod is structurally impossible rather than forbidden.
+- **Packaging** — TypeScript shipped and executed as-is (no build step, no
+  `dist/`), a bin loader hook for files under `node_modules`, and a
+  packed-tarball smoke test in `npm run check`.
+
+### Limits
+
+- **Pi only.** `--type claude | codex` is refused at `agent add`, `spawn`,
+  `wake`, and again at launch: the wrapper has one command line, and running pi
+  in claude's name would be a silent wrong agent.
+- **No default timeout, no default expiry.** Liveness is a pid plus our own
+  heartbeat; a pod idles as a registry record for as long as its goal is open.