loadout-ai 0.8.0 → 0.9.1

package/CHANGELOG.md

@@ -2,6 +2,142 @@
 
 ## Unreleased
 
+### Added
+
+- Snapshot capture and restore preserve Unix file permission modes, with
+  validation that rejects out-of-range values and tolerance for legacy
+  snapshots missing the `mode` field.
+- Provider cancellation via `AbortSignal` on adapter `start()` and
+  `submitTurn()` methods. Cancelled turns release the busy flag so new
+  turns can proceed.
+- Opt-in `loadout handoff ... --bundle <paths...>` context snapshots give the
+  receiving agent exact source context, with versioned references and visible
+  truncation metadata, while preserving all existing handoff messages.
+- Evidence-backed handoff completion with human criteria, optional shell-free
+  executable/JSON argv checks, bounded pass/fail evidence, and failed checks
+  that remain pending instead of being reported done.
+- Reusable built-in and project-local handoff templates with positional
+  placeholder expansion, bounded context bundles, and verification defaults.
+- Preview-first coordination setup, exact cross-boundary contract detection,
+  Git-author ownership mappings, and idempotent discussion-to-implementation
+  plans linked to their generated handoff tasks.
+
+### Changed
+
+- Log compaction preserves ownership, contract, and decision state by
+  extracting the latest checkpoint for each state key before removing events.
+  Double compaction is stable.
+- Auto-detected contracts handle mixed `import { A, type B }` syntax and
+  reject incomplete multi-line `const` declarations as unpublishable instead
+  of emitting truncated contract bodies.
+- Auto-detected contracts preserve exact supported declarations, expose a
+  source hash, distinguish current from stale revisions, and require both
+  `--publish` and `--yes`. Unsupported declarations require manual completion.
+- Git ownership confidence includes every author touching a directory and maps
+  agent identities explicitly with `agent=Git Author`.
+- Verification processes run outside the handoff log lock, so other agents can
+  continue sending tasks while a long check runs; completion remains atomic.
+
+### Fixed
+
+- Coordination lock recovery uses atomic rename so concurrent recoverers
+  cannot both delete and recreate the lock file. Post-acquisition token
+  verification ensures the winner still holds the lock after write.
+- Normalized contract-scanner paths across Windows and POSIX platforms and made
+  the verification cwd test independent of Windows short-path spelling.
+- Removed generated directories and redundant parent/child claims from
+  one-command coordination setup.
+
+### Security
+
+- Handoff bundles are limited to 20 project-relative text files, 32 KiB per
+  file and 50 KiB total. Creation and reading reject symlinks, traversal,
+  binary files, and internal `.git/` or `.handoff/` sources; common secrets are
+  redacted before owner-only atomic persistence.
+- Handoff text and completion output are redacted at the canonical write
+  boundary. Verification output is capped at 8 KiB per stream and command
+  execution requires `--run-verification`, is timeout-bounded, project-scoped,
+  and shell-free.
+- Template names are validated before every read or delete so traversal cannot
+  escape `.handoff/templates/`.
+
+## 0.9.0 - 2026-09-03
+
+### Removed
+
+- Model routing (`loadout route`, policy files, model-config routing). The
+  feature was too subjective and prices rotted within weeks. Handoff and the
+  factual coordination protocol replace model-selection advice.
+
+### Changed
+
+- Moved handoff code from `src/core/routing/` to `src/core/delegation/`, and
+  model/credential configuration to `src/core/agents/`. API-access parsing
+  remains in `src/core/routing/access.ts` because it still governs setup choices.
+- Renamed the `loadout-router` first-party skill to `loadout-handoff`, stripped
+  model advice, and focused it on delegation and factual project coordination.
+- All JSON HTTP responses are now streamed through a bounded reader with
+  per-endpoint byte caps and timeouts. Oversized or timed-out responses
+  are rejected before parsing.
+- Release workflow runs `verify:full` (includes coverage) instead of `verify`.
+- npm description and keywords aligned with the project's actual scope.
+
+### Fixed
+
+- Validated every handoff log entry against a strict Zod schema at parse time.
+  Schema-invalid lines are reported as corrupt without hiding valid neighbors.
+- Tracking an existing provider session no longer submits an implicit snapshot
+  turn when automatic delivery is disabled. Provider quota is now spent only by
+  an explicit start/send operation or the opt-in bridge.
+- Coordination tests now exercise Windows with platform-appropriate permission
+  assertions and launch the MCP test process through Node rather than a POSIX
+  package shim.
+
+### Added
+
+- Bounded Claude Code ↔ Codex design rooms via `loadout coord discuss`. The two
+  providers alternate proposal and critique turns on one technical question,
+  then record a linked public transcript, final decision, alternatives, and
+  unresolved disagreement. Fresh and explicit existing sessions are supported.
+- Discussion safety controls: exact preflight turn accounting, 1-8 rounds, a
+  hard paid-turn budget, a bounded per-turn timeout, sequential reply IDs,
+  no-edit/no-tool prompts, singleton bridge ownership, kill-switch checks, and
+  visible failure without silent provider retries.
+
+- Live coordination module (`loadout coordinate`) with typed events for
+  contracts, file ownership, decisions, progress updates, and acknowledgements.
+  Events use monotonic sequence numbers and cursor-based reads so reconnecting
+  agents never miss a message.
+- `loadout serve` starts an MCP server exposing the same coordination tools
+  so both Claude Code and Codex can connect to a shared project coordinator.
+  The MCP runtime is packaged and smoke-tested as a normal dependency.
+- Provider-session bridge commands backed by Claude Code's print-mode CLI and
+  the official Codex SDK. The bridge resumes explicit session IDs and delivers
+  relevant events as follow-up turns at safe boundaries; it does not claim
+  mid-turn injection or shared private context.
+- Bridge safeguards: one process per project, concurrent cross-provider
+  delivery, passive updates, an automatic-turn cap, untrusted-data framing,
+  owner-only session state, and provider responses that are displayed but not
+  persisted.
+- `loadout daemon start` runs a local HTTP coordination server with REST API,
+  SSE push subscriptions, and a live web dashboard showing contracts, file
+  ownership, agent activity, and real-time event feed.
+- Automatic secret redaction — API keys, tokens, passwords, JWTs, and other
+  credentials are stripped from coordination events at the canonical storage
+  boundary before CLI, MCP, or HTTP writes are persisted.
+- Log retention and compaction (`loadout coord compact`) — configurable max
+  events and max age, atomic log rewrite with archived backup.
+- Live file watcher (`loadout coord watch`) detects new coordination events
+  via `fs.watch` with sub-second latency, no daemon required.
+- `loadout coord status` shows a colored terminal overview of ownership,
+  contracts, and acknowledgement state.
+- Conflict preview (`loadout coord conflicts`) — before an agent writes, shows
+  what the other agent changed in the same files with git diffs.
+- Contract diffing (`loadout coord diff`) — auto-generates a structured delta
+  when a contract revision bumps, showing exactly what changed.
+- Coordination replay (`loadout coord replay`) — plays back the full
+  coordination timeline as a formatted narrative story.
+
 ## 0.8.0 - 2026-09-02
 
 ### Security