Skip to content

Allow VeriReel runtime bindings in testing#1119

Merged
cbusillo merged 1 commit into
mainfrom
verireel-shared-runtime-key-safety
Jun 2, 2026
Merged

Allow VeriReel runtime bindings in testing#1119
cbusillo merged 1 commit into
mainfrom
verireel-shared-runtime-key-safety

Conversation

@cbusillo
Copy link
Copy Markdown
Owner

@cbusillo cbusillo commented Jun 2, 2026

Summary

  • correct VeriReel runtime key-safety rules from prod_only to shared_safe
  • keep the rules restricted to context verireel and instances testing/prod

Why

PR #1118 added the missing VeriReel binding classifications, but the policy model disallows prod_only for testing targets. VeriReel uses the same binding keys for testing and prod, so the active policy needs a class allowed in both runtime classes while still tightly scoped by context and instance.

Failure evidence after #1118 seed import: product-config dry-run for VeriReel testing private values still failed with runtime_key_safety_failed, trace launchplane_req_fc7e3218b0fb456c8fb37cfa9fcf4e81.

Validation

  • npx --yes prettier --check import-material/launchplane/seed-imports/catalog.json
  • uv run python -m unittest tests.test_product_onboarding.ProductOnboardingTests.test_launchplane_seed_import_catalog_validates_contracts tests.test_product_onboarding.ProductOnboardingTests.test_launchplane_seed_import_script_requires_target_id_env tests.test_product_onboarding.ProductOnboardingTests.test_launchplane_seed_import_script_patches_provider_targets

@cbusillo cbusillo merged commit 9dc9860 into main Jun 2, 2026
12 checks passed
@cbusillo cbusillo deleted the verireel-shared-runtime-key-safety branch June 2, 2026 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant