Investigation Summary
- The unfiltered E2E run at
eb560abae63f89183406b3cc273ecb8bf12ccfd2 reached the managed startup profile validator.
- Five messaging jobs rejected valid hydrated plan fields before sandbox startup.
- Boolean
messaging.plan.buildSteps[*].value.pin fields are package-install metadata, not credentials.
- Canonical
UPPER_ENV_KEY=<credential-placeholder> values in messaging.plan.agentRender[*].lines[*] contain placeholders, not credential material.
- No existing issue matches these failure signatures.
Description
Stock managed onboarding carries the hydrated messaging plan in the managed startup profile. The generic credential-shape scanner rejects schema-owned fields that contain only a boolean package pin or a canonical OpenShell credential placeholder.
Expected behavior: the validator accepts these exact schema forms and continues to reject raw credentials or placeholder-shaped data at any other path.
Actual behavior: onboarding fails with Invalid managed startup profile before the sandbox starts.
Reproduction Steps
- Dispatch the E2E workflow at
eb560abae63f89183406b3cc273ecb8bf12ccfd2 with empty jobs and targets.
- Run the managed messaging targets.
- Observe one of these failures:
messaging.plan.buildSteps[*].value.pin has a credential-shaped field name
messaging.plan.agentRender[*].lines[*] contains credential-shaped string data
Environment
- Workflow: unfiltered E2E run 32068537791
- Runner: GitHub-hosted Ubuntu
- Runtime: OpenShell Docker driver with the published managed-image cohort
- Candidate commit:
eb560abae63f89183406b3cc273ecb8bf12ccfd2
Failure Evidence
Acceptance Criteria
- The validator accepts a boolean only at
messaging.plan.buildSteps[*].value.pin.
- The validator accepts a single canonical environment assignment only at
messaging.plan.agentRender[*].lines[*] when the right-hand side is an approved credential placeholder.
- Raw credential values, malformed assignments, and the same values at other paths still fail closed.
- All five affected targets pass in the complete unfiltered E2E run.
Relationship
Prerequisite for #9140. Related epic: #7744.
Investigation Summary
eb560abae63f89183406b3cc273ecb8bf12ccfd2reached the managed startup profile validator.messaging.plan.buildSteps[*].value.pinfields are package-install metadata, not credentials.UPPER_ENV_KEY=<credential-placeholder>values inmessaging.plan.agentRender[*].lines[*]contain placeholders, not credential material.Description
Stock managed onboarding carries the hydrated messaging plan in the managed startup profile. The generic credential-shape scanner rejects schema-owned fields that contain only a boolean package pin or a canonical OpenShell credential placeholder.
Expected behavior: the validator accepts these exact schema forms and continues to reject raw credentials or placeholder-shaped data at any other path.
Actual behavior: onboarding fails with
Invalid managed startup profilebefore the sandbox starts.Reproduction Steps
eb560abae63f89183406b3cc273ecb8bf12ccfd2with emptyjobsandtargets.messaging.plan.buildSteps[*].value.pin has a credential-shaped field namemessaging.plan.agentRender[*].lines[*] contains credential-shaped string dataEnvironment
eb560abae63f89183406b3cc273ecb8bf12ccfd2Failure Evidence
buildSteps[5].value.pinagentRender[0].lines[1]buildSteps[7].value.pinbuildSteps[0].value.pinbuildSteps[1].value.pinAcceptance Criteria
messaging.plan.buildSteps[*].value.pin.messaging.plan.agentRender[*].lines[*]when the right-hand side is an approved credential placeholder.Relationship
Prerequisite for #9140. Related epic: #7744.