Prepare 0.1.0-beta.2 feature freeze and release validation

docs/README.md

@@ -40,6 +40,7 @@ and [guides at that tag](https://github.com/ferese-wm/ferese/tree/v0.1.0-beta/do
 
 ## Development
 
+- [0.1.0-beta.2 preparation](releases/0.1.0-beta.2.md): feature freeze, changes and validation gates.
 - [Packages and releases](packaging.md): build Fedora and Arch packages and publish a tagged release.
 - [Development](development.md): build Ferese, run tests and check portal contracts.
 - [Publishing activities](development/activities.md): IPC schema, ownership, limits and templates.

docs/releases/0.1.0-beta.2.md

@@ -0,0 +1,55 @@
+# 0.1.0-beta.2 preparation
+
+The 0.1.0 feature set is frozen as of October 14, 2026. Changes after the freeze
+are limited to regression fixes, release preparation and documentation.
+Beta 2 is being validated. It has not been released.
+
+## Changes since 0.1.0-beta
+
+- Native launcher with app, file and window search, category browsing and theme support.
+- Panel styles, the Morph hub and configurable Live Activities.
+- Tabbed window groups and named keyboard binding modes.
+- Night light, animated temperature changes and brightness shortcuts on the lock screen.
+- Window blur controls and reorganized Settings pages.
+- Region recording with audio, fractional-scale capture fixes and idle capture-cache cleanup.
+- Complete CRTC matching, bounded resize waits and output-specific DMA-BUF feedback.
+- Layer and popup focus fixes, managed-window activation and outside-launcher touch dismissal.
+- Security-context filtering for both privileged clipboard protocols. Ordinary clipboard
+  access remains available, and host clipboard tools retain data-control access.
+
+## Release gates
+
+Record the full candidate commit with each log, artifact and hardware report.
+If a fix changes the candidate, rerun validation on the new commit before tagging.
+
+- [x] Freeze the 0.1.0 feature set.
+- [x] Set the workspace and lockfile version to `0.1.0-beta.2` and prepare release notes.
+- [ ] Pass formatting and Clippy with warnings denied.
+- [ ] Pass workspace tests, capture and recorder checks, Python tests and headless integration tests.
+- [ ] Build Fedora 44 RPMs and Arch packages from the same candidate.
+- [ ] Validate direct DRM: login/logout, locking, suspend/resume, lid and monitor changes,
+  fullscreen, screenshots and screen sharing.
+- [ ] Test fresh Fedora 44 and Arch installs and upgrades from `0.1.0-beta`.
+  Check existing configurations, PAM, services and display-manager session selection.
+- [ ] Pass native soak runs with crash, RSS, file-descriptor and client-exit recovery checks.
+- [ ] Resolve release blockers, attach validation evidence and publish the tested candidate.
+
+## Validation procedure
+
+Use the **Release packages** workflow's manual dispatch on the candidate branch.
+It runs release checks and builds both package formats. Confirm that the run's
+`headSha` matches the candidate. Manual dispatch does not publish a release.
+
+For local checks, follow [Development](../development.md). Use the
+[native soak runner](../native-soak-testing.md) in a disposable session and retain
+its declared duration and resource budgets with the results. A short smoke run
+does not satisfy the full soak gate.
+
+Package builds alone do not establish install or upgrade compatibility.
+Record the distribution, package version, configuration changes and session results
+for each fresh install and upgrade. Hardware reports also need the GPU, driver,
+kernel and monitor setup.
+
+The reported login flash still needs reproduction on the candidate. The bar's
+initial material publication was changed, but the separate info-modal report
+has not been confirmed. DMA-BUF refresh cost also remains unprofiled.