- 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
