Make console output compact and readable

README.md

@@ -87,7 +87,7 @@ The script installs frameworks in dependency order, followed by Microsoft Store
 
 Windows cannot deploy an older copy of a framework that is already present. When the same framework is already provisioned or registered at the same or a newer version, the script skips that step. If provisioning rejects an older framework because a newer one is installed, the script logs a warning and defers the decision to verification.
 
-After installation, the script asks Windows for the result. It confirms that each installed app is registered for the current user with status `Ok`. When provisioning, it also confirms that each app is provisioned and that every dependency is provisioned at the required version for new users. Anything not confirmed is a partial failure, and the log summary lists every failure by name.
+After installation, the script asks Windows for the result. It confirms that each installed app is registered for the current user with status `Ok`. When provisioning, it also confirms that each app is provisioned and that every dependency is provisioned at the required version for new users. Anything not confirmed is a partial failure, and the final summary lists every failure by name.
 
 When run as SYSTEM, such as through Intune, SCCM, or MDT, the script only provisions packages. Windows registers them for users at sign-in. Do not combine SYSTEM execution with `-NoProvision`.
 
@@ -99,7 +99,9 @@ The online downloader relies on an undocumented Microsoft service. Changes to th
 
 ## Logs and troubleshooting
 
-The script prints its log path when installation starts. Saved copies normally write logs to `Logs` inside the working folder. When run through the online command, or if that folder is not writable, logs go to `%TEMP%\StoreInstall-Logs`.
+The console shows a short summary of the run: one line per package with its status (`OK`, `SKIP`, `WARN`, or `FAIL`), the verification results, and the outcome with its exit code. Problems are listed again at the end. The log file keeps every step with timestamps, including package file names and complete error messages.
+
+The script prints its log path when installation starts and again at the end. Saved copies normally write logs to `Logs` inside the working folder. When run through the online command, or if that folder is not writable, logs go to `%TEMP%\StoreInstall-Logs`.
 
 If Microsoft Store does not open, reboot after a fresh Windows installation, then check the installation log. You can also check Event Viewer under `Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server`.
 

docs/installer-reliability.md

@@ -6,7 +6,7 @@ Use the named options in `install.ps1`. The script supports Windows PowerShell 5
 
 The online command runs parameter binding and implementation variables in child scopes. It reports its result through `$LASTEXITCODE` without deleting existing variables from the calling session.
 
-Each default download folder has a unique name under the temporary directory. The script deletes that folder only when its path and ownership marker match the current run. `-KeepDownloads`, `-DownloadOnly`, and an explicit `-DownloadDir` preserve downloads. The script prints the selected folder in its log.
+Each default download folder has a unique name under the temporary directory. The script deletes that folder only when its path and ownership marker match the current run. `-KeepDownloads`, `-DownloadOnly`, and an explicit `-DownloadDir` preserve downloads. The log file records the selected folder. Download-only runs also print it at the end.
 
 `-DownloadTimeoutSeconds` limits each package download attempt. The default is 1800 seconds, and the accepted range is 1 through 86400 seconds. The downloader cancels a transfer that exceeds this limit. Metadata requests have separate timeouts. Retries mean the total run can take longer than one download deadline.