EffectWitness v0.3.3

EffectWitness 0.3.3 is a patch prerelease for the bounded MCP effect-evidence
harness.

What changed:

• The eight-call concurrent controls now use a dedicated 30-second response
  budget. This is strictly above two independent five-second SQLite busy
  windows plus scheduling headroom. Normal single-call controls remain at ten
  seconds, and the explicit 150 ms registered transport fault is unchanged.
• The SQLite WAL transition now occurs once when each effect-store instance is
  initialized, before concurrent requests. Later connections verify WAL
  read-only and retain FULL synchronous commits and five-second busy handling.
• A failed registered scenario still produces no artifact. Its exception now
  contains only registered scenario/check names, normalized exception types,
  and bounded witness/concurrency counts; raw messages and paths remain absent.
• Artifact-verifier tests copy one session-scoped sealed baseline instead of
  repeatedly running the ten-scenario integration matrix. A separate producer
  test continues to run and verify a fresh matrix.
• Schema-v3 and schema-v4 verifiers accept registered 0.3.3 producers while
  retaining compatibility with the registered 0.3.0, 0.3.1, and 0.3.2
  producers.
• The current bundled Windows schema-v4 reference is bound to source revision
  b99fa745cc98dd543dcd637d3523eabba864552e: 4 scenarios x 10 rounds,
  80 completed worker records, and 60 normalized mutating-call observations.

Why this is 0.3.3:

The public v0.3.0 tag was not released after its tag-triggered CI exposed a
low-probability client response-timeout path in one Windows/Python 3.12
schema-v2 test. The server-side witness still showed the registered two
attempts and one effect; the client had not confirmed the clean retry response.
The v0.3.1 tag was also not released: its tag CI found a separate low-level
transport regression that still used a five-second normal-call budget. The
v0.3.2 tag was not released after its Windows/Python 3.11 tag job exposed a
different eight-way misleading-control timeout late in repeated artifact
generation. This patch addresses that concurrency topology without retrying
calls, accepting errors, weakening evidence checks, or sealing partial output.

Verification:

• The exact tagged commit passed all 11 GitHub Actions jobs across Ubuntu and
  Windows, CPython 3.11-3.13, the exact real-filesystem lane, and the LangGraph
  replay lane.
• Local full suite: 202 passed and 2 skipped because this Windows host did not
  allow the two symlink-creation cases.
• The exact misleading eight-call concurrent control passed 30 consecutive
  local stress runs with no missing observation, attempt, or effect.
• The current bundled reference has 8 files (7 manifest-covered), 190,761
  total bytes, and manifest-file SHA-256
  0ab2e816ea484054f6d878f8132486c46a49cf4b828bb3ba4c3b173260aec7f7.
• The committed tree and extracted wheel/sdist passed the repository privacy
  scanner plus a private publication denylist before release.

Boundaries:

The evidence is local, synthetic, version/input/OS-bounded engineering
evidence. It makes no claim about exactly-once execution, arbitrary workflow or
MCP correctness, official conformance, production recovery, security,
performance, external review, adoption, deployment, or recruiting outcomes.
No model API or paid service was used by the evidence lanes.