docs: allow supervised code queue burst to ten

docs/reference/code-queue-supervision.md

@@ -33,7 +33,7 @@ Every Code Queue task must have a narrow ownership boundary.
 - State the write scope, validation scope, commit/push requirement, and forbidden actions directly in the prompt.
 - Include the relevant background in the prompt itself; issue links are supporting references, not required context.
 - Prefer existing queues and create new queues only when the existing lanes cannot express the ownership boundary.
-- Keep queue concurrency bounded by real execution capacity. A target around five concurrent lanes is useful only when the active tasks have distinct write scopes and the execution plane is healthy.
+- Keep queue concurrency bounded by real execution capacity. A target around five concurrent lanes is the normal operating point; the supervisor may expand up to about ten concurrent lanes when the active tasks have distinct write scopes, heartbeat/trace evidence is healthy, and the extra tasks remove real secondary friction rather than merely filling slots.
 
 Prompts for production-adjacent work must explicitly forbid heavy local checks on the master server when those checks are known to risk OOM, and must tell the worker which validation belongs in D601 CI, dev env, or a target service container.