agentharnesses-cli 0.1.2__tar.gz → 0.1.4__tar.gz

{agentharnesses_cli-0.1.2 → agentharnesses_cli-0.1.4}/PKG-INFO

@@ -1,12 +1,13 @@
 Metadata-Version: 2.4
 Name: agentharnesses-cli
-Version: 0.1.2
+Version: 0.1.4
 Summary: CLI tools for agentharnesses.io
 Project-URL: Homepage, https://agentharnesses.io
 Project-URL: Repository, https://github.com/agentharnesses/cli
 License-Expression: Apache-2.0
 Requires-Python: >=3.10
 Requires-Dist: click>=8.1
+Requires-Dist: harnesses-ref>=0.1.0
 Description-Content-Type: text/markdown
 
 # agentharnesses-cli
@@ -64,6 +65,35 @@ When using the `claude` preset (default), also installs:
             └── SKILL.md
 ```
 
+The metaskill is cloned fresh from [agentharnesses/metaskill](https://github.com/agentharnesses/metaskill) at init time, so you always get the latest version.
+
+### `ahar validate`
+
+Validate a harness directory structure:
+
+```bash
+ahar validate ./my-harness
+```
+
+### `ahar read`
+
+Read a property from a harness's `HARNESS.md` frontmatter:
+
+```bash
+ahar read ./my-harness name
+ahar read ./my-harness description
+```
+
+### `ahar prompt`
+
+Render a harness as prompt XML for agent injection:
+
+```bash
+ahar prompt ./my-harness
+```
+
+These commands are backed by [harnesses-ref](https://pypi.org/project/harnesses-ref/), the reference implementation for the Agent Harnesses standard.
+
 ## Publishing
 
 Releases are published to PyPI automatically when a version tag is pushed:

{agentharnesses_cli-0.1.2 → agentharnesses_cli-0.1.4}/README.md

@@ -53,6 +53,35 @@ When using the `claude` preset (default), also installs:
             └── SKILL.md
 ```
 
