Prepare Captail 0.1.8 Store release

[FaulMit]

Summary

• isolate the Microsoft Store FFmpeg runtime and validate native dependencies
• declare the required Microsoft Visual C++ framework dependency in the MSIX manifest
• move Store state and cache files into package-managed locations
• stop capture during Store package updates and uninstall operations
• make the regular installer stop Captail before uninstall and remove application data
• route automatic-capture replays by the active game instead of a stale Game Capture hook
• add a manual Microsoft Store workflow with build-only, draft, and certification modes

Why

Store installations could load incompatible FFmpeg DLLs, causing missing-entry-point failures. Store updates and removals also needed package lifecycle handling and package-owned state. Automatic capture could retain an inactive OBS hook and place a CS replay in another application's folder, such as Telegram. Microsoft Store submissions were entirely manual.

User impact

• Captail version advances to 0.1.8.
• Store FFmpeg startup and native runtime resolution are validated during packaging.
• Store update and uninstall operations request graceful capture shutdown.
• Automatic replay folders follow the game Captail selected for capture.
• Maintainers can build, stage, or submit an MSIX update from GitHub Actions without storing credentials in the repository.

Validation

• Release build: 0 warnings, 0 errors
• full .NET analyzer build: 0 warnings, 0 errors
• --qa-capability-model
• --qa-replay-routing
• --qa-auto-capture-policy
• Store lifecycle isolation test
• Store FFmpeg isolation test
• Store native dependency test: 26 native runtime users covered by VCLibs
• generated manifest identity: faulmit.Captail 0.1.8.0
• all four GitHub workflows pass actionlint 1.7.12
• git diff --check

Local regular-installer uninstall QA was not repeated while the installed Store build was active. The release workflow retains its install, launch, uninstall, process-exit, and AppData cleanup checks.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 172dbf8505

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Wait for Store shutdown before returning from lifecycle events

When an update or uninstall arrives during replay saving, SaveReplayGuardedAsync can hold _pipelineGate for up to the 45-second save timeout, but this handler stops waiting after 15 seconds and returns while RequestShutdownAsync is still blocked on that gate. The package operation can therefore continue with Captail still capturing or muxing, defeating the lifecycle isolation specifically when an active save needs protection; keep the lifecycle callback pending through the supported save duration or explicitly cancel/finish the save before returning.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Preserve data shared with Portable installations

When a user also runs the supported Portable ZIP, that build stores its configuration and caches in these same %APPDATA%\Captail and %LOCALAPPDATA%\Captail directories through AppDataPaths because it has no package identity. Uninstalling the regular Setup build now silently deletes the Portable installation's settings and cached metadata as well; scope cleanup to data owned by this installation or make removal of shared user data an explicit opt-in.

Useful? React with 👍 / 👎.