docs: two TODO items closed, and the cursor question answered

Closed: containers-do-not-bind and pointer-needs-a-container-or-a-screen. Both
were the same defect seen from two sides, and both are fixed by assigning
windows by pid -- two sessions now hold two outputs with a real browser on each,
and the pointer aims at a desk that has something in it.

The cursor item is rewritten with the answer rather than the speculation: the
compositor draws no cursor image for a virtual pointer, so no capture setting
can make one appear. The evidence is in the file, including the three wrong
answers that came before it and the boring measurement that settled it.

New item: killing a session left two browsers alive, found by counting windows
rather than sessions.
This commit is contained in:
Hermenix committed 2026-10-03 19:45:42 +00:00
1 parent acdfb2801e
commit cbf58f6443
5 files changed
+103 -175

No files matched your search

+18 -9
View File
@@ -10,16 +10,25 @@ Each file answers three questions and stops:
| item | severity | state |
| --- | --- | --- |
| [containers-do-not-bind](containers-do-not-bind.md) | high | containers built, tested, **switched off** in production |
| [pointer-needs-a-container-or-a-screen](pointer-needs-a-container-or-a-screen.md) | high | every cursor verb refuses while containers are off — nothing can be moved |
| [scroll-has-no-compositor-proof](scroll-has-no-compositor-proof.md) | medium | implemented; unit-tested; unproven against a real compositor |
| [cursor-visibility-in-captures](cursor-visibility-in-captures.md) | medium | unverified — the acceptance video shows no cursor |
| [reconcile-while-containers-are-off](reconcile-while-containers-are-off.md) | medium | worked around by restarting the compositor |
| [cursor-visibility-in-captures](cursor-visibility-in-captures.md) | high | answered: the compositor draws no cursor for a virtual pointer. Needs a decision on an overlay marker |
| [scroll-has-no-compositor-proof](scroll-has-no-compositor-proof.md) | medium | works live; unproven in a gate |
| [reconcile-while-containers-are-off](reconcile-while-containers-are-off.md) | medium | partly fixed: discovery now survives a restart; teardown still lives inside the feature |
| [kill-can-leave-the-app-alive](kill-can-leave-the-app-alive.md) | medium | found by counting windows, not sessions |
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.
Closed since this folder was written:
- *"Containers do not bind"* — fixed. Windows are assigned by the pid the
compositor reports, moved onto their desk's workspace and read back. Two
sessions now hold two outputs with a real browser on each.
- *"The pointer is unusable while containers are off"* — fixed with it. The
pointer aims at the session's desk, and desks hold applications.
- *"Discovery refuses when two compositor instances exist"* — fixed. Each
candidate is asked for its version and the one that answers is used.
Severity here means "how much of the feature is actually delivered", not "how
loud the failure is". The highest is highest because a whole class of work is
blocked on it: the pointer is exact and invisible, so nothing can show *where*
anything happened.
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.