agentforge-framework 0.2.2__tar.gz → 0.2.3__tar.gz

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentforge-framework
-Version: 0.2.2
+Version: 0.2.3
 Summary: A modular framework for coordinating specialized software agents.
 Author: Yash Mhatre
 License-Expression: Apache-2.0
@@ -145,7 +145,7 @@ without notice. See
 ```console
 $ pip install agentforge-framework
 $ agentforge --version
-agentforge 0.2.2
+agentforge 0.2.3
 ```
 
 That is the whole of it. The two routes below the naming note are for a machine
@@ -169,7 +169,7 @@ from the [latest release](https://github.com/yashmhatre/AgentForge/releases/late
 and install the file:
 
 ```console
-$ pip install agentforge_framework-0.2.2-py3-none-any.whl
+$ pip install agentforge_framework-0.2.3-py3-none-any.whl
 ```
 
 Publishing a release is a wizard rather than a checklist:
@@ -200,6 +200,14 @@ What each release contains is in [CHANGELOG.md](CHANGELOG.md).
 
 AgentForge never touches a model API and handles no credentials of its own. Whatever your coding-agent CLI is already authenticated with is what a Run costs.
 
+### Editors and IDEs
+
+AgentForge is a terminal tool. It runs fine from an IDE's terminal, but the IDE is not a Provider and its assistant is not one either.
+
+**Antigravity IDE cannot be a Provider** ([#101](https://github.com/yashmhatre/AgentForge/issues/101)). Checked by running it, so nobody has to derive it again: `antigravity-ide chat` accepts a prompt and reads stdin, which is the right shape for the argument vector — but it is a window launcher. Piping a prompt to it returns exit 0 immediately with `Reading from stdin via: …\code-stdin-XXXX` on stdout and nothing else, ever; the answer goes to a GUI session. A Provider adapter has to read the Agent's result off stdout, so there is nothing for `parse_output` to parse. The same is true of any editor CLI of this shape.
+
+**Do not run another agent against a checkout while a Run is going.** A Run commits every change to a file git already tracks, however it got there ([ADR-0015](docs/adr/0015-a-run-commits-what-it-declared.md)) — so a second agent's half-finished edits are committed into the Run's branch and attributed to a Role. Files nothing in the Run claimed are listed in the pull request body ([ADR-0023](docs/adr/0023-a-commit-names-what-nothing-claimed.md)), which makes it visible at Sign-off but does not prevent it. Use a separate clone.
+
 ## Commands
 
 | Command | What it does |
@@ -331,10 +339,21 @@ code rather than the verdict about the old code.
 
 Read [`CONTEXT.md`](CONTEXT.md) before writing anything, and [`docs/adr/`](docs/adr/) for the decisions that constrain it.
 
-## Tests
+## Changing AgentForge
+
+Clone it and install that clone editable. Never patch the installed copy.
 
 ```console
+$ git clone https://github.com/yashmhatre/AgentForge.git
+$ cd AgentForge
 $ pip install -e ".[dev]"
+```
+
+Editing `site-packages/agentforge_framework/` appears to work and is the one change nothing will catch: the local install diverges from what ships, so the thing that works is not the thing anybody else gets, and the fix is lost the next time the package is upgraded. If a Run is failing badly enough that patching the install looks like the way forward, that is a bug worth filing — [#101](https://github.com/yashmhatre/AgentForge/issues/101) is what happened the last time somebody reached for it.
+
+## Tests
+
+```console
 $ pytest
 ```
 

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/README.md

@@ -127,7 +127,7 @@ without notice. See
 ```console
 $ pip install agentforge-framework
 $ agentforge --version
-agentforge 0.2.2
+agentforge 0.2.3
 ```
 
 That is the whole of it. The two routes below the naming note are for a machine
@@ -151,7 +151,7 @@ from the [latest release](https://github.com/yashmhatre/AgentForge/releases/late
 and install the file:
 
 ```console
-$ pip install agentforge_framework-0.2.2-py3-none-any.whl
+$ pip install agentforge_framework-0.2.3-py3-none-any.whl
 ```
 
 Publishing a release is a wizard rather than a checklist:
@@ -182,6 +182,14 @@ What each release contains is in [CHANGELOG.md](CHANGELOG.md).
 
 AgentForge never touches a model API and handles no credentials of its own. Whatever your coding-agent CLI is already authenticated with is what a Run costs.
 
+### Editors and IDEs
+
+AgentForge is a terminal tool. It runs fine from an IDE's terminal, but the IDE is not a Provider and its assistant is not one either.
+
+**Antigravity IDE cannot be a Provider** ([#101](https://github.com/yashmhatre/AgentForge/issues/101)). Checked by running it, so nobody has to derive it again: `antigravity-ide chat` accepts a prompt and reads stdin, which is the right shape for the argument vector — but it is a window launcher. Piping a prompt to it returns exit 0 immediately with `Reading from stdin via: …\code-stdin-XXXX` on stdout and nothing else, ever; the answer goes to a GUI session. A Provider adapter has to read the Agent's result off stdout, so there is nothing for `parse_output` to parse. The same is true of any editor CLI of this shape.
+
+**Do not run another agent against a checkout while a Run is going.** A Run commits every change to a file git already tracks, however it got there ([ADR-0015](docs/adr/0015-a-run-commits-what-it-declared.md)) — so a second agent's half-finished edits are committed into the Run's branch and attributed to a Role. Files nothing in the Run claimed are listed in the pull request body ([ADR-0023](docs/adr/0023-a-commit-names-what-nothing-claimed.md)), which makes it visible at Sign-off but does not prevent it. Use a separate clone.
+
 ## Commands
 
 | Command | What it does |
@@ -313,10 +321,21 @@ code rather than the verdict about the old code.
 
 Read [`CONTEXT.md`](CONTEXT.md) before writing anything, and [`docs/adr/`](docs/adr/) for the decisions that constrain it.
 
-## Tests
+## Changing AgentForge
+
+Clone it and install that clone editable. Never patch the installed copy.
 
 ```console
+$ git clone https://github.com/yashmhatre/AgentForge.git
+$ cd AgentForge
 $ pip install -e ".[dev]"
+```
+
+Editing `site-packages/agentforge_framework/` appears to work and is the one change nothing will catch: the local install diverges from what ships, so the thing that works is not the thing anybody else gets, and the fix is lost the next time the package is upgraded. If a Run is failing badly enough that patching the install looks like the way forward, that is a bug worth filing — [#101](https://github.com/yashmhatre/AgentForge/issues/101) is what happened the last time somebody reached for it.
+
+## Tests
+
+```console
 $ pytest
 ```
 

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "agentforge-framework"
-version = "0.2.2"
+version = "0.2.3"
 description = "A modular framework for coordinating specialized software agents."
 readme = "README.md"
 requires-python = ">=3.11"

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/src/agentforge_framework/__init__.py

@@ -1,3 +1,3 @@
 """AgentForge — coordination of specialized software agents through reusable workflows."""
 
-__version__ = "0.2.2"
+__version__ = "0.2.3"

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/src/agentforge_framework/core/config.py

@@ -41,6 +41,13 @@ class Config:
     #: Command in the glossary's sense: nothing infers anything from it.
     test_suite: tuple[str, ...] = DEFAULT_TEST_SUITE
 
+    #: Whether the Context Pack comment publishes the symbols and import graph
+    #: it resolved, or only their counts. Off by default: the Issue already
+    #: carries the pack's file paths in the frozen Plan, and nothing else on it
+    #: carries private symbol names. A tracker whose audience matches the
+    #: code's turns this on. See ADR-0024.
+    publish_pack_inventory: bool = False
+
     def capability_for(self, provider: str) -> CapabilityTier:
         return self.provider_capabilities.get(provider, CapabilityTier.FRAGMENT)
 
@@ -55,7 +62,13 @@ def load_config(root: Path | str) -> Config:
     capabilities = dict(DEFAULT_CAPABILITIES)
     for name, provider in (data.get("providers") or {}).items():
         capabilities[str(name)] = CapabilityTier(provider["capability_tier"])
-    return Config(provider_capabilities=capabilities, test_suite=_test_suite(data))
+    return Config(
+        provider_capabilities=capabilities,
+        test_suite=_test_suite(data),
+        publish_pack_inventory=bool(
+            (data.get("context") or {}).get("publish_inventory", False)
+        ),
+    )
 
 
 def _test_suite(data: dict) -> tuple[str, ...]:

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/src/agentforge_framework/core/issues.py

@@ -381,6 +381,7 @@ def render_context_comment(
     context: ContextPack,
     plugins: Sequence[tuple[str, str]] = (),
     skipped: Sequence[str] = (),
+    publish_inventory: bool = False,
 ) -> str:
     """The pack this Run's Agents were handed, recorded before the first one ran.
 
@@ -390,6 +391,14 @@ def render_context_comment(
     invocation (ADR-0010), so this is a record of a Run rather than a contract
     the next one reads back.
 
+    `publish_inventory` decides whether the resolved symbols and import graph
+    are named or only counted. Off by default: the Issue already carries this
+    pack's file paths in the frozen Plan, so the file list discloses nothing
+    new, while private symbol names and the graph between modules appear
+    nowhere else on the tracker (ADR-0024). The counts stay either way, because
+    a pack that resolved more or less than a reader expected is most of what
+    this comment is read for.
+
     `plugins` and `skipped` are the Plugins that answered for this Run and the
     ones that raised while being asked. Both are named for the same reason the
     pack is: a prompt that grew, or one that did not grow when a reader expected
@@ -418,16 +427,29 @@ def render_context_comment(
     lines += [f"**Files ({len(context.files)}):**", ""]
     lines += [f"- `{path}`" for path in context.files]
 
-    for label, values in (("Symbols", context.symbols), ("Reaches for", context.references)):
-        if values:
-            lines += [
-                "",
-                f"<details><summary>{label} ({len(values)})</summary>",
-                "",
-                ", ".join(f"`{value}`" for value in values),
-                "",
-                "</details>",
-            ]
+    inventory = (("Symbols", context.symbols), ("Reaches for", context.references))
+    if publish_inventory:
+        for label, values in inventory:
+            if values:
+                lines += [
+                    "",
+                    f"<details><summary>{label} ({len(values)})</summary>",
+                    "",
+                    ", ".join(f"`{value}`" for value in values),
+                    "",
+                    "</details>",
+                ]
+    elif any(values for _, values in inventory):
+        lines += [
+            "",
+            (
+                "Symbol and reference counts are in the heading; the names are not "
+                "published. The Issue already carries this pack's file paths in the "
+                "frozen Plan, and a reader diagnosing a Run reads them against the "
+                "repository. Set `context.publish_inventory: true` where the tracker's "
+                "audience is the code's audience (ADR-0024)."
+            ),
+        ]
 
     if context.conventions:
         lines += ["", "**Conventions:**", ""]

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/src/agentforge_framework/core/project.py

@@ -142,6 +142,14 @@ gates:
     # The argument vector the `tests` Gate runs, in this repository.
     # {because}
     suite: [{suite}]
+
+context:
+  # Whether the Context Pack comment names the symbols and imports it resolved,
+  # or only counts them (ADR-0024). A Run posts that comment to the Issue, and
+  # a tracker can have a wider audience than the code — so the names are off
+  # unless this repository says otherwise. The file list is published either
+  # way: the frozen Plan on the Issue already carries it.
+  publish_inventory: false
 """
 
 

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/src/agentforge_framework/core/repo.py

@@ -145,6 +145,21 @@ class Repository:
         self._git("push", "--set-upstream", "origin", branch)
 
 
+def unclaimed(committed: Iterable[str], declared: Iterable[str]) -> tuple[str, ...]:
+    """Of the paths committed, the ones nothing in the Run said it would touch.
+
+    ADR-0015 commits every change to a tracked file however it arrived, and its
+    reasoning holds as long as the only writers are the Agents and the commands
+    they were allowed to run. A second agent editing the same checkout breaks
+    that — its half-finished work is committed into the Run's branch and
+    attributed to a Role, and nothing about the file on disk says otherwise
+    (#101). This does not change what is committed; it names what nothing
+    claimed, so the disclosure reaches the human at Sign-off.
+    """
+    named = {_normalize(path) for path in declared}
+    return tuple(path for path in committed if _normalize(path) not in named)
+
+
 def _normalize(path: str) -> str:
     r"""A declared path in the spelling `git status` uses.
 

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/src/agentforge_framework/core/runtime.py

@@ -24,7 +24,7 @@ from ..agents.decomposer import Approver, Decomposed, Decomposer, slice_task
 from ..agents.orchestrator import Exchange, Interviewer, Orchestrator, Planned
 from ..context.resolver import resolve_pack
 from ..providers import DEFAULT_PROVIDER, get_provider
-from .config import load_config
+from .config import Config, load_config
 from .contracts import (
     AgentResult,
     ContextPack,
@@ -64,7 +64,13 @@ from .registry import (
     fragments_for,
     gates_for,
 )
-from .repo import PreconditionFailed, Repository, branch_for_issue, open_repository
+from .repo import (
+    PreconditionFailed,
+    Repository,
+    branch_for_issue,
+    open_repository,
+    unclaimed,
+)
 from .workflow import Workflow, WorkflowError, load_workflow
 
 
@@ -144,7 +150,9 @@ class Forge:
 
     # --- preconditions -----------------------------------------------------
 
-    def _prepare(self, allow_commands: bool = False) -> tuple[Repository, GitHub, object]:
+    def _prepare(
+        self, allow_commands: bool = False
+    ) -> tuple[Repository, GitHub, object, Config]:
         """Every check that can fail for free, before anything is spent.
 
         Absent git, absent remote, absent `gh`, absent coding-agent CLI. A Run
@@ -157,11 +165,12 @@ class Forge:
             raise RunFailed(str(exc)) from exc
 
         github = GitHub(self.runner, repo.root)
+        config = load_config(repo.root)
         provider = get_provider(
             self.provider_name,
             self.runner,
             allow_commands=allow_commands,
-            config=load_config(repo.root),
+            config=config,
         )
         try:
             github.preflight()
@@ -169,7 +178,7 @@ class Forge:
         except (IssueError, RuntimeError) as exc:
             raise RunFailed(str(exc)) from exc
 
-        return repo, github, provider
+        return repo, github, provider, config
 
     # --- agentforge plan ---------------------------------------------------
 
@@ -208,7 +217,7 @@ class Forge:
         the caller supplies an approver that always says yes when the human
         asked for exactly that.
         """
-        repo, github, provider = self._prepare()
+        repo, github, provider, _config = self._prepare()
 
         # Only when interviewing: every stage is told to change nothing, and two
         # extra `git status` calls on an unattended pass buy nothing.
@@ -368,7 +377,7 @@ class Forge:
         off already suppresses them, and a Run with neither cannot say which of
         the two moved the total. See ADR-0016 for the three conditions.
         """
-        repo, github, provider = self._prepare(allow_commands=allow_commands)
+        repo, github, provider, config = self._prepare(allow_commands=allow_commands)
 
         if repo.is_dirty():
             raise RunFailed(
@@ -466,7 +475,10 @@ class Forge:
                     github.post_comment(
                         number,
                         render_context_comment(
-                            state.context, contributions(activation), activation.skipped
+                            state.context,
+                            contributions(activation),
+                            activation.skipped,
+                            publish_inventory=config.publish_pack_inventory,
                         ),
                     )
                 role = resolve_role(step.role)
@@ -535,14 +547,22 @@ class Forge:
             )
 
         changed = repo.changed_files()
+        declared = _declared_surface(state, results)
         committed = repo.commit_declared(
             f"{issue.title}\n\nImplements #{number} via AgentForge.",
-            _declared_surface(state, results),
+            declared,
         )
         # Left in the working tree on purpose (ADR-0015), and named rather
         # than dropped: the human at Sign-off is the only one who can say
         # whether an undeclared file was an Agent's work or its suite's.
         left = tuple(path for path in changed if path not in committed)
+        # The other half of the same disclosure. A tracked file is committed
+        # however it changed (ADR-0015), which is right when the only writers
+        # are the Agents and their commands, and is how a second agent sharing
+        # the checkout gets its work committed and attributed to a Role (#101).
+        # Naming these is the difference between a data-loss bug and a line at
+        # Sign-off.
+        unclaimed_paths = unclaimed(committed, declared)
         base = github.default_branch()
         # An empty working tree is only a failure when the branch has nothing on
         # it either. Plenty of Runs legitimately write nothing here: an audit
@@ -573,7 +593,7 @@ class Forge:
         repo.push(branch)
         url = github.open_draft_pr(
             title=issue.title,
-            body=_pr_body(number, state, results, committed, left),
+            body=_pr_body(number, state, results, committed, left, unclaimed_paths),
             head=branch,
             base=base,
         )
@@ -761,7 +781,7 @@ def _end(github: GitHub, issue: Issue, state: RunState) -> RunState:
     return state
 
 
-def _pr_body(number: int, state: RunState, results, committed, left=()) -> str:
+def _pr_body(number: int, state: RunState, results, committed, left=(), unclaimed=()) -> str:
     lines = [
         f"Closes #{number}.",
         "",
@@ -791,6 +811,21 @@ def _pr_body(number: int, state: RunState, results, committed, left=()) -> str:
             "",
         ]
         lines += [f"- `{path}`" for path in left]
+    if unclaimed:
+        lines += [
+            "",
+            "## Committed, but no Agent claimed them",
+            "",
+            (
+                "These are in the diff. Git already tracked them, so AgentForge committed "
+                "them however they changed (ADR-0015) — but neither the Plan nor any Agent "
+                "Result named them, so nothing in this Run says they are its work. Read "
+                "them before you sign off. Another agent or a person editing this checkout "
+                "while the Run was going is the reason worth ruling out."
+            ),
+            "",
+        ]
+        lines += [f"- `{path}`" for path in unclaimed]
     lines += [
         "",
         "---",

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/src/agentforge_framework.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentforge-framework
-Version: 0.2.2
+Version: 0.2.3
 Summary: A modular framework for coordinating specialized software agents.
 Author: Yash Mhatre
 License-Expression: Apache-2.0
@@ -145,7 +145,7 @@ without notice. See
 ```console
 $ pip install agentforge-framework
 $ agentforge --version
-agentforge 0.2.2
+agentforge 0.2.3
 ```
 
 That is the whole of it. The two routes below the naming note are for a machine
@@ -169,7 +169,7 @@ from the [latest release](https://github.com/yashmhatre/AgentForge/releases/late
 and install the file:
 
 ```console
-$ pip install agentforge_framework-0.2.2-py3-none-any.whl
+$ pip install agentforge_framework-0.2.3-py3-none-any.whl
 ```
 
 Publishing a release is a wizard rather than a checklist:
@@ -200,6 +200,14 @@ What each release contains is in [CHANGELOG.md](CHANGELOG.md).
 
 AgentForge never touches a model API and handles no credentials of its own. Whatever your coding-agent CLI is already authenticated with is what a Run costs.
 
+### Editors and IDEs
+
+AgentForge is a terminal tool. It runs fine from an IDE's terminal, but the IDE is not a Provider and its assistant is not one either.
+
+**Antigravity IDE cannot be a Provider** ([#101](https://github.com/yashmhatre/AgentForge/issues/101)). Checked by running it, so nobody has to derive it again: `antigravity-ide chat` accepts a prompt and reads stdin, which is the right shape for the argument vector — but it is a window launcher. Piping a prompt to it returns exit 0 immediately with `Reading from stdin via: …\code-stdin-XXXX` on stdout and nothing else, ever; the answer goes to a GUI session. A Provider adapter has to read the Agent's result off stdout, so there is nothing for `parse_output` to parse. The same is true of any editor CLI of this shape.
+
+**Do not run another agent against a checkout while a Run is going.** A Run commits every change to a file git already tracks, however it got there ([ADR-0015](docs/adr/0015-a-run-commits-what-it-declared.md)) — so a second agent's half-finished edits are committed into the Run's branch and attributed to a Role. Files nothing in the Run claimed are listed in the pull request body ([ADR-0023](docs/adr/0023-a-commit-names-what-nothing-claimed.md)), which makes it visible at Sign-off but does not prevent it. Use a separate clone.
+
 ## Commands
 
 | Command | What it does |
@@ -331,10 +339,21 @@ code rather than the verdict about the old code.
 
 Read [`CONTEXT.md`](CONTEXT.md) before writing anything, and [`docs/adr/`](docs/adr/) for the decisions that constrain it.
 
-## Tests
+## Changing AgentForge
+
+Clone it and install that clone editable. Never patch the installed copy.
 
 ```console
+$ git clone https://github.com/yashmhatre/AgentForge.git
+$ cd AgentForge
 $ pip install -e ".[dev]"
+```
+
+Editing `site-packages/agentforge_framework/` appears to work and is the one change nothing will catch: the local install diverges from what ships, so the thing that works is not the thing anybody else gets, and the fix is lost the next time the package is upgraded. If a Run is failing badly enough that patching the install looks like the way forward, that is a bug worth filing — [#101](https://github.com/yashmhatre/AgentForge/issues/101) is what happened the last time somebody reached for it.
+
+## Tests
+
+```console
 $ pytest
 ```
 

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/tests/test_config.py

@@ -17,6 +17,31 @@ def test_missing_config_uses_the_documented_provider_capability_defaults(tmp_pat
     assert not (tmp_path / ".agentforge").exists(), "the loader is read-only"
 
 
+def _config_file(tmp_path, text: str):
+    config_dir = tmp_path / ".agentforge"
+    config_dir.mkdir(exist_ok=True)
+    (config_dir / "config.yaml").write_text(text, encoding="utf-8")
+    return load_config(tmp_path)
+
+
+def test_the_pack_inventory_is_not_published_unless_the_project_says_so():
+    """ADR-0024. The safe direction is the default because the disclosure is
+    the unrecoverable half: a comment on a public tracker is published."""
+    assert load_config("/nowhere").publish_pack_inventory is False
+
+
+def test_a_project_whose_tracker_matches_its_code_publishes_the_inventory(tmp_path):
+    config = _config_file(tmp_path, "context:\n  publish_inventory: true\n")
+
+    assert config.publish_pack_inventory is True
+
+
+def test_a_project_can_say_no_as_explicitly_as_it_can_say_yes(tmp_path):
+    config = _config_file(tmp_path, "context:\n  publish_inventory: false\n")
+
+    assert config.publish_pack_inventory is False
+
+
 def test_capability_tiers_are_read_from_the_shared_config_file(tmp_path):
     config_dir = tmp_path / ".agentforge"
     config_dir.mkdir()

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/tests/test_issues.py

@@ -721,23 +721,52 @@ def test_a_run_where_nobody_reported_anything_says_nobody_reported_anything():
 # --- the pack, recorded where a Run is diagnosed ---------------------------
 
 
+A_PACK = ContextPack(
+    files=("src/loader.py",),
+    symbols=("src/loader.py::fetch",),
+    references=("requests",),
+    conventions=("no new dependencies",),
+)
+
+
 def test_the_run_log_records_the_pack_the_agents_were_shown():
     """A Run that went wrong is diagnosed against what its Agents could see."""
-    comment = render_context_comment(
-        ContextPack(
-            files=("src/loader.py",),
-            symbols=("src/loader.py::fetch",),
-            references=("requests",),
-            conventions=("no new dependencies",),
-        )
-    )
+    comment = render_context_comment(A_PACK)
 
     assert "### Context Pack" in comment
     assert "`src/loader.py`" in comment
-    assert "`src/loader.py::fetch`" in comment
     assert "no new dependencies" in comment
 
 
+def test_the_counts_survive_the_names_not_being_published():
+    """What the comment is read for. A pack that resolved more or less than the
+    reader expected is visible without naming anything (ADR-0024)."""
+    comment = render_context_comment(A_PACK)
+
+    assert "1 file, 1 symbol, 1 reference" in comment
+    assert "src/loader.py::fetch" not in comment
+    assert "requests" not in comment
+    assert "publish_inventory" in comment, "a reader who wants the names is told how"
+
+
+def test_the_inventory_is_published_when_the_repository_asks_for_it():
+    """A tracker whose audience is the code's audience loses nothing by it."""
+    comment = render_context_comment(A_PACK, publish_inventory=True)
+
+    assert "`src/loader.py::fetch`" in comment
+    assert "`requests`" in comment
+    assert "<details><summary>Symbols (1)</summary>" in comment
+
+
+def test_a_pack_with_no_symbols_explains_nothing_it_withheld():
+    """The note is a disclosure about withheld names. A pack that resolved none
+    has nothing to withhold, and saying so would be noise."""
+    comment = render_context_comment(ContextPack(files=("src/loader.py",)))
+
+    assert "publish_inventory" not in comment
+    assert "`src/loader.py`" in comment
+
+
 def test_a_run_with_no_pack_says_that_it_is_the_control():
     """The measurement in story twenty needs two Runs and a way to tell which
     of them was which."""

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/tests/test_project.py

@@ -117,6 +117,7 @@ def test_the_written_file_round_trips_through_load_config(tmp_path):
     config = load_config(tmp_path)
     assert config.test_suite == context.test_suite
     assert config.capability_for("codex") is context.capability_tier
+    assert config.publish_pack_inventory is False
 
 
 def test_an_argument_with_a_dash_in_it_survives_the_round_trip(tmp_path):
@@ -138,12 +139,13 @@ def test_the_file_says_which_values_were_detected_and_which_were_defaulted():
 
 
 def test_the_file_carries_no_key_nothing_reads():
-    """`docs/PLAN.md` promised a config owning plugin activation; `load_config`
-    reads two keys. A key that has no effect is a lie told to whoever edits it,
-    so activation is printed and the file says why (ADR-0020)."""
+    """`docs/PLAN.md` promised a config owning plugin activation, and the file
+    holds only what `load_config` reads. A key that has no effect is a lie told
+    to whoever edits it, so activation is printed and the file says why
+    (ADR-0020). Every key here arrived with its reader."""
     written = render_config(a_context(plugins=("sql", "databricks")))
 
-    assert set(yaml.safe_load(written)) == {"providers", "gates"}
+    assert set(yaml.safe_load(written)) == {"providers", "gates", "context"}
     assert "databricks" not in written
     # The absence is explained where somebody looking for the key will look.
     assert "no `plugins:` key here to edit" in written

{agentforge_framework-0.2.2 → agentforge_framework-0.2.3}/tests/test_runtime.py

@@ -1903,6 +1903,62 @@ def test_the_pull_request_lists_only_what_was_committed():
     assert "loader.cpython-311.pyc" not in body.split("## Left uncommitted")[0]
 
 
+#: A second agent editing the same checkout while the Run is going. The Run's
+#: own file is modified as expected; `src/telemetry.py` is somebody else's
+#: half-finished work, and git tracks it, so ADR-0015 commits it either way.
+CONCURRENT_EDIT = " M src/loader.py\n M src/telemetry.py\n"
+
+
+def test_a_committed_file_no_agent_claimed_is_named_in_the_pull_request():
+    """The concurrency hazard in #101. Antigravity's agent and a Run share one
+    checkout; ADR-0015 commits every change to a tracked file however it
+    arrived, so the other agent's work lands in the branch attributed to a Role.
+    Nothing about the file on disk says otherwise, so the Run says it instead."""
+    runner = a_runner()
+    runner.script("git", "status", "--porcelain", stdout=["", CONCURRENT_EDIT])
+    runner.script("claude", stdout=agent_says("completed", "retry added"))
+
+    forge(runner).implement(12, allow_commands=True)
+
+    assert "src/telemetry.py" in staged(runner), "ADR-0015 still commits it"
+    body = runner.argument_after("--body", "gh", "pr", "create")
+    unclaimed_section = body.split("## Committed, but no Agent claimed them")[1]
+    assert "- `src/telemetry.py`" in unclaimed_section
+    assert "- `src/loader.py`" not in unclaimed_section, (
+        "the Role declared this one; naming it would bury the one that matters"
+    )
+
+
+def test_a_run_whose_every_file_was_declared_says_nothing_about_unclaimed_ones():
+    """The section is a disclosure, not a fixture of the body. An ordinary Run
+    that names what it changed reads exactly as it did before."""
+    runner = a_runner()
+    runner.script("git", "status", "--porcelain", stdout=["", " M src/loader.py\n"])
+    runner.script("claude", stdout=agent_says("completed", "retry added"))
+
+    forge(runner).implement(12, allow_commands=True)
+
+    body = runner.argument_after("--body", "gh", "pr", "create")
+    assert "no Agent claimed" not in body
+
+
+def test_a_role_that_spelled_its_path_the_windows_way_still_claimed_the_file():
+    """A Role reports `src\\telemetry.py` and git answers `src/telemetry.py`.
+    Comparing those literally would accuse an Agent of somebody else's edit on
+    every Windows Run, which is the platform this hazard was found on."""
+    runner = a_runner()
+    runner.script("git", "status", "--porcelain", stdout=["", CONCURRENT_EDIT])
+    runner.script(
+        "claude",
+        stdout=agent_says("completed", "retry added", files=("src\\telemetry.py",)),
+    )
+
+    forge(runner).implement(12, allow_commands=True)
+
+    body = runner.argument_after("--body", "gh", "pr", "create")
+    assert "no Agent claimed" not in body
+
+
 def test_what_was_left_behind_is_named_rather_than_dropped():
     """A build artifact is the usual reason and an Agent writing outside its
     Step is the one worth reading, and only a human can tell them apart."""