Patch release closing FINDING-005 (DB migrations not auto-bootstrapped
in sidecar). The sidecar now bootstraps schema at startup via Flyway;
docker-compose dev users no longer need to apply migrations manually.

Companion change in `aria-runtime@9bd22d5`:
- build.gradle.kts: +flyway-core, +flyway-database-postgresql, +postgresql JDBC
- application.yml: spring.flyway.* configured against existing aria.postgres.*;
  baseline-on-migrate=true for safe upgrades; ARIA_FLYWAY_ENABLED=false
  for split-permission deployments where the sidecar lacks DDL grants
- src/main/resources/db/migration/: V001..V003 vendored from gatekeeper repo

Spec status: HLD v1.1.1, LLD v1.1.1, ERROR_CODES v1.1.1, DB_SCHEMA v1.1.2,
CODE_REVIEW_REPORT v1.1.2, RELEASE_NOTES (v0.1.0 + v0.1.1 patch).

All v0.1 critical gaps now closed:
- FINDING-003 (audit pipeline) — closed in v1.1.1 / aria-runtime@d487026 / ADR-009
- FINDING-005 (DB migrations) — closed in v1.1.2 / aria-runtime@9bd22d5

Remaining gaps (all minor, all v0.2+ scope):
- FINDING-001: ariactl CLI deferred (v0.2)
- PromptAnalyzer + ContentFilter stubs (v0.3 enterprise CISO)
- Karar B token role semantics open (v0.2)
- Reversible tokenisation (v0.2)
- WASM masking, Coverage/SAST re-run, latency-guard simplification (v0.2/deferred)

Human sign-off: docs/06_review/HUMAN_SIGN_OFF_v0.1.1.md (commit 80bfb29)
v0.1.x release cohort: 3dfcb5f + a63986f + f1e869e + 249474b + 7ea75cc + 80bfb29