docs(tasks): describe max 0.60.0 task rules, watch-tasks, assignees and tasks scan

[leemour]

Task

Make the shared Tasks pages (EN/RU/ES tasks and tasks-architecture) say what max 0.60.0 really does with tasks. max 0.60.0 is tag v0.60.0, commit c41c9ea0, on @wirecat/cli-core 0.326.0 and cli-base 0.43.5. It differs from 3e7a09e3, where the claims below were checked, only by max#720 (cli-base bump, lockfile, one test line). This PR also moves the max pin to v0.60.0.

Why

The pages still describe max as it was at the pinned v0.58.0 (cli-core 0.315.0). max 0.59.0 (cli-core 0.321.0) and 0.60.0 mount the same cli-core tasks command and task rules as tg. Because of that, the "only tg" lines and the "tasks apply in max" lines are wrong.

What

Each claim was checked against max at 3e7a09e3 and cli-core v0.326.0:

Page claim	Verdict	Evidence
In max, every unanswered question opens a task in any chat	wrong, removed	cli-core src/services/task-rules.ts:40-46 (RULES_IN), max src/domain/map.ts:344-355 (DIALOG→dialog, CHAT→group, CHANNEL→channel, anything else→unknown)
watch-tasks is tg only	wrong	max docs/commands.md tags add --chat; cli-core task-rules.ts:49,52-60 reads the tag; max CHANGELOG.md:60-62 (0.59.0)
max still calls it tasks apply / tasks_apply	wrong	max docs/commands.md:2543, CHANGELOG.md:72; cli-core src/mcp/tools/tasks.ts:379
max has the same commands except --assignee	wrong	max docs/commands.md:2364,2387
Only tg opens group tasks just for what is asked of you	wrong	the RULES_IN evidence above
Only tg reads the category list from the shared file	wrong	cli-core src/store/sqlite/open-store.ts:63 always sets sharedConfig; src/store/sqlite/tasks.ts:132; max opens its store through cli-core openStore
Two tasks from one message compared by their own words only in tg	wrong	shared store code in cli-core; no provider check
held skips a channel, and the scan opens nothing in a channel, only in tg	wrong	cli-core task-rules.ts:229-235 (applyTaskRulesToStored)

New caveat: in max, serve opens only the tasks of auto-reply rules. Question and mention tasks open on the next sync or review. Evidence: in max at 3e7a09e3, src/ never calls applyTaskRulesOnArrival or applyTaskRules. src/server/replies.ts:86-91 calls only openRequestTask. The cli-core serve-command.ts:260 that runs the rule pass is not mounted. max's own guide agrees: docs/groups.md:227 says "max personal serve в MAX задачи пока не открывает". This was found by reading the code; it was not run.

Not claimed: that max opens nothing in Saved Messages. MAX's chat mapping has no saved kind, so the pages now say "Saved Messages in Telegram". memo lines are unchanged and were not checked.

The watch-tasks "any member's reply closes a question" line now applies to max too. It needs 0.60.0 (cli-core 0.325.0, max CHANGELOG.md:36).

Pin move to v0.60.0

• tools.json: max docsRef v0.58.0 → v0.60.0; pnpm sync, pnpm docs:contracts.
• translations/max/*: the native diff v0.58.0..v0.60.0 changed more pages than commands and changelog, so all of them were updated and read in full before their fingerprints were accepted:
  • commands (EN/ES/RU): tasks scan, --assignee on tasks add / tasks plan, profile introduction without defaultProfile, contacts link … me, --transcribe, --permission only tightens.
  • bot, profiles, sessions, usage, configuration, configuration-reference (EN/ES): default_profile is gone; a profile comes from the first word or MAX_PROFILE.
  • mcp, permissions, remote (EN/ES): --permission only tightens; startup commands no longer pass messages.send=allow; an agent never deletes for everyone.
  • changelog (EN/ES): 0.59.0 and 0.60.0. cli-contract, bot, usage, changelog: versioned links → v0.60.0.
• permissions and browser-apps (EN/RU/ES): docs: tg 0.71.0 #304 said "max still accepts a looser level". max 0.59.0 made --permission only tighten, so the pages now say the flag only tightens in both tools.
• lib/command-rules.ts (EN/RU/ES): the "How commands work" block for tg and max no longer names a defaultProfile setting.
• scripts/docs-corrections.json: retired the max/commands defaultProfile correction (the native text no longer has it); localised the <профиль> placeholder in the max changelog, like the existing placeholder correction.
• docs/release-notes-review.json: max → v0.60.0; review record docs/reviews/2026-10-18-max-060-release.md.

Testing

• Local, after pnpm sync and pnpm docs:contracts: pnpm lint, pnpm search:check, pnpm docs:release-notes, pnpm typecheck, pnpm docs:check (strict docs quality: 0 reference gaps, 0 invalid examples) passed; pnpm test: 309 passed.
• pnpm docs:translation corrections over every max page: 0 broken.
• Full validation: run 39080431451.

🤖 Generated with Claude Code

[leemour]

Full validation (run 39071464017) passed: check, search-playground, and windows_install for tg and max on Node 22.16.0 and 24. The max pin is still v0.58.0. Move it to v0.60.0 after the release, before this PR merges.

[leemour]

Full validation on ef04ed0: run 39080431451 — success (check, search-playground, Windows install for tg and max).