docs: clarify Telegram goal scoping

[Logical-Leap]

Summary

Telegram supports multiple active /goal loops in parallel when they are in separate topics/sessions. The one-goal limit is per session, not global.

This documentation update now explicitly:

• shows that Topic A can run /goal Work on Repo A while Topic B simultaneously runs /goal Work on Repo B
• distinguishes parallel topic sessions from replacing a goal inside the same topic
• clarifies that /goal not automatically spawning a delegated child does not prevent multiple topic goal loops from running concurrently
• documents max_concurrent_sessions (null or 0 = unlimited)
• warns that session isolation is not filesystem isolation; separate repos are safe, while the same repo should use worktrees or serialized writes
• notes that the built-in command is singular: /goal

Verification

• cd website && npm run build
• Docusaurus production build completed successfully for en and zh-Hans

[GottZ]

This was generated by AI during triage.

Summary

Three PRs reference this issue. #29318 adds a deterministic pre-judge stop path for explicit DONE/BLOCKED sentinels, while #32536 changes turn-budget inference and #65707 documents Telegram session scoping without changing completion detection.

Related pull requests

• fix(goal): stop the /goal loop when the agent says it is done (#29090) #29318 best fix — (+402/-8) — n/a; recorded best fix: Adds final-line DONE/BLOCKED sentinel detection that stops the goal before the auxiliary judge, directly addressing repeated continuation after the agent reports completion or blockage. The automated keep_open review identifies a concrete salvage path: rebase onto the four-value judge interface and extend the sentinel instruction and tests to the current completion-contract prompt.
• feat: infer goal turn budgets up to 250 #32536 related — (+159/-17) — n/a: Infers per-goal budgets up to 250 turns but does not alter completion detection or add a stop path, so it does not fix the reported judge-driven continuation. Its automated keep_open review concerns the separate adaptive-budget feature and requests policy confirmation, canonical configuration documentation, and broader configured-cap coverage.
• docs: clarify Telegram goal scoping #65707 related — (+38/-0) — n/a: Documents per-session Telegram goal scoping, concurrent topic loops, and filesystem-isolation precautions; its documentation-only diff does not change goal evaluation or termination behavior.

Suggested consolidation

Author action on #29318: rebase onto main, update mocks for the four-value judge result, and extend the sentinel contract and tests to completion-contract prompts; this preserves the recorded best fix and follows its automated keep_open review rather than recommending merge prematurely. Keep #32536 and #65707 separate for independent triage because their adaptive-budget and Telegram-documentation changes are not duplicates of #29318.

Cross-PR triage: Reviewed 3 pull requests and 1 issue in this complex. Each diff was read against this issue; Assessment working set: 45 kB of PR diffs, 11 kB of issue/PR text, <1 kB of discussion (1 comments), 2 verify verdicts. verdicts reflect diff content, not PR titles. Part of an automated triage batch.