# Container And Test Host Handoff

Status: draft
Created: 2026-05-08

## Purpose

This note captures what should move into a container or dedicated test host
after local OpenCMIS TCK execution is stable.

Containerization is not a prerequisite for WP-0002 local execution.

## Candidate Runtime Image

The first dedicated runtime image should include:

- Python 3.11+
- Java runtime/JDK verified against OpenCMIS TCK 1.1.0
- Maven
- guide-board core
- `open-cmis-tck` extension

It should not bake in secrets or target-specific profiles.

## Mounts

Expected mounts:

```text
/profiles      target and assessment profiles
/credentials   optional credential files
/runs          generated guide-board run directories
/m2            optional Maven cache
```

For licensed or externally supplied assets, add:

```text
/assets
```

The current OpenCMIS TCK runtime uses Maven Central and does not require
vendored assets.

## Environment

Useful environment variables:

```text
CMIS_TCK_USER
CMIS_TCK_PASSWORD
MAVEN_OPTS
GUIDE_BOARD_EXTENSION_PATHS
```

The adapter should still prefer profile-level `credentials_ref` over implicit
environment assumptions.

## Network Assumptions

The test host must reach:

- the CMIS Browser Binding endpoint under test,
- Maven Central or an internal Maven mirror during dependency resolution,
- any internal credential source if file mounts are not used.

## Handoff Criteria

Move to a container or test host after:

- `scripts/bootstrap_opencmis_tck.py --resolve` is ready locally,
- at least one repository/type live run has produced guide-board evidence,
- real TCK output normalization has been reviewed,
- the maturity scorecard has its first evidence-backed output.