[clins1994]

Adds readme/LINE_CLIENT_SETTINGS.md, a short guide to the LINE app settings that change what a bridged message looks like or does. Read it before you test media, previews or notification features.

---

🇬🇧 More details

Summary

New doc next to readme/LETTER_SEALING.md, linked from the README. It lists the LINE settings that matter (photo quality, auto-download, autoplay for GIFs and videos, previews, notifications), what each one does, and what to test.

Why

A GIF can autoplay on one LINE client and wait for a tap on another with no bridge bug. Without this written down, testers read normal behavior as a bug or miss a real one.

Changes

• readme/LINE_CLIENT_SETTINGS.md: settings by area, sender versus receiver, testing without a second account, and "capture the Chrome extension first" with a link to beeper-line-skills.
• README.md: a link to the new doc after the Letter Sealing link.

How it was tested

Docs only. Every fact comes from a test run on 2026-10-25 with LINE iOS and LINE Chrome Extension 3.7.2 (a network capture plus manual checks on the phone). Android and Desktop are marked "unknown" because nobody has checked them.

Not tested (and why)

• A second account receiving a bridge-sent message. Only one tester was available.
• LINE Android and LINE Desktop settings. Marked "unknown" in the table.

🤖 Generated with Claude Code using clins:create-pr

Confidence Score: 5/5

The documentation changes appear safe to merge.

Summary

Adds a LINE client settings guide and links it from README.md.

All three previous findings are addressed:

• LINE client settings help testers read message behavior across apps.

No new actionable issues were found in the follow-up changes. The previous threads were unnumbered, so they have no entries in previousFindings.

_{Reviews (2) · Last reviewed commit: "docs: address greptile review on LINE cl..." · Reviewed by Greptile}

[clins1994]

@greptileai follow-up review

[clins1994]

Moved upstream: beeper#281