arbiter-suite 0.9.0.dev1__tar.gz → 0.9.2.dev1__tar.gz

arbiter_suite-0.9.2.dev1/PKG-INFO

@@ -0,0 +1,29 @@
+Metadata-Version: 2.4
+Name: arbiter-suite
+Version: 0.9.2.dev1
+Summary: Policy-controlled access to configured services for agents
+Author-email: Omry Yadan <omry@yadan.net>
+Maintainer-email: Omry Yadan <omry@yadan.net>
+License: MIT
+Project-URL: Homepage, https://github.com/omry/arbiter
+Project-URL: Repository, https://github.com/omry/arbiter
+Keywords: agent,policy,mcp,access-control,smtp,imap,security
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Communications :: Email
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: <3.15,>=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: arbiter-server==0.9.2.dev1
+Requires-Dist: arbiter-client==0.9.2.dev1
+Requires-Dist: arbiter-smtp==0.9.2.dev1
+Requires-Dist: arbiter-imap==0.9.2.dev1
+
+Arbiter suite meta package.

arbiter_suite-0.9.2.dev1/arbiter_suite.egg-info/PKG-INFO

@@ -0,0 +1,29 @@
+Metadata-Version: 2.4
+Name: arbiter-suite
+Version: 0.9.2.dev1
+Summary: Policy-controlled access to configured services for agents
+Author-email: Omry Yadan <omry@yadan.net>
+Maintainer-email: Omry Yadan <omry@yadan.net>
+License: MIT
+Project-URL: Homepage, https://github.com/omry/arbiter
+Project-URL: Repository, https://github.com/omry/arbiter
+Keywords: agent,policy,mcp,access-control,smtp,imap,security
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Communications :: Email
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: <3.15,>=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: arbiter-server==0.9.2.dev1
+Requires-Dist: arbiter-client==0.9.2.dev1
+Requires-Dist: arbiter-smtp==0.9.2.dev1
+Requires-Dist: arbiter-imap==0.9.2.dev1
+
+Arbiter suite meta package.

{arbiter_suite-0.9.0.dev1 → arbiter_suite-0.9.2.dev1}/arbiter_suite.egg-info/SOURCES.txt

@@ -1,5 +1,3 @@
-LICENSE
-README.md
 pyproject.toml
 arbiter_suite.egg-info/PKG-INFO
 arbiter_suite.egg-info/SOURCES.txt

arbiter_suite-0.9.2.dev1/arbiter_suite.egg-info/requires.txt

@@ -0,0 +1,4 @@
+arbiter-server==0.9.2.dev1
+arbiter-client==0.9.2.dev1
+arbiter-smtp==0.9.2.dev1
+arbiter-imap==0.9.2.dev1

{arbiter_suite-0.9.0.dev1 → arbiter_suite-0.9.2.dev1}/pyproject.toml

@@ -4,9 +4,9 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "arbiter-suite"
-version = "0.9.0.dev1"
+version = "0.9.2.dev1"
 description = "Policy-controlled access to configured services for agents"
