agent-containers 0.1.0.dev0__tar.gz

agent_containers-0.1.0.dev0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Anirban Basu
+
+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.

agent_containers-0.1.0.dev0/PKG-INFO

@@ -0,0 +1,195 @@
+Metadata-Version: 2.4
+Name: agent-containers
+Version: 0.1.0.dev0
+Summary: Deterministic onboarding and maintenance for hardened coding-agent containers
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Requires-Dist: pydantic>=2.11,<3
+Requires-Dist: tomlkit>=0.13,<1
+Requires-Dist: typer>=0.16,<1
+Requires-Python: >=3.12
+Project-URL: Repository, https://github.com/anirbanbasu/agent-containers
+Project-URL: Issues, https://github.com/anirbanbasu/agent-containers/issues
+Project-URL: Download, https://pypi.org/project/agent-containers/
+Description-Content-Type: text/markdown
+
+# agent-containers CLI
+
+The Python package is tested on Python 3.14 (with Python 3.12+ support). It
+validates profiles, produces offline plans, materializes bundled image recipes,
+and applies a direct-Docker deployment without launching an agent session.
+
+This directory will contain the standalone Python project for deterministic
+onboarding and maintenance of this repository's hardened agent images. The
+distribution and executable name is `agent-containers`; the Python import
+package will be `agent_containers`.
+
+## Agreed scope
+
+- Human-editable, versioned TOML profiles, with separate machine-managed
+  deployment state. Interactive prompts and noninteractive inputs use the same
+  validation model; unknown fields are errors.
+- Claude Code, OpenCode, Codex, and Hermes adapters, targeting Linux Docker Engine
+  and macOS Docker Desktop. Support claims require actual integration tests.
+- All four optional package categories: apt packages, npm packages, isolated uv
+  tools, and system Python libraries installed with uv.
+- Explicit custom file/directory mounts and copy-once configuration seeds,
+  without duplicating each agent's settings schema. Relative input paths resolve
+  against the profile directory; the workspace defaults to the launch directory.
+- Composable hosted/local/custom model endpoints, HTTP(S) proxies, CA trust,
+  egress gateways, and experimental observability integrations. Decant is
+  experimental and currently limited to Claude Code and Codex; it is disabled
+  unless a profile opts in. Opted-in Decant launches use user-scoped image,
+  container, and data-volume names and mount selected agent collection
+  subdirectories directly; the delegated volume bridge remains a separate
+  manual setup. Local inference engine installation and model
+  downloads are outside the agreed initial scope.
+- Explicit application and updates, retained prior deployments, and rollback of
+  the selected image and managed launch configuration. Rollback does not restore
+  mutable home-volume data or terminate existing sessions automatically.
+- Image recipes bundled from canonical `../agent-images/` sources in both wheel
+  and source distributions. No maintained duplicate or installed-package edits.
+
+## Safety and verification
+
+Preserve the repository's containment contract. Package selection must not
+silently expand runtime egress. Credentials must not appear in profiles, build
+arguments, images, logs, or command output; profiles reference runtime inputs.
+
+When a profile declares a proxy, its generated Docker launch exports both
+uppercase and lowercase `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` variables,
+and enables Node's environment proxy support. A profile `proxy.ca_file` or
+`proxy.ca_dir` is copied into the isolated image build context and installed
+into the image's system trust store. The generated launch points
+`SSL_CERT_FILE`, `REQUESTS_CA_BUNDLE`, and `NODE_EXTRA_CA_CERTS` at the merged
+system bundle. Certificate inputs are never placed in the shared canonical
+image assets; they are deployment-specific and excluded from command output.
+
+Gateway profiles require a host and port plus a read-only SSH key and pinned
+known-hosts input. These can be supplied through the dedicated profile paths or
+explicit mounts at `/etc/agent/gateway-key` and
+`/etc/agent/gateway-known-hosts`; bootstrap rules are restricted to literal
+IP addresses/CIDRs. Gateway user, Cloudflare Access hostname, and bootstrap
+allow rules are emitted only when gateway mode is explicitly configured.
+
+Langfuse support is experimental and opt-in for Claude Code, Codex, and
+OpenCode. The CLI installs the vendor-supported integration for the selected
+agent and emits only references to credential environment variables; it never
+stores credential values. A Langfuse endpoint must be present in the profile's
+egress allowlist (or be reached through a configured gateway). Langfuse is one
+of many possible OpenTelemetry backends, not a default telemetry provider.
+
+Unit and distribution tests must run without Docker. Integration tests require
+Docker and disposable resources, without real account logins. Offline plans and
+diagnostics must distinguish recorded state from inspected live state and mark
+runtime checks unavailable when Docker cannot be reached.
+
+Use direct Docker commands, not Compose, and package with `uv build` and the
+native `uv_build` backend, not Hatchling, with Python 3.12 or newer. Use `ty`
+for type checking and Ruff for linting/formatting. Both live in the `dev`
+dependency group; pytest and coverage live in `test`.
+
+From this directory, install contributor dependencies with
+`uv sync --group test --python 3.12`. Root `just test-cli` runs unit and packaging
+tests under coverage; `just check-cli` runs Ruff and ty. Coverage must reach 100%.
+Do not suppress type or coverage errors without a demonstrated, documented need.
+The packaging test builds a standalone source distribution and installs its
+rebuilt wheel in a fresh temporary environment; dependency downloads may be needed.
+
+The CLI prints its required ASCII banner before every invocation. Deployment
+state defaults to `$XDG_STATE_HOME/agent-containers/` (or
+`~/.local/state/agent-containers/`). On macOS Docker Desktop, `apply` keeps the
+host UID but uses image GID `1000`: the conventional macOS GID 20 collides with
+an existing Linux image group, and the project deliberately retains its
+Dockerfile collision rejection rather than silently joining that group.
+
+If the host mounts `/tmp` with `noexec`, use a dedicated executable temporary
+directory for pytest's `--basetemp` option. Pytest owns and clears that directory:
+never point it at an existing directory containing your files. No mount flags
+need changing. Tests still install outside the repository and use a fresh venv.
+
+The test suite covers CLI behavior, profile/state validation, generated build
+contexts, Docker argv construction, lifecycle transitions, and standalone
+sdist-to-wheel installation at 100% source coverage. It does not establish all
+runtime containment or agent compatibility claims; broader Docker integration
+tests remain to be implemented.
+
+Profile-managed npm and uv tools are installed into image-owned locations
+outside the persistent home during image creation only. Runtime root filesystems
+stay read-only, with the existing explicit writable mounts preserved. Manual
+home installations take PATH precedence; diagnostics must warn when they shadow
+image-managed executables. Do not delete existing home tools.
+
+The private implementation handoff is maintained in
+`../tmp-onboarding-codex.log`; the original discussion is in
+`../tmp-onboarding.md`. Both are intentionally ignored by Git.
+
+## Current commands
+
+`agent-containers create PROFILE.toml` interactively prompts for every profile
+section, validates the resulting model, and writes a new TOML file atomically.
+It refuses to replace an existing file and never contacts Docker. Secrets are
+never prompted for; provider authentication is represented only by an
+environment-variable name.
+
+`agent-containers validate PROFILE.toml` parses and validates a profile without
+contacting Docker or changing files.
+
+`agent-containers plan PROFILE.toml` compares the desired profile with optional
+recorded deployment JSON (`--state STATE.json`). It reports image versus launch
+changes and always discloses that live Docker state was not inspected.
+
+`agent-containers apply PROFILE.toml` materializes an isolated profile-owned
+build context, builds or verifies its retained image, copies any new seed only
+when its target is absent, and atomically selects deployment state. State is
+written to the standard per-user location unless `--state STATE.json` overrides
+it. `apply` does not launch an agent or terminate an existing session. After a
+successful apply it also refreshes the CLI-managed
+`$XDG_CONFIG_HOME/agent-containers/profiles.sh` (or
+`~/.config/agent-containers/profiles.sh`) with a namespaced shortcut for the
+profile. Source that file once from your shell startup file:
+
+```sh
+source "$HOME/.config/agent-containers/profiles.sh"
+```
+
+For example, a profile named `work-codex` becomes
+`agent_containers_work_codex`. The generated function evaluates the current
+directory when invoked, selects the profile's retained image and home volume,
+and forwards arguments to the agent. It does not accept arbitrary Docker
+options; use the documented generic shortcuts when an intentional one-off
+override is needed.
+
+By default, profile resources are namespaced with the host username and UID:
+an image tag and home volume created for `work` by one user cannot collide with
+the corresponding `work` resources created by another user on the same Docker
+host. Set `home_volume = "an-existing-volume"` in the profile when an existing
+named volume should be reused; that explicit name is an intentional sharing
+choice and is never silently renamed.
+
+Provider launch mappings are agent-specific: Claude Code uses its endpoint and
+model environment variables, Codex uses per-run configuration overrides, and
+Hermes uses per-run `--provider`/`--model` flags plus the documented base-URL
+environment for supported `custom`, `openai`, and `anthropic` routes. OpenCode
+endpoint/model fields are rendered into a secret-free JSON provider
+configuration for that invocation. The shared entrypoint writes it under
+`/tmp` and sets `OPENCODE_CONFIG`, so the profile does not modify the
+persistent OpenCode home.
+
+`agent-containers rollback PROFILE.toml` verifies and selects the immediately
+previous retained image and launch record. It previews restored egress,
+proxy/CA, and endpoint choices. It never restores persistent-home data or stops
+an existing agent session, and refreshes that profile's generated shortcut.
+
+`agent-containers doctor PROFILE.toml` is read-only. It reports Docker-daemon
+availability, the expected deployment-state file, and whether the selected
+image can be inspected; it creates, starts, and changes nothing.
+
+Before building a distribution, run `uv run --project cli python cli/scripts/bundle_image_assets.py`; 
+`just build-cli` does this automatically.
+The generated package-data directory is ignored, derived only from canonical
+`agent-images/`, and included in the wheel and source distribution.

