Propose a patch

Evidence

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

diff --git a/cli/lib/csv.ts b/cli/lib/csv.ts
--- a/cli/lib/csv.ts
+++ b/cli/lib/csv.ts
@@ -13,1 +13,0 @@
-const s = text.replace(/^/, '');
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -53,1 +53,0 @@
-storebound desktop, Releases › Send for review: the dry run of the submission with the build picked by number and the confirm step
@@ -55,1 +54,0 @@
-<summary>More screens: portfolio, growth charts, prices, checks, TestFlight, console plan</summary> ![Portfolio: every app of every studio with its state on bot

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/storebound/0.8.77

## Findings with a location
- `cli/lib/csv.ts:13` · Hidden zero-width characters detected — cli/lib/csv.ts:13 · Hidden zero-width characters detected — may conceal content
- `README.md:53` · Image alt text carrying instructions — README.md:53 · Image alt text carrying instructions
- `README.md:55` · Collapsed <details> block carrying instructions — README.md:55 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 3 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._