fix(pegboard): refresh runner config after envoy connect

Author: NathanFlurry

engine/packages/pegboard-envoy/src/conn.rs

@@ -279,6 +279,12 @@ pub async fn init_conn(
 		.custom_instrument(tracing::info_span!("envoy_init_tx")),
 	)?;
 
+	// Serverful pools update protocol version directly from the envoy
+	// connection path. Purge the runner-config caches so the first actor
+	// request after connect does not keep seeing a stale pre-mk2 config.
+	pegboard::utils::purge_runner_config_caches(ctx.cache(), namespace.namespace_id, &pool_name)
+		.await?;
+
 	// Send missed commands (must be after init packet)
 	if !missed_commands.is_empty() {
 		let msg = {

engine/packages/pegboard/src/ops/actor/create.rs

@@ -47,7 +47,11 @@ pub async fn pegboard_actor_create(ctx: &OperationCtx, input: &Input) -> Result<
 		ctx.subscribe::<crate::workflows::actor2::DestroyStarted>(("actor_id", input.actor_id)),
 		ctx.op(crate::ops::runner_config::get::Input {
 			runners: vec![(input.namespace_id, input.runner_name_selector.clone())],
-			bypass_cache: false,
+			// Protocol version decides whether we dispatch the mk1 or mk2 actor
+			// workflow. A freshly connected envoy can update this immediately
+			// before the first actor request, so this read must not use a stale
+			// cached runner config.
+			bypass_cache: true,
 		}),
 	)?;