Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix: address review feedback on documents-only check

Gate the intake guard on a new TelegramListener.AdmitDocuments field, wired
from settings.Meta.DocumentsOnly, so a text-less document reaches the detector
only when the check is enabled. It was admitted unconditionally before, which
stored it in the locator and inflated the per-user count --max-short-msg-count
bans on for operators who never turned the check on.

Measure req.AuthoredText() in DocumentsCheck instead of req.Msg. OnMessage
appends quoted and reply-to text to Msg, so replying to a long enough message
let a caption-less file clear the length gate on text its sender never wrote.

Rename the flag to --meta.document-only / META_DOCUMENT_ONLY and the web field
to metaDocumentOnly, matching the singular public names of the sibling media
checks; the Go field and the json/yaml/db tags stay plural, as VideosOnly does
behind --meta.video-only.

Spell out in the README what enabling the check costs: the locator and
--max-short-msg-count, plus the checks that need no message text and run before
the min-length gate — stop-words matched against username and user ID,
username-symbols, lua plugins and CAS. Note that a forwarded file or one
attached to a cross-chat reply is admitted regardless of the setting.

Claude-Session: https://claude.ai/code/session_019KjU5nM8wSMb3L9gELGnZu