agent_containers-0.1.0.dev0/README.md

@@ -0,0 +1,176 @@
+# agent-containers CLI
+
+The Python package is tested on Python 3.14 (with Python 3.12+ support). It
+validates profiles, produces offline plans, materializes bundled image recipes,
+and applies a direct-Docker deployment without launching an agent session.
+
+This directory will contain the standalone Python project for deterministic
+onboarding and maintenance of this repository's hardened agent images. The
+distribution and executable name is `agent-containers`; the Python import
+package will be `agent_containers`.
+
+## Agreed scope
+
+- Human-editable, versioned TOML profiles, with separate machine-managed
+  deployment state. Interactive prompts and noninteractive inputs use the same
+  validation model; unknown fields are errors.
+- Claude Code, OpenCode, Codex, and Hermes adapters, targeting Linux Docker Engine
+  and macOS Docker Desktop. Support claims require actual integration tests.
+- All four optional package categories: apt packages, npm packages, isolated uv
+  tools, and system Python libraries installed with uv.
+- Explicit custom file/directory mounts and copy-once configuration seeds,
+  without duplicating each agent's settings schema. Relative input paths resolve
+  against the profile directory; the workspace defaults to the launch directory.
+- Composable hosted/local/custom model endpoints, HTTP(S) proxies, CA trust,
+  egress gateways, and experimental observability integrations. Decant is
+  experimental and currently limited to Claude Code and Codex; it is disabled
+  unless a profile opts in. Opted-in Decant launches use user-scoped image,
+  container, and data-volume names and mount selected agent collection
+  subdirectories directly; the delegated volume bridge remains a separate
+  manual setup. Local inference engine installation and model
+  downloads are outside the agreed initial scope.
+- Explicit application and updates, retained prior deployments, and rollback of
+  the selected image and managed launch configuration. Rollback does not restore
+  mutable home-volume data or terminate existing sessions automatically.
+- Image recipes bundled from canonical `../agent-images/` sources in both wheel
+  and source distributions. No maintained duplicate or installed-package edits.
+
+## Safety and verification
+
+Preserve the repository's containment contract. Package selection must not
+silently expand runtime egress. Credentials must not appear in profiles, build
+arguments, images, logs, or command output; profiles reference runtime inputs.
+
+When a profile declares a proxy, its generated Docker launch exports both
+uppercase and lowercase `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` variables,
+and enables Node's environment proxy support. A profile `proxy.ca_file` or
+`proxy.ca_dir` is copied into the isolated image build context and installed
+into the image's system trust store. The generated launch points
+`SSL_CERT_FILE`, `REQUESTS_CA_BUNDLE`, and `NODE_EXTRA_CA_CERTS` at the merged
+system bundle. Certificate inputs are never placed in the shared canonical
+image assets; they are deployment-specific and excluded from command output.
+
+Gateway profiles require a host and port plus a read-only SSH key and pinned
+known-hosts input. These can be supplied through the dedicated profile paths or
+explicit mounts at `/etc/agent/gateway-key` and
+`/etc/agent/gateway-known-hosts`; bootstrap rules are restricted to literal
+IP addresses/CIDRs. Gateway user, Cloudflare Access hostname, and bootstrap
+allow rules are emitted only when gateway mode is explicitly configured.
+
+Langfuse support is experimental and opt-in for Claude Code, Codex, and
+OpenCode. The CLI installs the vendor-supported integration for the selected
+agent and emits only references to credential environment variables; it never
+stores credential values. A Langfuse endpoint must be present in the profile's
+egress allowlist (or be reached through a configured gateway). Langfuse is one
+of many possible OpenTelemetry backends, not a default telemetry provider.
+
+Unit and distribution tests must run without Docker. Integration tests require
+Docker and disposable resources, without real account logins. Offline plans and
+diagnostics must distinguish recorded state from inspected live state and mark
+runtime checks unavailable when Docker cannot be reached.
+
+Use direct Docker commands, not Compose, and package with `uv build` and the
+native `uv_build` backend, not Hatchling, with Python 3.12 or newer. Use `ty`
+for type checking and Ruff for linting/formatting. Both live in the `dev`
+dependency group; pytest and coverage live in `test`.
+
+From this directory, install contributor dependencies with
+`uv sync --group test --python 3.12`. Root `just test-cli` runs unit and packaging
+tests under coverage; `just check-cli` runs Ruff and ty. Coverage must reach 100%.
+Do not suppress type or coverage errors without a demonstrated, documented need.
+The packaging test builds a standalone source distribution and installs its
+rebuilt wheel in a fresh temporary environment; dependency downloads may be needed.
+
+The CLI prints its required ASCII banner before every invocation. Deployment
+state defaults to `$XDG_STATE_HOME/agent-containers/` (or
+`~/.local/state/agent-containers/`). On macOS Docker Desktop, `apply` keeps the
+host UID but uses image GID `1000`: the conventional macOS GID 20 collides with
+an existing Linux image group, and the project deliberately retains its
+Dockerfile collision rejection rather than silently joining that group.
+
+If the host mounts `/tmp` with `noexec`, use a dedicated executable temporary
+directory for pytest's `--basetemp` option. Pytest owns and clears that directory:
+never point it at an existing directory containing your files. No mount flags
+need changing. Tests still install outside the repository and use a fresh venv.
+
+The test suite covers CLI behavior, profile/state validation, generated build
+contexts, Docker argv construction, lifecycle transitions, and standalone
+sdist-to-wheel installation at 100% source coverage. It does not establish all
+runtime containment or agent compatibility claims; broader Docker integration
+tests remain to be implemented.
+
+Profile-managed npm and uv tools are installed into image-owned locations
+outside the persistent home during image creation only. Runtime root filesystems
+stay read-only, with the existing explicit writable mounts preserved. Manual
+home installations take PATH precedence; diagnostics must warn when they shadow
+image-managed executables. Do not delete existing home tools.
+
+The private implementation handoff is maintained in
+`../tmp-onboarding-codex.log`; the original discussion is in
+`../tmp-onboarding.md`. Both are intentionally ignored by Git.
+
+## Current commands
+
+`agent-containers create PROFILE.toml` interactively prompts for every profile
+section, validates the resulting model, and writes a new TOML file atomically.
+It refuses to replace an existing file and never contacts Docker. Secrets are
+never prompted for; provider authentication is represented only by an
+environment-variable name.
+
+`agent-containers validate PROFILE.toml` parses and validates a profile without
+contacting Docker or changing files.
+
+`agent-containers plan PROFILE.toml` compares the desired profile with optional
+recorded deployment JSON (`--state STATE.json`). It reports image versus launch
+changes and always discloses that live Docker state was not inspected.
+
+`agent-containers apply PROFILE.toml` materializes an isolated profile-owned
+build context, builds or verifies its retained image, copies any new seed only
+when its target is absent, and atomically selects deployment state. State is
+written to the standard per-user location unless `--state STATE.json` overrides
+it. `apply` does not launch an agent or terminate an existing session. After a
+successful apply it also refreshes the CLI-managed
+`$XDG_CONFIG_HOME/agent-containers/profiles.sh` (or
+`~/.config/agent-containers/profiles.sh`) with a namespaced shortcut for the
+profile. Source that file once from your shell startup file:
+
+```sh
+source "$HOME/.config/agent-containers/profiles.sh"
+```
+
+For example, a profile named `work-codex` becomes
+`agent_containers_work_codex`. The generated function evaluates the current
+directory when invoked, selects the profile's retained image and home volume,
+and forwards arguments to the agent. It does not accept arbitrary Docker
+options; use the documented generic shortcuts when an intentional one-off
+override is needed.
+
+By default, profile resources are namespaced with the host username and UID:
+an image tag and home volume created for `work` by one user cannot collide with
+the corresponding `work` resources created by another user on the same Docker
+host. Set `home_volume = "an-existing-volume"` in the profile when an existing
+named volume should be reused; that explicit name is an intentional sharing
+choice and is never silently renamed.
+
+Provider launch mappings are agent-specific: Claude Code uses its endpoint and
+model environment variables, Codex uses per-run configuration overrides, and
+Hermes uses per-run `--provider`/`--model` flags plus the documented base-URL
+environment for supported `custom`, `openai`, and `anthropic` routes. OpenCode
+endpoint/model fields are rendered into a secret-free JSON provider
+configuration for that invocation. The shared entrypoint writes it under
+`/tmp` and sets `OPENCODE_CONFIG`, so the profile does not modify the
+persistent OpenCode home.
+
+`agent-containers rollback PROFILE.toml` verifies and selects the immediately
+previous retained image and launch record. It previews restored egress,
+proxy/CA, and endpoint choices. It never restores persistent-home data or stops
+an existing agent session, and refreshes that profile's generated shortcut.
+
+`agent-containers doctor PROFILE.toml` is read-only. It reports Docker-daemon
+availability, the expected deployment-state file, and whether the selected
+image can be inspected; it creates, starts, and changes nothing.
+
+Before building a distribution, run `uv run --project cli python cli/scripts/bundle_image_assets.py`; 
+`just build-cli` does this automatically.
+The generated package-data directory is ignored, derived only from canonical
+`agent-images/`, and included in the wheel and source distribution.

