Replace Python development tooling with Make and containerized shell

docs/local-development.md

@@ -5,9 +5,13 @@ Task [#42](https://git.sendico.io/tech/sxchnge/issues/42),
 
 ## Build and bootstrap
 
-Requires Docker with Compose v2 and BuildKit, Python 3.10+ and Git. Docker builds
-Go, protobuf bindings and Flutter web; host Go, protoc and Flutter installations
-are not required for `make build && make up`. The first Flutter SDK download can
+Requires Make, a POSIX shell and a local Docker engine with Compose v2 and
+BuildKit. Docker builds Go, protobuf bindings and Flutter web; host Go, protoc
+and Flutter installations are not required for `make build && make up`. The
+tooling container includes Docker CLI, curl, jq, Git and OpenSSL. No host Python,
+jq, curl or Git installation is needed for these Make targets. It mounts
+the local Docker socket and workspace to orchestrate Compose; a remote Docker
+daemon is not supported. The first Flutter SDK download can
 take several minutes. Both ARM64 and AMD64 build from the same source definitions.
 
 ```sh
@@ -52,7 +56,7 @@ containers never mount it. You can also provision the same secret with a hidden
 terminal prompt, without placing the API key in shell history:
 
 ```sh
-python3 dev/local.py email
+make email
 make up
 ```
 
@@ -169,6 +173,7 @@ make ps
 make logs
 make down             # preserves named volumes and local bootstrap material
 make up               # idempotent provisioning and readiness checks
+make test-dev-tooling # offline shell and failure-path checks
 make test-dev-infra   # works before Resend provisioning
 make test-dev-rotation # real Vault rotations under BFF HTTP traffic
 make test-dev         # requires all six services running