-readme = "README.md"
+readme = { text = "Arbiter suite meta package.", content-type = "text/markdown" }
 requires-python = ">=3.10,<3.15"
 license = { text = "MIT" }
 authors = [
@@ -30,21 +30,10 @@ classifiers = [
   "Topic :: Software Development :: Libraries :: Python Modules",
 ]
 dependencies = [
-  "arbiter-core==0.9.0.dev1",
-  "arbiter-smtp==0.9.0.dev1",
-  "arbiter-imap==0.9.0.dev1",
-]
-
-[project.optional-dependencies]
-dev = [
-  "nox[pbs]>=2024.10,<2026.0",
-  "aiosmtpd>=1.4.6,<2.0",
-  "black>=25.0,<26.0",
-  "mypy>=1.11,<2.0",
-  "pytest>=7.4,<9.0",
-  "tomli>=2.0,<3.0",
-  "towncrier>=24.8,<25.0",
-  "trustme>=1.2,<2.0",
+  "arbiter-server==0.9.2.dev1",
+  "arbiter-client==0.9.2.dev1",
+  "arbiter-smtp==0.9.2.dev1",
+  "arbiter-imap==0.9.2.dev1",
 ]
 
 [project.urls]
@@ -54,22 +43,8 @@ Repository = "https://github.com/omry/arbiter"
 [tool.setuptools]
 py-modules = []
 
-[tool.pytest.ini_options]
-addopts = "--import-mode=importlib"
-testpaths = ["core/tests", "smtp/tests", "imap/tests"]
-pythonpath = ["core/src", "smtp/src", "imap/src"]
-
-[tool.mypy]
-python_version = "3.10"
-strict = true
-warn_unreachable = true
-mypy_path = "core/src:smtp/src:imap/src"
-
-[tool.black]
-target-version = ["py310"]
-
 [tool.towncrier]
 name = "Arbiter"
 filename = "NEWS.md"
-directory = "newsfragments"
+directory = "news"
 issue_format = "#{issue}"

arbiter_suite-0.9.0.dev1/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 Omry Yadan
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

arbiter_suite-0.9.0.dev1/PKG-INFO

@@ -1,214 +0,0 @@
-Metadata-Version: 2.4
-Name: arbiter-suite
-Version: 0.9.0.dev1
-Summary: Policy-controlled access to configured services for agents
-Author-email: Omry Yadan <omry@yadan.net>
-Maintainer-email: Omry Yadan <omry@yadan.net>
-License: MIT
-Project-URL: Homepage, https://github.com/omry/arbiter
-Project-URL: Repository, https://github.com/omry/arbiter
-Keywords: agent,policy,mcp,access-control,smtp,imap,security
-Classifier: Development Status :: 3 - Alpha
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Programming Language :: Python :: 3.14
-Classifier: Topic :: Communications :: Email
-Classifier: Topic :: Software Development :: Libraries :: Python Modules
-Requires-Python: <3.15,>=3.10
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: arbiter-core==0.9.0.dev1
-Requires-Dist: arbiter-smtp==0.9.0.dev1
-Requires-Dist: arbiter-imap==0.9.0.dev1
-Provides-Extra: dev
-Requires-Dist: nox[pbs]<2026.0,>=2024.10; extra == "dev"
-Requires-Dist: aiosmtpd<2.0,>=1.4.6; extra == "dev"
-Requires-Dist: black<26.0,>=25.0; extra == "dev"
-Requires-Dist: mypy<2.0,>=1.11; extra == "dev"
-Requires-Dist: pytest<9.0,>=7.4; extra == "dev"
-Requires-Dist: tomli<3.0,>=2.0; extra == "dev"
-Requires-Dist: towncrier<25.0,>=24.8; extra == "dev"
-Requires-Dist: trustme<2.0,>=1.2; extra == "dev"
-Dynamic: license-file
-
-# Arbiter
-
-Arbiter is a capability firewall between AI agents and services. Today it exposes policy-controlled access through MCP and a client CLI; additional interfaces may be added later. The current service surface covers sending mail over SMTP and reading IMAP folders through explicit account policies.
-
-## Project Status
-
-Current implementation status:
-
-- MCP server over stdio, SSE, or streamable HTTP via FastMCP
-- capability discovery with SMTP and IMAP account and operation metadata
-- SMTP submission with configured sender identity, TLS/auth settings, text/HTML bodies, and Bcc kept out of message headers
-- IMAP list/get/search/move/mark-read/delete tools scoped to configured accounts and folders
-- `arbiter.account.<service>` and reusable `arbiter.policy.<service>` objects
-  for per-service account policy
-- `arbiter` client CLI and `arbiter-server` server/operator CLI
-- Docker deployment files for a standard SMTP gateway and a hardened read-only IMAP variant
-
-Known open gaps:
-
-- durable audit storage is parked for post-v1, while startup/runtime logging is
-  the v1 observability focus
-- normalized error-code responses are still a design contract, while the
-  implementation currently surfaces Python/MCP errors
-- the agent-facing skill integration path is intentionally not implemented in
-  this repository yet
-
-## Development
-
-Create and use the repo-local virtualenv with:
-
-- `python3 -m venv .venv`
-- `.venv/bin/python -m pip install --upgrade pip`
-- `.venv/bin/python -m pip install -e ".[dev]" -e core -e smtp -e imap`
-
-Run the test suite from the repo root with:
-
-- `.venv/bin/python -m nox -s tests`
-- `.venv/bin/python -m nox -s lint`
-
-The `lint` session runs both `black --check` and the Arbiter `mypy` passes.
-
-For focused local runs without `nox`, use the same environment directly, for example:
-
-- `.venv/bin/python -m pytest core/tests/unit/test_config.py`
-- `.venv/bin/python -m pytest core/tests/unit/test_app.py`
-
-The Docusaurus website lives in [website/](website/):
-
-- `cd website && npm install`
-- `cd website && npm run start`
-- `cd website && npm run build`
-
-The design is documented in the `docs/` structure used by the MCP server template:
-
-- [docs/overview.md](docs/overview.md)
-- [docs/architecture.md](docs/architecture.md)
-- [docs/BACKLOG.md](docs/BACKLOG.md)
-- [docs/config.md](docs/config.md)
-- [docs/config_bootstrap.md](docs/config_bootstrap.md)
-- [docs/policies.md](docs/policies.md)
-- [docs/errors.md](docs/errors.md)
-- [docs/todo.md](docs/todo.md)
-- [docs/testing_backlog.md](docs/testing_backlog.md)
-- [docs/tools/account_summaries.md](docs/tools/account_summaries.md)
-- [docs/tools/smtp_send_email.md](docs/tools/smtp_send_email.md)
-- [docs/tools/imap.md](docs/tools/imap.md)
-
-## Local Streamable HTTP Run
-
-For local Codex or VS Code integration, run Arbiter as a streamable HTTP MCP
-server and point the client at:
-
-```text
-http://127.0.0.1:8025/mcp
-```
-
-Arbiter does not ship a runnable service config. Bootstrap a Hydra
-config, edit it, then run the server. The default config directory is
-`~/.arbiter`; pass `--config-dir <dir>` before a subcommand to use a different
-location. `config.local/` is ignored scratchspace for repository-local
-development.
-Plugin-owned object templates are created by the plugin command surface:
-
-```bash
-arbiter-server bootstrap arbiter
-arbiter-server bootstrap plugin smtp account primary
-```
-
-`${oc.env:...}` reads the process environment that your shell, supervisor,
-container runtime, or secret manager provides. For local runs, the root config
-can name one optional dotenv-style file to load before composition.
-
-See [docs/config_bootstrap.md](docs/config_bootstrap.md) for the generated file
-layout and composition flow.
-
-For local development, a shell-owned env file can be useful:
-
-```bash
-# ~/.arbiter/local.env
-SMTP_PRIMARY_ACCOUNT_USERNAME=agent@example.com
-SMTP_PRIMARY_ACCOUNT_PASSWORD=change-me
-ARBITER_IMAP_USERNAME=agent@example.com
-ARBITER_IMAP_PASSWORD=change-me
-```
-
-Point the root config at the env file:
-
-```yaml
-arbiter:
-  env_file: local.env
-```
-
-Existing process environment variables take precedence over values from the env
-file. Relative paths are resolved from the config directory.
-
-Build or refresh that file from the active config:
-
-```bash
-arbiter-server env bootstrap
-arbiter-server env check
-```
-
-`env bootstrap` keeps existing assignments, adds missing config references, and
-groups entries under sorted `# arbiter-*` blocks plus `# miscellaneous`.
-If `arbiter.env_file` is not set yet, it adds `arbiter.env_file: .env` to the
-root config first.
-
-Then run from this directory:
-
-```bash
-arbiter-server config check
-arbiter-server serve
-```
-
-`config check` and `serve` require at least one configured service account.
-
-Use `arbiter-server plugins list` to inspect installed service plugins before
-validating a config. Once the server is running, use the client CLI against the
-MCP endpoint:
-
-```bash
-arbiter mcp tools arbiter.mcp_url=http://127.0.0.1:8025/mcp
-arbiter cap arbiter.mcp_url=http://127.0.0.1:8025/mcp
-arbiter accounts list arbiter.mcp_url=http://127.0.0.1:8025/mcp
-```
-
-The client can also read the endpoint from a small config file:
-`~/.arbiter/arbiter-client.yaml`.
-
-```yaml
-arbiter:
-  mcp_url: http://127.0.0.1:8025/mcp
-```
-
-Override config values with Hydra-style `key=value` arguments after the
-command, or bootstrap the client config:
-
-```bash
-arbiter bootstrap client arbiter.mcp_url=http://127.0.0.1:8025/mcp
-```
-
-IMAP operations use folder-scoped UIDs returned by `imap:list_messages` and
-`imap:search_messages`; pass those ids back to `imap:get_message`,
-`imap:move_message`, `imap:mark_message_read`, or `imap:delete_message` with
-the same account and folder.
-
-## Read-Only Real Inbox Docker Run
-
-For a hardened Docker setup that reads a single real IMAP folder with Docker
-secrets and no SMTP access, see:
-
-- [deploy/readonly-imap/README.md](deploy/readonly-imap/README.md)
-
-## License
-
-Arbiter is distributed under the MIT License. See [LICENSE](LICENSE).

arbiter_suite-0.9.0.dev1/README.md

@@ -1,176 +0,0 @@
-# Arbiter
-
-Arbiter is a capability firewall between AI agents and services. Today it exposes policy-controlled access through MCP and a client CLI; additional interfaces may be added later. The current service surface covers sending mail over SMTP and reading IMAP folders through explicit account policies.
-
-## Project Status
-
-Current implementation status:
-
-- MCP server over stdio, SSE, or streamable HTTP via FastMCP
-- capability discovery with SMTP and IMAP account and operation metadata
-- SMTP submission with configured sender identity, TLS/auth settings, text/HTML bodies, and Bcc kept out of message headers
-- IMAP list/get/search/move/mark-read/delete tools scoped to configured accounts and folders
-- `arbiter.account.<service>` and reusable `arbiter.policy.<service>` objects
-  for per-service account policy
-- `arbiter` client CLI and `arbiter-server` server/operator CLI
-- Docker deployment files for a standard SMTP gateway and a hardened read-only IMAP variant
-
-Known open gaps:
-
-- durable audit storage is parked for post-v1, while startup/runtime logging is
-  the v1 observability focus
-- normalized error-code responses are still a design contract, while the
-  implementation currently surfaces Python/MCP errors
-- the agent-facing skill integration path is intentionally not implemented in
-  this repository yet
-
-## Development
-
-Create and use the repo-local virtualenv with:
-
-- `python3 -m venv .venv`
-- `.venv/bin/python -m pip install --upgrade pip`
-- `.venv/bin/python -m pip install -e ".[dev]" -e core -e smtp -e imap`
-
-Run the test suite from the repo root with:
-
-- `.venv/bin/python -m nox -s tests`
-- `.venv/bin/python -m nox -s lint`
-
-The `lint` session runs both `black --check` and the Arbiter `mypy` passes.
-
-For focused local runs without `nox`, use the same environment directly, for example:
-
-- `.venv/bin/python -m pytest core/tests/unit/test_config.py`
-- `.venv/bin/python -m pytest core/tests/unit/test_app.py`
-
-The Docusaurus website lives in [website/](website/):
-
-- `cd website && npm install`
-- `cd website && npm run start`
-- `cd website && npm run build`
-
-The design is documented in the `docs/` structure used by the MCP server template:
-
-- [docs/overview.md](docs/overview.md)
-- [docs/architecture.md](docs/architecture.md)
-- [docs/BACKLOG.md](docs/BACKLOG.md)
-- [docs/config.md](docs/config.md)
-- [docs/config_bootstrap.md](docs/config_bootstrap.md)
-- [docs/policies.md](docs/policies.md)
-- [docs/errors.md](docs/errors.md)
-- [docs/todo.md](docs/todo.md)
-- [docs/testing_backlog.md](docs/testing_backlog.md)
-- [docs/tools/account_summaries.md](docs/tools/account_summaries.md)
-- [docs/tools/smtp_send_email.md](docs/tools/smtp_send_email.md)
-- [docs/tools/imap.md](docs/tools/imap.md)
-
-## Local Streamable HTTP Run
-
-For local Codex or VS Code integration, run Arbiter as a streamable HTTP MCP
-server and point the client at:
-
-```text
-http://127.0.0.1:8025/mcp
-```
-
-Arbiter does not ship a runnable service config. Bootstrap a Hydra
-config, edit it, then run the server. The default config directory is
-`~/.arbiter`; pass `--config-dir <dir>` before a subcommand to use a different
-location. `config.local/` is ignored scratchspace for repository-local
-development.
-Plugin-owned object templates are created by the plugin command surface:
-
-```bash
-arbiter-server bootstrap arbiter
-arbiter-server bootstrap plugin smtp account primary
-```
-
-`${oc.env:...}` reads the process environment that your shell, supervisor,
-container runtime, or secret manager provides. For local runs, the root config
-can name one optional dotenv-style file to load before composition.
-
-See [docs/config_bootstrap.md](docs/config_bootstrap.md) for the generated file
-layout and composition flow.
-
-For local development, a shell-owned env file can be useful:
-
-```bash
-# ~/.arbiter/local.env
-SMTP_PRIMARY_ACCOUNT_USERNAME=agent@example.com
-SMTP_PRIMARY_ACCOUNT_PASSWORD=change-me
-ARBITER_IMAP_USERNAME=agent@example.com
-ARBITER_IMAP_PASSWORD=change-me
-```
-
-Point the root config at the env file:
-
-```yaml
-arbiter:
-  env_file: local.env
-```
-
-Existing process environment variables take precedence over values from the env
-file. Relative paths are resolved from the config directory.
-
-Build or refresh that file from the active config:
-
-```bash
-arbiter-server env bootstrap
-arbiter-server env check
-```
-
-`env bootstrap` keeps existing assignments, adds missing config references, and
-groups entries under sorted `# arbiter-*` blocks plus `# miscellaneous`.
-If `arbiter.env_file` is not set yet, it adds `arbiter.env_file: .env` to the
-root config first.
-
-Then run from this directory:
-
-```bash
-arbiter-server config check
-arbiter-server serve
-```
-
-`config check` and `serve` require at least one configured service account.
-
-Use `arbiter-server plugins list` to inspect installed service plugins before
-validating a config. Once the server is running, use the client CLI against the
-MCP endpoint:
-
-```bash
-arbiter mcp tools arbiter.mcp_url=http://127.0.0.1:8025/mcp
-arbiter cap arbiter.mcp_url=http://127.0.0.1:8025/mcp
-arbiter accounts list arbiter.mcp_url=http://127.0.0.1:8025/mcp
-```
-
-The client can also read the endpoint from a small config file:
-`~/.arbiter/arbiter-client.yaml`.
-
-```yaml
-arbiter:
-  mcp_url: http://127.0.0.1:8025/mcp
-```
-
-Override config values with Hydra-style `key=value` arguments after the
-command, or bootstrap the client config:
-
-```bash
-arbiter bootstrap client arbiter.mcp_url=http://127.0.0.1:8025/mcp
-```
-
-IMAP operations use folder-scoped UIDs returned by `imap:list_messages` and
-`imap:search_messages`; pass those ids back to `imap:get_message`,
-`imap:move_message`, `imap:mark_message_read`, or `imap:delete_message` with
-the same account and folder.
-
-## Read-Only Real Inbox Docker Run
-
-For a hardened Docker setup that reads a single real IMAP folder with Docker
-secrets and no SMTP access, see:
-
-- [deploy/readonly-imap/README.md](deploy/readonly-imap/README.md)
-
-## License
-
-Arbiter is distributed under the MIT License. See [LICENSE](LICENSE).

arbiter_suite-0.9.0.dev1/arbiter_suite.egg-info/PKG-INFO

@@ -1,214 +0,0 @@
-Metadata-Version: 2.4
-Name: arbiter-suite
-Version: 0.9.0.dev1
-Summary: Policy-controlled access to configured services for agents
-Author-email: Omry Yadan <omry@yadan.net>
-Maintainer-email: Omry Yadan <omry@yadan.net>
-License: MIT
-Project-URL: Homepage, https://github.com/omry/arbiter
-Project-URL: Repository, https://github.com/omry/arbiter
-Keywords: agent,policy,mcp,access-control,smtp,imap,security
-Classifier: Development Status :: 3 - Alpha
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Programming Language :: Python :: 3.14
-Classifier: Topic :: Communications :: Email
-Classifier: Topic :: Software Development :: Libraries :: Python Modules
-Requires-Python: <3.15,>=3.10
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: arbiter-core==0.9.0.dev1
-Requires-Dist: arbiter-smtp==0.9.0.dev1
-Requires-Dist: arbiter-imap==0.9.0.dev1
-Provides-Extra: dev
-Requires-Dist: nox[pbs]<2026.0,>=2024.10; extra == "dev"
-Requires-Dist: aiosmtpd<2.0,>=1.4.6; extra == "dev"
-Requires-Dist: black<26.0,>=25.0; extra == "dev"
-Requires-Dist: mypy<2.0,>=1.11; extra == "dev"
-Requires-Dist: pytest<9.0,>=7.4; extra == "dev"
-Requires-Dist: tomli<3.0,>=2.0; extra == "dev"
-Requires-Dist: towncrier<25.0,>=24.8; extra == "dev"
-Requires-Dist: trustme<2.0,>=1.2; extra == "dev"
-Dynamic: license-file
-
-# Arbiter
-
-Arbiter is a capability firewall between AI agents and services. Today it exposes policy-controlled access through MCP and a client CLI; additional interfaces may be added later. The current service surface covers sending mail over SMTP and reading IMAP folders through explicit account policies.
-
-## Project Status
-
-Current implementation status:
-
-- MCP server over stdio, SSE, or streamable HTTP via FastMCP
-- capability discovery with SMTP and IMAP account and operation metadata
-- SMTP submission with configured sender identity, TLS/auth settings, text/HTML bodies, and Bcc kept out of message headers
-- IMAP list/get/search/move/mark-read/delete tools scoped to configured accounts and folders
-- `arbiter.account.<service>` and reusable `arbiter.policy.<service>` objects
-  for per-service account policy
-- `arbiter` client CLI and `arbiter-server` server/operator CLI
-- Docker deployment files for a standard SMTP gateway and a hardened read-only IMAP variant
-
-Known open gaps:
-
-- durable audit storage is parked for post-v1, while startup/runtime logging is
-  the v1 observability focus
-- normalized error-code responses are still a design contract, while the
-  implementation currently surfaces Python/MCP errors
-- the agent-facing skill integration path is intentionally not implemented in
-  this repository yet
-
-## Development
-
-Create and use the repo-local virtualenv with:
-
-- `python3 -m venv .venv`
-- `.venv/bin/python -m pip install --upgrade pip`
-- `.venv/bin/python -m pip install -e ".[dev]" -e core -e smtp -e imap`
-
-Run the test suite from the repo root with:
-
-- `.venv/bin/python -m nox -s tests`
-- `.venv/bin/python -m nox -s lint`
-
-The `lint` session runs both `black --check` and the Arbiter `mypy` passes.
-
-For focused local runs without `nox`, use the same environment directly, for example:
-
-- `.venv/bin/python -m pytest core/tests/unit/test_config.py`
-- `.venv/bin/python -m pytest core/tests/unit/test_app.py`
-
-The Docusaurus website lives in [website/](website/):
-
-- `cd website && npm install`
-- `cd website && npm run start`
-- `cd website && npm run build`
-
-The design is documented in the `docs/` structure used by the MCP server template:
-
-- [docs/overview.md](docs/overview.md)
-- [docs/architecture.md](docs/architecture.md)
-- [docs/BACKLOG.md](docs/BACKLOG.md)
-- [docs/config.md](docs/config.md)
-- [docs/config_bootstrap.md](docs/config_bootstrap.md)
-- [docs/policies.md](docs/policies.md)
-- [docs/errors.md](docs/errors.md)
-- [docs/todo.md](docs/todo.md)
-- [docs/testing_backlog.md](docs/testing_backlog.md)
-- [docs/tools/account_summaries.md](docs/tools/account_summaries.md)
-- [docs/tools/smtp_send_email.md](docs/tools/smtp_send_email.md)
-- [docs/tools/imap.md](docs/tools/imap.md)
-
-## Local Streamable HTTP Run
-
-For local Codex or VS Code integration, run Arbiter as a streamable HTTP MCP
-server and point the client at:
-
-```text
-http://127.0.0.1:8025/mcp
-```
-
-Arbiter does not ship a runnable service config. Bootstrap a Hydra
-config, edit it, then run the server. The default config directory is
-`~/.arbiter`; pass `--config-dir <dir>` before a subcommand to use a different
-location. `config.local/` is ignored scratchspace for repository-local
-development.
-Plugin-owned object templates are created by the plugin command surface:
-
-```bash
-arbiter-server bootstrap arbiter
-arbiter-server bootstrap plugin smtp account primary
-```
-
-`${oc.env:...}` reads the process environment that your shell, supervisor,
-container runtime, or secret manager provides. For local runs, the root config
-can name one optional dotenv-style file to load before composition.
-
-See [docs/config_bootstrap.md](docs/config_bootstrap.md) for the generated file
-layout and composition flow.
-
-For local development, a shell-owned env file can be useful:
-
-```bash
-# ~/.arbiter/local.env
-SMTP_PRIMARY_ACCOUNT_USERNAME=agent@example.com
-SMTP_PRIMARY_ACCOUNT_PASSWORD=change-me
-ARBITER_IMAP_USERNAME=agent@example.com
-ARBITER_IMAP_PASSWORD=change-me
-```
-
-Point the root config at the env file:
-
-```yaml
-arbiter:
-  env_file: local.env
-```
-
-Existing process environment variables take precedence over values from the env
-file. Relative paths are resolved from the config directory.
-
-Build or refresh that file from the active config:
-
-```bash
-arbiter-server env bootstrap
-arbiter-server env check
-```
-
-`env bootstrap` keeps existing assignments, adds missing config references, and
-groups entries under sorted `# arbiter-*` blocks plus `# miscellaneous`.
-If `arbiter.env_file` is not set yet, it adds `arbiter.env_file: .env` to the
-root config first.
-
-Then run from this directory:
-
-```bash
-arbiter-server config check
-arbiter-server serve
-```
-
-`config check` and `serve` require at least one configured service account.
-
-Use `arbiter-server plugins list` to inspect installed service plugins before
-validating a config. Once the server is running, use the client CLI against the
-MCP endpoint:
-
-```bash
-arbiter mcp tools arbiter.mcp_url=http://127.0.0.1:8025/mcp
-arbiter cap arbiter.mcp_url=http://127.0.0.1:8025/mcp
-arbiter accounts list arbiter.mcp_url=http://127.0.0.1:8025/mcp
-```
-
-The client can also read the endpoint from a small config file:
-`~/.arbiter/arbiter-client.yaml`.
-
-```yaml
-arbiter:
-  mcp_url: http://127.0.0.1:8025/mcp
-```
-
-Override config values with Hydra-style `key=value` arguments after the
-command, or bootstrap the client config:
-
-```bash
-arbiter bootstrap client arbiter.mcp_url=http://127.0.0.1:8025/mcp
-```
-
-IMAP operations use folder-scoped UIDs returned by `imap:list_messages` and
-`imap:search_messages`; pass those ids back to `imap:get_message`,
-`imap:move_message`, `imap:mark_message_read`, or `imap:delete_message` with
-the same account and folder.
-
-## Read-Only Real Inbox Docker Run
-
-For a hardened Docker setup that reads a single real IMAP folder with Docker
-secrets and no SMTP access, see:
-
-- [deploy/readonly-imap/README.md](deploy/readonly-imap/README.md)
-
-## License
-
-Arbiter is distributed under the MIT License. See [LICENSE](LICENSE).

arbiter_suite-0.9.0.dev1/arbiter_suite.egg-info/requires.txt

@@ -1,13 +0,0 @@
-arbiter-core==0.9.0.dev1
-arbiter-smtp==0.9.0.dev1
-arbiter-imap==0.9.0.dev1
-
-[dev]
-nox[pbs]<2026.0,>=2024.10
-aiosmtpd<2.0,>=1.4.6
-black<26.0,>=25.0
-mypy<2.0,>=1.11
-pytest<9.0,>=7.4
-tomli<3.0,>=2.0
-towncrier<25.0,>=24.8
-trustme<2.0,>=1.2