Files
hyprland-headless-stream-pl…/docs/TODO
Hermenix 336474793f docs: the pointer is unusable while containers are off
Found live while trying to demonstrate the scroll verb that was just deployed:
every cursor verb resolves its target through _pointer_output, which requires a
container output, and no session has one -- because containers are off. So the
verb exists and cannot be used, and the acceptance video's missing cursor was
never a capture artefact: nothing could have moved it.

Recorded with the routes out (aim at the shared output when a session owns no
container; or fix the binding first and leave this alone), the cost of the
quick one, and the misleading hint that blames the compositor for a switched-off
feature.
2026-10-03 19:19:24 +00:00
..

TODO

Known, unfixed problems — each one real, none of them guessed at.

Each file answers three questions and stops:

  • The issue — what is actually wrong, with the evidence for it.
  • Ideas — more than one, and which one is the recommended route.
  • Why it matters — the impact, not the principle.
item severity state
containers-do-not-bind high containers built, tested, switched off in production
pointer-needs-a-container-or-a-screen high every cursor verb refuses while containers are off — nothing can be moved
scroll-has-no-compositor-proof medium implemented; unit-tested; unproven against a real compositor
cursor-visibility-in-captures medium unverified — the acceptance video shows no cursor
reconcile-while-containers-are-off medium worked around by restarting the compositor

Severity here means "how much of the feature is actually delivered", not "how loud the failure is". The high one is high because a working feature is turned off; the others are medium because they are gaps in proof, where the symptom of a real fault and the symptom of a working thing look identical.

When one of these is fixed, delete its file and the row — this folder is a list of what is still true, not a history of what was thought.