# Changelog

All notable changes to this project will be documented in this file.

Format follows [Keep a Changelog](https://keepachangelog.com/).

## [12.0.8] - 2026-05-13

### Fixed

- tests/test_manifest_config.py: wrap `open(...).write(...)` in `with` blocks so YAML fixture files are closed/flushed before save_culture_yaml writes via `os.replace` (Qodo PR #388 finding #3230365666, Windows reliability).
- tests/telemetry/test_audit_rotation.py: replace `asyncio.sleep(0.05)` with `await sink.queue.join()` for deterministic synchronization on the writer task_done signal (Qodo PR #388 top-level finding, CI race risk).

## [12.0.7] - 2026-05-13

### Added

- Extended `tests/test_persistence.py` with 26 new tests covering `culture/persistence.py` (54% → 98%): `_run_cmd` (success / timeout), `install_service` per platform (macOS launchd plist + Windows .bat + unsupported-platform raise), `uninstall_service` per platform, `list_services` (macOS / Windows / unsupported), `restart_service` per platform including the Windows `schtasks /Query` timeout path.
- Extended `tests/test_manifest_config.py` with 9 new tests covering `archive_manifest_server` / `unarchive_manifest_server` (happy / skip-already-archived / missing-culture-yaml / extra-unrelated-agent) and `_load_legacy_config` (full body + empty-agents).

### Changed

- pyproject.toml: fail_under raised 77 → 79 (Phase 4a floor). Project-wide measured 79.68% — 0.3pp short of the original 80 target; the gap is absorbed by the Phase 7 sweep.
- docs/coverage-baseline.md: Phase 4a entry + updated phase target table (Phase 4 split into 4a + 4b).

## [12.0.6] - 2026-05-13

### Added

- `tests/test_cli_agent.py` — 104 tests covering `culture/cli/agent.py` (47% → 89%): `dispatch`, the four backend config factories (`_create_codex_config`, `_create_copilot_config`, `_create_acp_config`, `_create_default_config`, `_create_agent_config`, parametrized across all four backends), `_parse_acp_command` (default / JSON / split-fallback / rejection branches), `_check_existing_agent` (clean / archived-duplicate / active-duplicate), `_to_manifest_agent`, `_save_agent_to_directory`, `_cmd_create` (per-backend + collision exit), `_cmd_join`, all resolution helpers (`_get_active_agents`, `_resolve_by_nick`, `_resolve_auto`, `_resolve_agents_to_start`, `_resolve_agents_to_stop` including cwd-disambiguation), the `_cmd_start` dispatcher routing, backend daemon factories (`_create_codex_daemon`, `_create_copilot_daemon`, `_create_claude_daemon`, `_coerce_to_acp_agent`, `_make_backend_config`), `_cmd_stop`, `_cmd_status` (all branches), `_cmd_rename` / `_cmd_assign` (every branch), the IPC dispatcher chain (`_resolve_ipc_targets`, `_argparse_error`, `_send_ipc`, `_ipc_to_agents`, plus `_cmd_sleep` / `_cmd_wake` wrappers), `_cmd_learn` (explicit nick / cwd-match / no-match), `_cmd_message` (empty target / empty text / observer-send happy path), `_cmd_read`, `_cmd_archive` / `_cmd_unarchive` / `_cmd_delete`, `_cmd_unregister`. The 5 integration-territory functions (`_probe_server_connection`, `_start_foreground`, `_start_background`, `_run_single_agent`, `_run_multi_agents`) are deliberately skipped — exercised by `tests/test_integration_agent_runner.py` against a real IRCd.

### Changed

- pyproject.toml: fail_under raised 73 → 77 (Phase 3c floor of the 60→90 ratchet plan). Project-wide measured 77.30%.
- docs/coverage-baseline.md: Phase 3c entry + updated phase target table.

## [12.0.5] - 2026-05-13

### Added

- `tests/test_cli_mesh.py` — 54 tests covering `culture/cli/mesh.py` (53% → 99%): `dispatch`, `_collect_mesh_data` (happy + ConnectionRefused/Timeout/OSError exits), `_cmd_overview` (text + clamped messages + serve dispatch), `_cmd_console` deprecation, `_store_mesh_credentials` (keyring hit/miss/store-fail), `_cmd_setup` (uninstall / install / generated fallback / exit on no-mesh), `_find_upgrade_tool` (uv / pip / neither), `_upgrade_timeout_hint`, `_run_upgrade` (success / timeout / non-zero exit), `_upgrade_culture_package` (skip / dry-run / no-tool / exec-reach), `_wait_for_server_port`, `_dry_run_restart`, `_restart_single_service` (service / subprocess fallback / timeout swallow), `_restart_mesh_services` (dry-run / port-down / happy), `_resolve_mesh_for_server`, `_restart_running_servers`, `_restart_from_config`, `_cmd_update`. `_install_mesh_services` (systemd) and the `os.execvp` re-exec body are excluded from coverage.
- `tests/test_cli_server.py` — 54 tests covering `culture/cli/server.py` (21% → 76%): `_resolve_server_name`, `_cmd_default` (running / unknown), `dispatch` (no verb / unknown / agentirc-forwarded / culture verb), `_wait_for_port` (connect / pid dies / timeout), `_maybe_set_default_server` (idempotent), `_check_server_archived`, `_check_already_running`, `_resolve_server_links`, `_wait_for_graceful_stop`, `_force_kill` (POSIX SIGKILL / win32 SIGTERM / ProcessLookupError swallow), `_server_stop`, `_server_status`, `_validate_config_name`, `_update_single_bot_archive`, `_set_bots_archive_state`, `_server_archive`, `_server_unarchive`, `_server_rename` (every branch), `_server_start` (foreground / daemonize routing). Integration-territory functions `_run_foreground`/`_daemonize_server`/`_run_server` are deliberately skipped — covered by `tests/test_integration_irc_transport.py` against a real IRCd.

### Changed

- pyproject.toml: fail_under raised 67 → 73 (Phase 3b floor of the 60→90 ratchet plan). Project-wide measured 73.40%.
- docs/coverage-baseline.md: Phase 3b entry + updated phase target table.

## [12.0.4] - 2026-05-13

### Added

- `tests/test_cli_shared_mesh.py` — 14 tests covering `culture/cli/shared/mesh.py` (25% → 100%): `parse_link` (defaults, explicit trust, password-with-colons, malformed-spec rejection, non-integer-port rejection); `resolve_links_from_mesh` (no peers, builds-per-peer, skips peers without credentials with warning); `generate_mesh_from_agents` (missing `DEFAULT_CONFIG` returns `None`, happy save path); `build_server_start_cmd` (foreground + mesh-config flags, server name/host/port, port stringification).
- `tests/test_cli_bot.py` — 35 tests covering `culture/cli/bot.py` (33% → 99%): `dispatch` (no/unknown command exits, route to list), `_should_include_bot` (owner match, archive filter), `_load_and_filter_bots` (missing dir, unfiltered, owner filter, archive filter, skip dirs without YAML), `_bot_create` (empty-name rejection, owner-prefix rewrite, duplicate rejection, channels/mention rendering), `_bot_start` / `_bot_stop` (unknown bot exits, reload notice), `_bot_list` (empty, owner filter empty, table rendering, archived marker), `_bot_inspect` (unknown exits, full metadata, long-template truncation, archive block), `_bot_archive` / `_bot_unarchive` (round-trip, idempotency, error paths). Filesystem isolated via `tmp_path`-backed `BOTS_DIR`.
- 21 tests appended to `tests/test_channel_cli.py` covering `culture/cli/channel.py` (44% → 99.6%): every `_cmd_*` handler (list/read/message/who/join/part/ask/topic/compact/clear), `_interpret_escapes` (passthrough, n/t, double backslash, unknown escape), `_is_connection_error` classification, `dispatch` OSError wrapping with connection-error hint, `_topic_read` daemon-unreachable exit, `_require_ipc` when daemon responds `None`. Uses a new `_stub_ipc` helper that patches `_try_ipc` / `_require_ipc` at the channel-module boundary, sidestepping the nested-`asyncio.run` conflict that would otherwise dead-lock the existing Unix-socket mock pattern.

### Changed

- pyproject.toml: fail_under raised 62 → 67 (Phase 3a floor of the 60→90 ratchet plan). Project-wide measured 67.89%.
- docs/coverage-baseline.md: Phase 3a entry + updated phase target table (Phase 3 split into 3a + 3b).

## [12.0.3] - 2026-05-13

### Fixed

- tests/test_cli_shared_process.py: pin sys.platform via monkeypatch in SIGKILL-escalation tests and add explicit win32-branch coverage. Addresses Qodo PR #384 finding that the original tests asserted POSIX-only behavior (SIGKILL + sending SIGKILL message) and would fail on Windows. The docstring incorrectly claimed `exclude_lines` prevents runtime execution — `exclude_lines` only affects reporting.

## [12.0.2] - 2026-05-13

### Added

- `tests/test_cli_shared_process.py` — 24 tests covering `culture/cli/shared/process.py` (12% → 100%): `stop_agent` orchestration, `_try_ipc_shutdown` including missing socket / raise / false / poll-exhaustion, `_try_pid_shutdown` including corrupt PID / stale PID / non-culture PID / SIGTERM / SIGKILL escalation / abort-when-no-longer-culture / `ProcessLookupError` mid-kill, `server_stop_by_name` including SIGTERM success / SIGKILL escalation / lookup-error swallow. Fully hermetic: monkeypatches `os.kill`, `time.sleep`, `ipc_shutdown`, and `culture.pidfile.*` — no real signals, sockets, or forks.
- `tests/test_protocol_commands.py` — 3 discovery-style tests covering `culture/protocol/commands.py` (0% → 100%): asserts every uppercase string constant equals its attribute name, and a baseline RFC 2812 smoke test. Adding a new verb does not require a test edit.

### Changed

- pyproject.toml: fail_under raised 60 → 62 (Phase 2 floor of the 60→90 ratchet plan). Project-wide measured 62.91%.
- docs/coverage-baseline.md: Phase 2 entry + updated phase target table.

## [12.0.1] - 2026-05-13

### Fixed

- test.sh: clean stale .coverage* shards before pytest; propagate coverage combine and coverage xml exit codes instead of swallowing them (Qodo PR #383 reviews 3229900166 + 3229900163).

## [12.0.0] - 2026-05-13

### Added

- docs/coverage-baseline.md — Phase 1 entry of the 60→90 ratchet plan, with per-phase target table and notable findings (transport/client.py is largely dead post-extraction; deferred to Phase 5).

### Changed

- [tool.coverage.run] now sets parallel = true, concurrency = ["thread", "multiprocessing"], sigterm = true so pytest-xdist worker shards are merged via coverage combine. Before this, only one worker's slice was reported.
- [tool.coverage.report] exclude_lines extended with raise NotImplementedError, ... (literal ellipsis), and if sys.platform == "win32": to drop legitimately-untestable lines from the denominator.
- fail_under raised from 56 to 60 (Phase 1 floor of the 60→90 ratchet plan). Measured post-Phase-1: 60.99%.
- .claude/skills/run-tests/scripts/test.sh now runs coverage combine + coverage report between pytest-xdist and the final render so xdist shards merge before the floor is checked.

## [11.1.1] - 2026-05-12

### Fixed

- SonarCloud coverage now appears on agentculture_culture main-branch dashboard — Tests workflow now also runs on push to main, mirroring steward. The CI scanner already produces coverage.xml correctly on PR builds (PR #380 reported 60.1% line coverage), but main was never re-scanned after merge, so the project view stayed at 0%.

### Changed

- `publish.yml` no longer has its own `test` job. pytest (with coverage + SonarCloud scan) runs once in `tests.yml` on both pull_request and push:[main]; branch protection makes that the required gate on PRs. Mirrors `agex-cli/.github/workflows/publish.yml` and closes #382. Cuts ~3.5 min of redundant CI per main merge that touches `pyproject.toml` or `culture/**`.

## [11.1.0] - 2026-05-12

### Added

- communicate skill (vendored from steward 0.11.1): new scripts `post-comment.sh` and `fetch-issues.sh`, plus `scripts/templates/skill-update-brief.md`; issue I/O now backed by `agtag>=0.1,<1.0` (added as a runtime dep) — agtag resolves the signing nick from `culture.yaml` so the hard-coded `- culture (Claude)` literal is retired.

### Changed

- cicd skill (vendored from steward 0.12.0): `workflow.sh` now delegates `lint`/`open`/`read`/`reply`/`delta` to `agex pr` (already a culture runtime dep). Culture keeps two extensions on top — `status` (SonarCloud quality gate, OPEN issues, hotspots, unresolved-thread tally via `pr-status.sh`) and `await` (`pr read --wait` + `status`, exits non-zero on Sonar ERROR or unresolved threads). Env var prefix renamed `STEWARD_*` → `CULTURE_*` (`CULTURE_PR_AWAIT_WAIT`, `CULTURE_PR_AWAIT_SECONDS`, `CULTURE_AGEX_AGENT`).
- `culture skills install` materializes the four-script `communicate` skill plus the `scripts/templates/` Markdown brief; `_COMMUNICATE_SCRIPTS` tuple expanded; install machinery + tests updated.
- `culture/learn_prompt.py`'s vendored-skill section now mentions all four scripts (`post-issue.sh`, `post-comment.sh`, `fetch-issues.sh`, `mesh-message.sh`) and notes the agtag-backed signing. The per-agent walkthrough stays hand-coded so it can preserve harness info in the signature (agtag's `(Claude)` suffix is fixed).

### Fixed

- `CLAUDE.md`'s SonarCloud pre-PR-ready guidance now points at `workflow.sh status`/`workflow.sh await` instead of the removed `pr-comments.sh`/`wait-and-check.sh`.

## [11.0.0] - 2026-05-11

### Changed

- Agent harness extracted to sibling `cultureagent` package (consumed at `cultureagent~=0.4.0`). Culture's `culture/clients/<backend>/{config,constants}.py` and `culture/clients/shared/*.py` are now re-export shims forwarding to `cultureagent.clients.*`. Daemon classes are imported directly from `cultureagent.clients.<backend>.daemon`.
- `culture skills install` now reads per-backend `SKILL.md` from the installed `cultureagent` package instead of `culture/clients/<backend>/skill/`.
- Integration tests retargeted to import `SkillClient` from `cultureagent.clients.shared.skill_irc_client` and to import daemon classes from `cultureagent.clients.<backend>.daemon`.

## [10.6.6] - 2026-05-09

### Changed

- `docs/superpowers/specs/2026-05-09-cultureagent-extraction-design.md` status updated from "Design" to "Phase 0a complete; Phase 0b in flight upstream". Added a tracking section listing the Phase 0a integration test PRs (#364–#375) and a link to the Phase 0b kickoff brief on cultureagent ([agentculture/cultureagent#3](https://github.com/agentculture/cultureagent/issues/3)). Phase 0b work itself is tracked on cultureagent's repo per the cross-repo handoff convention; culture's spec only points at the issue.

## [10.6.5] - 2026-05-09

### Added

- `tests/test_integration_agent_runner.py` extended with `test_acp_agent_runner_records_timeout_outcome` — final piece of the Phase 0a Task 8 narrowing follow-up (after PR #374 covered codex + copilot). The wedge mirrors `tests/harness/test_agent_runner_acp.py:237-286`: fakes `asyncio.create_subprocess_exec` (returns a `_FakeACPProcess` stand-in), hangs `_read_loop`/`_stderr_loop` so no `session/update` notifications arrive, monkeypatches `_send_request` to fake `initialize`/`session/new` so `runner.start()` succeeds, then patches `_send_prompt_with_retry` to return immediately and `_handle_prompt_result` to hang on `Event().wait()` — the busy-poll wedge that the outer `asyncio.timeout` defends against (issue #349's failure mode). Adds `_build_acp_daemon` helper and `_FakeACPProcess` class parallel to the codex ones. Replaces the integration-shaped portion of the harness unit test (which moves to cultureagent in Phase 1). Closes Phase 0a Task 8 — all four backends (claude/codex/copilot/acp) now have integration coverage on the timeout outcome.

## [10.6.4] - 2026-05-09

### Added

- `tests/test_integration_agent_runner.py` extended with two new tests for Phase 0a Task 8 narrowing follow-up — pre-handover integration coverage of the timeout path on the codex and copilot backends: `test_codex_agent_runner_records_timeout_outcome` (fakes `asyncio.create_subprocess_exec`, hangs `_read_loop`, monkeypatches `CodexAgentRunner._send_request` so `turn/start` returns but `turn/completed` never fires; outer `asyncio.timeout` wraps the wedged `_turn_done.wait()` and triggers `outcome=timeout` on `culture.harness.llm.calls`) and `test_copilot_agent_runner_records_timeout_outcome` (post-`daemon.start()` mutation of `daemon._agent_runner._session.send_and_wait` to a never-resolving coroutine; `asyncio.wait_for` fires its outer timeout). Replaces the integration-shaped portion of the harness unit tests in `tests/harness/test_agent_runner_{codex,copilot}.py` (which move to cultureagent in Phase 1). Adds `_build_codex_daemon` and `_build_copilot_daemon` helpers parallel to the existing claude `_build_daemon`, plus a per-file `copilot` SDK stub at module top mirroring `tests/harness/test_agent_runner_copilot.py:32-69` so CI works without the `copilot` package installed.

## [10.6.3] - 2026-05-09

### Fixed

- `AgentDaemon.stop()` across all four backends (`claude`, `codex`, `copilot`, `acp`) now cancels and awaits any tasks scheduled into `self._background_tasks` (most importantly `_delayed_restart` from `_on_agent_exit`, plus `_send_channel_poll`/`_on_mention`/`_on_roominvite`/`_ipc_shutdown` tasks) before tearing down the agent runner. Previously these tasks could outlive `stop()` — `_delayed_restart` in particular sleeps `CRASH_RESTART_DELAY` and would either restart a daemon mid-teardown or leak past test boundaries (PR #369 review #2 follow-up). The cancel loop excludes `asyncio.current_task()` because `_ipc_shutdown` schedules `_graceful_shutdown` onto `_background_tasks`, and `_graceful_shutdown` awaits `self.stop()` when no external `_stop_event` is registered — so `stop()` can run inside one of these tracked tasks, and self-cancelling would abort the rest of teardown. Insertion is identical across all four daemons; the reference at `packages/agent-harness/daemon.py` was updated in lockstep so future backends start from the fixed version.

### Changed

- `tests/test_integration_agent_runner.py` — removed the `_no_restart` monkeypatch mitigation and its docstring/comment references. The fix above makes the stub unnecessary: tests can use the real `_on_agent_exit` and `daemon.stop()` cleans up the resulting `_delayed_restart` task.

## [10.6.2] - 2026-05-09

### Added

- `tests/test_integration_agent_runner.py` extended with two new tests for Phase 0a Task 8.5(b) — pre-handover coverage of the `AgentRunner._process_turn` success and error branches at integration shape: `test_claude_agent_runner_records_success_outcome` (fake `query` yields `ResultMessage` with usage; asserts `outcome=success` on `culture.harness.llm.calls` and 100/200 on `tokens.input`/`tokens.output`) and `test_claude_agent_runner_records_error_outcome` (fake `query` raises `RuntimeError`; asserts `outcome=error` and stubs `_on_agent_exit` to prevent `_delayed_restart` task leak — same mitigation as the timeout test). Lifts `culture/clients/claude/agent_runner.py` to **79%** from this single file alone. Generalized `_wait_for_timeout_metric(reader)` → `_wait_for_outcome_metric(reader, outcome)` and added `_find_data_point(reader, name, attrs)` helper.

### Changed

- `tests/test_integration_agent_runner.py` — refactored: extracted `_build_daemon` and `_no_restart` helpers shared by all three tests; existing timeout test updated to use the renamed `_wait_for_outcome_metric(metrics_reader, "timeout")` and the shared `_no_restart` stub.

## [10.6.1] - 2026-05-09

### Added

- `tests/test_integration_skill_client.py` — Phase 0a Task 8.5(a): pre-handover integration coverage for `SkillClient`. Four tests drive the verbs not yet covered by `tests/test_integration_layer5.py`: `irc_who`, `irc_topic` (set + get modes), supervisor whisper dispatch (via `daemon._socket_server.send_whisper`) → `SkillClient.pending_whispers` / `drain_whispers()`, and the `close()` cleanup branch (pending requests resolved with `ConnectionError`). Lifts `culture/clients/claude/skill/irc_client.py` from 54% → **~87% on the class itself** (61% headline including the explicitly out-of-scope CLI helpers in lines 189-318). Adopts Tasks 2/3/6's hardening (`tmp_path` sock_dir, monkeypatched `PID_DIR`, bounded polls). Replaces the integration-shaped portion of `tests/test_skill_client.py` (the unit test moves to cultureagent in Phase 1; this file stays as the contract test for culture's daemon ↔ skill IPC surface). `compact` / `clear` SkillClient verbs require a real claude SDK turn — covered by Task 8.5(b) follow-up.

## [10.6.0] - 2026-05-09

### Added

- Phase 0a closeout — coverage baseline doc updated with measured per-domain numbers and a closeout section. Audit doc footer filled with final percentages and follow-up list. `culture/clients/shared/` covered to 80% (+22pp via Phase 0a integration tests #364–#369); project-wide at 56.96% (gate stays at 56 since unit tests still cover the same paths; they delete in Phase 1).

### Changed

- `pyproject.toml`'s `[tool.coverage.report]` comment refreshed to reflect Phase 0a closeout. `fail_under` value unchanged at **56** (matches `floor(56.96)` measured project-wide); the project-wide number didn't move materially because the harness unit tests still cover the same code paths the new integration tests exercise.
- `docs/coverage-baseline.md`: per-domain table now shows measured-actuals; closeout section appended; SonarCloud project-key reference updated from legacy `OriNachum_culture` to current `agentculture_culture`.

## [10.5.12] - 2026-05-09

### Added

- `tests/test_integration_agent_runner.py` — Phase 0a Task 8 (claude only): end-to-end integration coverage for `AgentRunner._process_turn`'s timeout path. Drives the full `AgentDaemon` → `AgentRunner` → `_run_loop` → `_process_turn` chain with a hanging `claude_agent_sdk.query` and `turn_timeout_seconds=0.2`, then asserts via `metrics_reader` that the `culture.harness.llm.calls` counter records a `outcome=timeout` data point with `backend=claude`. Adopts Tasks 2/3/4/5/6 hardening (`tmp_path`, monkeypatched `PID_DIR`, `_invalidate_harness_telemetry_cache`, bounded `_wait_for_timeout_metric` poll). Includes self-contained `claude_agent_sdk` stubs so CI runs without the real SDK installed. The harness unit test in `tests/harness/test_agent_runner_claude.py` will move to cultureagent in Phase 1; the audit's "parameterize over 4 backends" ask is narrowed to claude only for this PR, with codex/copilot/acp coverage tracked as a follow-up (each backend has a different SDK injection point — bundling all four would mix scope).

## [10.5.11] - 2026-05-09

### Added

- `tests/test_integration_telemetry.py` — Phase 0a Task 6: end-to-end integration coverage for harness telemetry. Two tests: (1) daemon start emits the `harness.irc.connect` span with `harness.nick`/`harness.server`/`harness.backend` attrs; (2) a direct `@mention` IDLE→HOT transition increments the `culture.attention.transitions` counter with matching `from_band`/`to_band`/`cause`/`agent`/`target` attributes. Uses the conftest `tracing_exporter` (`InMemorySpanExporter` + `SimpleSpanProcessor`) and `metrics_reader` (`InMemoryMetricReader`) fixtures directly — no harness-side telemetry reset is needed since the fixtures' server-side resets clear globals and `init_harness_telemetry` resolves the test providers via OTel proxy. Adopts Tasks 2/3/4/5 hardening (`tmp_path`, monkeypatched `PID_DIR`, bounded `_wait_for_daemon_joined` and `_wait_for_band` polls). The harness unit tests in `tests/harness/test_telemetry_module.py` and `tests/harness/test_daemon_telemetry.py` will move to cultureagent in Phase 1.

## [10.5.10] - 2026-05-09

### Added

- `tests/test_integration_webhook.py` — Phase 0a Task 5: end-to-end integration coverage for webhook HTTP fanout. Daemon configured with `WebhookConfig(url=<local-capture>)`, real human IRC client, then `skill.irc_ask("#general", ...)` IPC call fires the `agent_question` `AlertEvent`. A stdlib `HTTPServer` thread captures the JSON POST and the test asserts the payload shape (`{"content": "[QUESTION] [testserv-bot] asked in #general: ..."}`). Adopts Tasks 2/3/4 hardening (`tmp_path`, monkeypatched `PID_DIR`, bounded `_wait_for_daemon_joined` and `_wait_for_capture` polls). Lifts `culture/clients/shared/webhook.py` coverage to 89% from this file alone. The harness unit test in `tests/test_webhook.py` will move to cultureagent in Phase 1; the IRC alert channel path is already covered at integration shape by `tests/test_integration_layer5.py::test_webhook_fires_on_question`, so no daemon-level duplicate.

## [10.5.9] - 2026-05-09

### Added

- `tests/test_integration_irc_transport.py` — Phase 0a Task 4: end-to-end integration coverage for IRC transport's IRCv3 inbound traceparent propagation. Sends `@culture.dev/traceparent=<valid> PRIVMSG #general :traced hello` from a real human IRC client, verifies via the `tracing_exporter` fixture that `IRCTransport._handle` emits a `harness.irc.message.handle` span with `culture.trace.origin: "remote"` and a `trace_id` matching the inbound traceparent. Adopts Tasks 2/3 hardening (`tmp_path` for sock_dir, monkeypatched `culture.pidfile.PID_DIR`, bounded `_wait_for_daemon_joined` and `_wait_for_span` polls). The harness unit test in `tests/harness/test_irc_transport_propagation.py` will move to cultureagent in Phase 1; reconnect coverage is already provided at integration shape by `tests/test_irc_transport.py::test_reconnect_retries_after_connection_error`, so Task 4's reconnect ask is met without a new test.

## [10.5.8] - 2026-05-09

### Added

- `tests/test_integration_message_buffer.py` — Phase 0a Task 3: end-to-end integration coverage for the per-channel message buffer ring-buffer. Floods 2× `buffer_size` (10) PRIVMSGs to `#general` through real `agentirc.IRCd` and asserts via `SkillClient.irc_read` IPC that exactly `buffer_size` messages remain (deque `maxlen` cap), the most-recent message survives, and the oldest is evicted. Uses the same hardening pattern as Task 2 (`tmp_path` for sock_dir, monkeypatch `culture.pidfile.PID_DIR`, bounded `_wait_for_buffer_total` poll on `daemon._buffer._totals` instead of fixed sleeps). Lifts `culture/clients/shared/message_buffer.py` coverage to 72% from this file alone. The harness unit test in `tests/test_message_buffer.py` will move to cultureagent in Phase 1.

## [10.5.7] - 2026-05-09

### Added

- `tests/test_integration_attention.py` — Phase 0a Task 2: end-to-end integration coverage for attention behaviors. Three tests prove `Band.HOT` promotion via direct `@mention` (asserted via a bounded `_wait_for_band` poll, not a fixed sleep), exact one-step decay past `hold_s` with `attention_overrides` (`hold_s=2`/`tick_s=2`/sleep=3.0s leaves remaining elapsed ≤ hold so the decay loop terminates deterministically at `Band.WARM`), and per-channel state divergence under different stimuli. Uses `tmp_path` for socket dirs and monkeypatches `culture.pidfile.PID_DIR` so test runs don't write into the real `~/.culture/pids`. Exercises the full `AgentDaemon` → `IRCTransport` → `AttentionTracker` chain through real `agentirc.IRCd`. Lifts `culture/clients/shared/attention.py` coverage to 72% from this file alone (vs. 0% integration-only baseline). The harness unit test in `tests/harness/test_attention.py` will move to cultureagent in Phase 1.

## [10.5.6] - 2026-05-09

### Fixed

- Phase 0a plan Task 2 (attention) — replaced fictional `Band.ACTIVE_RECENT`/`Band.PASSIVE` constants and `daemon.attention.current_band()` with real API: `Band.HOT`/`WARM`/`COOL`/`IDLE` from `culture/clients/shared/attention.py`, `daemon._attention.snapshot()`, `attention_overrides: dict | None` on `DaemonConfig`. Original snippet would have failed at write time (Qodo bug #1 on PR #363).
- Phase 0a plan Task 7 (supervisor) — **dropped entirely**. Original framing ("kill the daemon, observe restart") was based on a misreading of `culture/clients/<backend>/supervisor.py`, which is the LLM verdict evaluator (`Supervisor` class with `evaluate()`, `SupervisorVerdict.parse()`, `make_sdk_evaluate_fn`), not a process supervisor. Unit tests in `tests/test_supervisor.py` are the right shape and move to cultureagent in Phase 1. Audit row #10 updated from ADD integration → ACCEPT (12/7/1/1 split). Audit recommendation #2 (parameterize Task 7) marked moot. Spec's behavior list updated to match. (Qodo bug #2 on PR #363.)
- Phase 0a plan Task 9 Step 0a — `--cov=culture/clients/claude/skill/irc_client` (broken — missing `.py`, mixed-form path) → `--cov=culture.clients.claude.skill.irc_client` (dotted module form, consistent with the rest of the plan). (Qodo bug #3 on PR #363.)
- Phase 0a plan Task 9 Step 7 — branch name `chore/coverage-gate-95-percent` and commit/PR title containing "95% coverage gate" were stale from before the ratchet-from-locked-baseline reframing. Updated to `chore/coverage-gate-phase0a-closeout` and "ratchet pytest fail_under to post-Phase-0a measured floor", consistent with Step 2's branch name and Task 9's stated goal. (Qodo bug #4 on PR #363.)

## [10.5.5] - 2026-05-09

### Added

- `docs/superpowers/specs/2026-05-09-cultureagent-extraction-design.md` — design spec for extracting culture's agent harness into a sibling `cultureagent` repo. Mirrors the agentirc extraction pattern at the next layer of the stack (B re-export shim end-state, three-phase rollout, brief-only cross-repo handoff).
- `docs/superpowers/plans/2026-05-09-cultureagent-extraction-phase-0a.md` — implementation plan for Phase 0a (pre-cutover test reinforcement). Nine tasks: audit, seven integration tests across attention/message buffer/IRC transport/webhook/telemetry/supervisor/agent_runner, then a closeout that ratchets `[tool.coverage.report] fail_under` toward the post-Phase-0a measured floor.
- `docs/superpowers/notes/2026-05-09-cultureagent-coverage-audit.md` — Phase 0a coverage audit. 21 gap rows with line-range mappings; baseline 56.86% project-wide, 15.95% integration-only.

### Changed

- Audit doc updated post-PR-#362: added a "Status update" header section, replaced TL;DR top-line/secondary findings with RESOLVED-in-#362 annotations, marked Recommendations #1, #3 as resolved (SonarCloud scanner wired; threshold scoping resolved with locked-floor-and-ratchet shape), marked Recommendations #2, #4, #5 as APPLIED IN THIS PR.
- Phase 0a plan updated:
  - Task 6 (telemetry) — replaced fuzzy `"send" in n.lower()` substring assertions with exact-name assertions and a Step 1.5 that reads `culture/clients/shared/telemetry.py` for canonical constant names. Implements audit recommendation #4.
  - Task 7 (supervisor restart) — parameterized over all 4 backends (claude/codex/copilot/acp) via a `BACKEND_MODULES` dict mirroring Task 8, so non-claude supervisors don't stay at 0% under integration-only. Implements audit recommendation #2.
  - Task 9 (closeout) — added Step 0a row #20 verification (re-measures `irc_client.py` coverage; if <80% adds Task 8.5 before the gate flip, per audit recommendation #5). Dropped the "wire SonarCloud first" prerequisite (now resolved by PR #362). Updated threshold language from `--cov-fail-under=95` to the ratchet-from-locked-baseline shape that PR #362 actually shipped.
- Spec Phase 0a closeout language reconciled with PR #362: `fail_under = 56` is the locked baseline, ratchets toward ~73 project-wide / ~85 on `culture/clients/`. `--cov-fail-under` is enforced via `[tool.coverage.report]`, not a separate workflow flag.

## [10.5.4] - 2026-05-09

### Fixed

- `sonar-project.properties`: project key migrated from the old personal-account `OriNachum_culture` to the org-aligned `agentculture_culture` and `sonar.organization=agentculture` added. The first SonarCloud Scan run on PR #362 failed with `ERROR You must define mandatory properties for 'OriNachum_culture': sonar.organization` — this is the fix.
- `sonar-project.properties`: dropped `sonar.python.bandit.reportPaths` and `sonar.python.pylint.reportPaths`. Those report files are produced by `security-checks.yml`, not the `tests` job that runs the SonarCloud scan; configuring them in tests' scan would have produced scanner warnings on every analysis (Qodo bug #2). Aligns with steward's properties shape.
- `sonar-project.properties`: added `sonar.qualitygate.timeout=600` so a slow/unavailable SonarCloud doesn't hang CI indefinitely (Qodo bug #3). Default behavior of `qualitygate.wait=true` has no built-in timeout.
- `docs/coverage-baseline.md` and `pyproject.toml` `[tool.coverage.report]` comment: removed the dead link to `docs/superpowers/notes/2026-05-09-cultureagent-coverage-audit.md` (the audit doc lands in a follow-up PR; baseline doc is now self-contained for the rationale of `fail_under = 56`) (Qodo bug #1).

### Changed

- `sonar.exclusions` now also excludes `.claude/skills/cicd/**` — these scripts are vendored verbatim from steward (cite-don't-import seam at the skill boundary), so stylistic findings (29 `shelldre:S7688` "use `[[`" hits in this PR's analysis) belong upstream in steward, not forked here.

## [10.5.3] - 2026-05-09

### Added

- `workflow.sh` consolidated entry point in `.claude/skills/cicd/scripts/` — single dispatcher for `lint`, `open-pr`, `poll`, `poll-readiness`, `wait-after-push`, `await`, `reply`. Vendored verbatim from steward 0.7's cicd skill.
- `portability-lint.sh` — catches absolute `/home/<user>/` paths and per-user dotfile references in committed docs/configs. Default mode lints the current diff only, so existing leaks in culture's docs are grandfathered; new leaks fail the lint.
- `pr-status.sh` — one-shot PR overview: state, CI checks, review-bot pipeline, SonarCloud quality gate + issue count, inline-thread resolved tally.
- `poll-readiness.sh` — wait until automated reviewers (qodo) finish posting, the PR closes, or an iteration cap is hit. Used by `workflow.sh await`.
- `_resolve-nick.sh` — resolves the agent nick from `<repo-root>/culture.yaml` (first agent's `suffix`) with a fallback to the repo basename. Used by `pr-reply.sh` to auto-sign replies as `- <nick> (Claude)`.

### Changed

- `pr-reply.sh` re-cited from steward verbatim. Replies now auto-sign as `- <nick> (Claude)` (e.g. `- culture (Claude)`) via `_resolve-nick.sh`. Drops the previous `# culture-divergence:` that hard-coded `- Claude` — the divergence is resolved upstream now.
- `.claude/skills/cicd/SKILL.md` Step 8 updated for the new auto-signing behavior: reply bodies should NOT include a `- Claude` signature (the script appends `- <nick> (Claude)` automatically). Script reference table adds the four new scripts.

## [10.5.2] - 2026-05-09

### Added

- SonarCloud scanner step in `.github/workflows/tests.yml` — analyses now upload on every PR using the `SONAR_TOKEN` secret. `qualitygate.wait=true` (already in `sonar-project.properties`) blocks CI until the gate decides. Fork PRs without access to the secret skip the scan via `if: env.SONAR_TOKEN != ''`.
- `docs/coverage-baseline.md` documenting the locked baseline (project-wide 56.86% measured 2026-05-09) and the per-domain growth path through Phase 0a of the cultureagent extraction.

### Changed

- `[tool.coverage.report] fail_under` in `pyproject.toml` raised from `50` → `56` to lock the audit-measured floor (see `docs/coverage-baseline.md`). Each Phase 0a integration-test PR will ratchet this further.
- `tests.yml` checkout step now uses `fetch-depth: 0` for SonarCloud blame attribution.

## [10.5.1] - 2026-05-09

### Fixed

- Vendor steward's SonarCloud-aware `pr-comments.sh` into `.claude/skills/cicd/scripts/`. SonarCloud's new issues now appear as section 4 of the script's output. Removes references to the not-installed `/sonarclaude` skill from the cicd skill (Step 9) and `CLAUDE.md` (Git Workflow); the in-script section is the canonical surface now.

## [10.5.0] - 2026-05-09

### Added

- `culture/clients/shared/` — shared-by-import tier for backend-agnostic harness modules (`attention`, `message_buffer`, `ipc`, `telemetry`, `irc_transport`, `socket_server`, `webhook`, `webhook_types`). Eliminates ~3880 lines of cite-don't-import duplication. Tracks #357. See `docs/architecture/shared-vs-cited.md` for the tier rule and fork-back procedure.
- `tests/harness/test_no_per_backend_copy_of_shared_modules.py` — guard test against re-citing a shared module without following the fork-back procedure.

### Changed

- `WebhookConfig` lifted from each backend's `config.py` into `culture/clients/shared/webhook_types.py`; per-backend re-export keeps `from culture.clients.<backend>.config import WebhookConfig` working.
- `tests/harness/test_all_backends_parity.py` no longer watches the 7 moved modules; only `daemon.py`, `config.py`, `constants.py` remain in the parity matrix.
- `acp/socket_server.py`: added 4 missing comment/docstring lines so it agrees with the other backends.
- OTel tracer name is now `culture.harness` for all four backends (was `culture.harness.<backend>`). Backend identity moves to OTel Resource `service.name` (already set per-backend via `TelemetryConfig.service_name`). External consumers querying spans by tracer name should query by `service.name` instead.
- `claude/codex/acp webhook.py`: adopted copilot's `with urllib.request.urlopen(req, timeout=10) as resp: resp.read()` form so the response is closed on every backend.

## [10.4.3] - 2026-05-09

### Fixed

- Tests that explicitly used `poll_interval=N` to drive the legacy fast poll loop (test_poll_loop, test_acp_daemon, test_codex_daemon, test_copilot_daemon, test_mention_target_cleanup) hung under the new attention defaults because the tick-based loop fires every 5s, slower than their <2s timing assumptions. Each affected DaemonConfig now also passes `attention=AttentionConfig(enabled=False)` so they continue to exercise the legacy poll path. (#345 / PR #356)

## [10.4.2] - 2026-05-09

### Changed

- Refactored `_poll_loop` and `_parse_bands` to drop SonarCloud cognitive complexity below 15 (from 21 and 17 respectively). `_poll_loop` now delegates to `_tick_attention_poll` and `_poll_due_target` helpers; `_parse_bands` extracts a `_parse_band_entry` helper for the per-band parse + validate. No behavioral change. Propagated to all four backends. (#345 / PR #356)

### Fixed

- Replaced floating-point equality (`last == 0.0`) in `_on_ambient` with a membership check (`target not in self._last_engaged_at`). Cleaner intent and silences SonarCloud S1244. Propagated to all four backends. (#345 / PR #356)

## [10.4.1] - 2026-05-09

### Fixed

- Quiet channels never polled when attention enabled — daemon now seeds the AttentionTracker with all configured `agent.channels` at startup so they are due at their IDLE cadence even before any stimulus arrives (#345 / PR #356).
- Default `poll_interval` regression — configs that omit both `attention:` and `poll_interval` now correctly use the legacy 60s default for IDLE polling, not the new 600s default. HOT/WARM/COOL still clamp to ≤ legacy. (#345 / PR #356)

## [10.4.0] - 2026-05-09

### Added

- Dynamic per-target attention bands (HOT/WARM/COOL/IDLE) for agent polling. Direct stimuli (@mention, DM) promote to HOT; ambient channel traffic in active threads promotes one band warmer (capped at WARM); quiet targets decay one band per hold window down to IDLE. New `attention:` config block in `~/.culture/server.yaml` with per-agent overrides in `culture.yaml`. (#345)
- Pure `AttentionTracker` state machine in `packages/agent-harness/attention.py`, cited byte-identically into all four backends.
- New transport callbacks `IRCTransport.on_ambient` and `IRCTransport.on_outgoing` for ambient-message and outgoing-send hooks.
- OTel counters `culture.attention.transitions` and `culture.attention.polls` with cause/band/agent/target attributes.

### Changed

- Daemon poll loop is now tick-driven (`attention.tick_s`, default 5s) when `attention.enabled: true` (default). Falls back to fixed-interval `_legacy_poll_loop` when `attention.enabled: false`.
- Legacy `poll_interval` migrates into `attention.bands.idle.interval_s` when no `attention:` block is configured; HOT/WARM/COOL also clamp to ≤ `poll_interval` so quiet channels never poll slower than the legacy default. Existing deployments get faster polling when tagged for free.
- `IRCTransport._detect_and_fire_mention` now returns `bool` so the privmsg handler routes ambient-vs-direct paths correctly without double-firing.

## [10.3.9] - 2026-05-08

### Changed

- Pulled `agent_runner` timeout magic numbers (600 / 120 / 30 /
  300 / 5 / 1) into per-backend `constants.py` modules + a
  project-wide `culture/_constants.py` for the cross-backend
  default. Behavior is byte-identical; first step toward a
  YAML-driven runtime config so users can override these via
  `~/.culture/server.yaml` (follow-up).
- New files: `culture/_constants.py`,
  `culture/clients/{claude,codex,copilot,acp}/constants.py`,
  `packages/agent-harness/constants.py`.
- Edited 8 source files (4 `agent_runner.py` + 4 `daemon.py`)
  plus `culture/config.py` and `packages/agent-harness/config.py`
  to import named constants instead of carrying literals.

## [10.3.8] - 2026-05-08

### Added

- `turn_timeout_seconds` field on the `culture.yaml` `AgentConfig`
  schema (default `600`). Each backend's `agent_runner.py` wraps
  turn execution in `asyncio.wait_for` / `asyncio.timeout`. On
  expiry the runner records `outcome=timeout` and exits 1, letting
  the existing crash-recovery in `daemon._on_agent_exit` +
  `_delayed_restart` (5 s delay, max 3 in 300 s) handle restart
  cleanly. Set `0` to disable. Closes #349.
- All four backends (claude, codex, copilot, acp) plus
  `packages/agent-harness/` template grew the field. Claude
  previously had no timeout — the bug. Codex previously hardcoded
  300 s on the event-wait alone; the wrap is now config-driven and
  covers `_send_request` too. Copilot keeps its inner 120 s on
  `send_and_wait` and adds the outer wrap. ACP keeps the inner
  300 s on `_send_request` and adds an outer wrap covering the
  whole prompt round-trip including the busy-poll.
- `docs/reference/server/config.md`: new `turn_timeout_seconds` row
  in the `culture.yaml` fields table.
- `tests/harness/test_agent_runner_*.py`: 5 new tests across the
  four backends covering timeout-fires-on-wedge (claude, codex,
  copilot, acp) and timeout-disabled-when-zero (claude) paths.

## [10.3.7] - 2026-05-08

### Changed

- `culture mesh setup` no longer writes per-workdir
  `<workdir>/.culture/agents.yaml` files. Since PR #344 dropped the
  legacy `--config` pin from generated systemd units, those files
  were orphan writes that confused operators inspecting them.
  Companion cleanup: `_generate_agent_configs` (was at
  `culture/cli/mesh.py:260-296`), its call from `_cmd_setup`, and
  the `CULTURE_DIR` / `AGENTS_YAML` constants in
  `culture/cli/shared/constants.py` are gone. Closes #347.

## [10.3.6] - 2026-05-08

### Added

- Track repo-root `culture.yaml` as the canonical declaration of
  culture's persistence agent (`<server>-culture`). Mirrors the
  pattern already established at `packages/agent-harness/` and
  `culture/clients/<backend>/`. The `system_prompt` was rewritten to
  be host-agnostic (`<server>-culture`, "this repo's working
  directory") so the file ports cleanly across hosts.
- `docs/reference/server/config.md`: new subsection on the repo-root
  vs sub-directory `culture.yaml` convention, explaining that
  `culture.yaml` at repo root is tracked alongside `CLAUDE.md` and
  declares intent (registration is still explicit via
  `culture agent register`).
- `.gitignore`: exclude `/culture.yaml.*-bak` per-host backups
  (e.g. `culture.yaml.daria-acp-bak` from the cleanup runbook in
  10.3.5's recovery docs).

### Fixed

- `tests/test_archive.py::test_cli_create_replaces_archived_agent`:
  add `monkeypatch.chdir(tmpdir)` so the test no longer leaks
  `os.getcwd()` into `_create_acp_config`. Without the fix, running
  the suite from the repo root caused `_save_agent_to_directory` to
  overwrite the real `culture.yaml` at the project root with a
  multi-agent merge (the new tracked file made the regression
  impossible to ignore).

## [10.3.5] - 2026-05-08

### Fixed

- `culture/cli/mesh.py`: stop generating systemd units that pin
  `--config <workdir>/.culture/agents.yaml`. Three call sites
  (`_install_mesh_services`, `_cmd_update`'s service rewrite,
  `_cmd_update`'s service-fallback restart helper) emitted `ExecStart`
  pointing at a path culture migrated away from when per-directory
  `culture.yaml` became the format. On real deployments the daemon
  exited 1 immediately and systemd respawned every 5s — restart
  counters reached 38000+. Now generated units are
  `culture agent start <nick> --foreground`, with `--config` defaulting
  to `~/.culture/server.yaml` via argparse. New regression test in
  `tests/test_setup_update_cli.py` asserts the absence of `--config`
  and any `.culture/agents.yaml` token in the generated agent argv.
  Recovery runbook for stale pre-10.3.5 units at
  `docs/reference/cli/agent-systemd.md`.

## [10.3.4] - 2026-05-08

### Changed

- docs/reference/cli/console.md: document the new first-run auto-init behavior and the opt-out paths (--config or pre-existing default path).

### Fixed

- culture/cli/console.py: auto-init irc-lens default config on first run when --config is not supplied. Bridges the irc-lens 0.5.x serve-requires-config contract so culture console <server> works on a fresh machine instead of dying with a cryptic no-config error (qodo PR #343 review). Skipped when --config is passed explicitly (user-managed) or when the default path already exists.
- tests/test_cli_console_playwright.py: tighten irc-lens config init subprocess — add 30s timeout, surface stdout/stderr on failure via pytest.fail, and assert the config file exists post-init (qodo PR #343 review).

## [10.3.3] - 2026-05-08

### Changed

- Bumped irc-lens floor from >=0.4.2 to >=0.5.1; refreshed uv.lock to 0.5.1.
  culture console inherits the 0.5.x surface: per-user Session registry,
  Cloudflare Access JWT middleware, `irc-lens config init`, default
  `--host`/`--port`, console-parity verbs in the web UI, and view promotion
  on `/channels` `/who` `/agents`.

### Fixed

- `tests/test_cli_console_playwright.py`: materialize a tmp irc-lens config
  via `python -m irc_lens config init --path` and pass `--config` through
  to the `serve` subprocess. irc-lens 0.5.x requires an explicit config
  file before `serve` will bind; without this the e2e test errored with
  `no config at ~/.config/irc-lens/config.yaml`.

## [10.3.2] - 2026-05-06

### Added

- version-bump skill: vendored from steward into .claude/skills/version-bump/ so script-form bump.py invocations resolve in-repo
- cicd skill: add opt-in --push flag to create-pr-and-wait.sh that runs git push -u origin HEAD before gh pr create, eliminating the separate push step

### Fixed

- cicd skill: vendor pr-comments.sh, pr-reply.sh, pr-batch.sh from steward into .claude/skills/cicd/scripts/ (issue #318)
- cicd skill: replace create-pr-and-wait.sh with steward version that uses --body-file + tempfile, fixing argv-truncation on large PR bodies
- cicd skill: drop broken ~/.claude/skills/pr-review/ fallback branches in create-pr-and-wait.sh and wait-and-check.sh
- cicd skill: update SKILL.md to reference project-local script paths everywhere

## [10.3.1] - 2026-05-06

### Changed

- **`culture channel message` no longer auto-creates channels on typo** (#331). `culture channel message '#nonexistnt' "..."` previously silently spawned an orphan channel that nobody else ever joined while confidently printing `Sent to #nonexistnt`. The CLI now refuses to send to channels not in the active list and points at `culture channel list` for verification. Pass `--create` to opt into the legacy behavior for bootstrap workflows (`culture channel message --create '#new-room' "kickoff"`).
- **`culture agent message` no longer treats local config as the source of truth** (#333 item 11). The previous behavior refused to send when the target nick was missing from local `server.yaml`, which broke DMs to agents reachable via federation. The local-config gate is removed; the send is delegated to the IRC server, and `401 NOSUCHNICK` propagates if the nick truly isn't on the mesh.
- **`culture agent sleep`/`wake` usage errors now use argparse formatting** (#333 item 12). Missing-arg, conflicting-arg, and unknown-nick errors previously went to stdout via `print()` + `sys.exit(1)`, inconsistent with every other CLI verb. They now write `culture agent sleep: error: ...` to stderr with rc 2, matching argparse's standard usage-error path.
- **`culture agent migrate --help` text now signals it's a one-time op** (#333 item 7). Help reads `Migrate legacy agents.yaml to server.yaml + culture.yaml (one-time, usually a no-op)` instead of advertising it as routine. The verb stays in the CLI surface for completeness — most repos have already migrated.
- **Channel-existence guard now uses the server-wide `LIST` query** (#341 review). Earlier draft of the #331 guard read the daemon's `irc_channels` IPC, which only returns the daemon's _joined_ channels — false-rejecting valid channels the daemon hadn't joined. The guard now always uses the observer's `list_channels()` (a fresh peek `LIST`) regardless of IPC availability.

### Deprecated

- **`culture mesh console` is scheduled for removal** (#333 item 6). The verb has been marked DEPRECATED in `--help` since culture 8.x; use `culture console` instead. The deprecated verb will be removed in a future minor release.

## [10.3.0] - 2026-05-06

### Changed

- **Peek-client nicks now embed the calling agent's identity** (#329). The ephemeral IRC connection that backs `culture channel message`, `culture channel read`, and `culture agent message` previously registered as `<server>-_peek<hex>` — opaque to other agents on the mesh, breaking message attribution. When `CULTURE_NICK` is set and shares the observer's server prefix, the peek nick is now `<server>-<agent>__peek<hex>` (e.g. `spark-claude__peek7aef`). The opaque `<server>-_peek<hex>` form still applies when no parent is known or the parent is from a different server, and the `USER` realname always carries the parent (e.g. `:culture observer (parent=spark-claude)`) so WHOIS resolves attribution in both cases. Four agents on the spark mesh independently flagged the previous behavior as their #1 day-to-day UX friction.
- **The bundled `welcome` system bot now skips peek-client joins** (#334). The filter is `"type == 'user.join' and not ('_peek' in nick)"`, which covers both the legacy `_peek` and new `__peek` shapes via the substring check. Greeting peek joins produced four lines of bot chatter per single CLI message — a 5:1 noise-to-signal ratio that buried real conversation in `culture channel read`.

### Added

- **`docs/agentirc/peek-clients.md`** documents the peek nick naming convention and the bot-filter contract (`'_peek' in nick`) so user-defined bots in deployments (like `spark-culture-greeter` and `spark-culture-chain-bot` on the spark mesh) can adopt the same filter and stop reacting to transient peek joins.

## [10.2.2] - 2026-05-06

### Fixed

- **`culture explain` no longer lists shipped namespaces as `(coming soon)`** (#330). Six namespaces (`agent`, `server`, `mesh`, `channel`, `bot`, `skills`) had no registered explain handler, so the dispatcher rendered them with the "(coming soon)" marker even though all six were fully shipped — confusing new agents reading `culture explain` during onboarding ("the CLI is mostly stubs"). Each shipped namespace now has a hand-curated explain handler in `culture/cli/introspect.py` that lists its main verbs and a one-paragraph summary. The unshipped `identity` and `secret` namespaces were dropped from `_NAMESPACES` until they actually exist on the CLI.

## [10.2.1] - 2026-05-06

### Fixed

- **`culture server <forwarded-verb> --help` now reaches agentirc** (#332). Previously `culture server restart --help` (and `link`, `logs`, `version`, `serve`) errored with `culture: error: unrecognized arguments: --help` because argparse's `REMAINDER` subparser leaked `--help` back to the root parser instead of capturing it. The fix bypasses argparse entirely for the forwarded surface: a new `_maybe_forward_to_agentirc()` helper in `culture/cli/__init__.py` short-circuits `culture server <forwarded-verb> ...` straight into `agentirc.cli.dispatch` before parser construction. All five forwarded verbs now show their proper agentirc help banner. The existing `test_forwarded_verb_is_reachable` regression test was strengthened to assert exit 0 + agentirc banner content (the prior assertion was too lenient and silently accepted the bug).

## [10.2.0] - 2026-05-05

### Changed

- **Manifest-loader warnings now fire once per process and tell you how to fix them** (#328). Previously every `culture` CLI invocation re-emitted the full `culture.yaml missing for X — skipping` / `Error loading X — skipping` block, sometimes 4–8 times in a single command, drowning real output. Each broken `(server, suffix)` entry now warns at most once per process, and the message now ends with the exact remediation: `… run 'culture agent unregister <suffix>' to remove this stale manifest entry`. Test helpers `culture.config.reset_manifest_warning_state()` and `culture.bots.config.reset_fires_event_warning_state()` clear the dedup state when needed.
- **`culture agent status` no longer leaks archived or malformed bots** (parts of #333). The bot table at the bottom of `agent status` reused a different code path from `culture bot list` and ignored the `archived` flag — so an archived `spark-culture-test-bot` and a malformed empty-name row were visible only there. `print_bot_listing` now accepts `show_archived` (threaded from `--all`), filters archived bots by default, and skips configs with empty names. The output matches `culture bot list`.
- **`fires_event` deprecation INFO logs once per bot per process** instead of on every config load. Same dedup pattern as the manifest warnings.

## [10.1.0] - 2026-05-05

### Added

- **`culture console` now detects same-port conflicts before invoking irc-lens.** When the web port (default `8765`) is already bound by a culture-owned console, the CLI looks at the recorded pidfile/sidecar instead of letting irc-lens fail with `[Errno 98] address already in use`:
  - **Same target, same port** → prints `culture console is already running for 'spark' at http://127.0.0.1:8765/` and exits `0`. No more spurious "port busy" when you re-run from a second terminal.
  - **Different target** → prints a 3-bullet hint (open the existing URL, `culture console stop && culture console <new>`, or `--web-port 8766` for side-by-side) and exits `1`. Culture never auto-kills another console — that decision stays with you.
  - **Foreign irc-lens without a pidfile** → prints a recovery hint pointing at `ss`/`lsof` so you can find and stop the owner manually.
  - **Foreign non-irc-lens owner** → falls through to irc-lens's own `cannot bind web port` error, the right message for arbitrary processes.
  - **Stale pidfile** (dead PID, or PID belongs to a non-culture process) → silently cleaned up before the new console starts.
- **`culture console stop [--web-port N]`** — culture-owned verb that gracefully stops the locally-running console on the given port (default `8765`): `SIGTERM` with a 5-second grace, then a re-validated `SIGKILL` (re-checks `is_culture_process` before escalation, so a PID recycled during the grace window doesn't catch an errant kill). Idempotent on a missing pidfile, and refuses to signal a process whose `/proc/<pid>/cmdline` doesn't include "culture" — preserving rather than deleting state files in that case.
- **Per-port state files under `~/.culture/pids/`** — `console-<port>.pid`, `console-<port>.port`, and a `console-<port>.json` sidecar (with `pid`, `server_name`, `nick`, `host`, `irc_port`, `web_port`) are written at start and removed at exit. Per-port keying is what makes side-by-side runs on `--web-port 8766` actually independent: each console owns its own slot and `stop --web-port` only touches the requested one. Cleanup is bound to the call via `try/finally` (no `atexit` handler — that would survive `monkeypatch` undo and risk deleting real state on pytest exit).
- **`--web-port=N` form** is now understood by the conflict-detection shim (previously only the two-token `--web-port N` was parsed; the equals form silently inspected the default port).
- **Same-target comparison** uses the full `(server_name, nick, host, irc_port)` tuple, so pure-passthrough `culture console serve --nick lens …` re-runs hit the exit-0 path, and two different IRC endpoints with the same nick are correctly classified as different targets. Server name is threaded through from the resolved-server path rather than derived from `nick.split('-')`, which was truncating hyphenated server names like `my-server` to `my`.
- **`docs/reference/cli/console.md`** — full reference for the new conflict UX, the `stop` verb, and the on-disk state layout.

## [10.0.2] - 2026-05-05

### Changed

- **Restructured public-facing docs** — README leads with the canonical positioning paragraph; new `docs/culture/ecosystem-map.md` page renders the AgentCulture org map from two YAML data files (`_data/agentculture_repos.yml`, `_data/culture_subcommands.yml`).
- **Documented planned rename of `culture afi` → `culture contract`** in all public copy. The CLI still exposes `culture afi` as a passthrough to `afi-cli` today; the rename itself ships in a later release.

### Added

- **Org-wide repo registry** at `_data/agentculture_repos.yml` with category, maturity, description, package, and docs link for every public repo in `agentculture/`.
- **Subcommand registry** at `_data/culture_subcommands.yml` with `ready`/`planned` status and the sibling repo backing each `culture <verb>`.
- **Reference doc** at `docs/resources/registry.md` documenting the schemas and naming steward + ghafi as registry-hygiene owners.

## [10.0.1] - 2026-05-05

### Changed

- **`culture mesh update` now streams uv/pip output** instead of capturing it. A long-running upgrade (e.g. fresh major-version install pulling in `claude-agent-sdk` ~73 MiB plus the OpenTelemetry stack) is no longer indistinguishable from a hang — uv's progress bars and download messages show through to the terminal in real time.
- **Default upgrade timeout raised from 120s to 600s.** The old ceiling spuriously fired mid-download on slow links during major-version bumps even though the upgrade was making progress.

### Added

- **`culture mesh update --upgrade-timeout SECONDS`** flag to override the default 600s ceiling for sites with very slow or very fast networks.
- **Expanded timeout hint.** When the upgrade does time out, the CLI now suggests three recovery paths instead of one: run `uv tool upgrade culture` (or `pip install --upgrade culture`) directly, rerun with a larger `--upgrade-timeout`, or `--skip-upgrade` to restart services without upgrading.

## [10.0.0] - 2026-05-05

### Changed (breaking)

- **Reverted `culture chat` → `culture server`.** The IRC-mesh subcommand is `culture server` again. The brief 9.0.0 detour through `culture chat` conflated server lifecycle (`start` / `stop` / `status` / `default` / `rename` / `archive` / `unarchive`) with chat operations — they're distinct nouns. `culture server` is now the canonical home for both the lifecycle verbs and the agentirc passthrough verbs (`restart` / `link` / `logs` / `version` / `serve`). **Migration:** replace any `culture chat <verb>` invocation in scripts, skills, and service definitions with `culture server <verb>`. The 9.1.0 stderr deprecation warning on `culture server` already promised this would land in 10.0.0.

### Removed (breaking)

- **`culture chat` is gone.** Argparse rejects it with `invalid choice`. There is no deprecation alias this round; the 9.1.0 → 10.0.0 cycle is the migration window.

### Added

- **`communicate` skill** — vendored from [agentculture/steward](https://github.com/agentculture/steward) (per [#324](https://github.com/agentculture/culture/issues/324)). Ships under `culture/skills/communicate/` and is materialized into each backend's skills root by `culture skills install <backend>` alongside the existing `irc` and `culture` skills. Two scripts: `post-issue.sh` (cross-repo GitHub issues, auto-signed `- culture (Claude)`) and `mesh-message.sh` (Culture mesh channel messages, unsigned — IRC nick is the speaker).
- **`culture agent learn` references the vendored skill.** A new "Cross-Repo + Mesh Communication via Vendored Skill" section in the learn prompt points at `<skill-dir>/communicate/scripts/{post-issue,mesh-message}.sh` and explains how the vendored skill (signs as `- culture (Claude)`) differs from the per-agent walkthrough (signs as `- <nick> (<harness>)`).

## [9.1.0] - 2026-05-05

### Added

- **`culture console`** — top-level passthrough wrapper around [`irc-lens`](https://github.com/agentculture/irc-lens), the reactive web console for AgentIRC. `culture console <server>` resolves the culture server name to host/port/nick before delegating; explicit irc-lens verbs (`serve`, `learn`, `explain`, `overview`, `cli`) flow through unchanged. Universal verbs (`culture explain console`, `culture overview console`, `culture learn console`) wire through `culture.cli._passthrough.register_topic`. Spec: `docs/superpowers/specs/2026-05-05-culture-console-design.md`. Subprocess-vs-in-process tradeoff tracked in [#322](https://github.com/agentculture/culture/issues/322).

### Deprecated

- **`culture mesh console`** — emits a stderr warning and forwards to `culture console`. Removal target: 10.0.
- **`culture/console/` Textual TUI package** — module-level `DeprecationWarning`. Removal target: 10.0.

## [9.0.0] - 2026-05-04

### Changed (breaking)

- **Renamed `culture server` → `culture chat`.** The new noun fits what culture actually is — an agent chat mesh, not a generic server. The 7 culture-owned verbs (`start`, `stop`, `status`, `default`, `rename`, `archive`, `unarchive`) keep their behavior under the new noun. New agentirc verbs (`restart`, `link`, `logs`, `version`, `serve`) land under `culture chat` for free via a passthrough into `agentirc.cli.dispatch`. The legacy `culture server` keeps working through 9.x as a deprecation alias that prints a stderr warning and routes to the same handlers; removed in 10.0.0.
- **Bundled IRCd deleted.** `culture/agentirc/{ircd,server_link,channel,events,room_store,thread_store,history_store,rooms_util,skill}.py`, `culture/agentirc/skills/`, `culture/agentirc/__main__.py` are gone. Culture now embeds `agentirc.ircd.IRCd` from the [`agentirc-cli`](https://pypi.org/project/agentirc-cli/) PyPI package directly (the path A2 set up). ~3,800 LOC of bundled fork removed.
- **`python -m culture.agentirc` is removed.** Use `agentirc` (CLI) or `python -m agentirc` instead. Reachable through `culture chat <verb>` for the lifecycle verbs.
- **`culture/agentirc/{client,remote_client}.py` moved to `culture/transport/`** (`git mv` preserves blame). Code that imported them under the old path needs to update — `culture/bots/*` and `culture/clients/*/daemon.py` are already updated.
- **`parse_room_meta` moved to `culture/clients/shared/rooms.py`.** All four client daemons (`claude`, `codex`, `copilot`, `acp`) updated to import from the new location. The function lived in the bundled `culture/agentirc/rooms_util.py` before A3.
- **Test harness migrated to `agentirc.ircd.IRCd`.** `tests/conftest.py`, `tests/telemetry/*`, and the bot/event/welcome/transport-tag tests now construct the public class instead of the bundled fork. Agentirc-internal tests (federation, rooms, threads, history, skills, events_*) deleted from culture's test tree — they live in agentirc's repo now.

### Kept (transitional)

- **`culture/agentirc/config.py`** remains as a re-export shim over `agentirc.config` through the 9.x line; removed in 10.0.0. Existing `from culture.agentirc.config import ServerConfig` keeps resolving.
- **`culture/agentirc/__init__.py`** re-exports `ServerConfig` / `LinkConfig` / `TelemetryConfig` from the same shim, so `from culture.agentirc import ServerConfig` keeps working.
- **`culture/agentirc/docs/`** is the source for the AgentIRC section of culture.dev — CI still copies it to `docs/agentirc/` before the Jekyll build. Can be revisited once culture's docs and agentirc's own docs visibly diverge.

### Migration notes for users

- Skills, scripts, and agent prompts that say `culture server` keep working with a stderr warning. Update them when you next touch them.
- Code importing `culture.agentirc.{ircd,channel,events,...}` is broken. There is no replacement under `culture.*`; depend on `agentirc-cli` and import from `agentirc.*` directly.
- Code importing `culture.agentirc.{client,remote_client}` — switch to `culture.transport.{client,remote_client}`.
- Code importing `culture.agentirc.rooms_util.parse_room_meta` — switch to `culture.clients.shared.rooms.parse_room_meta`.
- Code importing `culture.agentirc.config` — still works through the shim; remove in 10.0.0.

### Notes

- Final phase of the agentirc extraction. A1 (config dataclasses, 8.8.0, #309) and A2 (bot framework rewrite, 8.10.0, #319) preceded this. Spec: `docs/superpowers/specs/2026-04-30-agentirc-extraction-design.md`. Plan: `docs/superpowers/plans/2026-05-02-agentirc-extraction-track-a3.md` plus the verb-ownership and noun-rename decisions from this PR.
- Pre-existing bot-load race ([#317](https://github.com/agentculture/culture/issues/317)) is independent of this PR; tracked for a follow-up patch.

## [8.10.0] - 2026-05-03

### Changed

- `culture server start` now embeds `agentirc.ircd.IRCd` in-process directly, via the public class promoted in agentirc 9.6.0 ([agentculture/agentirc#22](https://github.com/agentculture/agentirc/issues/22) / PR #23). The bundled IRCd in `culture/agentirc/` is now orphaned in the production path; it is reached only by the test suite and is slated for deletion in Phase A3.
- Rewrote `culture/bots/virtual_client.py` as a thin subclass over the public `agentirc.virtual_client.VirtualClient` (also promoted in agentirc 9.6.0). The 231-LOC file collapsed to 31 LOC; user-visible bot behavior (channel JOINs, `@`-mention notices, `send_dm`, `broadcast_to_channel`) is unchanged. Culture-specific glue (BotConfig, template engine, `fires_event` chaining, owner DM) lives in `culture/bots/bot.py`, not in VirtualClient.
- Webhook listener (`webhook_port`) ownership moved from the bundled `culture/agentirc/ircd.py` to `culture/bots/bot_manager.py`. agentirc 9.5+ stopped binding the port itself; consumers (culture) now own the listener. `BotManager` gains `start()` / `stop()` lifecycle methods that wrap bot loading and HttpListener bind/unbind.
- `_run_server` in `culture/cli/server.py` wraps the post-`ircd.start()` body in a `try/finally` so `bot_manager.stop()` and `ircd.stop()` always run on shutdown — even if bot teardown raises.
- Bumped dep floor `agentirc-cli>=9.4,<10` → `agentirc-cli>=9.6,<10`.
- `Event` / `EventType` imports retargeted from `culture.agentirc.skill` to `agentirc.protocol` in the three sites that survive Phase A3 (`culture/bots/virtual_client.py`, `culture/bots/bot.py`, `culture/telemetry/audit.py` — TYPE_CHECKING). The bundled `culture.agentirc.skill` re-exports stay intact for the test suite, which still drives the bundled IRCd via `tests/conftest.py` until A3.

### Notes

- Plan: `docs/superpowers/plans/2026-05-02-agentirc-extraction-track-a2.md`. Spec: `docs/superpowers/specs/2026-04-30-agentirc-extraction-design.md` ("Implementation status" table, A2 row).
- One deviation from the canonical plan: Task 10 ("Test harness migration" — switching `tests/conftest.py` and bot tests from the bundled IRCd to `agentirc.ircd.IRCd`) is **deferred to Phase A3**. The full test suite (1157 tests) passes unchanged on the bundled IRCd, which is structurally compatible with the public class — migrating now would be diff churn without behavioral risk reduction. The smoke test exercises the production agentirc IRCd + culture BotManager path end-to-end.
- A pre-existing bot-load race (`Bot.start()` "Nick already in use" when one bot's `user.join` event triggers another bot's lazy-start during `BotManager.load_bots`) was surfaced in A2's smoke test and tracked at [#317](https://github.com/agentculture/culture/issues/317) for a follow-up patch. The error log is misleading but bot behavior is unaffected; this race exists identically on the bundled IRCd path and was not introduced by A2.

## [8.9.0] - 2026-05-03

### Changed

- Renamed the `coordinate` skill to `communicate` and broadened its scope to cover the agent's full communication toolkit — both in-mesh chat (`culture channel` CLI: message, read, who, ask, join, part, list, plus collaboration patterns @mentions / `[FINDING]` / `#general` / `#knowledge` / `#ops` / DMs) AND cross-repo hand-off briefs (`post-issue.sh`). The two surfaces now share one SKILL.md with a decision table for picking between them. Same `post-issue.sh` script (now at `.claude/skills/communicate/scripts/post-issue.sh`); same auto-signature `- culture (Claude)`; same conventions for self-contained briefs and title format.
- `culture agent learn` (and the top-level `culture learn`) prompt now ends with a "Cross-Repo Coordination" section that teaches the `communicate` skill — when to use in-mesh chat vs cross-repo issues, the `post-issue.sh` invocation, and the don't-double-post rule. The `learn` CLI verb itself is unchanged: it remains the agent self-teaching prompt; what changed is what it teaches (now covers both halves of agent communication).
- `CLAUDE.md` "Sibling alignment" section updated to reference `communicate` instead of `coordinate` in the example skill list.

### Migration

- `bash .claude/skills/coordinate/scripts/post-issue.sh ...` invocations need to be updated to `bash .claude/skills/communicate/scripts/post-issue.sh ...`. No other interface change — same flags, same signature, same behavior. No back-compat shim at the old path; if scripts in your environment still reference `coordinate/`, they'll fail.

### Notes

- This is a SKILL rename + scope expansion, not a CLI rename. `culture agent learn` and `culture learn` keep their names — the user clarified that "learn is for agents to learn how to use" and the skill name "communicate" is the right noun for the broader communication toolkit. The CLI verb teaches the skill; both names are now correct for what they do.
- The rename mirrors steward 0.8's `coordinate` → `communicate` rename. Culture's signature literal stays `- culture (Claude)`.

## [8.8.1] - 2026-05-03

### Changed

- Renamed `.claude/skills/pr-review/` → `.claude/skills/cicd/` to align with steward 0.7's skill-name convention (per [agentculture/culture#314](https://github.com/agentculture/culture/issues/314)). The `name:` field in `SKILL.md` becomes `cicd`; the description preserves the existing trigger phrases ("create PR", "review comments", "address feedback", "resolve threads") plus adds "use pr-review" / "use cicd" so existing automation keeps resolving here. The script names inside (`create-pr-and-wait.sh`, `wait-and-check.sh`) stay as-is.
- Doc references to the old skill name updated across `coordinate/SKILL.md` (4 mentions), the in-flight A2/A3 extraction plans (3 mentions), `docs/culture/reflective-development.md`, and `docs/superpowers/specs/2026-04-08-reflective-development-deepening-design.md`. Forward-facing slash-command references in three historical plans (`mesh-events.md`, `otel-foundation.md`, `agentirc-extraction-track-a.md`) updated to `/cicd` with an inline note about the rename, so future readers don't get mixed instructions. CHANGELOG entries about historical PRs that mentioned `pr-review` at the time are intentionally not rewritten (those are diffs of past releases). Global-fallback paths (`~/.claude/skills/pr-review/scripts/pr-status.sh`) in three older otel plans are intentionally preserved — those refer to the user's global skills directory which still uses the old name.
- The two project-local scripts (`create-pr-and-wait.sh`, `wait-and-check.sh`) retain their `~/.claude/skills/pr-review/scripts/pr-comments.sh` global fallback — steward's rename is in-repo only, the user's global skills directory still holds the trio (`pr-comments.sh`, `pr-reply.sh`, `pr-batch.sh`) under the old name. Header comments note this lag.

### Added

- `## Sibling alignment` section in project `CLAUDE.md` pointing at [agentculture/steward](https://github.com/agentculture/steward) as the alignment hub for AgentCulture skills (per culture#314 Ask 2). New contributors editing skills here now have an in-repo signal that there's a sibling tracking skill evolution.

## [8.8.0] - 2026-05-01

### Added

- `agentirc-cli>=9.4,<10` runtime dependency — the IRCd config dataclasses (`ServerConfig`, `LinkConfig`, `TelemetryConfig`) are now sourced from the published `agentirc-cli` PyPI distribution (imported as `agentirc.config`) instead of culture's local copy. First step of the Track A cutover described in [agentculture/culture#308](https://github.com/agentculture/culture/issues/308).

### Changed

- `culture/agentirc/config.py` is now a re-export shim over `agentirc.config` — `from culture.agentirc.config import ServerConfig` continues to work and resolves to the same class as `from agentirc.config import ServerConfig` (no parallel-dataclass identity hazard). The shim will be deleted alongside the rest of `culture/agentirc/` in Phase A3 once the bot-runtime story is settled (see agentculture/agentirc#15).
- Canonical call sites retargeted to import directly from `agentirc.config`: `culture/cli/shared/mesh.py`, `culture/config.py`, `culture/telemetry/{metrics,tracing,audit}.py`, `tests/conftest.py`. Bot-runtime call sites (`culture/bots/*`, `culture/agentirc/ircd.py`, `culture/cli/server.py:_run_server`, `culture/clients/*/daemon.py`) intentionally retain their `culture.agentirc.*` imports — those reach internal IRCd/Event/parse_room_meta surfaces that are not yet exposed in agentirc's public API.

### Removed

- Bootstrap-era `agentirc-cli` and `agentirc` alias publish steps from `.github/workflows/publish.yml`. `agentirc-cli` is now owned by [agentculture/agentirc](https://github.com/agentculture/agentirc) and published from there; culture's TestPyPI/PyPI workflow no longer co-publishes itself under those names (the OIDC trust policy was transferred along with the package). Culture continues to publish itself as `culture` on both indices.
- `agentirc-cli` / `agentirc` fallback chain in `culture/__init__.py` `__version__` resolution. The fallback would silently report agentirc's installed version as culture's version now that the alias names refer to a separate package.

## [8.7.1] - 2026-04-27

### Added

- `tests/test_socket_path_convergence.py`: parametric regression test asserting all 8 daemon+skill resolvers agree with the CLI's `agent_socket_path()` for both `XDG_RUNTIME_DIR` set and unset.
- `tests/test_constants.py`: unit tests pinning `culture_runtime_dir()` contract (env precedence, `~/.culture/run/` fallback, mode 0700).

### Changed

- `culture channel {message,list,read}`: when `CULTURE_NICK` is set but the daemon IPC is unreachable or rejects the request, the CLI now prints a stderr warning naming the nick, the socket path, and the GitHub issue tracker before falling back to the peek-nick observer. The fallback itself is preserved for human use (no `CULTURE_NICK`).

### Fixed

- Converged all socket-path resolvers (4 backend daemons, 4 skill irc_clients, overview collector, harness package reference impl) on `culture_runtime_dir()` so the CLI and daemon agree on the IPC socket path when `XDG_RUNTIME_DIR` is unset (macOS default). Previously the daemon listened on `/tmp/culture-<nick>.sock` while the CLI looked in `~/.culture/run/`, causing `culture channel message` to silently fall back to an anonymous `_peek<random>` nick (#302, regression of #203).

## [8.7.0] - 2026-04-26

### Added

- OTEL bot instrumentation (Plan 7): bot.event.dispatch and bot.run spans, culture.bot.invocations counter, culture.bot.webhook.duration histogram, aiohttp-server auto-instrumentation on the webhook listener.

### Changed

- docs/agentirc/telemetry.md updated with the 8.7.0 section; harness-telemetry.md cross-link updated.

## [8.6.0] - 2026-04-26

### Added

- Harness-side OTEL: 3 spans (harness.irc.connect, harness.irc.message.handle, harness.llm.call) and 4 LLM metrics (culture.harness.llm.tokens.input/output, call.duration, calls).
- W3C traceparent injection on outbound IRC + extraction on inbound — single trace_id now spans server, federation, and harness in the cross-process tree.
- Per-backend telemetry citation across claude/codex/copilot/acp with all-backends parity test (24 tests across 6 dimensions) locking down drift.
- docs/agentirc/harness-telemetry.md — new operator guide for the harness OTEL pillar.

### Changed

- packages/agent-harness/{telemetry.py,config.py,culture.yaml,irc_transport.py,daemon.py} — reference module for the citation pattern.
- culture/clients/{claude,codex,copilot,acp}/{telemetry.py,config.py,culture.yaml,irc_transport.py,daemon.py,agent_runner.py} — telemetry citation, harness.llm.call span wrap, record_llm_call invocation.
- tests/harness/ — 70 new tests (24 parity + 46 module/runner/transport/daemon).

### Fixed

- Code-quality fixes from review: zero-token usage extraction (0 no longer silenced), tracer-name from constant (no hardcoded strings), module-top imports of record_llm_call across all 4 backends.

## [8.5.0] - 2026-04-25

### Added

- `culture/telemetry/audit.py` — `AuditSink` with bounded `asyncio.Queue` + dedicated writer task + daily/size rotation + `0600`/`0700` perms.
- Public `culture.telemetry.AuditSink`, `init_audit`, `build_audit_record`, `utc_iso_timestamp`.
- `TelemetryConfig.audit_enabled` (default `True`), `audit_dir`, `audit_max_file_bytes`, `audit_rotate_utc_midnight`, `audit_queue_depth` — independent of `telemetry.enabled` (audit fires even with OTEL off).
- `culture/protocol/extensions/audit.md` — JSONL record schema as a stable contract.
- `docs/agentirc/audit.md` — operator guide.
- Audit metrics extend the Plan-3 `MetricsRegistry`: `culture.audit.writes` (Counter, labels `outcome=ok|error`) and `culture.audit.queue_depth` (UpDownCounter).
- `IRCd.__init__` creates the sink; `IRCd.start()` awaits `sink.start()`; `IRCd.stop()` awaits `sink.shutdown()` so SERVER_WAKE / SERVER_SLEEP both land in the JSONL.
- `IRCd.emit_event` submits one record per event after the `irc.event.emit` span; `trace_id` / `span_id` captured inside the span for cross-pillar joins.
- `Client._process_buffer` submits `PARSE_ERROR` records for malformed inbound lines.
- Federation audit: federated `message` events arrive on the receiver with `origin=federated`, `peer=<peer_name>`. Federated lifecycle events (JOIN/PART/QUIT) are deferred — see #296.

## [8.4.0] - 2026-04-25

### Added

- `culture/telemetry/metrics.py`: `init_metrics(config)` + `MetricsRegistry` dataclass for all 15 server-side instruments — mirrors `tracing.py`'s idempotency + no-op pattern.
- Public `culture.telemetry.MetricsRegistry` and `culture.telemetry.init_metrics`.
- `TelemetryConfig.metrics_enabled` (default `True`) and `metrics_export_interval_ms` (default 10000).
- Message-flow metrics: `culture.irc.bytes_sent`, `culture.irc.bytes_received`, `culture.irc.message.size`, `culture.privmsg.delivered`.
- Events metrics: `culture.events.emitted`, `culture.events.render.duration`.
- Federation metrics: `culture.s2s.messages` (inbound), `culture.s2s.relay_latency`, `culture.s2s.links_active`, `culture.s2s.link_events`.
- Client metrics: `culture.clients.connected`, `culture.client.session.duration`, `culture.client.command.duration`.
- `culture.trace.inbound` counter — closes Plan 2's deferral.
- `tests/conftest.py` `metrics_reader` fixture parallel to `tracing_exporter`.
- `tests/telemetry/_metrics_helpers.py` — `get_counter_value`, `get_histogram_count`, `get_up_down_value`.

## [8.3.0] - 2026-04-25

### Added

- `irc.s2s.session` span over ServerLink connection lifetime.
- `irc.s2s.<VERB>` per-verb spans on inbound federation messages with traceparent extraction and the inbound mitigation rules from `culture/protocol/extensions/tracing.md`.
- `irc.s2s.relay` span on outbound relay enforcing the re-sign-per-hop rule.
- `irc.client.session` span over Client connection lifetime (#290).
- `irc.join` and `irc.part` spans (#290).
- Public `culture.telemetry.context_from_traceparent` and `culture.telemetry.current_traceparent` helpers.
- Single traceparent injection choke point at `ServerLink.send_raw`.
- End-to-end propagation tests proving one `trace_id` spans federated client → server → relay → server hops.

### Changed

- `Client._dispatch` span name and `irc.command` attribute now uppercase, matching `ServerLink._dispatch` convention.

### Fixed

- `_replay_event` uses the hasattr-guarded comparison so string-typed federated `event.type` no longer skips the typed fast path. (#291)

## [8.2.0] - 2026-04-24

### Added

- OpenTelemetry foundation: `culture/telemetry/` package with TracerProvider bootstrap, W3C trace context extract/inject helpers for IRCv3 tags, and `TelemetryConfig` block in `server.yaml`.
- Protocol extension: `culture.dev/traceparent` and `culture.dev/tracestate` IRCv3 tags (`culture/protocol/extensions/tracing.md`).
- Server-side tracing: `IRCd.emit_event`, `Client._dispatch`, `Client._process_buffer` (with parse-error compensation), and PRIVMSG dispatch/delivery paths now emit spans.
- Outbound traceparent injection on `Client.send` and `Client.send_raw` when a span is active.
- Operator docs at `docs/agentirc/telemetry.md` and starter collector config at `docs/agentirc/otelcol-template.yaml`; `docs/reference/server/config.md` documents the new `telemetry` block.
- Dependencies: `opentelemetry-api`, `opentelemetry-sdk`, `opentelemetry-exporter-otlp-proto-grpc`, `opentelemetry-semantic-conventions`.

## [8.1.0] - 2026-04-23

### Added

- `culture afi` namespace — passthrough to the standalone `afi-cli` (Agent First Interface scaffolder) with argparse-REMAINDER argument forwarding, parallel to `culture devex`.
- Universal verbs register the `afi` topic; `culture explain afi` / `culture overview afi` / `culture learn afi` all route through `afi-cli` 0.3+ and `culture explain` no longer marks `culture afi` as coming-soon.
- `afi-cli>=0.3,<1.0` as a library dependency (0.3 added the `overview` verb + sixth rubric bundle per agentculture/afi-cli#5).
- `culture/cli/_passthrough.py` — shared plumbing for `culture <ext>` subcommands that embed a sibling CLI. Supplies `run()`, `capture()`, and `register_topic()` so each passthrough module stays a thin adapter.

### Changed

- `culture/cli/devex.py` refactored onto the new shared passthrough helper. Behaviour is preserved (explain/overview/learn argv and typer app invocation unchanged); the module shrinks to a package-specific entry adapter and a single `register_topic` call. When agex-cli adopts the agent-first CLI contract (`main(argv) -> int`, tracking: agentculture/agex-cli#30), the adapter collapses to a direct delegation.

## [8.0.0] - 2026-04-22

### Added

- `culture afi`, `culture identity`, and `culture secret` surfaced as (coming soon) namespaces in `culture explain` output. `culture identity` will wrap a future standalone `zehut-cli`; `culture secret` will wrap `shushu-cli`; `culture afi` shares its name with the standalone `afi-cli`.

### Changed

- BREAKING: Renamed `culture agex` to `culture devex` (developer experience) — more familiar terminology and visually distinct from `culture agent`. The upstream `agex-cli` / `agent_experience` library is unchanged; only culture's public command name differs.
- Positioning docs, README, and site chrome refreshed to reflect the new identity: culture is the framework of agreements that makes agent behavior portable, inspectable, and effective, surfacing explain/overview/learn at every CLI level.

## [7.4.0] - 2026-04-22

### Added

- culture agex passthrough to the standalone agex CLI (new subcommand embedding agex via typer)
- Universal verbs culture explain, culture overview, culture learn at the CLI root, with a per-topic handler registry (culture/cli/introspect.py)
- agex-cli>=0.13,<1.0 as a library dependency

## [7.3.0] - 2026-04-21

### Added

- `sitemap-agentirc.html`: Liquid-templated sub-sitemap emitted at `/agentirc/sitemap.xml`, listing only pages under `/agentirc/*`. `sitemap.xml` index (from 7.2.3) extended to list it alongside `/sitemap-main.xml` and `/agex/sitemap.xml`.
- AgentIRC section in the main just-the-docs nav (`has_children: true`, `nav_order: 10`) grouping the four runtime pages.

### Changed

- Fold AgentIRC into the main Culture Jekyll build under `/agentirc/*` permalinks. Retire `_config.agentirc.yml` and the separate `_site_agentirc/` target. Completes the one-origin consolidation plan: `culture.dev`, `culture.dev/agex/`, and `culture.dev/agentirc/` all live on a single origin now.

### Removed

- `_config.agentirc.yml` — no longer a separate Jekyll build target.
- `_plugins/site_filter.rb` — dropped the per-build `sites:` filter; single-build semantics make it a noop. Existing `sites:` front matter on docs is now harmless metadata.
- `.github/workflows/docs-check.yml`: second Jekyll build step and the `sites:` front-matter presence check — single build, no filter.
- `.gitignore` and `_config.base.yml`: `_site_agentirc/` entries.
- `rel=related` links to `site.data.sites.agentirc` in `_includes/head_custom.html` — same-origin now, no longer semantically meaningful; agex `rel=related` retained.

### Fixed

- `docs/culture/features.md` and `docs/culture/index.md`: eliminated double-slash bug from `{{ site.data.sites.agentirc }}` concatenations (the data value now ends in a trailing slash from culture 7.2.1) by switching those cross-references to same-origin `relative_url` links.

## [7.2.3] - 2026-04-21

### Added

- `sitemap.xml` (sitemap index, gated on `site.build_site`).
- `sitemap-main.xml` (enumerates only HTML pages in the current build; opts out via `sitemap: false` front matter).

### Changed

- Replace `jekyll-sitemap` auto-generation with an explicit sitemap index (`/sitemap.xml`) plus a Liquid-templated sub-sitemap (`/sitemap-main.xml`). On the culture build the index points at `culture.dev/sitemap-main.xml` + `culture.dev/agex/sitemap.xml`; on the agentirc build it points at `agentirc.dev/sitemap-main.xml`. Sets the stage for adding `culture.dev/agentirc/sitemap.xml` once AgentIRC folds under `culture.dev/agentirc` (Phase 4 of the one-origin consolidation).

## [7.2.2] - 2026-04-21

### Changed

- Supersedes PR #274, which tried to solve cross-site flicker via `preconnect` hints across the three-subdomain topology. The one-origin consolidation (`culture.dev/agex`, `culture.dev/agentirc`) makes those preconnects moot; only the dark-paint CSS and `aux_links_new_tab` change carry forward.

### Fixed

- `_includes/head_custom.html`: add `color-scheme` meta + inline dark-paint `<style>` to eliminate the white flash on cold-cache first paint.
- `_config.culture.yml` + `_config.agentirc.yml`: `aux_links_new_tab: false` so sibling-site clicks stay in-tab (one-site feel after the consolidation). Power users can still Ctrl/Cmd-click for a new tab.

## [7.2.1] - 2026-04-21

### Changed

- `_data/sites.yml`: agex URL → `https://culture.dev/agex/` (was `https://agex.culture.dev`)
- `_config.culture.yml` + `_config.agentirc.yml`: aux_links and footer_content agex links retargeted to `https://culture.dev/agex/`

## [7.2.0] - 2026-04-18

### Added

- Console: full CommonMark markdown rendering in chat panel — bold/italic/inline code/strikethrough, OSC 8 hyperlinks, fenced code blocks with syntax highlighting, headings, lists, blockquotes, and tables (#233)
- Console: docs/reference/console.md reference page covering chat-panel markdown rendering

### Changed

- Console: ChatPanel.add_message now writes a header line ([ts] icon nick:) followed by a Rich Markdown body, instead of a single Rich-markup string — this also closes a latent footgun where bracketed text in agent messages could be reinterpreted as Rich markup

## [7.1.5] - 2026-04-18

### Added

- `jekyll-redirect-from` plugin (Gemfile + `_config.base.yml`) so `/why-culture/` redirects cleanly to `/what-is-culture/` (#267)
- `docs/resources/positioning.md`: canonical positioning snippets (paragraph + reference points + usage notes). Source of truth for README, repo description, site meta, and LLM summarizers (#267)

### Changed

- Renamed `docs/culture/why-culture.md` to `docs/culture/what-is-culture.md` and rewrote the body to lead with the definitional framing Culture is a professional workspace for specialized agents. Added a Reference points section that names OpenClaw, Codex, Claude Code as neighbors rather than targets (#267)
- `docs/culture/vision.md` retitled to The Culture vision; `nav_order` pushed to 2 behind the new What is Culture? page. Intro trimmed to remove the duplicate definitional sentence (#267)
- `docs/culture/mental-model.md` Persistence section reframed: removed the not one-shot task execution contrast; persistence now presented as a property that supports continued participation in the culture (#267)
- `docs/culture/agent-lifecycle.md` heading changed from Education is not one-shot to Education is continuous. Same meaning, positive framing (#267)

## [7.1.4] - 2026-04-18

### Changed

- Renamed "Assimilai pattern" to "Citation pattern" throughout live docs, configs, and template headers to align with the sibling project rename from `assimilai` to `citation-cli`. Historical specs and plans left intact. See [citation-cli](https://github.com/OriNachum/citation-cli).
- Backend culture.yaml system prompts now say "Apply changes using the citation pattern (cite, don't import)" across claude, codex, copilot, acp.
- Template header comments in packages/agent-harness/ switched from `# ASSIMILAI: Replace BACKEND` to `# CITATION: Replace BACKEND`.
- Test nick in tests/test_daemon_config.py and use-case doc nick both renamed from `spark-assimilai` to `spark-citation-cli` (aligned).

## [7.1.3] - 2026-04-18

### Added

- `docs/culture/features.md`: new Features page at `/features/` with four groups (workspace itself, humans managing it, bring your agents, open foundation) (#248)
- `docs/superpowers/specs/2026-04-17-sites-repositioning-design.md`: design spec for the positioning change (#248)

### Changed

- culture.dev homepage repositioned around "The professional workspace for agents." — new hero headline, kicker, sub, room-panel visual anchor, and Features card in docs grid (#248)
- agentirc.dev homepage repositioned around "The runtime and protocol that powers Culture." — new hero headline, kicker, sub, and inline federation-mesh SVG visual anchor (#248)
- Stack diagram on culture.dev relabels "Harnesses" row to "Agents" to land the workforce metaphor (#248)
- Cross-site callouts reworded: culture.dev → AgentIRC now emphasises runtime internals; agentirc.dev → Culture now emphasises running it (#248)
- `_config.culture.yml` and `_config.agentirc.yml` site descriptions updated to the new taglines (#248)
- `_sass/custom/custom.scss`: added `.room-panel`, `.federation-mesh`, `.feature-group` component styles (#248)

## [7.1.2] - 2026-04-17

### Changed

- Pin all GitHub Actions workflow uses: to full commit SHAs (SonarCloud minor, #258)
- Document Python API for events.register/validate_event_type/render_event in docs/agentirc/events.md (#249)
- Document Python API for bot filter DSL and template engine in docs/agentirc/bots.md (#249)
- Note in ConsoleIRCClient docstring that it intentionally does not negotiate CAP message-tags (#249)

### Fixed

- Remove unused PEER_CAPABILITY_EVENTS constant from culture/constants.py (#249)

## [7.1.1] - 2026-04-17

### Changed

- Added markdownlint-cli2 to the pre-commit hook set via the upstream DavidAnson/markdownlint-cli2 repo. Contributors running `pre-commit install` now get markdown linting on staged .md files automatically — no system install required (pre-commit provisions its own Node environment).
- Tuned .markdownlint-cli2.yaml to fit the repo's existing conventions: MD024 uses `siblings_only` so Keep-a-Changelog headings pass; MD025/MD033/MD041 disabled for Jekyll pages that derive their H1 from front matter and use inline HTML; added `_site_*/**` and `docs/superpowers/**` to ignores.
- Merged duplicated `### Changed` blocks inside CHANGELOG [0.21.0] that the new lint rule surfaced.

## [7.1.0] - 2026-04-17

### Changed

- Refactored `_handle_channel_mode` in `culture/agentirc/client.py`: extracted `_apply_mode_char` and `_broadcast_mode_change` helpers to drop cognitive complexity from 21 to ≤15 (SonarCloud S3776)
- Background task GC safety in `ircd.py` `_notify_local_quit`: `asyncio.ensure_future` replaced with a tracked `asyncio.create_task` using the existing `self._background_tasks` set + `add_done_callback(discard)` pattern

### Fixed

- culture mesh update no longer hangs on broken/unresponsive systemd units — all subprocess calls in persistence.py and cli/mesh.py now have explicit timeouts (30s for service restarts, 30s for CLI fallbacks, 120s for package upgrade)
- fires_event chain not triggering downstream bots (#260) — the bot.yaml loader now accepts fires_event at the top level as well as under output:, so configs that put the block at the top level emit events as expected
- Daemon log flushing stops after startup — replaced logging.basicConfig's default StreamHandler (which inherits stderr buffering from interpreter startup) with an explicit logging.FileHandler so runtime log records flush per-record

## [7.0.4] - 2026-04-17

### Fixed

- Reduce cognitive complexity and fix code quality issues across CLI modules (SonarCloud S3776, S1192, S5886, S108)

## [7.0.3] - 2026-04-17

### Fixed

- Duplicate _ERR_CHANNEL_PREFIX string in all 5 daemon files (S1192)
- Cognitive complexity in claude/daemon.py _poll_loop (CC 22, S3776)
- Cognitive complexity in agent-harness/daemon.py _poll_loop (CC 22, S3776)
- Cognitive complexity in codex/daemon.py _relay_response_to_irc (CC 44, S3776)
- Cognitive complexity in copilot/daemon.py _relay_response_to_irc (CC 23, S3776)
- Cognitive complexity in acp/daemon.py _relay_response_to_irc (CC 23, S3776)
- Cognitive complexity in acp/agent_runner.py start() (CC 17, S3776)

## [7.0.2] - 2026-04-17

### Fixed

- Cognitive complexity in observer.py (CC 22→~13)
- Cognitive complexity in ircd.py (CC 18→~12)
- Cognitive complexity in server_link.py (CC 33→~14)

## [7.0.1] - 2026-04-17

### Fixed

- Wrong AgentConfig/DaemonConfig import types in test helpers (S5655)
- Constant if-False condition replaced with unreachable yield pattern (S5797)

## [7.0.0] - 2026-04-17

Mesh Events (issue #123) — lifecycle and activity notifications as IRCv3-tagged
PRIVMSGs, event-triggered bots, and pub/sub composition chains.

> Versions 6.3.0 through 6.11.2 were development increments for this feature
> and were never published. Their changes are consolidated here as 7.0.0.

### Breaking Changes

None. Existing clients, bots, and federation links continue to work unchanged.
The major bump reflects the scope of the feature addition (new protocol verb,
new subsystem, new bot trigger type).

### Added

- **Event system** — `system-<server>` pseudo-user surfaces lifecycle events
  as IRCv3-tagged PRIVMSGs with `@event=<type>;event-data=<b64json>` tags
- **Built-in event catalog** — 18 event types across channel-scoped
  (`user.join/part/quit`, `room.create/archive/meta`, `tags.update`) and global
  (`agent.connect/disconnect`, `server.wake/sleep/link/unlink`,
  `console.open/close`)
- **IRCv3 message-tags** — `Message.parse()` extracts tags; CAP negotiation
  (`CAP REQ :message-tags`) in all agent backends and server
- **`#system` channel** — auto-created at startup for global event delivery;
  `system-<server>` VirtualClient auto-joined
- **Reserved `system-*` nicks** — rejected for non-server clients
  (`432 ERR_ERRONEUSNICKNAME`)
- **SEVENT S2S verb** — generic federation relay for lifecycle events with
  `_origin` loop prevention and trust policy filtering
- **HistorySkill** stores lifecycle events — `HISTORY RECENT` replays
  agent.connect, server.wake, room.create, etc.
- **Filter DSL** — safe recursive-descent expression parser (`==`, `!=`, `in`,
  `and`, `or`, `not`, dotted field access) for bot event triggers
- **Bot event triggers** — `trigger.type: event` with filter DSL evaluation;
  `fires_event` output for pub/sub bot chains with rate limiting (10/sec)
- **System bots** — package-bundled bots discovered at startup from
  `culture/bots/system/<name>/bot.yaml`; welcome bot greets on `user.join`
- **All-backends CAP** — claude, codex, copilot, acp, and agent-harness
  transports negotiate `message-tags` during connection
- **Documentation** — `docs/agentirc/events.md`, `docs/agentirc/bots.md`,
  `culture/protocol/extensions/events.md`

## [6.2.3] - 2026-04-15

### Changed

- docs: post-#231 retrospective — CLAUDE.md guidance for pre-branch checklist, format-before-commit, pre-push code review, SonarCloud pre-ready; new doc-test-alignment subagent; /pr-review skill step for SonarCloud query

## [6.2.2] - 2026-04-14

### Fixed

- console: handle BrokenPipeError/ConnectionResetError in _send_raw; surface a red system notice in the chat panel instead of letting the asyncio task crash (#230)

## [6.2.1] - 2026-04-13

### Added

- Copy-paste guidance in help screen (Shift+drag bypasses TUI mouse capture in modern terminals)

### Fixed

- #227: Tab now cycles channels (added priority=True to override Textual Screen focus-cycling)
- #226: Alt+Left/Right jump by word in chat input; Alt+Backspace deletes previous word
- #225: `culture channel message` interprets literal \n, \t, and \\ (escape-an-escape); observer splits multi-line text into one PRIVMSG per line and rejects all-empty-after-interpretation input with a non-zero exit
- #224: Exiting overview now reloads the current channel history (was empty)
- Help screen now opens on F1 (Ctrl+H stays as secondary — most terminals forward it as Backspace)

## [6.2.0] - 2026-04-12

### Added

- Agent status indicators in console sidebar (#218) — shows working/idle/paused/circuit-open for each agent
- Auto-read channel history on switch (#219) — loads last 20 messages when switching channels via Tab, sidebar click, or /join
- Help menu — /help command and Ctrl+H keybinding showing all commands and keybindings

### Fixed

- Joined message no longer wiped by channel switch clear_log

## [6.1.1] - 2026-04-11

### Changed

- Remove Python API sections from all backend SKILL.md files — agents should use culture channel CLI exclusively

### Fixed

- IRC skill teaches agents to use internal module path instead of culture CLI (#215)

## [6.1.0] - 2026-04-10

### Added

- Two-site docs architecture: agentirc.dev (runtime layer) and culture.dev (full solution)
- Dark terminal theme (visual-anchor palette) replacing warm cream Anthropic theme
- Site filter Jekyll plugin for per-page content selection via sites: front matter
- 4-bucket content model: agentirc/, culture/, shared/, reference/
- Custom SCSS components: hero sections, docs grids, stack diagrams, harness chips, CTA buttons
- Cross-site linking via _data/sites.yml
- docs-check CI workflow validating both site builds

### Changed

- Consolidated 23 per-backend harness docs into 4 single-page references
- Restructured 92 docs files into 4 content buckets with sites: front matter tags
- Replaced GitHub Pages deployment with Cloudflare Pages dual-site build
- Rewrote README.md for dual-site structure

## [6.0.2] - 2026-04-10

### Changed

- AgentIRC local docs with Jekyll pipeline copy step

## [6.0.1] - 2026-04-10

### Fixed

- agent create/join/delete/archive/unarchive/rename crash with manifest-format server.yaml (#208)
- Auto-migrate legacy agents.yaml to manifest format on first load
- Server rename/archive/unarchive now work with manifest format

## [6.0.0] - 2026-04-10

### Changed

- **BREAKING:** Renamed internal Python package `culture.server` to `culture.agentirc`. All imports must update from `culture.server.*` to `culture.agentirc.*`. CLI command `culture server` and config path `~/.culture/server.yaml` are unchanged.
- **AgentIRC** is now the official name for the server engine in documentation.

## [5.0.4] - 2026-04-10

### Fixed

- Reduce cognitive complexity of _cmd_topic in channel CLI
- Fix f-string with no replacement fields in topic error message

## [5.0.3] - 2026-04-10

### Added

- New channel subcommands: join, part, ask, topic, compact, clear

### Changed

- Channel CLI routes through agent daemon IPC when CULTURE_NICK is set
- All SKILL.md files and learn prompt use culture channel CLI instead of python3 -m
- Mesh update readiness probe verifies PID-based server identity

### Fixed

- culture channel message sends as agent nick instead of temporary peek nick (#203)
- IRC skill references culture channel CLI instead of broken python3 -m path (#202)

## [5.0.2] - 2026-04-09

### Fixed

- Handle missing credential tool (secret-tool/security/powershell) gracefully instead of crashing the server
- Report restart failures in mesh update instead of claiming success

## [5.0.1] - 2026-04-09

### Added

- Topic subcommand for IRC skill (#192)
- @mention validation warnings for unknown nicks (#196)
- GitHub issues skill for Claude Code

### Fixed

- Whitespace-only messages now rejected (#195)
- join/part channel state desync with # prefix validation (#194)
- Sending to unjoined channels now returns error (#193)
- Agents can now read own messages in channel history (#191)
- Codex backend meta-response stripping (#197)

## [5.0.0] - 2026-04-09

### Added

- Mesh overview shows stopped/registered agents from server.yaml manifest (#178)

### Changed

- CLI docs use correct noun-group syntax (culture agent create, culture channel read, etc.) (#186)
- Replaced non-existent culture send with culture channel message / culture agent message (#187)
- All doc references updated from agents.yaml to server.yaml (#188)
- Documented --mesh-config, --webhook-port, --data-dir server start flags (#189)

### Fixed

- Mesh overview now includes agents that are registered but not running

## [4.5.2] - 2026-04-09

### Fixed

- Agent status now reports the circuit-open state correctly instead of showing running (#179)
- Agent status list now distinguishes paused and sleeping agents correctly (#180)
- Learn prompt now includes compact/clear commands and ask --timeout (#181)
- Non-Claude backend skill docs now include the required features and comply with the all-backends rule (#182)
- Admin skill and learn prompt now include the missing CLI commands (#183)
- Mesh overview now indicates when bots are archived (#184)

## [4.5.1] - 2026-04-09

### Fixed

- Fix mesh overview crash after agent config migration (str has no attribute items)

## [4.5.0] - 2026-04-09

### Added

- Decentralized agent configuration with per-directory culture.yaml files
- New ~/.culture/server.yaml for machine-level config with agent manifest
- CLI: culture agent register/unregister for managing agent directories
- CLI: culture agent migrate for one-time migration from agents.yaml
- Unified culture/config.py module with AgentConfig, ServerConfig, auto-detection
- culture.yaml definitions for harness template and backend agents (#harness channel)

### Changed

- Agent config split: per-agent settings in culture.yaml, server settings in server.yaml
- CLI agent commands now support both server.yaml and legacy agents.yaml formats

## [4.4.3] - 2026-04-08

### Changed

- Regenerate all favicons, including `/favicon.ico` and `/assets/images/favicon.ico`, from the source image with proper cropping and optimization
- Reduce `/favicon.ico` from 1.4 MB to 3.5 KB and optimize `/assets/images/favicon.ico`
- Remove original source image (IMG_3161.png)

## [4.4.2] - 2026-04-08

### Fixed

- Codex/copilot: preserve HOME for auth tokens instead of isolating (#159)
- Codex: fix turn sync race condition causing concatenated rapid-mention responses (#165)
- All backends: sleep scheduler no longer overrides manual pause (#162)
- All backends: poll loop filters @mention messages to prevent duplicate responses (#160)
- All backends: turn errors now send feedback to IRC channel (#163)
- All backends: consecutive turn failure circuit breaker pauses agent after 3 failures (#164)
- Status query response verified not leaking to IRC channel (#161)

## [4.4.1] - 2026-04-07

### Fixed

- Config save operations no longer strip backend-specific fields like acp_command (#150)
- Agent status detail uses cached description by default, --full for live query; IPC deadline increased to 15s (#152)
- DMs now activate agents — _detect_and_fire_mention handles direct messages in all backends (#153)
- ACP agent runner preserves HOME/XDG_CONFIG_HOME for auth tokens; warns on authMethods, fails fast on session creation failure (#154)
- _coerce_to_acp_agent now copies the icon field (#155)
- _make_backend_config passes supervisor, poll_interval, sleep_start, sleep_end to non-claude backends (#156)
- ACP load_config strips unknown fields, matching claude/codex/copilot pattern (#157)

## [4.4.0] - 2026-04-07

### Added

- SQLite-backed persistent channel history (survives server restarts)
- --data-dir CLI flag for server start (default: ~/.culture/data)

### Fixed

- Multi-line messages truncated to first line in send_privmsg and thread methods
- data_dir never wired to ServerConfig, silently disabling room/thread persistence

## [4.3.7] - 2026-04-07

### Fixed

- Extract duplicate string constants (S1192, #85)
- Remove redundant exception classes in except clauses (S5713, #86)
- Clean up unused variables and function parameters (S1481/S1172, #88)
- Remove f-strings without replacement fields (S3457, #89)
- Address hardcoded credential warnings with test constants (S2068, #90)
- Fix miscellaneous code quality issues: asyncio.timeout, nested ternaries, empty methods, CSS contrast (S7483/S3358/S1186/S7924, #91)

## [4.3.6] - 2026-04-07

### Changed

- CLI module docstring updated with current subcommand sets (#147)

### Fixed

- agent message silently succeeds for nonexistent targets (#132)
- channel message silently succeeds for nonexistent channels (#133)
- agent sleep/wake error messages use wrong command names (#134)
- server subcommands ignore default server, hardcode culture (#135)
- agent start/stop inconsistent behavior with no nick argument (#137)
- channel message and bot create accept empty strings (#138)
- bot archive/unarchive missing --config flag (#139)
- inconsistent error message casing in agent archive vs unarchive (#140)
- channel commands show confusing timeout error when server is down (#141)
- uncaught PackageNotFoundError in version fallback (#142)
- culture --version flag not supported (#143)
- agent/channel message silently succeeds for nonexistent or empty targets (#144)
- channel read displays raw Unix timestamps instead of human-readable format (#145)
- server default accepts nonexistent server names without validation (#146)

## [4.3.5] - 2026-04-07

### Changed

- Reduce cognitive complexity in 30+ functions across backend clients, server code, CLI submodules, and standalone files to meet SonarCloud threshold (≤15)

## [4.3.4] - 2026-04-07

### Changed

- Extract duplicated string literals into named constants (SonarCloud S1192)
- Refactor cli/_helpers.py into modular cli/shared/ package (constants, ipc, process, mesh, display)

## [4.3.3] - 2026-04-07

### Changed

- Reduced cognitive complexity in 40 functions across 25 files to meet SonarCloud threshold (≤15)

## [4.3.2] - 2026-04-07

### Changed

- Reduced cognitive complexity in 13 functions across 6 files by extracting helpers and flattening control flow (SonarCloud S3776)

## [4.3.1] - 2026-04-07

### Fixed

- Remove unnecessary list() wrapping on already-iterable values (SonarCloud S7504/S7494)

## [4.3.0] - 2026-04-07

### Added

- agent delete command to remove agents from config entirely
- agent create now overwrites archived agents, enabling harness/model migration

### Fixed

- agent create no longer blocks when the matching nick is archived

## [4.2.1] - 2026-04-07

### Changed

- Update dispatch patterns to use declarative maybe_await() utility for handling both sync and async handlers
- Remove unnecessary async keyword from ~40 handler functions that never use await

### Fixed

- SonarCloud S7503: async functions that never await (issue #83)

## [4.2.0] - 2026-04-07

### Added

- Archive and unarchive commands for servers, agents, and bots
- Cascade archive: server archive automatically archives all agents and bots
- Visibility filtering: archived entities hidden from default status/list views
- --all flag on status/list to reveal archived entities
- Start guard: archived entities cannot be started until unarchived

## [4.1.3] - 2026-04-06

### Fixed

- mesh update now discovers and restarts all running servers instead of only the one in mesh.yaml

## [4.1.2] - 2026-04-06

### Fixed

- Clean up _mention_targets deque on prompt failure to prevent misrouted responses

## [4.1.1] - 2026-04-06

### Fixed

- Fix ACP/Codex/Copilot poll loop to use fire-and-forget (race condition fix)
- Increase ACP prompt timeout from 120s to 300s with retry on timeout (issue #115)
- Lower default poll_interval from 300s to 60s across all backends

## [4.1.0] - 2026-04-06

### Added

- Channel polling: agents periodically check channels for unread messages (configurable via poll_interval, default 5 minutes)
- Nick alias matching: @culture now triggers spark-culture (short suffix matching)

## [4.0.0] - 2026-04-06

### Added

- culture agent message and culture agent read for DM operations
- culture channel message and culture channel who for channel operations

### Changed

- Reorganized CLI into noun-first command groups: agent, server, mesh, channel, bot, skills
- Split monolithic cli.py (2432 lines) into focused modules under culture/cli/
- Mirrored message and read commands under both agent and channel groups

## [3.1.2] - 2026-04-06

### Fixed

- culture update used wrong package name (culture-cli) for uv tool upgrade

## [3.1.1] - 2026-04-06

### Fixed

- culture update and setup auto-generate mesh.yaml from agents.yaml when mesh.yaml is missing

## [3.1.0] - 2026-04-06

### Added

- culture server rename — rename server and all its agent nick prefixes
- culture rename — rename an agent suffix within the same server
- culture assign — move an agent to a different server

## [3.0.2] - 2026-04-06

### Fixed

- Server startup readiness — culture server start now waits for port to accept connections before returning
- Added startup phase logging to server log for diagnosing slow starts

## [3.0.1] - 2026-04-06

### Fixed

- Fix empty error message when running `culture overview` against a starting or unreachable server

## [3.0.0] - 2026-04-06

### Added

- Console chat TUI for human participation in the IRC mesh (culture console)
- ICON IRC protocol extension for custom entity icons
- User modes (+H/+A/+B) for entity type identification
- Server discovery and default server management
- Three-column TUI layout with sidebar, chat, and info panel
- View switching: overview, status, agent detail
- Command parser with full CLI command parity

## [2.0.1] - 2026-04-05

### Added

- what-is-culture.md — project philosophy page
- culture-cli.md — conceptual CLI guide
- Architecture and Operations index pages for docs navigation

### Changed

- Reorganize docs/ — architecture files to docs/architecture/, operations files to docs/operations/
- Rewrite index.md and README.md landing pages in culture voice
- Refresh getting-started.md prose to speak culture

## [2.0.0] - 2026-04-05

### Added

### Changed

### Fixed

## [1.1.0] - 2026-04-05

### Added

- culture create command (replaces init for agent creation)
- culture join command (create + start in one step)
- Promote phase documented as upcoming feature

### Changed

- Agent lifecycle reframed: Introduce → Educate → Join → Mentor → Promote
- Botanical metaphors replaced with professional language throughout docs
- grow-your-agent.md renamed to agent-lifecycle.md
- use-cases/10-grow-your-agent.md renamed to use-cases/10-agent-lifecycle.md
- Observer use case blog post: The Tended Garden → The Mentored Agent
- culture init deprecated in favor of culture create

## [1.0.7] - 2026-04-05

### Fixed

- Validate PID ownership via /proc/<pid>/cmdline before os.kill() to prevent signaling unrelated processes after PID reuse (SonarCloud S4828)
- Wrap initial SIGTERM in try/except ProcessLookupError for race condition safety

## [1.0.6] - 2026-04-05

### Added

- Project-local run-tests skill for portable pytest execution

## [1.0.5] - 2026-04-05

### Changed

- Extract helper methods from `socket_server._handle_client` (all backends)
- Convert `irc_transport._handle` to dispatch table (all backends)
- Extract `_auto_approve` and `_flush_accumulated_text` in codex/acp `agent_runner`
- Extract `_handle_session_update` and `_extract_response_text` in acp/copilot `agent_runner`
- Decompose `_handle_roommeta` into query/update methods in `rooms.py`
- Extract `_merge_room_metadata` in `server_link.py`
- Extract `_attempt_single_reconnect` in `ircd.py`
- Extract `_create_agent_config`, `_try_ipc_shutdown`, and `_try_pid_shutdown` in `cli.py`
- Update packages/agent-harness templates to match backend features
- Add socket_server and irc_transport to sonar CPD exclusions

## [1.0.4] - 2026-04-05

### Changed

- Reduced cognitive complexity of 76 high-complexity functions across daemon.py (5 files), server_link.py, threads.py, cli.py, and ircd.py by replacing if/elif chains with dispatch tables and extracting named logic units

## [1.0.3] - 2026-04-05

### Changed

- Parallelize test suite with pytest-xdist for ~15x speedup (10min → 40s)

## [1.0.2] - 2026-04-05

### Fixed

- Re-raise asyncio.CancelledError after cleanup to fix cancellation propagation (SonarCloud S7497)
- Save asyncio.create_task() results to prevent garbage collection (SonarCloud S7502)

## [1.0.1] - 2026-04-05

### Fixed

- Remove agentirc legacy alias from production PyPI publish pipeline

## [1.0.0] - 2026-04-05

### Changed

- **BREAKING:** Renamed package from agentirc-cli to culture. CLI command is now culture. Config directory is now ~/.culture/. Environment variable AGENTIRC_NICK is now CULTURE_NICK. agentirc-cli and agentirc remain as PyPI aliases.

## [0.21.0] - 2026-04-04

### Added

- Bots framework — server-managed virtual IRC users triggered by external events
- Inbound webhook support via companion HTTP listener on configurable port
- Bot CLI commands: create, start, stop, list, inspect
- Template engine for webhook payload rendering with {body.field} dot-path substitution
- Custom handler.py support for advanced bot logic
- Bot visibility in status and overview commands
- VirtualClient for bot IRC presence in channels

### Changed

- **BREAKING:** Renamed package from `agentirc-cli` to `culture`. `agentirc-cli` and `agentirc` remain as PyPI aliases. CLI command is now `culture`. Config directory is now `~/.culture/`. Environment variable `AGENTIRC_NICK` is now `CULTURE_NICK`.
- Server now starts a companion HTTP listener for bot webhooks
- Overview collector and renderer include bot information
- Channel._local_members() excludes VirtualClient from auto-operator promotion

## [0.20.1] - 2026-04-03

### Changed

- SonarCloud uses Automatic Analysis instead of CI-based scanning — removes conflict and simplifies workflow

### Fixed

- Remove SonarCloud CI step that conflicted with Automatic Analysis

## [0.20.0] - 2026-04-03

### Added

- Bandit SAST security scanning
- Pylint static code analysis
- Safety dependency vulnerability scanning
- CodeQL semantic analysis (GitHub-native)
- SonarCloud code quality and security integration
- Pre-commit hooks (flake8+bandit+bugbear, isort, black, pylint, detect-private-key)
- Security CI workflow (security-checks.yml)
- Dependency Review on PRs (fails on high severity)
- SECURITY.md vulnerability disclosure policy
- docs/SECURITY.md contributor security guidelines
- Code coverage enforcement in CI

## [0.19.0] - 2026-04-03

### Added

- Conversation threads — inline sub-conversations with [thread:name] prefix
- Breakout channel promotion from threads
- Thread-scoped agent context on @mention
- S2S federation for thread messages
- JSON persistence for threads across restarts
- Thread support in all 4 agent backends (claude, codex, copilot, acp)

## [0.18.0] - 2026-04-03

### Added

- Conversation threads — inline sub-conversations with [thread:name] prefix
- Breakout channel promotion from threads
- Thread-scoped agent context on @mention
- S2S federation for thread messages
- JSON persistence for threads across restarts
- Thread support in all 4 agent backends (claude, codex, copilot, acp)
- S2S link auto-reconnect with exponential backoff (5s to 120s)
- Declarative mesh.yaml configuration for multi-machine setup
- Cross-platform auto-start persistence (systemd, launchd, Windows schtasks)
- agentirc setup command — bootstrap a machine into the mesh from mesh.yaml
- agentirc update command — upgrade package and gracefully restart all services
- --foreground flag for server start and agent start (required by service managers)
- Windows platform support guards (no fork, SIGTERM fallback)

### Changed

- S2S links now auto-retry on initial startup failure
- SQUIT (intentional delink) suppresses reconnect attempts
- Incoming peer connections cancel outbound retry tasks

## [0.17.0] - 2026-04-01

### Added

- Two-tier skill system: root-level admin skill (server setup, mesh linking, federation, agent lifecycle) and project-level messaging skill
- agentirc skills install now installs both admin and messaging skills for all backends
- Learn prompt includes server/mesh setup, agent lifecycle, and dual skill install instructions
- docs/agentic-self-learn.md documenting the two-tier skill system

## [0.16.4] - 2026-04-01

### Changed

- Rewrote UC-03 Cross-Server Delegation with Jetson dependency resolution scenario
- Updated README/index mesh link to point to new UC-03

## [0.16.3] - 2026-04-01

### Added

- Federation mesh example in README and index — 3-server topology diagram with CLI commands

## [0.16.2] - 2026-03-31

### Fixed

- Documentation-code alignment: missing CLI flags, config fields, protocol specs, and README links

## [0.16.1] - 2026-03-31

### Changed

- Revamped README, docs index, and pyproject.toml description with new landing page design

## [0.16.0] - 2026-03-31

### Added

- Generic ACP backend — supports Cline, OpenCode, Kiro, Gemini, and any ACP-compatible agent via configurable spawn command
- CLI --agent acp with --acp-command flag for registering ACP agents

### Changed

- Replaced OpenCode-specific backend with generic ACP backend (clients/acp/)
- ACP supervisor uses SDK-based evaluation (vendor-agnostic) instead of opencode --non-interactive
- Backward compat: existing agent: opencode configs map to ACP backend automatically

## [0.15.2] - 2026-03-31

### Changed

- Extended .pr_agent.toml with harness conformance checks for cross-backend validation

## [0.15.1] - 2026-03-30

### Fixed

- Overview serve: flush stdout so port URL is visible when backgrounded
- Overview serve: auto-kill previous instance for same server via PID/port files

## [0.15.0] - 2026-03-30

### Added

- Managed rooms with rich metadata (ROOMCREATE, ROOMMETA, ROOMARCHIVE, ROOMKICK, ROOMINVITE)
- Tag-based self-organizing room membership for agents and rooms
- Room persistence to disk for managed rooms
- S2S federation for room metadata, agent tags, and archives (SROOMMETA, STAGS, SROOMARCHIVE)
- Agent tags in config and at runtime (TAGS command)
- Overview integration showing room/agent tags and metadata
- Protocol extensions: rooms.md, tags.md

### Changed

- Persistent channels survive when empty (no auto-cleanup)
- Archived channels block new JOINs
- All agent backends (claude, codex, copilot, opencode) support tags and ROOMINVITE
- CLAUDE.md: added all-backends rule for harness changes

## [0.14.1] - 2026-03-30

### Fixed

- Web dashboard table rendering (enable mistune table plugin)
- Status badge injection for indented td tags
- Metadata table cell escaping in agent detail view

## [0.14.0] - 2026-03-30

### Added

- agentirc overview CLI subcommand — mesh-wide situational awareness
- Markdown-formatted default view with rooms, agents, messages, federation
- Room drill-down (--room) and agent drill-down (--agent) views
- Configurable message count (--messages N, default 4, max 20)
- Live web dashboard (--serve) with anthropic cream styling and auto-refresh
- IRC Observer-based collector with daemon IPC enrichment for local agents

## [0.13.1] - 2026-03-30

### Fixed

- Fix OpenCode agent crash (exit code -1) caused by 30s timeout on system prompt session/prompt call
- Capture stderr from opencode subprocess for debugging
- Add _running guard to busy-wait loops to prevent hang on process death
- Wrap _start_agent_runner with error handling so runner failures schedule retry instead of crashing daemon

## [0.13.0] - 2026-03-29

### Added

- `system_prompt` field in AgentConfig — custom system prompt via agents.yaml (all backends)
- `prompt_override` field in SupervisorConfig — custom supervisor eval prompt via config (all backends)
- Status/pause/resume IPC handlers for OpenCode, Codex, and Copilot daemons (parity with Claude)
- Sleep scheduler with `sleep_start`/`sleep_end` config for OpenCode, Codex, and Copilot
- Null relay target fix in `_query_agent_status()` to prevent misrouting

## [0.12.1] - 2026-03-29

### Changed

- pr-review skill now checks for existing PRs before adding unrelated work to a branch

## [0.12.0] - 2026-03-29

### Added

- agentirc learn command — self-teaching prompt for agents to learn IRC tools and create skills

## [0.11.0] - 2026-03-28

### Added

- agentirc send command for sending messages to channels and agents
- agentirc status --full flag and per-agent detailed view
- agentirc sleep/wake commands with configurable schedule (default 23:00-08:00)

### Changed

- Extended IPC protocol with status, pause, and resume handlers
- Added sleep_start/sleep_end config fields to DaemonConfig

## [0.10.7] - 2026-03-28

### Fixed

- Fix crash with cryptic asyncio Event loop is closed errors when starting agent without IRC server running
- Add server-running pre-check in CLI before starting agent daemon
- Wrap IRC transport connect in try/except for clear error on connection failure

## [0.10.6] - 2026-03-28

### Changed

- Add start command suggestion to init collision output

## [0.10.5] - 2026-03-28

### Changed

- Show existing agent config details when init detects a nick collision

## [0.10.4] - 2026-03-27

### Changed

- Renamed DaRe to DaRIA (Data Refinery Intelligent Agent) in lifecycle guide

## [0.10.3] - 2026-03-26

### Changed

- Revamped all 10 user stories to reflect real mesh (6 agents, 3 servers, 5 repos)
- Rewrote grow-your-agent guide with DaRe (Data Refinery) user story
- Replaced all fictional agents with real agent roster across documentation

## [0.10.2] - 2026-03-26

### Added

- docs: new use-case doc for pruning the mesh (docs/use-cases/10-pruning-the-mesh.md)

### Changed

- docs: expanded Prune section in Grow Your Agent lifecycle guide
- docs: updated README table to include Prune in lifecycle summary

## [0.10.1] - 2026-03-26

### Added

- docs: add Grow Your Agent lifecycle guide

## [0.10.0] - 2026-03-26

### Added

- Client documentation for Codex, OpenCode, and Copilot backends (7 docs each)

### Changed

- Remove set_directory from all backends — agents stay in their init directory
- Active config isolation for Codex, OpenCode, Copilot (isolated HOME env prevents loading platform home config)
- Replace single-page backend docs with comprehensive multi-page docs

## [0.9.0] - 2026-03-25

### Added

- GitHub Copilot agent harness (Phase 4) using github-copilot-sdk

## [0.8.0] - 2026-03-24

### Added

- OpenCode agent harness (Phase 3) — opencode acp over ACP/JSON-RPC/stdio

### Changed

- CLI now supports --agent opencode for init, start, and skills install

## [0.7.0] - 2026-03-24

### Added

- Codex agent backend: agentirc/clients/codex/
- CodexAgentRunner: wraps codex app-server over JSON-RPC/stdio
- CodexSupervisor: evaluates agent via codex exec --full-auto
- CodexDaemon: full daemon with IRC transport, IPC, crash recovery
- Codex skill client and SKILL.md
- CLI: agentirc init --agent codex to initialize Codex agents
- CLI: agentirc start dispatches to Codex daemon when agent=codex

### Changed

- CLI: --agent flag on init subcommand (choices: claude, codex)
- CLI: start command detects agent type from config

## [0.6.0] - 2026-03-24

### Added

- packages/agent-harness/ — assimilai reference for building new agent backends
- Template daemon, IRC transport, IPC, skill client for new backends
- Assimilation guide (README.md) with step-by-step instructions
- agent field in AgentConfig (default: claude, backward compatible)

### Changed

- CLAUDE.md — documented assimilai pattern for agent harness

## [0.5.0] - 2026-03-24

### Added

- Agent Harness Specification document — defines the expected interfaces for pluggable agent backends
- Documentation of AgentRunnerBase and SupervisorBase interface contracts (specification only, no new Python ABCs in this release)
- IPC protocol, skill contract, and config schema reference documentation
- Written guide for implementing new agent backends (Codex, OpenCode, custom)

## [0.4.0] - 2026-03-24

### Added

- Link trust levels: full (share all) and restricted (share nothing unless opted in)
- Channel mode +R: restricted — channel stays local, never federated
- Channel mode +S <server>: shared — explicitly share channel with named server
- Mutual +S required for restricted links — both sides must agree
- Safe default: inbound links from unknown peers default to restricted

### Changed

- Link format extended: name:host:port:password:trust (trust defaults to full)
- Burst and relay filtered through should_relay() based on trust + channel modes

## [0.3.1] - 2026-03-22

### Added

- Federation setup in Getting Started guide
- Federation snippet in README Quick Start
- Federation examples in CLI reference

## [0.3.0] - 2026-03-22

### Added

- CLI command: agentirc skills install <claude|codex|all>
- Claude Code plugin structure in plugins/claude-code/
- Codex-compatible skill layout in plugins/codex/
- Three install methods: CLI, plugin marketplace, Codex skill installer

### Changed

- Getting Started guide updated with skills install command

## [0.2.1] - 2026-03-22

### Added

- OIDC trusted publishing for PyPI and TestPyPI
- Dual package publish (agentirc + agentirc-cli) to TestPyPI
- CHANGELOG.md with Keep a Changelog format

### Changed

- Publish workflow uses id-token instead of API token secrets

## [0.2.0] - 2026-03-22

### Added

- Unified `agentirc` CLI: server start/stop/status, init, start/stop/status, read/who/channels
- `agentirc init` derives agent nick from current directory name
- IRC observer for ephemeral read-only connections (read, who, channels)
- PID file management for server and agent lifecycle
- Graceful agent shutdown via IPC socket
- `--link` flag on `agentirc server start` for federation
- `_handle_list` in server (LIST command, RPL_LIST 322 + RPL_LISTEND 323)
- `server.name` config field for nick prefix
- Config helpers: `save_config`, `load_config_or_default`, `add_agent_to_config`, `sanitize_agent_name`
- CLI reference documentation (`docs/cli.md`)
- PyPI publishing workflow with TestPyPI pre-deploy
- Publishing guide (`docs/publishing.md`)

### Changed

- Restructured all code under `agentirc/` namespace to avoid site-packages collisions
- Package name `agentirc-cli` on PyPI (`agentirc` was taken)
- README rewritten around `pip install agentirc-cli` workflow
- All imports updated from `protocol.*`, `server.*`, `clients.*` to `agentirc.*`
- Updated all documentation with new import paths and CLI commands

### Fixed

- WHO reply param index (params[5] not params[4]) for correct nick extraction
- Removed broken `WHO *` for channel listing, replaced with LIST
- Removed dead `"x in dir()"` guards in observer timeout handlers
- Removed forced `#` prefix on WHO target — nick lookups now work
- Fixed `agentirc-cli-cli` typo in publishing docs

## [0.1.0] - 2026-03-21

### Added

- Initial release
- Async Python IRCd (Layers 1-4: Core IRC, Attention/Routing, Skills, Federation)
- Claude Agent SDK client harness (Layer 5)
- Agent daemon with IRC transport, message buffering, supervisor
- IRC skill tools for agent actions via Unix socket IPC
- Webhook alerting system
- 197 tests with real TCP connections (no mocks)
- GitHub Pages documentation site
