mhoennigandClaude Opus 5 aa5ea091ae docs: RFC 0005 has nothing left open (#9) ...

The last item was the socket inside a build sandbox for Werkator's own
integration tests. It is in place: a systemd user unit serves a werkdock
API socket in Werkator's build-environment home, .werkator.yml points
DOCKER_HOST at it, and the Testcontainers smoke test that had skipped
itself on every host that mattered now runs on the webspace and passes —
1 test, 0 ignored, 12.3s.

That test is this RFC's alarm. If werkdock's Engine API subset ever
stops being enough for Testcontainers, Werkator's own build says so
rather than a person noticing months later.

Documentation only, no version bump.

Squashed from branch rfc-0005-closed and pushed to main directly.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-11 08:20:18 +02:00

..

0001-implementation-language.md

Werkdock RFC 0001 accepted: Go it is

2026-09-01 06:42:13 +02:00

0002-docker-compatible-surface.md

RFC 0005 milestone 2: instance lifecycle — run -d, ps, stop, logs, rm, exec (#4)

2026-09-10 20:55:59 +02:00

0003-composable-toolchain-mounts.md

RFC 0004: docker-compatible image creation

2026-09-05 23:05:19 +02:00

0004-docker-compatible-image-creation.md

Pull (#2)

2026-09-10 19:26:55 +02:00

0005-services-and-testcontainers.md

docs: RFC 0005 has nothing left open (#9)

2026-09-11 08:20:18 +02:00