Draw the crosshair cursor natively so it moves at mouse speed

[laveshparyani]

The client reported the cursor feeling slow ("cursor ka speed slow ho rha… mouse dpi normal krdena"). It was, by design:

• the real pointer was hidden everywhere with cursor: none !important
• a page element then eased after the mouse over 0.32 s (gsap.quickTo, "trails by a beat")

Removing the easing alone isn't enough. A cursor the page draws always runs a frame or two behind the one the operating system draws, because it can only move when the page renders.

Fix

The same crosshair and the same hover reticle are now CSS cursor images — 32×32 SVG data URIs, hotspot at the centre, each ending in a keyword fallback (crosshair / pointer). The OS draws them, so they move at mouse speed, with no JavaScript and no per-frame work. Applied only on fine pointers ((pointer: fine) and (hover: hover)).

It can no longer invert against what's underneath like the old mix-blend-mode: difference element, so it's dark ink with a 1 px light halo. Checked on the measured page ground (#e6e5e1) and on the footer.

Also restored

cursor: none had taken two things away:

• The text cursor in inputs and the textarea is back.
• One consistent clickable cursor. Six class-level cursor: pointer rules would have beaten a plain element rule, so some buttons would show the hand and others the reticle. They now all use the same --cursor-link token.

Verified

• Minified CSS: tokens intact inside the media query, fallbacks present, zero cursor: pointer left.
• In the browser: both images decode at 32×32; page text shows the crosshair; nav links, buttons, the Call/WhatsApp buttons, select, labels and footer links show the reticle; input and textarea show text.

Cursor.jsx and the FEATURES.cursor flag are removed.