[SourceAura]

Mandara — the Jurai suite's launcher

Summon, type, run. One mouth, four lanes, in order: apps
(fuzzy-matched desktop entries), commands (a leading >, or a
query nothing else answers), actions (lock, screenshot, sleep —
through the host's own SessionActions seam), and files
(path-shaped queries walk folders; plain words search the home).

TAB locks a lane, and the lock crystallizes as a rune chip above
the field — a crystal token in the shape of the Obelisk's runes
from Jurai shell, where Mandara was born as a palace: an AI core,
a ROM lineage, organs, a war room. All of that is cut. What
crossed is the omnibar and its manners: one centred dark-glass
plate, the prism beam under the input, rows that answer with a
glyph, a name, and a hint of what the row is, her mark 曼 ghosted
behind the plate, her name lettered small at the foot.

v1.0.1 is the foundation, proven on hyperion (the proving floor):
storecheck green, the full install → activate → remove → fallback
cycle, framed open on the real desktop, and set as the machine's
launcher through launcher.json — where she has held through
restarts since.

The road from here is parity and beyond, in version bumps behind
this seal: frecency ranking with pinned and recent apps, a calc
lane, running windows as results, a web lane, then the base
launcher's remaining providers (packages, media, snippets,
script, radio) — and the locked rune segments learning the deeper
work they were kept for.

— 0xSrcAura

[SourceAura]

Closed by the author: filed ahead of my own captains OK, and it carries a face he has since ruled against. Mandara returns as a faithful port of her Jurai shell face when he calls it — this PR should not have been opened. — 0xSrcAura