feat(deploy): containerization + WP-specific deploy + config examples

- Containerfile: top-level container build (Chainguard-base per estate convention).
- deploy/: compose.yaml + setup.sh + verify-sqli.sh + local-test.sh + DEPLOY.adoc + Containerfile.ols-local.
- examples/: wharf-cli.toml + yacht-agent.toml — sample configs.
- eclexiaiser.toml: eclexia (sustainabot policy engine) config.

Per the 2026-04-26 graduation plan (AI-WORK-todo.md item -4).

Author: hyperpolymath

Cargo.lock

@@ -0,0 +1,42 @@
+# SPDX-License-Identifier: PMPL-1.0-or-later
+# SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
+
+# Multi-stage Containerfile for Project Wharf
+# Builds both wharf-cli and yacht-agent binaries
+# Uses Chainguard images for minimal attack surface
+
+# Builder stage — Wolfi-base with Rust toolchain
+FROM cgr.dev/chainguard/wolfi-base:latest AS builder
+
+RUN apk add --no-cache rust pkgconf openssl-dev gcc glibc-dev
+
+WORKDIR /build
+
+# Copy workspace files
+COPY Cargo.toml Cargo.lock ./
+COPY crates/ crates/
+COPY bin/ bin/
+# Dummy xtask for workspace resolution
+RUN mkdir -p xtask/src && echo 'fn main() {}' > xtask/src/main.rs
+COPY xtask/Cargo.toml xtask/Cargo.toml
+
+# Build release binaries
+RUN cargo build --release --bin wharf --bin yacht-agent
+
+# Runtime image for wharf-cli
+FROM cgr.dev/chainguard/wolfi-base:latest AS wharf-cli
+
+COPY --from=builder /build/target/release/wharf /usr/local/bin/wharf
+
+ENTRYPOINT ["wharf"]
+CMD ["--help"]
+
+# Runtime image for yacht-agent (wolfi-base — glibc required)
+FROM cgr.dev/chainguard/wolfi-base:latest AS yacht-agent
+
+COPY --from=builder /build/target/release/yacht-agent /yacht-agent
+
+EXPOSE 3306 33060 9001
+
+ENTRYPOINT ["/yacht-agent"]
+CMD ["--help"]

Containerfile

