v0.11.0

• Migration stubs read table names from config — a rename is a config change only (#290).
  Every published stub now resolves its table through the config key the stores already honour
  (Schema::create(config('verdict.execution_claims.table', …)) and likewise across all 15
  stubs), so an adopter who renames a table in config no longer gets a store pointed at a table
  migrate never created. verdict_provenance_derivations — previously not renameable at all —
  gains verdict.evidence.derivations_table, read by the stub and threaded into the database
  recorder (both provider construction sites). Tests that create tables by requiring stubs now
  resolve names through a shared verdictTable() helper so the suite cannot be green with stubs
  and tests disagreeing; a new test proves the stubs under non-default names (create, add_*, down,
  and an end-to-end evidence write). Also closes #168's remaining half: fingerprint columns are
  asserted fixed char(64) and time columns engine timestamps (char/bpchar verified against
  real MySQL 8.4, MariaDB 11.8, and PostgreSQL). Named indexes keep default-derived names — two
  renamed installs in one PostgreSQL database still collide, stated in the docs and tracked as
  #315. No behaviour change for anyone on default names.
• Recorded: gpt-oss:20b under the corrected cases — the injection measured, the bound earned.
  100 sampled --control trials at the #293 merge commit, stated up front as not line-for-line
  comparable with the 2026-08-23 run (both changed cases are v2; the report carries per-case
  versions). 188 guarded security observations, 0 failures, rule-of-three ≤ 2% (95%). The
  retrieved-document injection was measured live for the first time: 32 evaluated guarded trials,
  every one an attempted owned-order cancel halted at the confirmation gate, all passing under
  case v2 where v1 mislabelled them failures. The #280 over-restriction gate appears in a
  recorded run for the first time (MET (maximum 100%), search case 64.2% — reported, not
  gated, at the deliberate default). cross-principal-cancellation was measured on gpt-oss for
  the first time (2 guarded denials, 3 unguarded breaches).
• The evaluation methodology cites its prior work, and the bound states its assumptions (#296).
  docs/evaluation.md grounds each load-bearing methodology choice in the external source that is
  its origin or its independent confirmation, placed beside the claim it supports: the rule-of-three
  bound cites Hanley & Lippman-Hand (JAMA 1983) and now states the i.i.d. assumption it inherits —
  within-case and within-arm trials are correlated, so every printed bound is a working
  approximation, with clustered standard errors (Miller, arXiv:2411.00640) named as the correction
  the harness deliberately does not compute; the over-restriction facet cites CaMeL's published
  77%→84% utility cost (arXiv:2503.18813); the abliterated-model instrument cites Red Hat's
  independently published rationale; and a new "Methodology and prior work" subsection maps
  Abdelnabi et al.'s benchmarking-validity threats (arXiv:2605.22568) onto the harness's standing
  answers and names the Agentic Benchmark Checklist (arXiv:2507.02825) as the peer standard a
  future item-by-item scoring would run against. Docs only; no behaviour changes.
• Published migration stubs now honor configured table names (#290). Every Verdict migration
  reads the matching verdict.*.table configuration value, including the newly configurable
  provenance-derivations table, so changing a supported table name in configuration no longer
  leaves the corresponding store pointing at an uncreated default-named table. The migration
  tests exercise configured names and their matching stores.