Coven v0.4.10

Coven v0.4.10

A fresh install can now create its first familiar without Cave, and Copilot
replies reach the stream on Windows.

npm install -g @opencoven/cli@0.4.10
coven doctor

CLI

• coven familiar create <display name> (also coven familiars create) adds
  one familiar to familiars.toml and seeds
  <COVEN_HOME>/workspaces/familiars/<id>/ with starter SOUL.md and
  IDENTITY.md. --id, --emoji, --role and --description are
  optional.
  • The roster is written under an exclusive lock and staged beside the
    original before it is renamed into place. Existing roster bytes and
    workspace files are never changed.
  • A roster that does not parse, cannot take another entry, or already has
    the id is refused and left as it was.
  • --json prints {id, displayName, workspace, created}, or
    {created: false, error: {code, message}} with a non-zero exit. The
    error codes are invalid_argument, invalid_id, familiar_exists,
    roster_invalid, roster_changed and io_error.

Windows

• An attached coven run <harness> --stream-json without a native stream
  bridge discarded the harness's stdout, so Copilot's and external adapters'
  replies never reached the stream. Every harness except Codex now forwards
  both stdout and stderr. Each pipe drains on its own thread. Status and exit
  codes are unchanged. Claude and coven-code were not affected.

Threads

• An unscheduled authority-lane proposal can no longer be approved. Its writer
  label was client-supplied, and a label copied from the disclosed ward
  fingerprint allowed a Tier-1 apply. A new approval is refused with 409
  legacy-authority-approval-unsupported, and the proposal stays pending
  until it is rejected or expires. Scheduled proposals, Tier-0 refusal and
  recovery of an apply that already began are unchanged.

Docs

• docs/HOME-LAYOUT.md describes what the daemon, Cave and familiar
  workspaces create under COVEN_HOME, and how anything is moved. Nothing
  under COVEN_HOME is ever deleted.

Build

• The dependency audit ignores RUSTSEC-2024-0449 (unsafe-libyaml) until
  YAML parsing moves off it.
• CI gives the push-only macOS Rust tests 30 minutes. At 20 they were being
  cancelled after their last suite passed, which failed the PR gate on main.

Certification
Each built-in harness was verified against the tagged commit with
coven setup <harness> --verify-only --report-json:

Harness	CLI	Platform	Commit	Result
claude	2.1.299	macos-aarch64	d6afbffd	completed
codex	0.162.1	macos-aarch64	d6afbffd	completed
copilot	1.0.97	macos-aarch64	d6afbffd	completed