feat(P27): add Examples section to every module README (D-058)

Each module README (10 primitives + 2 patterns) now has a ## Examples
section before ## Versioning, referencing and excerpting the validated
simple.yaml + complex.yaml (+ mysql.yaml for RDS) example contracts. The
RDS README includes a Multi-engine variation subsection (D-059).

---ci---
project: acdl
phase: 27
milestone: v1.7
status: execute
---/ci---

modules/l1/s3/README.md

@@ -56,6 +56,45 @@ pipeline as the regression baseline).
 - **Public access block** — add `aws_s3_bucket_public_access_block` to prevent data exfiltration (SOC2 CC6.1, GDPR Art.32).
 - **Lifecycle policy** — add `aws_s3_bucket_lifecycle_configuration` for retention enforcement (GDPR Art.5(2), HIPAA §164.530(j)).
 
+## Examples
+
+Validated example contracts are in [`examples/`](examples/). The platform-test
+pipeline validates them against `schemas/contract.schema.json`.
+
+### Simple
+
+A minimal deployment:
+
+[`examples/simple.yaml`](examples/simple.yaml)
+```yaml
+uses: acdl/pipelines/deploy.yaml@v1.6
+module: s3
+environment: dev
+inputs:
+  bucket_name: my-simple-bucket
+  region: us-east-1
+```
+
+### Complex
+
+A production deployment with optional inputs:
+
+[`examples/complex.yaml`](examples/complex.yaml)
+```yaml
+uses: acdl/pipelines/deploy.yaml@v1.6
+module: s3
+environment: dev
+inputs:
+  bucket_name: my-production-bucket
+  region: us-east-1
+```
+
+> **Note:** the s3 primitive's compliance extensions (Object Lock, access
+> logging, public access block, lifecycle policy) are documented in the
+> Compliance extension points section above but not yet wired as inputs.
+> The complex example uses the same inputs as the simple example;
+> compliance extensions are roadmap.
+
 ## Versioning
 
 `1.0.0` — interface MAJOR, behavior MINOR, lifecycle PATCH. MAJOR bumps