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
@@ -217,1 +217,0 @@
-<summary><b><code>get_judgment</code></b></summary> 取得單筆判決的結構化全文。 - 輸入：`jid`（從 `search_judgments` 結果取得）或 `url` - 輸出：`{case_id, court, date, main_text, facts, re
diff --git a/mcp_server/tests/test_coverage_tier1.py b/mcp_server/tests/test_coverage_tier1.py
--- a/mcp_server/tests/test_coverage_tier1.py
+++ b/mcp_server/tests/test_coverage_tier1.py
@@ -56,1 +56,0 @@
-z.writestr("EnLaw.json", "" + json.dumps({"Laws": laws}))

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.8.3. 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: mcp-taiwan-legal-db: Collapsed <details> block carrying instructions (KillerSkills verdict caution 79)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 79/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mcp-taiwan-legal-db/1.8.3

## Findings with a location
- `README.md:217` · Collapsed <details> block carrying instructions — README.md:217 · Collapsed <details> block carrying instructions
- `mcp_server/tests/test_coverage_tier1.py:56` · Hidden zero-width characters detected — mcp_server/tests/test_coverage_tier1.py:56 · 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._