why are session hijacking each other across repo to do completely unrelated w...

why are session hijacking each other across repo to do completely unrelated work. this totally ruins the context of the hijack session as it does totally unrelated work for another session. the session model doesn't make any sense and is totally broken, and there are not settings to control any off it. i only ever want child sessions that inherit from their parent, nothing else

---
| Field | Value |
| --- | --- |
| App version | 1.1.3 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 7 (Week 1) |

Reproduce the session crossover in the /chat path using app version 1.1.3 on Windows 10. Confirm that unrelated sessions share or inherit work unexpectedly, then define completion as ensuring only explicitly parent-child sessions share context and unrelated sessions remain isolated.

Vom Indexierungsmodell aus dem Issue-Text verfasst.