Skip to content

Launchplane batch: #4684 - #4693

Merged
shiny-code-app[bot] merged 3 commits into
mainfrom
launchplane/train/cbusillo/launchplane/main/merge-train-batch-cbusillo-launchplane-main-c35e7425981c7000
Oct 24, 2026
Merged

shiny-code-app[bot] merged 3 commits into
mainfrom
launchplane/train/cbusillo/launchplane/main/merge-train-batch-cbusillo-launchplane-main-c35e7425981c7000

Conversation

@shiny-code-app

Copy link
Copy Markdown
Contributor

This PR lands Launchplane's tested candidate 652a6bf035409f10579828c9a83340dddc386a9d through the protected merge endpoint. Constituent PRs and reviewed heads:

Launchplane revalidates every constituent and records the shared landing effect. Keep source PRs and branches intact. Let the Launchplane controller merge this PR; do not merge it by hand or update its generated branch. An out-of-controller merge without a preceding admission remains fenced for explicit reconciliation. The controller confirms constituent completion after landing.

Owner test notes

#4684 Keep code-protocol values readable in scrubbed stored-record snapshots

#4684 has no Client test notes.

The installed read-only qualification (run 40097365197) exported format 2
and started the candidate, then rejected a scrubbed product profile:
the scrubber had pseudonymized ProductSecretConfigRequirement.integration,
which validators compare to runtime_environment.

Code-protocol values now survive only in fields that declare them with
the existing x-launchplane-snapshot-protocol marker: secret integration,
the testing/prod lane kinds at every lane-instance reference site, and
the defaults non-runtime profiles compare against. The same word in any
other field is still pseudonymized. Database prefixes and public DNS
names and addresses get format-valid pseudonyms only when the real
validator accepts the source value, so invalid history still fails.
Positional tuple schemas and all-digit hex digests are handled too.

Refs #3413
Review: a valid 40-character hex-looking database prefix could become
a digit-leading digest and fail, depending on the export salt. Format
substitutes now run before the hex rule, which returns to its original
order. Derive the oversized-prefix input from the schema, and state in
the docs which invalid history still fails.

Refs #3413
@shiny-code-app
shiny-code-app Bot merged commit 5cc8351 into main Oct 24, 2026
72 checks passed
@shiny-code-app
shiny-code-app Bot deleted the launchplane/train/cbusillo/launchplane/main/merge-train-batch-cbusillo-launchplane-main-c35e7425981c7000 branch October 24, 2026 15:39
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.

0 participants