local-dev: prune broken engines on rebuild + document one-time bake

`make rebuild` runs `compose build --no-cache backend gateway` plus
a fresh `up -d --wait`. It must therefore also reap any engine
container whose bind-mount source went away during host downtime,
otherwise the new backend image boots into a stack with the same
orphan that triggered the heal flow in the first place.

Also extend the troubleshooting note: pulling the heal-cycle fix
requires one explicit `make rebuild` so the backend image picks up
the pre-bootstrap reconciler tick. Without that, `make up` runs
the new Makefile target but the legacy backend cannot follow
through, and the developer is left staring at a `cancelled`
sandbox with no running replacement.

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

This commit is contained in:

Ilia Denisov

2026-05-10 22:40:27 +02:00

parent edc9709bd6

commit ff53cc0ad3

2 changed files with 14 additions and 1 deletions

									
										tools/local-dev/Makefile
									
		+1
		-1
	
												View File
												
				@@ -36,7 +36,7 @@ help:

				up: build-engine prune-broken-engines

					$(COMPOSE) up -d --wait

				rebuild: build-engine

				rebuild: build-engine prune-broken-engines

					$(COMPOSE) build --no-cache backend gateway

					$(COMPOSE) up -d --wait