---
id: w1/m18/t006
title: Update docs/ADR004-deployment.md for the shipped rootDir behavior
worker: worker1
status: done
estimate: 20m
depends_on: [w1/m18/t002, w1/m18/t004]
---

## Objective

Replace the now-stale "no `spec.rootDir` field yet" gotcha in `docs/ADR004-deployment.md` with an accurate description of the shipped behavior and its remaining limits.

## Context

- `docs/ADR004-deployment.md:157` — current gotcha reads: *"Build-from-git needs a root Dockerfile today — BuildKit builds from the repo root; a repo whose Dockerfile sits in a subdirectory (no `spec.rootDir` field yet) won't build. CNB (`spec.builder: buildpack`) is likewise not yet in-cluster."*
- The "In-cluster builds (BuildKit → Zot)" section (`docs/ADR004-deployment.md:143-152`) is the natural place to describe the new `spec.rootDir` behavior inline.

## Steps

1. Rewrite the line-157 gotcha to state `spec.rootDir` now exists and works for the Dockerfile builder; keep the caveat that buildpack/CNB builds still aren't in-cluster (so `rootDir` is moot there until kpack lands).
2. Add a short note in the "In-cluster builds" section describing that a non-empty `rootDir` scopes both the build context and the webhook's auto-deploy path filter.
3. Run `npx prettier@3.4.2 --write "**/*.md"` (repo rule) after editing.

## Files

- `docs/ADR004-deployment.md`

## Acceptance criteria

- [x] The stale "no `spec.rootDir` field yet" line is removed/corrected
- [x] The doc mentions both build-context scoping and webhook path-filter scoping
- [x] `npx prettier@3.4.2 --write "**/*.md"` run and clean

## Out of scope

- `docs/ADR018-render-parity.md` updates (covered by t007, the Render parity standing task).
