fix(quality-loop): backport GITINTEGRATION actor and mask parent workflow name to release/2-13

[buarki]

What

Cherry-picks 3 commits from main to release/2-13:

• 29ea89d35 — feat(proto): add GITINTEGRATION actor type (feat(proto): add GITINTEGRATION actor type for git-provider-triggered flows #8108)
• df570bb2b — feat(controlplaneclient): sticky-family child actor inheritance (feat(controlplaneclient): let chained children inherit the parent's actor for sticky families #8119)
• d0ca94397 — fix(quality-loop): mask parent workflow name on child running context (fix(quality-loop): mask parent workflow name on child running context #8136)

Why

• No released tag has fix(quality-loop): mask parent workflow name on child running context #8136: release/2-12 diverged before the QL actor type existed, and release/2-13 was cut before feat(proto): add GITINTEGRATION actor type for git-provider-triggered flows #8108.
• Standalone cherry-pick of fix(quality-loop): mask parent workflow name on child running context #8136 fails with modify/delete conflicts, because fix(quality-loop): mask parent workflow name on child running context #8136 touches files introduced by feat(proto): add GITINTEGRATION actor type for git-provider-triggered flows #8108 and feat(controlplaneclient): let chained children inherit the parent's actor for sticky families #8119.
• Bringing the full chain is the only way the fix can compile on this branch.

Validation

• go build ./... passes.
• go test ./pkg/api/v1/testkube/... ./pkg/controlplaneclient/... -count=1 passes.

After merge

Cut the next 2.13.x tag and bump the runner pin to it. Child executions will surface Git Integration on the running context name instead of the internal parent workflow name.

[greptile-apps]

Greptile Summary

This backport adds the git-integration actor contract and carries that actor through the Control Plane, runner, toolkit, and nested scheduling flow so Quality Loop children display a masked parent name. The source schemas, generated artifacts, standalone implementation, and commercial Control Plane consumer are coordinated, and no blocking defect was identified.

Confidence Score: 5/5

The PR appears safe to merge, with the Quality Loop actor and child-context propagation implemented consistently across the relevant runtime and protocol boundaries.

The parent actor is fetched with the execution, transported through the additive protobuf field, serialized into the toolkit configuration, and converted back into the expected git-integration context for nested schedules.

Important Files Changed

Filename	Overview
proto/testkube/testworkflow/execution/v1/get_execution_workflow_response.proto	Adds a backward-compatible response field carrying the parent actor type and name.
pkg/runner/grpc/client.go	Reconstructs the parent running context and includes it in the execution configuration passed to the runtime.
pkg/controlplaneclient/execution_self.go	Uses sticky actor rules to classify nested Quality Loop executions and replace the internal parent workflow name.
pkg/testworkflows/testworkflowexecutor/utils.go	Adds consistent forward and reverse mappings between gitintegration actors and the QUALITYLOOP protocol type.
pkg/controlplane/agent_grpc_runner.go	Projects the standalone parent execution’s actor context into the workflow response.

Sequence Diagram

sequenceDiagram
    participant CP as Control Plane
    participant Runner
    participant Toolkit
    participant Scheduler
    CP->>Runner: GetExecutionWorkflow(running_context)
    Runner->>Toolkit: InternalConfig with parent actor
    Toolkit->>Scheduler: Schedule child as QUALITYLOOP
    Scheduler->>Scheduler: Rebuild gitintegration actor context
    Scheduler-->>CP: Child labeled Git Integration

Loading

_{Reviews (1): Last reviewed commit: "fix(quality-loop): mask parent workflow ..." | Re-trigger Greptile}