[ROSETTA] Fail parse command when polling times out

[isolomatov-gd]

In src/rosetta-cli/rosetta_cli/services/document_service.py, timed-out pending documents are reported but not included in the returned failure count. ParseCommand can therefore exit successfully while documents remain unparsed; return an unsuccessful result or typed timeout and cover complete and mixed pending cases.

[github-actions]

Rosetta Triage

Classification: bug — parsing can time out while the command reports success.
Priority assessment: Medium — the CLI can state a successful result although some requested documents remain unparsed.

Findings:

• The polling loop reports pending documents at timeout but does not include them in its returned failure count.
• ParseCommand uses that failure count as its exit-status decision, so a timeout can return exit code 0.
• Existing parse-command tests cover document-status selection; they do not cover all-pending or mixed completion-and-timeout outcomes.

Suggestions:

• Make timeout a terminal unsuccessful outcome, either by counting all pending documents as failed or by returning a typed timeout result that ParseCommand maps to a nonzero exit code.
• Add focused tests for all-pending and mixed completed/pending timeout cases, including the command exit status.

Next steps: Implement the focused polling-result change and its tests. Related issue #349 concerns timeout configuration documentation and is not a duplicate.

Automated triage by Rosetta agent