Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -96,1 +96,0 @@
-<summary><b>One run, step by step</b></summary> ``` every day at DIGEST_TIME /digest, /digest 48 │ │ ▼ ▼ for each channel: new posts since the last delivered di
diff --git a/summarix_telegram/utils/text.py b/summarix_telegram/utils/text.py
--- a/summarix_telegram/utils/text.py
+++ b/summarix_telegram/utils/text.py
@@ -53,1 +53,0 @@
-return re.sub(r"\n[ \t​]*(?:\n[ \t​]*)+", "\n\n", linked).strip()  # at most one blank line

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.1. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: summarix-telegram: Collapsed <details> block carrying instructions (KillerSkills verdict caution 50)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 50/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/summarix-telegram/1.2.1

## Findings with a location
- `README.md:96` · Collapsed <details> block carrying instructions — README.md:96 · Collapsed <details> block carrying instructions
- `summarix_telegram/utils/text.py:53` · Hidden zero-width characters detected — summarix_telegram/utils/text.py:53 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 2 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._