Files
hyprland-headless-stream-pl…/docs/TODO/README.md
T
HermenixandClaude Opus 5 6b395305e0 scroll: one verb, two axes, and the sign carries the direction
A session could move a cursor and press it, but not scroll. The protocol
already had the request -- zwlr_virtual_pointer_v1.axis(time, axis, value) --
it had simply never been implemented, in the driver or the broker.

  hhstream session pointer scroll <id> --axis vertical --amount 3

Positive is down (vertical) or right (horizontal): the protocol's direction,
not a choice of ours, which is why direction travels in the sign and there is
deliberately no up/down vocabulary layered over it. The output is whatever the
last warp aimed at, exactly like a button, so scrolling somewhere else is a
warp first -- and the lease is what keeps the whole gesture atomic. Bounded at
100 wheel clicks per request on both sides, because a decimal-point slip should
be a refusal rather than a session scrolled somewhere unrecoverable.

The resume point is re-stamped, not moved: the cursor did not go anywhere, so
the coordinates are re-affirmed and only the stamp advances. Recorded in the
contract as an amendment to the frozen op set, because adding an op to a frozen
interface should be visible rather than implied.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-10-03 19:05:39 +00:00

25 lines
1.3 KiB
Markdown

# 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](containers-do-not-bind.md) | high | containers built, tested, **switched off** in production |
| [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 |
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.