feat(plugin): stabilize plugin interface and otel package

[zhongkechen]

Summary

• remove the experimental documentation and runtime FutureWarning from the plugins handler parameter
• keep payload-bearing plugin API fields experimental with source documentation and dataclass metadata
• require every plugin info field containing input, output, result, or error to carry the experimental marker
• mark the OTel distribution as Production/Stable
• add regression coverage for warning behavior, payload-field markers, and package metadata

Testing

• focused payload-field marker test passed
• Python compilation passed for all changed Python files
• OTel package metadata assertions passed
• git diff --check passed

The local shell only provides Python 3.10, while the SDK requires Python 3.11+, so the focused test used compatibility shims for typing.Self, datetime.UTC, and enum.StrEnum. CI will run the full suite with the supported toolchain.

[github-actions]

Codex AI review

No actionable findings. Residual risk is limited to tests not being executed under the review constraints.

Reviewed commit 7ac7acc6a7dae231f2abbb8e37f9780cc9b89af0. Workflow run

[github-actions]

Claude AI review

No actionable findings.

This is a clean, well-scoped stabilization PR:

• execution.py — removes the FutureWarning on the plugins parameter and the now-unused warnings import; docstring updated consistently. No remaining references to the removed warning.
• plugin.py — adds metadata={"experimental": True} plus attribute docstrings to OperationInfo.result, OperationInfo.error, and InvocationEndInfo.error. InvocationEndInfo.error retains default=None and stays non-kw_only, so dataclass field ordering is unaffected. Inherited fields keep their metadata, so the new marker test correctly covers subclasses.
• otel/pyproject.toml — classifier bumped to Development Status :: 5 - Production/Stable, matched by the new test_package_metadata.py.
• Tests — test_durable_execution_loads_plugins_when_handler_is_initialized now escalates FutureWarning to an error under warnings.catch_warnings(), correctly asserting the new no-warning behavior; test_payload_fields_are_marked_experimental enforces the experimental marker across all nine plugin info dataclasses.

The attribute docstrings are no-op statements and are not flagged by the configured Ruff rule set (E4/E7/E9/F/TID252; no B018).

Residual test risk (not a finding):

• test_payload_fields_are_marked_experimental iterates a hardcoded tuple of info types; a future info dataclass with an input/output/result/error field would need to be added to that tuple to stay covered.
• Per the PR description, local runs used Python 3.10 compatibility shims (typing.Self, datetime.UTC, enum.StrEnum) since the SDK targets 3.11+; the full suite is expected to run on CI with the supported toolchain.
• Marking the OTel distribution Production/Stable while its payload fields (result/error) remain flagged EXPERIMENTAL is an intentional product/classifier decision, not a code defect.

Reviewed commit 7ac7acc6a7dae231f2abbb8e37f9780cc9b89af0. Workflow run