A Mac listing is not a native Mac Demo.

First identify which product you are looking at

Check the exact app name before treating a missing install option as a broken Steam client. The Demo access guide links the separate child listing.

Apple Silicon and Intel have different evidence

The parent currently publishes macOS 12.0 Monterey, Apple M1, 8 GB RAM, Apple M1 integrated graphics with Metal support and 5 GB available storage, and explicitly requires an Apple processor.

In the September 29 Mac update, the developer said the technical port ran on Apple Silicon and still needed signing/notarization before publishing. On October 2, they said they did not have an Intel Mac to test and could not confirm how it worked there.

For an Intel Mac, keep that untested boundary. Do not read an old intention to make something available as a current Intel-support guarantee, and do not replace the current Apple-processor requirement with an assumed Intel equivalent.

CrossOver can render the game while menu input fails

An October 2 player report described a specific Windows-Demo-through-CrossOver problem: the game rendered, and dragging the hanging lantern worked, but Play, Settings and Exit did not respond to pointer or keyboard input.

The October 3 developer reply said native macOS had been tested, but CrossOver/Wine had not. They also noted a recently introduced input system for controller/Steam Deck work as a possible factor to investigate. That is a developer hypothesis, not a confirmed Wine repair.

• Separate visible rendering from functioning menus and gameplay controls.
• Record your Mac chip, macOS version, Demo build and CrossOver/Wine version.
• Describe which interaction works and which fails; the lantern-versus-menu distinction is useful evidence.
• Check the latest replies in the Mac Support thread before repeating an older setup.

No universal runtime flag, menu shortcut or reinstall fix is established by these reports.

Choose the next step without mixing platforms

If you want the native Mac release, verify the current parent listing and actual native download availability when it launches. If you are evaluating the Windows Demo on a Mac, treat the compatibility layer as part of the test and preserve your existing configuration.

The historical top-left cursor bug is a different reported symptom from an otherwise stable pointer that cannot click Wine menus. A controller being detected also does not prove a complete, working handheld layout.

A clear platform decision

You can identify native parent support, the Windows-only Demo and a Wine-based experiment separately. An unresolved report includes the actual app, chip, OS, runtime and input symptom.