Capture live-Docker release-host evidence for private alpha

[Joncallim]

Goal

Record release-host live-Docker evidence for the private-alpha gate without overstating what was validated.

Plain-English Context

DockerMap is meant to inspect real Docker hosts, so a release should not rely only on mock data or a developer laptop. This issue asks an agent to run the live-Docker check on the actual release-style host and record exactly what passed, what versions were used, and what still needs attention.

Roadmap Source

• docs/planning/ROADMAP.md -> Now: Private Alpha Hardening -> Capture release-host evidence.
• docs/release/RELEASE_CHECKLIST.md -> Execute After Next Commit -> capture live-Docker evidence on the release host with npm run test:live-docker, including Docker and Compose versions.

Recommended Agent

Primary: qa-evidence

Handoff note: use release-ops only if the release host itself needs deployment or environment setup before tests can run.

Scope

Target areas:

• docs/release/RELEASE_CHECKLIST.md
• release notes location if one already exists
• docs/testing/TESTING_PLAN.md only if the evidence procedure is stale or incomplete
• tests/e2e only if the live-Docker test itself is broken and the maintainer asks for a fix

Direction

1. Run this on the intended Docker-capable Linux release host, not a mock-only local environment.
2. Record the exact commit SHA under test.
3. Record host OS/kernel and tool versions needed to interpret the result: Node, npm, Rust, Cargo, Docker, Docker Compose, and browser/Playwright browser if applicable.
4. Run npm run test:live-docker and preserve the exact pass/fail result.
5. If the command fails, capture the failing step and recommend keeping the release gate open.
6. Do not edit app behavior as part of this issue unless explicitly redirected; this issue is for evidence capture.
7. Do not include secrets, host tokens, auth headers, or private URLs in the issue comment or docs.

Acceptance Criteria

• Release evidence identifies the commit SHA and the release host context.
• npm run test:live-docker result is recorded with Docker and Compose versions.
• The release checklist is updated to show the evidence status for the live-Docker gate.
• Any failure includes a plain-English reason and a next action instead of being marked complete.
• No private token, credential, auth header, or sensitive host path is pasted into docs or comments.

Validation Commands

Run on the release host and record exact results:

• git rev-parse HEAD
• node --version
• npm --version
• rustc --version
• cargo --version
• docker --version
• docker compose version
• uname -a
• npm run test:live-docker

State any skipped commands and why.

Closure Evidence

When resolved, post a comment using the repository evidence format:

## Resolution Evidence
- What changed:
- Why this resolves the issue:
- How I checked it:
- Remaining risk or follow-up:

Recommendation: This issue appears resolved and can be closed by a maintainer.

If the command could not be run on the release host, recommend keeping the issue open. Do not close the issue automatically.

[Joncallim]

Resolution Evidence

• What I checked: I ran the live-Docker evidence capture on the current Linux host at commit 3d18e918ebbf5f514294f5c85e5a7bdaba14311e.
• Host/tooling used: Ubuntu 24.04.4 LTS, Linux 6.8.0-106-generic x86_64, Node v25.8.2, npm 11.16.0, Rust/Cargo 1.88.0, Docker client/server 29.3.0 via passwordless sudo, Docker Compose v5.1.1, Playwright 1.61.0, Google Chrome 149.0.7827.114.
• Result: npm run test:live-docker passed: 1 live-Docker Playwright test passed in 48.7s. A follow-up cleanup check found no leftover dockermap-e2e fixture containers.
• Important caveat: Direct Docker socket access is denied for the current shell, so the harness used the supported sudo -n docker fallback. Also, I cannot independently confirm that this exact machine is the intended private-alpha release host.

Recommendation: Leave this issue open unless a maintainer confirms this is the intended private-alpha release host. If this host is confirmed, the evidence above supports closing the issue; otherwise it should stay open until the same command and evidence capture are run on the actual release host.

[Joncallim]

Resolution Evidence

• What changed: Attempted the live-Docker release-evidence pass from commit 17c7dd1ef0e8bc53b33a7367eef4283e830053a8 on July 3, 2026, and recorded the host/tool context from this machine: Darwin 25.5.0 arm64, Node v26.4.0, npm 11.17.0, rustc 1.88.0, cargo 1.88.0, Docker 29.5.3, and Docker Compose v5.1.4.
• Why this resolves the issue: It does not fully resolve the issue yet. This run was on a macOS workstation, not the intended Docker-capable Linux release host, and npm run test:live-docker did not complete.
• How I checked it: Ran git rev-parse HEAD, uname -a, node --version, npm --version, rustc --version, cargo --version, docker --version, docker compose version, and npm run test:live-docker. The live-Docker check failed after about 1.4 minutes while docker compose -p dockermap-e2e-mr4zvmqz -f /var/folders/j5/wl06phn904v7z5wrg04dh3z40000gn/T/dockermap-live-e2e-axbnb1/compose.yaml up -d was still pulling busybox:1.36.1 for the fixture stack.
• Remaining risk or follow-up: This issue still needs a run on the intended Linux release/review host. Before relying on this harness for release evidence, investigate why the fixture image pull does not complete on this machine.

Recommendation: Keep this issue open until the exact commands above are rerun and recorded on the Linux release host.