Propose a patch

Evidence

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

diff --git a/src/export/html.js b/src/export/html.js
--- a/src/export/html.js
+++ b/src/export/html.js
@@ -19,1 +19,0 @@
-…st NAMED = { amp: '&', lt: '<', gt: '>', quot: '"', apos: "'", nbsp: ' ', shy: '­', ndash: '–', mdash: '—', hellip: '…', euro: '€', copy: '©', reg: '®', middot: …
diff --git a/src/check/probe.js b/src/check/probe.js
--- a/src/check/probe.js
+++ b/src/check/probe.js
@@ -359,1 +359,0 @@
-const words = (hit.textContent.match(/[\p{L}\p{N}­-]+/gu) || []).sort((a, b) => b.length - a.length);

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.0. 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: kiekkist: Hidden zero-width characters detected (KillerSkills verdict caution 77)

## 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 77/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/kiekkist/0.2.0

## Findings with a location
- `src/export/html.js:19` · Hidden zero-width characters detected — src/export/html.js:19 · Hidden zero-width characters detected — may conceal content
- `src/check/probe.js:359` · Hidden zero-width characters detected — src/check/probe.js:359 · 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._