Skip to content

Audit conformance experiments for complete first-party SDK coverage #122

Description

@rmcdaniel

Request

The owner requested an audit of the existing experiments so portable behavior is not tested in just PHP, Python, or Rust by accident. Scheduled after the current Cloud pricing/contact rollout.

Acceptance

  • Inventory current experiment definitions and map them to the public conformance runbook.
  • Replace unjustified language-only instructions with explicit PHP/Python/Rust coverage and every meaningful supported workflow/activity direction, including cross-language child and Nexus behavior where applicable.
  • Identify genuinely language-specific or embedded-only cases explicitly; do not invent meaningless Cartesian combinations.
  • Cover authoring, inputs/results, retries, timeouts, heartbeats, cancellation, signals/queries/updates, replay/restarts, upgrades, and failure recovery as applicable to each experiment.
  • Keep executable instructions, prerequisites, expected outcomes, and cleanup clear for a new human or agent using only public repositories.
  • Keep Cloud account data, infrastructure, provisioning and chaos procedures in the private Cloud repository; link the private follow-up there without exposing its details here.
  • Run focused representative checks for changed instructions and report outcomes on GitHub. Do not commit generated per-run evidence or rebuild a conformance pipeline.

GitHub remains the source of truth. Reuse ordinary repository commands and GitHub Actions for public happy paths; maintainers handle exceptions directly.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions