agentirc-cli 0.15.1__tar.gz → 0.15.2__tar.gz

agentirc_cli-0.15.2/.pr_agent.toml

@@ -0,0 +1,38 @@
+[pr_reviewer]
+extra_instructions = """
+## Project Context
+
+- The `packages/` directory is ONLY for the "assimilai" pattern (internal packages copied into other projects). Top-level directories like `server/`, `protocol/`, and `clients/` are standalone application packages — they belong at the top level, NOT under `packages/`.
+- The "no mocks for the server" testing rule applies to IRC server tests only. Client libraries (like SkillClient) may use mock/stub servers in unit tests. Integration tests in `test_integration_layer5.py` exercise the real server stack.
+- Nick format validation (`<server>-<agent>`) is enforced by the IRC server at connection time. Config loading is a data layer and should not duplicate server-side validation.
+- Features explicitly marked as TODO or listed in the spec's "Deferred Features" section are known limitations, not bugs.
+- The `clients/` directory contains agent client harnesses (daemons). It is NOT an internal package for assimilation.
+
+## Harness Conformance (CRITICAL)
+
+The authoritative spec is `docs/agent-harness-spec.md`. There are 4 agent backends under `agentirc/clients/` — claude, codex, copilot, opencode — plus a reference implementation in `packages/agent-harness/`. The all-backends rule: a feature that exists in only one backend is a bug.
+
+When reviewing changes to any file under `agentirc/clients/` or `packages/agent-harness/`, apply these checks:
+
+### Cross-backend propagation
+When a PR changes a file in `agentirc/clients/<backend>/`, check whether the same change must be applied to the other 3 backends. If corresponding files in other backends were not updated, flag each missing backend. Exception: `agent_runner.py` and `supervisor.py` contain backend-specific logic — only structural/interface changes need propagation, not internal implementation details.
+
+### Generic file identity
+These files MUST be identical across all 4 backends and `packages/agent-harness/`, except for import paths (`from agentirc.clients.<backend>.`): `irc_transport.py`, `message_buffer.py`, `socket_server.py`, `ipc.py`, `webhook.py`, `skill/irc_client.py`. If any of these is changed in one backend, flag that all other backends AND the reference in `packages/agent-harness/` must get the same change.
+
+### Interface contract
+If `agent_runner.py` is modified, verify the public interface still satisfies `docs/agent-harness-spec.md` AgentRunnerBase: `start(initial_prompt)`, `stop()`, `send_prompt(text)`, `is_running()`, `session_id` property, `on_message` callback, `on_exit` callback. If `supervisor.py` is modified, verify SupervisorBase: `start()`, `stop()`, `observe(turn)`, `on_whisper` callback, `on_escalation` callback. Flag any missing or renamed interface members.
+
+### Daemon contract
+If `daemon.py` is modified, verify all IPC dispatch handlers are still present: `irc_send`, `irc_read`, `irc_ask`, `irc_join`, `irc_part`, `irc_who`, `irc_channels`, `compact`, `clear`, `shutdown`. Also verify structural features (crash recovery, `_mention_targets`, sleep scheduler) are consistent across backends. If a structural feature is added to one daemon, flag its absence in the others.
+
+### Config schema
+If `config.py` is modified, verify the same dataclass field names and types exist across all 4 backends. Only default values may differ by backend (e.g., model names). If a new field is added to one backend's config, flag its absence in the others.
+
+### SKILL.md consistency
+If any `SKILL.md` under `agentirc/clients/<backend>/skill/` is modified, verify all backends' SKILL.md documents the same required commands: send, read, ask, join, part, channels, who. Flag format or content inconsistencies.
+
+### Spec-doc alignment
+If `docs/agent-harness-spec.md` is changed, verify that client docs in `docs/clients/` and the actual code in `agentirc/clients/` still match the updated spec. If code or docs under `docs/clients/` is changed, verify it does not contradict the spec.
+"""
+num_max_findings = 10

{agentirc_cli-0.15.1 → agentirc_cli-0.15.2}/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to this project will be documented in this file.
 
 Format follows [Keep a Changelog](https://keepachangelog.com/).
 
+## [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
 
 

{agentirc_cli-0.15.1 → agentirc_cli-0.15.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentirc-cli
-Version: 0.15.1
+Version: 0.15.2
 Summary: IRC protocol chatrooms for AI agents (and humans allowed)
 Project-URL: Homepage, https://github.com/OriNachum/agentirc
 Author: Ori Nachum

agentirc_cli-0.15.2/agentirc/__init__.py

@@ -0,0 +1,3 @@
+from importlib.metadata import version as _v
+
+__version__ = _v("agentirc-cli")

agentirc_cli-0.15.2/docs/harness-conformance.md

@@ -0,0 +1,84 @@
+---
+title: "Harness Conformance"
+parent: "Agent Harness"
+nav_order: 8
+---
+
+# Harness Conformance Checks
+
+## Overview
+
+Qodo PR review is configured to enforce conformance across all 4 agent
+backends (claude, codex, copilot, opencode). When a PR touches files under
+`agentirc/clients/` or `packages/agent-harness/`, Qodo applies 7 checks
+that prevent backends from drifting apart.
+
+The authoritative spec is `docs/agent-harness-spec.md`.
+
+## Configuration
+
+All conformance rules live in `.pr_agent.toml` under the `[pr_reviewer]`
+section's `extra_instructions` field.
+
+## Checks
+
+### 1. Cross-backend propagation
+
+When a file in one backend changes, Qodo flags if the corresponding files
+in the other 3 backends were not updated. Exception: `agent_runner.py` and
+`supervisor.py` contain backend-specific logic — only structural/interface
+changes need propagation.
+
+### 2. Generic file identity
+
+These files must be identical across all backends and the reference in
+`packages/agent-harness/`, except for import paths:
+
+- `irc_transport.py`
+- `message_buffer.py`
+- `socket_server.py`
+- `ipc.py`
+- `webhook.py`
+- `skill/irc_client.py`
+
+### 3. Interface contract
+
+Changes to `agent_runner.py` or `supervisor.py` are checked against the
+spec's `AgentRunnerBase` and `SupervisorBase` interfaces.
+
+**AgentRunnerBase** requires: `start(initial_prompt)`, `stop()`,
+`send_prompt(text)`, `is_running()`, `session_id`, `on_message`, `on_exit`.
+
+**SupervisorBase** requires: `start()`, `stop()`, `observe(turn)`,
+`on_whisper`, `on_escalation`.
+
+### 4. Daemon contract
+
+Changes to `daemon.py` are checked for all IPC dispatch handlers:
+`irc_send`, `irc_read`, `irc_ask`, `irc_join`, `irc_part`, `irc_who`,
+`irc_channels`, `compact`, `clear`, `shutdown`.
+
+Structural features (crash recovery, `_mention_targets`, sleep scheduler)
+must be consistent across backends.
+
+### 5. Config schema
+
+Changes to `config.py` must preserve the same field names and types across
+all backends. Only default values (model names, agent identifiers) may
+differ.
+
+### 6. SKILL.md consistency
+
+All backends' `SKILL.md` must document the same required commands: `send`,
+`read`, `ask`, `join`, `part`, `channels`, `who`.
+
+### 7. Spec-doc alignment
+
+Changes to `docs/agent-harness-spec.md` are cross-referenced against
+client docs in `docs/clients/` and the code in `agentirc/clients/`.
+Changes to client docs or code are checked against the spec.
+
+## Adding New Checks
+
+Edit `.pr_agent.toml` and add a new subsection under the
+`## Harness Conformance (CRITICAL)` heading in `extra_instructions`.