foundry-testing-actor 0.2.0__tar.gz → 0.3.0__tar.gz

{foundry_testing_actor-0.2.0 → foundry_testing_actor-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: foundry-testing-actor
-Version: 0.2.0
+Version: 0.3.0
 Summary: Runs a headless Claude Code black-box test-authoring session against one capability's own testing repo — a papeete-actor for one use, with the capability supplied by a sidecar.
 Project-URL: Homepage, https://github.com/papeete-hub/foundry-testing-actor
 Author-email: Papeete Consulting <yoann.remy@outlook.com>
@@ -202,7 +202,7 @@ It never opens a pull request, and never runs what it wrote beyond `pytest --col
 
 | rendering | from |
 |---|---|
-| `ACME.PARTS.CAP.SUP.007.WID-testing` | actor name, git `user.name` (repo half of `source_repo`) |
+| `ACME.PARTS.CAP.SUP.007.WID-testing` | actor name, git `user.name` (`{capability}-testing`) |
 | `acme-lab/ACME.PARTS.CAP.SUP.007.WID-implementation` | `implementation_repo`, when not declared |
 | `acme.parts/sup.007.wid` | the id, split at its `CAP` segment |
 | `acme.parts.cap.sup.007.wid-backend-tests` | the name `papeete-version` versions the test image under |

{foundry_testing_actor-0.2.0 → foundry_testing_actor-0.3.0}/README.md

@@ -179,7 +179,7 @@ It never opens a pull request, and never runs what it wrote beyond `pytest --col
 
 | rendering | from |
 |---|---|
-| `ACME.PARTS.CAP.SUP.007.WID-testing` | actor name, git `user.name` (repo half of `source_repo`) |
+| `ACME.PARTS.CAP.SUP.007.WID-testing` | actor name, git `user.name` (`{capability}-testing`) |
 | `acme-lab/ACME.PARTS.CAP.SUP.007.WID-implementation` | `implementation_repo`, when not declared |
 | `acme.parts/sup.007.wid` | the id, split at its `CAP` segment |
 | `acme.parts.cap.sup.007.wid-backend-tests` | the name `papeete-version` versions the test image under |

{foundry_testing_actor-0.2.0 → foundry_testing_actor-0.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "foundry-testing-actor"
-version = "0.2.0"
+version = "0.3.0"
 description = "Runs a headless Claude Code black-box test-authoring session against one capability's own testing repo — a papeete-actor for one use, with the capability supplied by a sidecar."
 readme = "README.md"
 requires-python = ">=3.11"

{foundry_testing_actor-0.2.0 → foundry_testing_actor-0.3.0}/src/foundry_testing_actor/config.py

@@ -14,7 +14,7 @@ They are now derivations of two fields. Nothing in this package spells a capabil
     source_repo           <owner>/ACME.PARTS.CAP.SUP.007.WID-testing   ← and the only repo
 
     implementation_repo   <owner>/<capability>-implementation  (declared only when it differs)
-    actor_name            <repo half of source_repo>
+    actor_name            {capability}-testing
     actor_slug            same, lowercased, dots to hyphens
     git_author_name       actor_name
     git_author_email      {actor_slug}@users.noreply.github.com
@@ -26,6 +26,15 @@ They are now derivations of two fields. Nothing in this package spells a capabil
     image_name(c)         {capability lowercased}-{c}          ← what implementation versions
     image_ref(r,c,v)      {r}/{capability_path}/{c}:{v}        ← what implementation published
 
+IDENTITY IS `capability` + ROLE, NOT THE REPO HALF. `actor_name` used to be whatever came after
+the `/` in `source_repo`, which reads as a derivation but is really an assumption: that one
+repository holds exactly one actor. Every sidecar in existence satisfies
+`source_repo == "<owner>/" + capability + "-" + ROLE`, so deriving the name from the two facts it
+was always shorthand for produces the identical string — and it keeps producing the right one when
+a capability's three actors come to share a repository, where the repo half would name all three
+the same thing. `source_repo` is unchanged and still required: it is where this actor clones from
+and pushes to, which is a different question from who it is.
+
 THE IMAGE REFS ARE A THREE-WAY CONTRACT. `image_ref` must stay byte-identical to what the
 implementation actor publishes, because this actor recomputes it rather than being told it — and
 `test_image_ref` is what the orchestrating actor parses back apart to run. A component's tests are
@@ -66,6 +75,10 @@ _CAPABILITY_SEGMENT = "cap"
 # convention never writes the field at all, and one that does not says so in one line.
 _IMPLEMENTATION_SUFFIX = "-implementation"
 
+# The role this package plays for the capability it serves. Half of this actor's identity — see
+# `CapabilityConfig.actor_name` — and the half that is a property of the package, not of the use.
+ROLE = "testing"
+
 # What an unsubstituted placeholder looks like: a bare lowercase word in braces, and nothing else.
 # Narrow on purpose — see `CapabilityConfig.expand`.
 _PLACEHOLDER = re.compile(r"\{([a-z_]+)\}")
@@ -233,6 +246,7 @@ class CapabilityConfig:
         )
         # Force the derivations that can fail, here rather than at the first request that needs
         # one. A capability id with no `cap` segment is a typo, and it should not survive startup.
+        _split_repo(config.source_repo, "source_repo")
         _ = config.capability_path, config.actor_name, config.implementation_repo
         return config
 
@@ -240,8 +254,13 @@ class CapabilityConfig:
 
     @property
     def actor_name(self) -> str:
-        """The repo half of `source_repo` — this actor's own name, and its git author name."""
-        return _split_repo(self.source_repo, "source_repo")[1]
+        """`{capability}-{ROLE}` — this actor's own name, and its git author name.
+
+        Not the repo half of `source_repo`, which is the same string for every sidecar that
+        exists but stops being this actor's name alone the moment a capability's actors share a
+        repository. See this module's own docstring.
+        """
+        return f"{self.capability}-{ROLE}"
 
     @property
     def actor_slug(self) -> str:

{foundry_testing_actor-0.2.0 → foundry_testing_actor-0.3.0}/src/foundry_testing_actor/schemas/agentic-context.schema.yaml

@@ -71,8 +71,9 @@ fields:
     type: string
     doc: >-
       `<owner>/<repo>` of the TESTING repository this actor clones, writes black-box tests into,
-      and pushes a `test/<task_id>` branch to. The actor's own name and its git commit identity
-      are derived from the repo half.
+      and pushes a `test/<task_id>` branch to. Where it works, not who it is: the actor's own
+      name and its git commit identity are `<capability>-testing`, derived from `capability`
+      and this package's own role.
 
   implementation_repo:
     type: string

{foundry_testing_actor-0.2.0 → foundry_testing_actor-0.3.0}/tests/test_config.py

@@ -258,3 +258,48 @@ def test_components_may_not_be_empty(sidecar_dict, write_sidecar):
     sidecar_dict["components"] = []
     with pytest.raises(ConfigError, match="empty"):
         CapabilityConfig.load(write_sidecar(sidecar_dict))
+
+
+# ── identity: capability + role, not the repo half ──────────────────────────────────────────
+
+def test_the_actor_name_is_exactly_what_the_repo_half_used_to_be(config):
+    """The no-op half of the change, pinned.
+
+    `actor_name` was `_split_repo(source_repo)[1]`. It is `{capability}-{ROLE}` now. Every
+    sidecar that exists satisfies `source_repo == "<owner>/" + capability + "-" + ROLE`, so the
+    two derivations agree on all of them — which is what makes this releasable on its own, ahead
+    of any repository moving.
+    """
+    assert config.source_repo == f"acme-lab/{config.capability}-testing"
+    assert config.actor_name == config.source_repo.partition("/")[2]
+    assert config.actor_name == "ACME.PARTS.CAP.SUP.007.WID-testing"
+
+
+def test_the_actor_name_no_longer_follows_the_repository(sidecar_dict, write_sidecar):
+    """The point of the change: three actors in one repository still have three names.
+
+    A consolidated capability repository is named for the capability alone, with no role suffix,
+    because all three of its actors live in it. Under the old derivation this actor would have
+    been called `ACME.PARTS.CAP.SUP.007.WID` — and so would both of its siblings.
+    """
+    sidecar_dict["source_repo"] = "acme-lab/ACME.PARTS.CAP.SUP.007.WID"
+    sidecar_dict["implementation_repo"] = "acme-lab/ACME.PARTS.CAP.SUP.007.WID"
+    config = CapabilityConfig.load(write_sidecar(sidecar_dict))
+    assert config.actor_name == "ACME.PARTS.CAP.SUP.007.WID-testing"
+    assert config.git_author_name == config.actor_name
+    assert config.actor_slug == "acme-parts-cap-sup-007-wid-testing"
+    assert config.clone_prefix("TASK-042") == "acme-parts-cap-sup-007-wid-testing-TASK-042-"
+
+
+def test_a_malformed_source_repo_is_refused_even_when_the_implementation_repo_is_declared(
+        sidecar_dict, write_sidecar):
+    """`actor_name` used to validate this shape on its way past.
+
+    The only other reader of `source_repo` at load time is `implementation_repo`, and it reaches
+    the field ONLY when it is not declared — so a sidecar that declares one would have carried a
+    malformed `source_repo` all the way to its first clone.
+    """
+    sidecar_dict["source_repo"] = "just-a-name"
+    sidecar_dict["implementation_repo"] = "acme-lab/ACME.PARTS.CAP.SUP.007.WID-implementation"
+    with pytest.raises(ConfigError, match="source_repo"):
+        CapabilityConfig.load(write_sidecar(sidecar_dict))

{foundry_testing_actor-0.2.0 → foundry_testing_actor-0.3.0}/uv.lock

@@ -18,7 +18,7 @@ wheels = [
 
 [[package]]
 name = "foundry-testing-actor"
-version = "0.2.0"
+version = "0.3.0"
 source = { editable = "." }
 dependencies = [
     { name = "papeete-actor-synchronous-messaging" },