dck-dockerfile — a repository's own development container

This skill renders one repository's development container from the devcontainer-kit template and proves it with a real build. Each repository gets its own files; no shared base image is involved:

File	What it is
`.devcontainer/devcontainer.json`	what VS Code / Cursor open: the same compose service as `dev.sh`
`.devcontainer/dck.toml`	the source of truth: runtime, ports, layers, agents
`docker/local/<service>/Dockerfile`	FROM the runtime's official image pinned by digest; Neovim, DeepWorkPlan Vim (`--strict`), Herdr, gh, herdr-peers, every download verified; the agents layer when asked
`docker/local/<service>/dck/`	the build scripts the Dockerfile copies (vendored by dck)
`docker/local/docker-compose.yaml`	the service, loopback ports, named volumes, the host SSH agent
`dev.sh`	the entry point: `bash dev.sh up`

It speaks devcontainer-kit interface 2. Read interface in dck doctor --json first. If dck is missing, tell the user and show the pinned install line. Do not install it without being asked: