epic-5/story-3: Add Planned Expansion Surfaces for Async and Framework Integrations - #45

…-compat audit

Beads: ai-driven-product-dev-gfy3
Agent: fullstack-sdk-dev
Status: completed
Forward-compat audit grounded in actual post-5.2 module tree; no Phase-3 code.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Beads: ai-driven-product-dev-ugkj
Agent: fullstack-sdk-dev
Status: completed
Looking-ahead in index; async/framework forward-refs in migration + extending
docs; changes/+story-5-3-async-framework-roadmap.internal.md fragment.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…py + flush.py rows)

Beads: ai-driven-product-dev-gfy3
Review finding: audit table claimed to cover every MVP module but omitted
tracking/tracker.py and tracking/flush.py. Both added with extend-with-sibling
verdicts. No production code; gates green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

… parity

The rules engine implemented only 8 of the 10 comparison operators present
in the JS reference and PHP SDK. isIn and regexMatches were missing, so any
config using "value in list" or regex audience rules silently never matched
(unknown match_type resolves to None -> rule item returns False).

- Add _is_in and _regex_matches, registered under "isIn"/"regexMatches".
  Semantics mirror the JS source of truth (regex catches re.error -> False).
- 20 unit tests (10 per operator) matching PHP ComparisonsTest granularity.
- 17 cross-SDK parity vectors (9 isIn, 8 regexMatches).

Full suite: 799 passed; ruff + mypy --strict clean; rule parity 44 vectors pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…t UA and report status

Tracking events were POSTed to the config CDN host (returning 403) instead of
the separate metrics endpoint. Adds TransportConfig.track_base_url (default
https://[project_id].metrics.convertexperiments.com/v1, JS/PHP parity),
substitutes [project_id] at request time, and POSTs to {track_base}/track/{key}.

Also sets User-Agent: ConvertAgent/1.0 so the metrics bot filter does not
silently drop events (200-but-discarded), and propagates the HTTP status code
on the success path so QueueReleasedPayload.status_code carries the real 2xx
(send_tracking now returns int).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Adds demo/run_demo.py — an OFFLINE (committed fixture, deterministic, no
network) and LIVE (sdk_key against staging) manual-verification harness that
runs the full FullStack arc: experience -> feature-rollout experience ->
segments -> conversion + delivery report.

Mirrors the JS and PHP demos: buckets the feature rollout via run_experience
(key test-experience-ab-fullstack-4, per php-sdk config; the JS demo's
test-feature-rollout-1 is stale), passes location=events and the mobile=true
audience attribute, and sets the country=US default segment. Self-diagnoses
any non-bucketing via diagnose_experience. Excludes demo/ from the sdist,
gitignores demo/.env, and lints demo/ in CI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…ollout-1 typed vars

The committed demo harness (49de4e9) had unilaterally overridden the frozen
qs-12 spec's feature-rollout decision: it used PHP's run_experience on
test-experience-ab-fullstack-4 and printed raw string variables_data, instead
of the spec's JS-authoritative run_feature('test-feature-rollout-1') resolving
typed variables (bool/string/integer). This left two gaps: the OFFLINE output
did not match the README contract, and the typed-variables acceptance criterion
was unmet.

Align the implementation to the spec:
- config_fixture.json: re-key the feature to test-feature-rollout-1; declare the
  4 typed vars the README shows; drop the redundant rollout-as-experience block;
  correct the _comment (JS-authoritative; LIVE override via env var).
- run_demo.py: step [2] now calls run_feature(test-feature-rollout-1) printing
  typed vars + status + via experience/variation; move the audience attrs +
  country default-segments LIVE-only so OFFLINE output is byte-identical to the
  README; correct the misleading comments.
- test_demo_harness.py: flip the feature-key assertions/comments back to
  test-feature-rollout-1; the /api/v1/config route guard is unchanged.

OFFLINE output now byte-matches demo/README.md verbatim. Full suite 828 passed,
ruff + mypy green, demo/ excluded from sdist + wheel, zero src/ changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

… py3.10 match under py39 gate)

anyio 4.x uses `match` statements (Python 3.10+) in its internals. When mypy
descends into anyio transitively via `import httpx` in
src/convert_sdk/adapters/transport/httpx_transport.py, it fails under our
`python_version = "3.9"` target with:
  anyio/_core/_tasks.py:361: error: Pattern matching is only supported in
  Python 3.10 and greater [syntax]

This is dependency drift (anyio version churn), not a code defect. The fix
adds "anyio.*" to the existing [[tool.mypy.overrides]] block that already
skips click.* and towncrier.* for the same reason — third-party packages that
use newer syntax than our minimum-Python target.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>