v0.7.5 — Dashboard setup, folder icons, and reliability fixes

Release notes and downloads

• Added configurable folder emoji icons through .lore/config.yaml in the
  dashboard knowledge tree, plus a new gradient-slash PWA app icon.
• The dashboard now goes straight to the passkey login page when sign-in is
  needed, and file copy actions sit beside the file name as icons.
• Fixed failed knowledge-facts scans getting stuck on the same queued path
  after a restart; failed scans now rebuild from docset roots while keeping
  the last completed results readable.
• analytics show tree-size and largest-docs skip unreadable descendants
  and report skipped paths instead of failing the whole result. An unreadable
  root still fails.
• find lists aliased docsets once by default; -L follows aliases, and an
  alias supplied as the starting point is still walked. ls -l and stat
  show aliases as links, and ls -R no longer descends through them.
• ls -l and stat now show write bits according to the caller's grant.
• publish rejects extra arguments instead of silently ignoring them; its
  two-argument examples have been corrected.
• Added a knowledge cleanup recipe and a
  deployment guide with Fly.io, EC2 and DigitalOcean platform pages.
• Added the Build your company brain on OpenLore recipe,
  which explains what OpenLore already solves for a shared knowledge layer and
  walks through laying it out as docsets, connecting data sources, giving it to
  agents and capturing knowledge from across the organisation.
• Added a Setup view to the dashboard that shows how the
  instance is configured for the signed-in identity: connection addresses,
  server features, each docset's paths, grants, inbox and folder rules, and a
  configuration tree listing every readable .lore/config.yaml and, for
  sessions that may edit configuration, the live lore.json and
  openlore.yml. The Files tree and fuzzy finder no longer list .lore
  folders or the /opt/openlore config mount; configuration files live on the
  Setup view instead.
• Sessions with lore:config:edit can now read the running server's
  openlore.yml at /opt/openlore/openlore.yml, beside lore.json. The file
  is read-only over the VFS and is mounted only when the server was started
  from a config file.

Full changelog: v0.7.4...v0.7.5