crew: the out-of-credit rescue sends a task to prompt-logging free routes without opt-in

[AbirAbbas]

When a task runs out of credit, codeaf moves the task onto free routes whose providers may log prompts. The free-routes switch is off by default, and nothing asks the person first. They see free routes in use (may log prompts) on the crew line only afterwards.

This happens:

• At task start, when the OpenRouter balance is known to be low (≤ $0.50). This is chat: know the OpenRouter balance, start a near-zero account on free models, keep the whole 402 sentence #1440.
• When a past 402 is remembered, or a provider's credit is known to be zero.
• Mid-task after a 402 (crew: route the worker, planner and checker per task (Pareto crew) #1436). Up to three free pools receive the running task's whole context.

OpenRouter's own account privacy setting still blocks those pools server-side, if the person has set it. Since #1518, the manual (models-and-cost.md) states this rescue truthfully.

Ruling needed

Should the rescue onto prompt-logging routes stay automatic, or require the free-routes switch or a one-time consent? If consent is required, what should happen instead on a 402: stop with add credit on openrouter to continue?

Where

The fallback ladder's free-pool rung in internal/crewroute, and the low-balance start from #1440 (search may log prompts).