agentwire-dev 1.45.0__tar.gz → 1.46.0__tar.gz

{agentwire_dev-1.45.0 → agentwire_dev-1.46.0}/.github/PULL_REQUEST_TEMPLATE.md

@@ -9,8 +9,8 @@ Before submitting, please make sure:
 4. For bug fixes: include a test that would have caught the bug
 5. For new features: include tests and update docs if needed
 
-By submitting this PR, you agree to the Contributor License Agreement:
-https://github.com/dotdevdotdev/agentwire-dev/blob/main/CLA.md
+By submitting this PR, you certify the Developer Certificate of Origin
+(https://developercertificate.org/) — sign off your commits with `git commit -s`.
 -->
 
 ## Summary

agentwire_dev-1.46.0/.github/workflows/pytest.yml

@@ -0,0 +1,62 @@
+# Pytest CI gate (#323).
+#
+# 1,191+ test functions exist in the repo; before this workflow none ran in CI,
+# so `main` could (and did, #249) go red unnoticed. This runs the suite on every
+# PR and every push to main and is the whole win: a trustworthy green/red signal.
+#
+# Hermetic by design — the runner has no live tmux session or portal, so tests
+# that spawn a real tmux binary (the WS-connect and speak-fanout PTY paths) are
+# marked `requires_tmux` and deselected here. They still run locally where tmux
+# is on PATH. Per the council guardrail we do NOT chase coverage % or block PRs
+# on flaky/tmux-dependent tests.
+#
+# Coverage is measured and surfaced (term-missing in the log + a table in the
+# run's job summary + an uploaded coverage.xml artifact) but is REPORT-ONLY:
+# there is deliberately no --cov-fail-under, so a low percentage never reds the
+# build. The point is visibility — letting the maintainer spot untested
+# new/changed handlers (#487) — not a threshold gate.
+name: pytest
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  pytest:
+    name: pytest (hermetic)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+
+      - name: Sync dependencies
+        run: uv sync --extra dev
+
+      - name: Run test suite (tmux-dependent tests deselected) + coverage
+        run: >
+          uv run --no-sync pytest -q -m "not requires_tmux"
+          --cov=agentwire --cov-report=term-missing --cov-report=xml
+
+      - name: Publish coverage summary (report-only)
+        if: always()
+        run: |
+          {
+            echo '## Coverage (report-only — no threshold gate)'
+            echo ''
+            echo '```'
+            uv run --no-sync coverage report 2>/dev/null || echo 'no coverage data'
+            echo '```'
+          } >> "$GITHUB_STEP_SUMMARY"
+
+      - name: Upload coverage.xml artifact
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: coverage-xml
+          path: coverage.xml
+          if-no-files-found: ignore

agentwire_dev-1.46.0/.github/workflows/ruff.yml

@@ -0,0 +1,33 @@
+# Ruff lint gate (#485).
+#
+# `ruff` was a declared dev dep with full config ([tool.ruff.lint]
+# select = E,F,I,N,W in pyproject.toml) but no workflow ever invoked it, so
+# lint regressions landed on main unnoticed — including a guaranteed
+# NameError crash in `agentwire hooks status` that sat for ~5 months because
+# only a pyflakes-class gate catches an undefined name in a code path with no
+# test coverage. This runs ruff on every PR and every push to main and fails
+# the build on any lint error in the configured set.
+name: ruff
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  ruff:
+    name: ruff (lint)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+
+      - name: Sync dependencies
+        run: uv sync --extra dev
+
+      - name: Run ruff (configured set in pyproject.toml)
+        run: uv run --no-sync ruff check agentwire/ tests/

agentwire_dev-1.46.0/.github/workflows/security.yml

@@ -0,0 +1,104 @@
+# Security CI for the damage-control matcher.
+#
+# Three independent signals:
+#   1. bypass-corpus  — the load-bearing gate. Asserts the known evasion vectors
+#                       (quoting/escaping, $VAR, substitution, tilde/$HOME secret
+#                       reads, non-rm deletion) stay BLOCK/ASK and a corpus of
+#                       safe everyday commands keeps PASSing. Merges gate on this.
+#   2. bandit         — static scan tuned to a meaningful green gate. Intentional
+#                       `shell=True` / localhost `verify=False` sites are skipped in
+#                       pyproject [tool.bandit]; the step fails only on NEW
+#                       high-severity high-confidence findings.
+#   3. pip-audit      — known-vuln scan over the resolved dependency set, on PRs
+#                       and a weekly cron.
+name: security
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  schedule:
+    - cron: "0 7 * * 1"  # Mondays 07:00 UTC
+
+jobs:
+  bypass-corpus:
+    name: damage-control bypass corpus (merge gate)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      - name: Sync dependencies
+        run: uv sync --extra dev
+      - name: Hooks are in sync with _core.py
+        run: uv run --no-sync python scripts/regen_damage_control_hooks.py --check
+      - name: Run bypass + sync + control-plane corpus
+        run: >
+          uv run --no-sync pytest -q
+          tests/unit/test_damage_control_bypass.py
+          tests/unit/test_damage_control_sync.py
+          tests/unit/test_control_plane_protection.py
+
+  bandit:
+    name: bandit
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      # Meaningful green gate: tuned config (pyproject [tool.bandit]) skips the
+      # intentional-by-design test-IDs (subprocess/shell, localhost verify=False,
+      # asserts), and we fail only on high-severity high-confidence findings.
+      # Green on the clean tree today; red only on NEW genuinely-dangerous code.
+      - name: Run bandit
+        run: uvx bandit -c pyproject.toml -r agentwire --severity-level high --confidence-level high
+
+  pip-audit:
+    name: pip-audit (advisory)
+    runs-on: ubuntu-latest
+    # Advisory, not a merge gate: hard-blocking every PR on transitive CVEs is
+    # noise. Keep it running on PRs + the weekly cron for visibility; the
+    # damage-control bypass corpus is the hard merge gate. Direct portal-facing
+    # deps are bumped explicitly in pyproject; transitive fixes land via lock
+    # bumps. See docs/wiki/security/pip-audit.md for the residual-CVE rationale.
+    continue-on-error: true
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      # PR/push audit is scoped to RUNTIME deps only (--no-dev, no optional
+      # extras) so the signal tracks what the default install actually ships.
+      # The heavy torch/onnxruntime+gradio chain lives behind the tts/stt
+      # extras and is covered by the full audit on the weekly cron below.
+      - name: Export runtime (default) dependencies
+        run: uv export --no-emit-project --no-dev --format requirements-txt -o requirements.txt
+      # Residual starlette CVEs are un-bumpable: starlette is transitive via mcp
+      # and the fixes require starlette >=1.0, but the tts extra (gradio ->
+      # chatterbox-tts) caps starlette <1.0 in the universal resolution. agentwire
+      # speaks MCP over stdio and serves the portal with aiohttp, so starlette's
+      # HTTP request-handling CVEs are not on a reachable path. Documented +
+      # ignored here so the advisory signal stays meaningful; revisit when mcp /
+      # chatterbox-tts relax the ceiling. See docs/wiki/security/pip-audit.md.
+      - name: Audit runtime dependencies
+        run: >
+          uvx pip-audit -r requirements.txt
+          --ignore-vuln PYSEC-2026-161
+          --ignore-vuln CVE-2026-48818
+          --ignore-vuln CVE-2026-48817
+          --ignore-vuln CVE-2026-54283
+          --ignore-vuln CVE-2026-54282
+      # Full audit including optional extras (tts/stt: torch, onnxruntime,
+      # gradio, ...). Weekly only and never ignore-filtered — surfaces the full
+      # backlog for review without blocking or spamming every PR.
+      - name: Export all dependencies (incl. optional extras)
+        if: github.event_name == 'schedule'
+        run: uv export --no-emit-project --all-extras --format requirements-txt -o requirements-all.txt
+      - name: Full audit (weekly cron, optional extras)
+        if: github.event_name == 'schedule'
+        run: uvx pip-audit -r requirements-all.txt

{agentwire_dev-1.45.0 → agentwire_dev-1.46.0}/.github/workflows/tts-smoke.yml

@@ -12,13 +12,19 @@ on:
     branches: [main]
     paths:
       - "pyproject.toml"
+      - "uv.lock"
       - "agentwire/tts/**"
       - ".github/workflows/tts-smoke.yml"
   pull_request:
     paths:
       - "pyproject.toml"
+      - "uv.lock"
       - "agentwire/tts/**"
       - ".github/workflows/tts-smoke.yml"
+  # Transitive wheel/onnxruntime changes can break Intel-mac resolution without
+  # touching any path above; a weekly cron catches that proactively (#487).
+  schedule:
+    - cron: "0 7 * * 2"  # Tuesdays 07:00 UTC
 
 jobs:
   torchless-import:

{agentwire_dev-1.45.0 → agentwire_dev-1.46.0}/CONTRIBUTING.md

@@ -2,9 +2,13 @@
 
 Thank you for your interest in contributing to AgentWire!
 
-## Contributor License Agreement
+## Developer Certificate of Origin
 
-By submitting a pull request, you agree to the terms of our [Contributor License Agreement](CLA.md). This allows us to maintain our dual-licensing model (AGPL v3 + commercial) while accepting community contributions.
+AgentWire is licensed under the [Apache License 2.0](LICENSE), and we use the [Developer Certificate of Origin](https://developercertificate.org/) (DCO) instead of a CLA — there is nothing to sign. You simply add a `Signed-off-by` line to each commit, certifying you wrote the patch (or otherwise have the right to submit it under Apache-2.0):
+
+    Signed-off-by: Jane Developer <jane@example.com>
+
+Add it automatically with `git commit -s` (use your real name and an email that matches your commit author). That's the whole process.
 
 ## Development Setup
 

agentwire_dev-1.46.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 dotdev
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.