0.69.11

Agent task routing

Fixed: __PASS__:<recipient> was mis-parsed when the message held an
earlier colon or a space after the colon (#1265, thanks
@Wizhill05; reported in #1263 by @JoeyTan21).

Task._parse_routing extracted the recipient with
content.split(":")[1], which takes the text after the first colon
anywhere in the message rather than the one belonging to __PASS__.
Two real failures followed:

• a message like "Note: __PASS__:Alice" routed to " __PASS__"
  instead of Alice;
• a space after the colon ("__PASS__: Alice") kept the leading
  whitespace, so the task hung looking for a sub-task named " Alice".

Recipient extraction now splits on __PASS__: itself, stops at any
following colon, and strips surrounding whitespace. If your agents emit
__PASS__: inside a sentence, or with a space before the recipient
name, routing now resolves the name you meant. Covered by new cases in
tests/main/test_msg_routing.py.

Contributing

• The contribution guide now asks for a real application rather than a
  general use case, so proposals arrive with a concrete problem
  attached (#1272).

Full changelog:
0.69.10...0.69.11