+The metaskill is cloned fresh from [agentharnesses/metaskill](https://github.com/agentharnesses/metaskill) at init time, so you always get the latest version.
+
+### `ahar validate`
+
+Validate a harness directory structure:
+
+```bash
+ahar validate ./my-harness
+```
+
+### `ahar read`
+
+Read a property from a harness's `HARNESS.md` frontmatter:
+
+```bash
+ahar read ./my-harness name
+ahar read ./my-harness description
+```
+
+### `ahar prompt`
+
+Render a harness as prompt XML for agent injection:
+
+```bash
+ahar prompt ./my-harness
+```
+
+These commands are backed by [harnesses-ref](https://pypi.org/project/harnesses-ref/), the reference implementation for the Agent Harnesses standard.
+
 ## Publishing
 
 Releases are published to PyPI automatically when a version tag is pushed:

{agentharnesses_cli-0.1.2 → agentharnesses_cli-0.1.4}/pyproject.toml

@@ -7,6 +7,7 @@ readme = "README.md"
 requires-python = ">=3.10"
 dependencies = [
     "click>=8.1",
+    "harnesses-ref>=0.1.0",
 ]
 
 [project.urls]
@@ -25,3 +26,8 @@ source = "vcs"
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/ahar"]
+
+[dependency-groups]
+dev = [
+    "pytest>=7.0",
+]

{agentharnesses_cli-0.1.2 → agentharnesses_cli-0.1.4}/src/ahar/commands/init.py

@@ -14,39 +14,25 @@ _MAINTAIN_SKILLS_INDEX_DEST = "skills/maintenance/SKILLS.md"
 _MAINTAIN_SKILL = """\
 ---
 name: modify-harness
-description: Use when asked to maintain, update, or extend this harness — updating HARNESS.md, adding skills and references, managing the skill index.
+description: Update harness structure files — HARNESS.md, SKILLS.md indexes, REFERENCES.md — to keep routing and descriptions accurate as the harness evolves.
 ---
 
-## Maintaining the Harness
+## Role
 
-When asked to maintain, update, or extend this harness, follow these conventions.
+Keep the harness self-consistent when skills or references are added, renamed, or removed.
 
-When **maintaining the harness** (adding, moving, or renaming files), use `reverse_disclose.py` to find every `.md` file above the target that links to it — so you can update all references that would break:
+## What to do
 
-```
-python3 .claude/skills/agent-harnesses/scripts/reverse_disclose.py <target_path>
-```
+1. Use reverse progressive disclosure (via the `agent-harnesses` skill) to find which index files reference the target path
+2. Read the current state of each affected file
+3. Apply the change: add, update, or remove the relevant entry
+4. Ensure descriptions remain accurate and routing summaries reflect actual contents
 
-Run this before and after any structural change. The output lists each ancestor `.md` file that references the target, with line numbers and link text, so nothing is left pointing to a stale path.
+## Conventions
 
-### HARNESS.md
-- Keep the `## Skills` section in sync with entries in `skills/SKILLS.md`
-- Keep the `## References` section in sync with entries in `references/REFERENCES.md`
-- Update the `description` frontmatter field when the harness scope changes
-
-### Adding a skill bucket
-1. Create `skills/<bucket-name>/<skill-name>/SKILL.md` with a frontmatter `name` and `description`
-2. Add an entry to `skills/<bucket-name>/SKILLS.md` summarizing when to use the skill
-3. Ensure `skills/SKILLS.md` references the bucket
-4. Add a bullet to the `## Skills` section in `HARNESS.md`
-
-### Adding a reference document
-1. Add the document to `references/`
-2. Add an entry to `references/REFERENCES.md` describing the document's purpose
-3. Add a bullet to the `## References` section in `HARNESS.md`
-
-### General conventions
-- Keep skill descriptions actionable: "Use when..." not "This skill..."
+- Keep `HARNESS.md` `## Skills` and `## References` sections in sync with `skills/SKILLS.md` and `references/REFERENCES.md`
+- Update the `description` frontmatter in `HARNESS.md` when the harness scope changes
+- Skill descriptions should be actionable: "Use when..." not "This skill..."
 - Reference documents should be stable facts; skill buckets contain executable guidance
 - Prefer updating existing skill buckets over creating new ones when scope overlaps
 """
@@ -81,17 +67,9 @@ TODO: write the entry message Claude should internalize when this harness loads.
 
 ## How to Find Information for Claude
 
-Use the `agent-harnesses` skill to explore the harness, just in time, based on prompts from the user. Run `disclose.py` with `python3` against this harness directory to progressively explore its contents — select only what is relevant and repeat until the session is complete, then read the returned resources.
-
-Do not load skills or references speculatively. Use `disclose.py` to find resources when necessary. Any time you need to find anything in the harness, and you don't already know where it exists, use `disclose.py`.
-
-When **maintaining the harness** (adding, moving, or renaming files), use `reverse_disclose.py` to find every `.md` file above the target that links to it — so you can update all references that would break:
-
-```
-python3 .claude/skills/agent-harnesses/scripts/reverse_disclose.py <target_path>
-```
+Use the `agent-harnesses` skill to explore the harness just in time, based on prompts from the user. Select only what is relevant and repeat until the session is complete, then read the returned resources.
 
-Run this before and after any structural change. The output lists each ancestor `.md` file that references the target, with line numbers and link text, so nothing is left pointing to a stale path.
+When **maintaining the harness** (adding, moving, or renaming files), consult the `agent-harnesses` skill for reverse progressive disclosure to keep routing files in sync.
 
 ## Skills
 

agentharnesses_cli-0.1.4/tests/test_init.py

@@ -0,0 +1,137 @@
+import json
+from pathlib import Path
+
+import pytest
+from click.testing import CliRunner
+
+from ahar.commands.init import scaffold
+from ahar.main import cli
+
+
+# --- scaffold unit tests ---
+
+def test_scaffold_creates_required_files(tmp_path):
+    scaffold(str(tmp_path), "my-harness")
+    assert (tmp_path / "HARNESS.md").exists()
+    assert (tmp_path / "README.md").exists()
+    assert (tmp_path / ".gitignore").exists()
+    assert (tmp_path / ".claude" / "settings.json").exists()
+    assert (tmp_path / "skills" / "SKILLS.md").exists()
+    assert (tmp_path / "references" / "REFERENCES.md").exists()
+
+
+def test_scaffold_harness_md_contains_name(tmp_path):
+    scaffold(str(tmp_path), "my-harness")
+    content = (tmp_path / "HARNESS.md").read_text()
+    assert "name: my-harness" in content
+
+
+def test_scaffold_settings_registers_marketplace(tmp_path):
+    scaffold(str(tmp_path), "my-harness")
+    settings = json.loads((tmp_path / ".claude" / "settings.json").read_text())
+    assert "my-harness" in settings["extraKnownMarketplaces"]
+    assert settings["extraKnownMarketplaces"]["my-harness"]["source"]["source"] == "directory"
+    assert settings["extraKnownMarketplaces"]["my-harness"]["source"]["path"] == str(tmp_path)
+
+
+def test_scaffold_settings_enables_plugin(tmp_path):
+    scaffold(str(tmp_path), "my-harness")
+    settings = json.loads((tmp_path / ".claude" / "settings.json").read_text())
+    assert "my-harness@my-harness" in settings["enabledPlugins"]
+    assert settings["enabledPlugins"]["my-harness@my-harness"] is True
+
+
+def test_scaffold_gitignore_excludes_settings(tmp_path):
+    scaffold(str(tmp_path), "my-harness")
+    content = (tmp_path / ".gitignore").read_text()
+    assert ".claude/settings.json" in content
+
+
+# --- init CLI tests ---
+
+def test_init_empty_preset_creates_scaffold(tmp_path):
+    runner = CliRunner()
+    with runner.isolated_filesystem(temp_dir=tmp_path):
+        result = runner.invoke(cli, ["init", "test-harness"], input="empty\n")
+        assert result.exit_code == 0
+        assert Path("HARNESS.md").exists()
+        assert Path("skills/SKILLS.md").exists()
+        assert Path("references/REFERENCES.md").exists()
+
+
+def test_init_uses_directory_name_as_default(tmp_path):
+    runner = CliRunner()
+    with runner.isolated_filesystem(temp_dir=tmp_path):
+        result = runner.invoke(cli, ["init"], input="empty\n")
+        assert result.exit_code == 0
+        content = Path("HARNESS.md").read_text()
+        assert f"name: {Path.cwd().name}" in content
+
+
+def test_init_fails_if_already_initialized(tmp_path):
+    runner = CliRunner()
+    with runner.isolated_filesystem(temp_dir=tmp_path):
+        Path("HARNESS.md").write_text("---\nname: existing\ndescription: x\n---\n")
+        result = runner.invoke(cli, ["init"], input="empty\n")
+        assert result.exit_code == 1
+
+
+def test_init_empty_preset_skips_metaskill(tmp_path):
+    runner = CliRunner()
+    with runner.isolated_filesystem(temp_dir=tmp_path):
+        result = runner.invoke(cli, ["init", "test-harness"], input="empty\n")
+        assert result.exit_code == 0
+        assert not Path(".claude/skills/agent-harnesses").exists()
+
+
+# --- validate CLI tests ---
+
+def _make_valid_harness(path: Path) -> Path:
+    (path / "HARNESS.md").write_text(
+        "---\nname: Test Harness\ndescription: A test harness.\n---\nBody.\n"
+    )
+    return path
+
+
+def test_validate_valid_harness(tmp_path):
+    _make_valid_harness(tmp_path)
+    runner = CliRunner()
+    result = runner.invoke(cli, ["validate", str(tmp_path)])
+    assert result.exit_code == 0
+    assert "valid" in result.output
+
+
+def test_validate_invalid_harness(tmp_path):
+    (tmp_path / "HARNESS.md").write_text("no frontmatter")
+    runner = CliRunner()
+    result = runner.invoke(cli, ["validate", str(tmp_path)])
+    assert result.exit_code == 1
+
+
+# --- read CLI tests ---
+
+def test_read_name(tmp_path):
+    _make_valid_harness(tmp_path)
+    runner = CliRunner()
+    result = runner.invoke(cli, ["read", str(tmp_path), "name"])
+    assert result.exit_code == 0
+    assert result.output.strip() == "Test Harness"
+
+
+def test_read_description(tmp_path):
+    _make_valid_harness(tmp_path)
+    runner = CliRunner()
+    result = runner.invoke(cli, ["read", str(tmp_path), "description"])
+    assert result.exit_code == 0
+    assert result.output.strip() == "A test harness."
+
+
+# --- prompt CLI tests ---
+
+def test_prompt_renders_xml(tmp_path):
+    _make_valid_harness(tmp_path)
+    runner = CliRunner()
+    result = runner.invoke(cli, ["prompt", str(tmp_path)])
+    assert result.exit_code == 0
+    assert "<harness" in result.output
+    assert "Test Harness" in result.output