devnen 4ef27fcd33 feat(cli): URL truncation warning + --url-encoded flag ... When bash splits a URL at & or ? (a common foot-gun), webclaw receives only the truncated prefix and silently fetches the wrong page. Per issue #6: 1. Heuristic warning: if the URL ends with '&' or contains '?' with no '=' after, emit a stderr warning before fetching: # webclaw: warning: URL looks truncated (ends with '&' or '?'); did the shell split it? Quote the URL or use --url-encoded. 2. New flag --url-encoded: parallel input that asserts the user has handled escaping. Suppresses the truncation warning since intent is explicit. Fetch proceeds in both cases; this is informational only. 4 new tests in webclaw-cli. Workspace 720 -> 724.		2026-05-24 08:18:38 +02:00
..
webclaw-cli	feat(cli): URL truncation warning + --url-encoded flag	2026-05-24 08:18:38 +02:00
webclaw-core	feat(core): word-count breakdown in header — article vs chrome split	2026-05-23 23:56:14 +02:00
webclaw-fetch	feat(fetch): periodic progress stderr line on slow fetches	2026-05-24 00:24:51 +02:00
webclaw-llm	fix: support LLM provider compatibility options	2026-05-06 11:36:53 +02:00
webclaw-mcp	feat(core): word-count breakdown in header — article vs chrome split	2026-05-23 23:56:14 +02:00
webclaw-pdf	Initial release: webclaw v0.1.0 — web content extraction for LLMs	2026-03-23 18:31:11 +01:00
webclaw-server	feat(core): word-count breakdown in header — article vs chrome split	2026-05-23 23:56:14 +02:00