Propose a patch

Evidence

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

diff --git a/templates/settings.html b/templates/settings.html
--- a/templates/settings.html
+++ b/templates/settings.html
@@ -25,1 +25,0 @@
-First-run doctor: the same three paths as `taxclaw doctor`
@@ -190,1 +189,0 @@
-<summary>Custom endpoint</summary> <input name="openai_compat_base_url" placeholder="https://… (empty = provider preset)" value="{{ cfg.openai_compat_base_url }
diff --git a/src/ai.py b/src/ai.py
--- a/src/ai.py
+++ b/src/ai.py
@@ -55,1 +55,0 @@
-text = (text or "").strip().lstrip("").strip()

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.1.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: taxclaw: Collapsed <details> block carrying instructions (KillerSkills verdict blocked 49)

## 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 **BLOCKED 49/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/taxclaw/1.1.0

## Findings with a location
- `templates/settings.html:190` · Collapsed <details> block carrying instructions — templates/settings.html:190 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `src/ai.py:55` · Hidden zero-width characters detected — src/ai.py:55 · Hidden zero-width characters detected — may conceal content
- `templates/settings.html:25` · HTML comment carrying imperative instructions to the agent — templates/settings.html:25 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file

## 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._