[huangruiteng]

Summary

• route configured_chat_all events across topics in one configured chat while failing closed on ambiguous Goal routes
• reply at chat root for top-level source events and inside the source topic for threaded events
• preserve reply line breaks and project a bullet-points-preferred editorial hint
• expose the new route ambiguity in the desktop connection health view

Compatibility

Existing inbox configs keep source_thread placement. Newly generated Goal Topic inbox configs opt into source_context.

Validation

• python -m pytest -q tests/extensions/test_lark_inbox_reactions.py tests/extensions/test_lark_goal_topic_connections.py tests/extensions/test_lark_goal_topic_runtime.py (55 passed)
• python examples/lark-event-inbox-smoke.py
• npm run build:desktop
• loopx canary premerge --from-git-diff (18/18 checks passed)
• public/private boundary scan: clean

Future-facing pass

Kept routing authority in the existing typed Lark route decision and reused the extension-owned inbox config; no new capability or speculative abstraction was added.