agent_containers-0.1.0.dev0/pyproject.toml

@@ -0,0 +1,108 @@
+[build-system]
+requires = ["uv_build>=0.12.10,<0.13"]
+build-backend = "uv_build"
+
+[project]
+name = "agent-containers"
+version = "0.1.0.dev0"
+description = "Deterministic onboarding and maintenance for hardened coding-agent containers"
+license = "MIT"
+license-files = ["LICEN[CS]E*"]
+readme = "README.md"
+requires-python = ">=3.12"
+dependencies = [
+    "pydantic>=2.11,<3",
+    "tomlkit>=0.13,<1",
+    "typer>=0.16,<1",
+]
+classifiers = [
+    "Development Status :: 2 - Pre-Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.12",
+]
+
+[project.urls]
+Repository = "https://github.com/anirbanbasu/agent-containers"
+Issues = "https://github.com/anirbanbasu/agent-containers/issues"
+Download = "https://pypi.org/project/agent-containers/"
+
+[project.scripts]
+agent-containers = "agent_containers.cli:app"
+
+[dependency-groups]
+dev = [
+    "ty>=0.0.1,<1",
+    "ruff>=0.11,<1",
+]
+test = [
+    "pytest>=8.4.1,<10",
+    "coverage>=7.9.1,<8",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = [
+    "--import-mode=importlib",
+    "--strict-markers",
+]
+markers = [
+    "packaging: builds and installs distributions without Docker",
+    "integration: requires an explicitly enabled disposable Docker environment",
+]
+
+[tool.ruff]
+target-version = "py312"
+line-length = 120
+include = [
+    "src/agent_containers/**/*.py",
+    "tests/**/*.py",
+]
+
+[tool.ruff.lint]
+extend-select = [
+    "Q",
+    "RUF100",
+    "RUF018",
+    "C90",
+    "UP",
+    "I",
+    "D",
+    "TID251",
+]
+ignore = [
+    "D100",
+    "D102",
+    "D104",
+    "D105",
+    "D107",
+]
+
+[tool.ruff.lint.mccabe]
+max-complexity = 15
+
+[tool.ruff.lint.isort]
+combine-as-imports = true
+known-first-party = ["agent_containers"]
+
+[tool.ruff.lint.pydocstyle]
+convention = "google"
+
+[tool.ruff.format]
+docstring-code-format = false
+
+[tool.ty.environment]
+python-version = "3.12"
+
+[tool.ty.rules]
+possibly-unresolved-reference = "warn"
+
+[tool.coverage.run]
+source = ["agent_containers"]
+omit = ["tests/*"]
+
+[tool.coverage.report]
+fail_under = 100
+skip_covered = true
+show_missing = true
+precision = 2

agent_containers-0.1.0.dev0/pyproject.toml.orig

@@ -0,0 +1,86 @@
+[build-system]
+requires = ["uv_build>=0.12.10,<0.13"]
+build-backend = "uv_build"
+
+[project]
+name = "agent-containers"
+version = "0.1.0.dev0"
+description = "Deterministic onboarding and maintenance for hardened coding-agent containers"
+license = "MIT"
+license-files = ["LICEN[CS]E*"]
+readme = "README.md"
+requires-python = ">=3.12"
+dependencies = [
+    "pydantic>=2.11,<3",
+    "tomlkit>=0.13,<1",
+    "typer>=0.16,<1",
+]
+
+classifiers = [
+    "Development Status :: 2 - Pre-Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.12",
+]
+
+[project.urls]
+Repository = "https://github.com/anirbanbasu/agent-containers"
+Issues = "https://github.com/anirbanbasu/agent-containers/issues"
+Download = "https://pypi.org/project/agent-containers/"
+
+[project.scripts]
+agent-containers = "agent_containers.cli:app"
+
+[dependency-groups]
+dev = [
+    "ty>=0.0.1,<1",
+    "ruff>=0.11,<1",
+]
+test = [
+    "pytest>=8.4.1,<10",
+    "coverage>=7.9.1,<8",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = ["--import-mode=importlib", "--strict-markers"]
+markers = [
+    "packaging: builds and installs distributions without Docker",
+    "integration: requires an explicitly enabled disposable Docker environment",
+]
+
+[tool.ruff]
+target-version = "py312"
+line-length = 120
+include = ["src/agent_containers/**/*.py", "tests/**/*.py"]
+
+[tool.ruff.lint]
+extend-select = ["Q", "RUF100", "RUF018", "C90", "UP", "I", "D", "TID251"]
+mccabe = { max-complexity = 15 }
+ignore = ["D100", "D102", "D104", "D105", "D107"]
+
+[tool.ruff.lint.isort]
+combine-as-imports = true
+known-first-party = ["agent_containers"]
+
+[tool.ruff.lint.pydocstyle]
+convention = "google"
+
+[tool.ruff.format]
+docstring-code-format = false
+
+[tool.ty.environment]
+python-version = "3.12"
+
+[tool.ty.rules]
+possibly-unresolved-reference = "warn"
+
+[tool.coverage.run]
+source = ["agent_containers"]
+omit = ["tests/*"]
+
+[tool.coverage.report]
+fail_under = 100
+skip_covered = true
+show_missing = true
+precision = 2

agent_containers-0.1.0.dev0/src/agent_containers/__init__.py

@@ -0,0 +1 @@
+"""Deterministic onboarding and maintenance for hardened agent containers."""

agent_containers-0.1.0.dev0/src/agent_containers/__main__.py

@@ -0,0 +1,6 @@
+"""Support python -m agent_containers."""
+
+from agent_containers.cli import app
+
+if __name__ == "__main__":
+    app()