docs(contact): Cross-reference report reason keyword lists

The accepted --reason keywords live in both ReportReasons (action, validation)
and reportReason (telegram, mapping); the layers can't share a source. Add
sync notes so adding a reason to one without the other doesn't silently report
as spam.

Author: cuiko

internal/action/contact/report.go

@@ -9,8 +9,10 @@ import (
 	"github.com/vika2603/telegram-cli/internal/ui"
 )
 
-// ReportReasons are the keywords accepted by `tg contact report --reason`,
-// mapped (in the telegram layer) to a tg.ReportReasonClass.
+// ReportReasons are the keywords accepted by `tg contact report --reason`.
+// Keep this set in sync with reportReason() in internal/telegram/contacts.go,
+// which maps each keyword to a tg.ReportReasonClass — a keyword present here but
+// missing there would silently report as spam.
 var ReportReasons = map[string]bool{
 	"spam":             true,
 	"violence":         true,

internal/telegram/contacts.go

@@ -138,7 +138,10 @@ func ReportPeer(ctx context.Context, api *tg.Client, resolver *peer.Resolver, q
 	return nil
 }
 
-// reportReason maps a validated reason keyword to a tg.ReportReasonClass.
+// reportReason maps a validated reason keyword to a tg.ReportReasonClass. Keep
+// the cases in sync with ReportReasons in internal/action/contact/report.go;
+// the action layer validates the keyword before it reaches here, so the default
+// is only a safety net.
 func reportReason(reason string) tg.ReportReasonClass {
 	switch reason {
 	case "violence":