Week 1 infrastructure: Docker environments, deploy pipeline, bookstore-core scaffold

Docker Compose environments for dev/staging/production (MariaDB, Redis,
Caddy, Action Scheduler cron sidecar), an idempotent deploy script,
git-hook-based deploy pipeline, backup/restore scripts, and the
bookstore-core plugin stub with WooCommerce HPOS compatibility declared.

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

deploy/restore.sh

@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+# Restores a backup INTO STAGING ONLY. Deliberately has no production path —
+# the launch gate is "a full backup has been restored into staging," never
+# production overwritten by a drill.
+set -euo pipefail
+
+DB_DUMP="${1:?Usage: restore.sh <db-dump.sql.gz> <uploads.tar.gz>}"
+UPLOADS_ARCHIVE="${2:?Usage: restore.sh <db-dump.sql.gz> <uploads.tar.gz>}"
+REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+cd "$REPO_ROOT"
+
+ENV_FILE=".env.staging"
+set -a
+# shellcheck disable=SC1090
+source "$ENV_FILE"
+set +a
+
+COMPOSE="docker compose -f docker-compose.yml -f docker-compose.staging.yml --env-file ${ENV_FILE}"
+
+echo "!! this OVERWRITES the staging database and uploads !!"
+read -r -p "type 'restore' to continue: " confirm
+[[ "$confirm" == "restore" ]] || { echo "aborted"; exit 1; }
+
+echo "==> restoring database"
+gunzip -c "$DB_DUMP" | $COMPOSE exec -T db sh -c "exec mysql -u\"\$MARIADB_USER\" -p\"\$MARIADB_PASSWORD\" \"\$MARIADB_DATABASE\""
+
+echo "==> restoring uploads"
+ARCHIVE_DIR="$(cd "$(dirname "$UPLOADS_ARCHIVE")" && pwd)"
+ARCHIVE_NAME="$(basename "$UPLOADS_ARCHIVE")"
+$COMPOSE run --rm -T -v "${ARCHIVE_DIR}:/restore:ro" wordpress \
+  tar -xzf "/restore/${ARCHIVE_NAME}" -C /var/www/html/wp-content
+
+echo "==> restore complete — verify the site before treating the drill as passed"