@@ -0,0 +1,22 @@
+# SPDX-License-Identifier: PMPL-1.0-or-later
+# SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
+#
+# OpenLiteSpeed local dev image — WordPress-ready with MySQL extensions
+# EXCEPTION: No Chainguard OLS image exists — litespeedtech base required
+
+FROM docker.io/litespeedtech/openlitespeed:1.8.5-lsphp83
+
+# lsphp83-common (bundled in base) provides gd, mbstring, xml, zip
+# Only need to add packages not already included
+RUN apt-get update && apt-get install -y --no-install-recommends \
+    lsphp83-mysql \
+    lsphp83-curl \
+    lsphp83-intl \
+    lsphp83-imagick \
+    lsphp83-redis \
+    && apt-get clean \
+    && rm -rf /var/lib/apt/lists/*
+
+EXPOSE 8088
+
+WORKDIR /var/www/vhosts/localhost/html

deploy/Containerfile.ols-local

@@ -0,0 +1,144 @@
+// SPDX-License-Identifier: PMPL-1.0-or-later
+= Project Wharf — Deployment Guide
+:toc: left
+:icons: font
+
+== Prerequisites
+
+* A Linux server (Debian 12+, Ubuntu 22.04+, Fedora 38+, or any distro with podman)
+* `podman` or `docker` installed
+* At least 2 GB RAM, 10 GB disk
+* Ports 8080, 8443, 9001 available
+
+== Quick Start (5 minutes)
+
+[source,bash]
+----
+# Clone the repo
+git clone https://github.com/hyperpolymath/project-wharf.git
+cd project-wharf/deploy
+
+# Run the setup script
+sudo ./setup.sh --domain example.com
+
+# Start the stack
+sudo podman compose -f ../infra/selur-compose.yaml up -d
+
+# Verify
+curl http://localhost:9001/health
+# → {"status":"ok","moored":false,...}
+----
+
+== What Gets Deployed
+
+[cols="1,2,1"]
+|===
+| Service | Purpose | Port
+
+| `yacht-agent` | Security enforcer (DB proxy, integrity, mooring API) | 3306, 9001
+| `yacht-nginx` | Reverse proxy (TLS termination, static files) | 8080, 8443
+| `mariadb` | Database (shadowed behind yacht-agent proxy) | 33060 (internal)
+|===
+
+== Architecture
+
+[source,text]
+----
+Internet → nginx:8080/8443 → PHP-FPM → yacht-agent:3306 → MariaDB:33060
+                                              ↑
+                                     AST-aware SQL filter
+                                     (blocks injection)
+----
+
+WordPress connects to the database on port 3306, which is the yacht-agent's proxy.
+The agent parses every SQL statement's AST and enforces table-level write policies.
+
+== Managing Your Site
+
+=== From Your Local Machine (The Wharf)
+
+[source,bash]
+----
+# Install the wharf CLI
+cargo install --path bin/wharf-cli
+
+# Initialize your fleet
+wharf init --adapter wordpress
+
+# Push changes to the yacht
+wharf moor example.com
+
+# Verify remote integrity
+wharf integrity verify --remote example.com
+----
+
+=== On the Server (The Yacht)
+
+[source,bash]
+----
+# Check agent status
+curl http://localhost:9001/stats
+
+# View metrics (Prometheus format)
+curl http://localhost:9001/metrics
+
+# Check health
+curl http://localhost:9001/health
+----
+
+== Local Development (Podman Compose)
+
+For a quick local proof-of-concept with WordPress behind the SQL proxy:
+
+[source,bash]
+----
+cd deploy
+
+# Automated: downloads WordPress, generates wp-config.php, builds + starts stack
+bash local-test.sh
+
+# Visit WordPress setup wizard
+# http://localhost:8080
+
+# Prove SQL injection is blocked (6 tests)
+bash verify-sqli.sh
+
+# Check agent stats
+curl http://localhost:9001/stats
+
+# Tear down
+podman compose down
+rm -rf wharf-local/    # removes all data
+----
+
+=== Local Stack Architecture
+
+[source,text]
+----
+Browser :8080 → OLS (web) → PHP/WordPress → agent:3306 → db:3306 (MariaDB)
+                                                ↑
+                                       AST SQL parser (sqlparser 0.39)
+                                       Blocks writes to wp_users, wp_options, wp_posts
+                                       Blocks DROP/ALTER/TRUNCATE always
+----
+
+=== Services
+
+[cols="1,2,1"]
+|===
+| Service | Purpose | Port
+
+| `db` | MariaDB 10.11 (hidden, no host exposure) | 3306 (internal)
+| `agent` | yacht-agent SQL proxy + API | 3306 (proxy), 9001 (API)
+| `web` | OpenLiteSpeed 1.8.5 + PHP 8.3 | 80→8080 (host)
+|===
+
+== Security Notes
+
+* The default signature scheme is `ml-dsa-87-only` (FIPS 204, post-quantum safe)
+* To enable hybrid Ed448+ML-DSA-87 signatures (not yet audited):
+  set `signature_scheme = "hybrid"` in `yacht-agent.toml`
+* WordPress is configured with `DISALLOW_FILE_EDIT` and `DISALLOW_FILE_MODS`
+* All code changes go through the mooring protocol (cryptographically signed)
+* The database proxy blocks writes to `wp_users`, `wp_options`, `wp_posts` tables
+* `DROP TABLE` and `ALTER TABLE` are always blocked regardless of table

deploy/DEPLOY.adoc

@@ -0,0 +1,165 @@
+# Project Wharf — Local Deployment Session Summary
+<!-- SPDX-License-Identifier: PMPL-1.0-or-later -->
+
+**Date:** 2026-02-14
+**Status:** COMMITTED TO GITHUB. GitLab push pending (broken pack object).
+
+---
+
+## What Was Done
+
+### Bug Fixes (3 files)
+
+| File | Bug | Fix |
+|------|-----|-----|
+| `infra/containers/Containerfile.agent` | Wolfi doesn't have `musl-dev`, `cargo`, or `rustup` packages | Switched to glibc build: `rust pkgconf openssl-dev gcc glibc-dev`, removed musl target/RUSTFLAGS, build from `target/release/`, runtime `wolfi-base` |
+| `Containerfile` (line 35) | yacht-agent stage uses `static` image but binary is glibc-linked → segfault | Changed to `cgr.dev/chainguard/wolfi-base:latest` |
+| `adapters/wordpress-wharf/wharf-adapter.php` | Reads flat `$stats['queries_allowed']` but `/stats` returns nested `{"queries":{"allowed":N}}`. Also reads `moored`/`firewall_mode` from `/stats` but they're on `/status` | Rewrote `wharf_fetch_agent_stats()` to fetch both `/stats` and `/status`, maps nested JSON to flat format |
+
+### New Files (4 files)
+
+| File | Purpose |
+|------|---------|
+| `deploy/Containerfile.ols-local` | OLS 1.8.5 + lsphp83 with mysql/curl/intl/imagick/redis extensions |
+| `deploy/compose.yaml` | 3-service podman compose: db (MariaDB 10.11), agent (yacht-agent), web (OLS) |
+| `deploy/local-test.sh` | Automated: create dirs, download WP, fetch real salt keys, write wp-config.php (DB_HOST=agent:3306), copy adapter plugin, build containers, start stack, health check |
+| `deploy/verify-sqli.sh` | 6 SQL injection tests via `podman exec` through agent proxy |
+
+### Documentation Updated (8 files)
+
+| File | Changes |
+|------|---------|
+| `CHANGELOG.adoc` | Added "Local Deployment Proof" section |
+| `TOPOLOGY.md` | Added local deployment architecture diagram + `local-deploy` row in dashboard |
+| `AI.a2ml` | Added "Local Deployment" section |
+| `deploy/DEPLOY.adoc` | Added local dev instructions, architecture diagram, services table |
+| `.machine_readable/STATE.scm` | Added `local-deployment-proof` milestone with 5 sub-milestones |
+| `.machine_readable/ECOSYSTEM.scm` | Added `openlitespeed` and `mariadb` as related projects |
+| `.machine_readable/META.scm` | Added 2 ADRs: `glibc-runtime-containers`, `ols-local-deployment` |
+| `.gitignore` | Added `deploy/wharf-local/` |
+
+### Verification Results
+
+- **cargo test**: 63/63 passed (40 wharf-core + 19 wharf-cli + 4 yacht-agent)
+- **Stack**: All 3 containers healthy, WordPress installation wizard served at :8080
+- **Agent**: `/health` → OK, `/stats` → real counters (321 allowed, 3 blocked), `/status` → active
+- **verify-sqli.sh**: 6/6 passed
+  - SELECT → PASS (forwarded)
+  - INSERT INTO wp_users → BLOCKED
+  - DROP TABLE → BLOCKED
+  - ALTER TABLE → BLOCKED
+  - TRUNCATE TABLE → BLOCKED
+  - UNION SELECT injection → BLOCKED
+
+---
+
+## Commit
+
+```
+ece13ac feat: local E2E deployment proof — WordPress behind yacht-agent SQL proxy
+```
+
+15 files changed, 578 insertions(+), 38 deletions(-)
+
+**Pushed to:** GitHub ✅
+**Pushed to:** GitLab ❌ (see below)
+
+---
+
+## Remaining: GitLab Push
+
+**Two issues blocking GitLab push:**
+
+### Issue 1: Diverged history
+GitLab has 3 old MR-based commits not in GitHub's history (`64fc965`, `5827c3f`, `bf1aac3`). Needs force-push to overwrite with canonical GitHub history.
+
+### Issue 2: `main` branch is protected + API token expired
+- GitLab `main` branch is protected (no force push allowed)
+- GitLab API token (`glpat-dYz2_j--...`) is **EXPIRED**
+- SSH auth works but can't change branch protection via SSH
+- `glab` CLI also uses the expired token
+
+### Fix (manual steps required)
+
+```bash
+# Step 1: Refresh GitLab token
+# Go to: https://gitlab.com/-/user_settings/personal_access_tokens
+# Create new token with api + write_repository scopes
+# Update ~/.netrc with new token
+
+# Step 2: Unprotect main
+GL_TOKEN="<new-token>"
+PROJECT_ID=$(curl -sf --header "PRIVATE-TOKEN: $GL_TOKEN" \
+  "https://gitlab.com/api/v4/projects?search=project-wharf&owned=true" | python3 -c "import sys,json; print(json.load(sys.stdin)[0]['id'])")
+curl --request DELETE --header "PRIVATE-TOKEN: $GL_TOKEN" \
+  "https://gitlab.com/api/v4/projects/$PROJECT_ID/protected_branches/main"
+
+# Step 3: Force push from clean clone (already at /tmp/wharf-push.git)
+cd /tmp/wharf-push.git
+git push --force git@gitlab.com:hyperpolymath/project-wharf.git main
+
+# Step 4: Re-protect main
+curl --request POST --header "PRIVATE-TOKEN: $GL_TOKEN" \
+  "https://gitlab.com/api/v4/projects/$PROJECT_ID/protected_branches?name=main&push_access_level=40&merge_access_level=40"
+
+# Step 5: Clean up
+rm -rf /tmp/wharf-push.git
+```
+
+### Also fix the local repo's broken pack (optional)
+
+The local `.git` has a broken pack object (`501faf18`) from the old GitLab fetch. Not urgent — local repo works fine for everything except `git gc`.
+
+```bash
+cd /var$REPOS_DIR/project-wharf
+git remote remove gitlab
+git remote add gitlab git@gitlab.com:hyperpolymath/project-wharf.git
+# After GitLab is force-pushed with clean history:
+git fetch gitlab
+```
+
+---
+
+## How to Use the Local Stack
+
+```bash
+cd /var$REPOS_DIR/project-wharf/deploy
+
+# Start everything (downloads WP, builds containers, starts stack)
+bash local-test.sh
+
+# WordPress setup wizard
+# http://localhost:8080
+
+# Agent API
+curl http://localhost:9001/health
+curl http://localhost:9001/stats
+
+# Prove SQL injection blocked
+bash verify-sqli.sh
+
+# Tear down
+podman compose down
+rm -rf wharf-local/   # removes all runtime data
+```
+
+### Key Architecture Detail
+
+```
+Browser :8080 → OLS (port 80) → PHP/WordPress → agent:3306 (yacht-agent) → db:3306 (MariaDB)
+                                                      ↑
+                                             AST SQL parser (sqlparser 0.39)
+                                             Blocks: INSERT wp_users, DROP, ALTER, TRUNCATE, UNION
+```
+
+WordPress `wp-config.php` has `DB_HOST = 'agent:3306'` — all SQL goes through the proxy.
+MariaDB is NOT exposed to the host network.
+
+---
+
+## Next Steps (Future Sessions)
+
+1. **GitLab push** — use the fix above
+2. **Production VPS** — deploy to stamp-protocol.org with real TLS
+3. **WordPress setup** — complete the install wizard, activate Wharf adapter plugin
+4. **Bitbucket/Codeberg** — mirror when those forges are unblocked