Item 1 said the broker reads none of the container or pointer configuration. That was true and is not: the settings are parsed beside Policy and a switched-off container host reports itself unavailable with the key named. The item now records what actually matters about it -- that containers are off on the deployment machine because no window can be put in one -- and the section links docs/TODO/, where each open problem has its impact written down. The TODO folder itself landed in the previous commit by accident (a `git add -A docs` swept it in with the scroll work); this commit only makes it findable.
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 |
| 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.