AOCI-CODE v0.1.1

AOCI-CODE v0.1.1 is built from a9b803fa47ac2a9c3a2da48209c9030db513612d.

A security update of the PostgreSQL driver. Nothing else changes: the Go
toolchain, the other dependencies, the MCP tool surface, input schemas,
formal-asset formats, and scope identities are those of v0.1.0, and a
repository aligned under v0.1.0 stays aligned. Upgrade if a PostgreSQL
source's connection string uses require_auth or channel_binding=require
without sslmode=verify-full; MySQL and openGauss sources do not use this
driver.

• Update the PostgreSQL driver github.com/jackc/pgx/v5 to 5.12.0, which
  moves github.com/jackc/puddle/v2 to 2.2.3. pgx 5.12.0 fixes
  GHSA-95fj-3fxw-g62g: from 5.9.0, a server could skip the authentication that
  require_auth or channel_binding=require demanded, so a PostgreSQL source
  relying on those without sslmode=verify-full could be answered by an
  impersonating server. AOCI sends only fixed catalog queries, so the exposure
  was a forged snapshot, not business data. GHSA-j38q-h3ph-jjpq does not reach
  AOCI, which never sends simple-protocol batches. The release module set is
  the same 22 modules, and both license texts are byte-identical.
• Known issue, unchanged from v0.1.0: running aoci cognition onboard apply
  again on an onboarding that already completed writes the session back to
  apply_pending, then answers onboarding_artifact_conflict. The formal
  assets and the Baseline are untouched, and Verify, Check, and the Guide
  still report aligned; only the transaction and approval states that
  cognition onboard status reads from .aoci/onboarding/active.json
  disagree. Run Apply once. The v0.2.0 line returns the recorded result
  instead and repairs a session left this way.

See docs/install.md and docs/supply-chain.md for asset verification.