reworked known_bugs.

doc/known-bugs.md

@@ -5,32 +5,41 @@ This document tracks currently known issues and limitations.
 
 ## Open issues
 
-- **Prompt execution time is inaccurate in Windows Terminal (WSL)**
-	- **Status:** open, likely not fully fixable with the current Bash prompt model.
-	- **Symptoms:** in Windows Terminal, the displayed duration includes idle time
-		and typing time, and is consistently higher than real command execution time.
-		Behavior differs across terminal environments:
-		- In a native Linux terminal (including Linux shells launched through WSL),
-			timing starts when Enter is pressed and stops when the prompt is shown again.
-		- In Windows Terminal, timing appears to start/stop on prompt display events.
-	- **Technical context:** execution time is measured from a `DEBUG` trap plus
-		`PROMPT_COMMAND`, using `date +%s%N` deltas. In WSL + Windows Terminal,
-		timer precision and scheduling behavior can introduce jitter that does not
-		match wall-clock perception.
-	- **Likely cause:** Windows Terminal does not handle Bash timing-related events
-		in the same way as native Linux terminals.
-	- **Impact:** cosmetic/observability issue only. Commands are executed normally.
-	- **Workarounds:**
-		- Use a native Linux terminal under WSL (for example QTerminal, Terminator,
-			Konsole, etc.) to recover the expected Enter→prompt timing behavior.
-		- Use `/usr/bin/time -p <command>` (or `time <command>`) when accurate timing is needed.
-		- Treat prompt timing as an approximate indicator in this environment.
+- None :-)
 
 ---
 
-## Rain/Matrix rendering is slow on Windows
+## Won't fix
 
-- **Description:** The rain and matrix terminal effects are significantly slower on Windows, especially with high density settings.
-- **Cause:** This is due to the way Windows handles terminal display updates, which is inherently less efficient than on Unix-like systems.
+These issues are caused by platform or environment limitations outside the scope of this
+project and will not be addressed in Bash.
+
+### Prompt execution time is inaccurate in Windows Terminal (WSL)
+
+- **Description:** In Windows Terminal the displayed duration includes idle and typing time,
+  and is consistently higher than actual command execution time. In a native Linux terminal
+  (including WSL shells inside Konsole, QTerminal, etc.) timing correctly starts on Enter and
+  stops when the prompt reappears; in Windows Terminal, timer events appear tied to prompt
+  display rather than to the Enter keypress.
+- **Cause:** Execution time is measured via a `DEBUG` trap and `PROMPT_COMMAND` using
+  `date +%s%N` deltas. WSL + Windows Terminal introduces scheduling jitter between Bash signal
+  events and the underlying Windows terminal layer that does not match wall-clock perception.
+- **Impact:** Cosmetic / observability only — commands execute normally.
+- **Status:** Not fixable in Bash; this is a limitation of the Windows Terminal / WSL
+  integration layer.
+- **Workarounds:**
+  - Use a native Linux terminal under WSL (Konsole, QTerminal, Terminator, etc.) to
+    recover the expected Enter→prompt timing behavior.
+  - Use `/usr/bin/time -p <command>` or the shell built-in `time` when accurate timing
+    is required.
+  - Treat prompt timing as an inacurate indicator in this environment.
+
+### Rain/Matrix rendering is slow on Windows
+
+- **Description:** The rain, matrix and rainbow terminal effects are significantly slower
+  on Windows, especially with high density settings on every terminal software.
+- **Cause:** This is due to the way Windows handles terminal display updates, which is
+  inherently less efficient than on Unix-like systems.
 - **Status:** Not fixable in Bash; this is a limitation of Windows terminal design.
-- **Workaround:** Lower the density parameter for better performance, or use a Unix-like environment for optimal speed.
+- **Workaround:** Lower the density parameter for better performance, or use a Unix-like
+  environment for optimal speed.