diff --git a/README.md b/README.md index b9c2087..9cae4d1 100644 --- a/README.md +++ b/README.md @@ -80,12 +80,11 @@ an item failure, reports reboot requirements, and never restarts Windows. Close a running portable application before updating it. The working version remains available until its replacement is fully activated, then older versions are removed. -PDF Presenter is the first portable release package. The desktop profile follows -its preview channel, verifies `SHA256SUMS`, and creates a Start menu shortcut at -Start → Config Central → idle-org that launches `pdf-presenter.exe` directly -with its embedded icon. It is also registered as a per-user PDF handler, with a -separate PDF document icon based on its turquoise presentation mark. After the -first `cc update-software` or full apply, open its Windows Default Apps page: +The desktop profile installs PDF Presenter and PPTX Reporter as verified portable +packages and creates per-user Start menu shortcuts under Config Central. PDF +Presenter is also registered as a per-user PDF handler, with a separate document +icon based on its turquoise presentation mark. After the first +`cc update-software` or full apply, open its Windows Default Apps page: ```powershell Start-Process 'ms-settings:defaultapps?registeredAppUser=ConfigCentral.idle-org.pdf-presenter' diff --git a/docs/advanced_commands.md b/docs/advanced_commands.md index 3f7a737..12b599b 100644 --- a/docs/advanced_commands.md +++ b/docs/advanced_commands.md @@ -331,18 +331,18 @@ terminal open with the outcome in `$LASTEXITCODE`. ## Portable package updates -The desktop profile includes PDF Presenter 0.1.33 for Windows x64 from the -[upstream preview release](https://proxy.dandaedre.com/gitea/idle-org/pdf-presenter/releases/tag/v0.1.33). -Its ZIP and executable were checked against the published SHA256SUMS. Upstream -marks this release as a preview with unsigned Windows binaries; native Windows -acceptance remains pending here too. +The desktop profile includes PDF Presenter 0.1.91 and PPTX Reporter 0.2.0 for +Windows x64 from their published portable releases. Their exact ZIP hashes and +executable paths were checked against each release's SHA256SUMS and artifact +manifest. The Windows binaries are unsigned; native Windows acceptance remains +pending here too. Portable packages use `provider: "portable"`, user scope and a version pinned in Git. `source` is a namespace (here `idle-org`), not a WinGet source. They appear alongside WinGet packages in `cc plan`, `cc status`, `cc apply` and full `cc sync`. Config-only commands and the scheduled config sync leave software alone. -To update installed software, close PDF Presenter and run: +To update installed software, close PDF Presenter and PPTX Reporter and run: ```powershell cc update-software @@ -355,9 +355,9 @@ portable packages and asks WinGet to apply each declared package's policy by exact ID. PDF Presenter follows the newest eligible preview or stable release. Unmanaged WinGet applications are left alone. Configs are not planned or changed. Each release lookup resolves one exact ZIP, reads its exact entry from -`SHA256SUMS`, and verifies the downloaded archive before activation. A lookup or -checksum failure is reported for that package while independent packages -continue. As with `sync`, local checkout changes must be committed or removed +`SHA256SUMS`, and verifies the downloaded archive before activation. Both tools +follow stable releases. A lookup or checksum failure is reported for that package +while independent packages continue. As with `sync`, local checkout changes must be committed or removed before the fetch; Config Central never discards them automatically. After the software run, the installed checkout is advanced to the resolved commit with a fast-forward-only merge so subsequent `cc` commands use the refreshed version.