Stage durable Pulumi-side repro artifacts for provider issues after the routing question has already narrowed to a Pulumi repro, or when the user explicitly asks for that help. Use when Codex needs to create maintainer-quality examples or tests in a provider repo, preserve the exact lifecycle path that matters, prefer repo-native repros over ad hoc temp directories, and report what can or cannot be executed without credentials.
Stage the smallest durable Pulumi-side repro that honestly captures the issue.
Prefer repo-native examples and tests over temporary scratch work. Use ad hoc local directories only as a fallback or quick probe, not as the main artifact.
Stay in the repro lane. Do not restart ownership analysis here unless the repro
result directly contradicts the current working theory.
Prefer triage-provider-issue first unless a prior pass already established
that a Pulumi repro is the next best action or the user explicitly invoked this
skill.
Read references/repro-shape.md before editing.
--refresh --run-program is part of the question, stage that path
explicitly rather than mentioning it abstractly.Leave behind: