docs: clarify --max-iterations is optional and defaults to unlimited

[JonyanDunh]

Make the existing "default = unlimited" behavior explicit in every user-facing surface, and stop showing --max-iterations 0 as the way to express "no cap". The natural way is now to just omit the flag.

No production code or behavior changes. Pure documentation cleanup. No version bump (following the convention of #7 and #15).

Why

The current behavior (verified in scripts/setup-watchdog.js:22 and hooks/stop-hook.js:154) is already that not passing --max-iterations means an unlimited loop — maxIterations defaults to 0 in the parser, and the hook's hard-stop check is if (state.max_iterations > 0 && ...), so a value of 0 never triggers the cap.

But the docs were misleading users into thinking --max-iterations 0 was something they had to write to opt into "unlimited", when actually omitting the flag is exactly equivalent. Worse, the --no-classifier section's example showed --no-classifier --max-iterations 0 as the canonical "unbounded ralph-loop-style run" syntax, which made the 0 look mandatory for that use case.

What changed

commands/help.md (the in-Claude-Code reference users see via /watchdog:help)

• The --no-classifier example dropped from --no-classifier --max-iterations 0 to plain --no-classifier
• The --max-iterations option description now leads with "optional safety cap" and explicitly states "If you don't pass it, the loop is unlimited"
• The --no-classifier option description's "Pair with --max-iterations 0" advice changed to "Just omit --max-iterations"
• The "Best Practices" item renamed from "Always set --max-iterations" to "Set --max-iterations for most tasks", with an explicit note that omitting the flag is the correct way to express "unlimited"

scripts/setup-watchdog.js (printHelp())

• The no-classifier quick-usage example dropped its --max-iterations 20 and gained an inline comment # no --max-iterations = unlimited
• A new three-line trailer at the bottom of the help output explicitly explains that --max-iterations is optional and --max-iterations 0 is no longer needed

All 7 READMEs (README.{md,zh,es,ja,ko,vi,pt}.md)

• The --no-classifier subsection's example dropped --max-iterations 0
• The surrounding paragraph reworded to lead with "--max-iterations is optional" and explicitly tell the user they no longer need to pass --max-iterations 0
• The "Best Practices" section fix(commands): /watchdog:stop was pointing at a non-existent script #4 renamed from "Always set --max-iterations" to "Set --max-iterations for most tasks", with a new paragraph explicitly endorsing flag omission for unlimited loops

Backward compatibility

The CLI still accepts --max-iterations 0 exactly as before — it is parsed, stored as max_iterations: 0 in the state file, and the hook treats it as "no cap" because the > 0 check fails. Existing watchdogs that pass 0 keep working unchanged. This PR only changes the recommended and documented way to express "unlimited"; the supported ways now include both "omit the flag" and "pass 0", with the former being the new natural form.

No state file schema changes. No new fields. No new flags. No version bump.

Scope

• commands/help.md — 4 spots
• scripts/setup-watchdog.js — printHelp() block only
• README.md + 6 translations — 2 spots each (no-classifier subsection + Best Practices fix(commands): /watchdog:stop was pointing at a non-existent script #4)

Zero changes to lib/, hooks/, test/, or .claude-plugin/. No state file schema changes. No new tests required (no behavior change).

Test plan

• 132-test suite still passes locally (132 active + 2 skipped, 0 failures)
• node --test test/*.test.js clean — no test additions or modifications
• Confirmed no stale --max-iterations 0 user-facing examples remain (the only matches are in the new explanatory text and the existing backward-compat test)
• CI will confirm on the standard matrix (jsonlint + markdownlint will catch any markdown issues in the new README content)

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com