mcp-forge/tests
Hans Aschauer 9ceeaa1eda Re-wire mcp_forge to use pod_executor
- Created adapters/ module with SimpleBackend and JupyterBackend wrappers
- Adapters map ForgeConfig to pod_executor explicit parameters
- Updated server.py to use pod_executor components:
  - PodmanClient and SecureContainerManager from pod_executor
  - SimpleFileAuditLogger and BasicValidator from pod_executor
  - Removed old execution/ and podman/ imports

- Updated all tool files:
  - execute_python.py: imports from adapters
  - document_state.py: uses jupyter_backend instead of session_manager
  - resources.py: updated session references

- Updated builder files to import from pod_executor:
  - image_builder.py: PodmanClient, parse_memory_string
  - environment_builder.py: PodmanClient

- Fixed test: test_resource_limits_storage_quota_in_podman_params
  - Storage is tracked internally but not in Podman params
  - All 40 pod_executor tests now passing

Key architectural change:
- pod_executor is now the execution engine
- mcp_forge adapters provide ForgeConfig compatibility layer
- Separation of concerns: execution vs MCP protocol
2026-02-07 11:11:06 +01:00
..
builder initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
config initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
execution Fix error handling and update tests for Jupyter backend 2026-02-07 08:20:20 +01:00
integration initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
mcp initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
pod_executor Re-wire mcp_forge to use pod_executor 2026-02-07 11:11:06 +01:00
podman initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
security initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
server initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
__init__.py initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00