fix(quick-dev): drop the activation gate sentence from the rendered workflow

The gate ported from #2398 defended against runtime customization
indirection: agents guessed resolver outputs instead of executing them,
silently skipping append steps. render.py inlines the prepend/append
entries into the rendered workflow.md, so there is nothing left to
short-circuit, and each inlined list already carries its own execute-
in-order imperative. In the default install both lists render as
_None._ and the gate is pure noise.

src/bmm-skills/4-implementation/bmad-quick-dev/workflow.md

@@ -71,8 +71,6 @@ Execute each of these steps in order (`_None._` means skip):
 
 {workflow.activation_steps_append}
 
-Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
-
 ## WORKFLOW ARCHITECTURE
 
 This uses **step-file architecture** for disciplined execution: