v1.0.1 — the Intune wizards can finally make the .intunewin

v1.0.1 — the Intune wizards can finally make the .intunewin

The desktop Intune wizard now creates the .intunewin file. Through v1.0.0
it exported the source folder and then told you to open README.txt and run
Microsoft's IntuneWinAppUtil.exe yourself — even when that file was sitting
right next to spoolsmith-gui.exe. The GUI had no code that ever looked for it.
That was a gap, not a design choice: only the CLI's intune build could run the
tool, and only if you passed both --content-prep-tool and
--content-prep-output.

Now, all three entry points behave the same way:

• Put IntuneWinAppUtil.exe in the same folder as SpoolSmith and you are done.
  intune build, intune wizard and the desktop wizard find it there, export the
  bundle, and create install.intunewin in a new <export folder>-intunewin
  folder beside the export. Only that one file name in that one folder is ever
  looked for — nothing on PATH, nothing searched for — so what runs is a file you
  placed there or chose yourself.
• The desktop review page has a Content Prep tool field and an output folder.
  The tool is filled in when it is found beside the program. Export reviewed
  package exports and then packages; Create .intunewin from the exported
  folder retries the packaging step alone if it failed, without exporting again.
  Closing the window while the tool runs stops it.
• intune build needs neither flag any more. Either --content-prep-tool or
  --content-prep-output may be given alone, and the new --no-content-prep
  exports the bundle only even when the tool is present. intune wizard shows the
  detected tool in its review step and offers a path (or none) under advanced
  settings.

It fails safely. A missing tool, or an output folder inside the export, is
refused before anything is exported. If Microsoft's tool fails, the exported
folder is left complete and the tool's own output is shown. And SpoolSmith now
reports success only if install.intunewin actually exists — previously a tool
that exited 0 without producing a package would have been reported as a success
on the CLI.

Still local and manual where it always was: SpoolSmith does not download the
Content Prep Tool, sign in to a tenant, or upload or assign the app in Intune.

Notes

• The old rule that both content-prep flags must be given together is gone. An
  existing intune build ... --content-prep-tool X --content-prep-output Y command
  behaves exactly as before.
• A build that previously only exported the bundle will now also create the
  .intunewin if IntuneWinAppUtil.exe happens to be beside spoolsmith.exe.
  Use --no-content-prep to keep the old behavior.
• intune wizard scripts that answer the advanced-settings questions need one
  more answer (the tool path, after the export folder). The wizard requires an
  interactive terminal, so this only affects scripted terminal sessions.
• Verified with Microsoft's real IntuneWinAppUtil.exe, from the CLI and through
  the real desktop app. The reviewed-package screenshot on the product site is
  refreshed for the new fields.