DAP SHADERS 6.2
===============
Same shaders as 6.1. This release fixes the installer, which had been broken
since 5.5 without anyone noticing, and adds a plain-text Windows installer so
you are not asked to trust an unsigned binary.

If you are publishing one build, publish this one.


FIXED - the bundled installer never worked in 5.5, 5.7, 6.0 or 6.1
  The installer copies the shaderpack into your Minecraft folders. To do that it
  looks for the shaderpack zip sitting NEXT TO itself - it cannot copy the archive
  it is currently inside.

  The original V5 download handled this by containing a second, plain copy of the
  shaderpack alongside the installer. When the build pipeline was rewritten for
  5.5 that nested copy was dropped, so extracting any of those builds and running
  the installer produced "payload missing" and stopped. The download still worked
  perfectly as a drag-and-drop shaderpack, which is exactly why it went unnoticed
  for four releases.

  The nested copy is back. The download is still a valid drop-in shaderpack on its
  own, and the installer inside it now has something to install.

  The installer files are also loose in the release folder next to the zips, so
  that folder can be run directly without extracting anything.

FIXED - the macOS / Linux installer had a hardcoded filename
  It looked for exactly "DAP Shaders 1.20-26.2.zip". Release zips carry their
  version in the name now ("DAP Shaders 6.2 1.20-26.2.zip"), so the name stopped
  matching and the script reported its own payload as missing. It matches by
  pattern now, the way the Windows version already did.

  Its banner also still said 5.0, and its closing instructions told you to select
  "DAP-Shaders_4.0" in Video Settings - a shader name that has not existed for two
  major versions.

NEW - a plain-text Windows installer
  "Run DAP Shaders Installer.cmd" and "DAP Shaders Installer.ps1".

  The .exe is not code-signed, so Windows shows "unknown publisher" and some
  antivirus heuristics object to an unsigned program that writes into several
  folders. That cannot be fixed in code. An unsigned executable triggers those
  warnings because it is unsigned - the only real fixes are a paid code-signing
  certificate (which then takes weeks of download volume before SmartScreen trusts
  it) or not shipping a binary.

  So there is now a PowerShell installer you can read in Notepad before running.
  Same behaviour as the .exe:
    - finds vanilla Minecraft plus Prism, MultiMC, Modrinth, CurseForge,
      GDLauncher and ATLauncher instances
    - reads each instance's Minecraft version where the launcher records it and
      installs the matching build - a 1.19 instance gets the 1.16-1.19 build
      automatically, without asking
    - installs the shaderpack under one canonical name so the in-game list shows a
      single "DAP Shaders" entry rather than one per version
    - removes older DAP packs only after the new one has landed, and only files
      whose name begins "DAP Shaders"
    - leaves a spare copy in Downloads
    - writes a log next to itself

  It has no network calls, no registry writes, no elevation, and does not launch
  other programs. Because it is text, you can verify that rather than believe it.

  The .exe is still included for anyone who prefers the small window. It was
  checked for this release: it is a .NET WinForms file-copier with no networking,
  no registry access and no process launching. That is reassuring but it is not a
  substitute for a signature, and the README now says so plainly instead of
  brushing the warning off.

ALSO
  Each release zip now carries its own CHANGELOG, so the version's notes travel
  with the download instead of only living in the release folder.


NOT CHANGED
  Nothing in the shaders. 6.2 and 6.1 render identically - the light and tone
  measurements are byte-for-byte the same. If you already tested 6.1 and liked it,
  6.2 is that build with a working installer.


   - DAPTIME
