[P5][OS-01] Dedicated session and immutable distribution

Programme: #1
Epic: #34

## Objective
Package the same user-space personal runtime as a dedicated desktop session and then a recoverable Rust-heavy operating-system distribution without making inference a privileged boot dependency.

## Scope
- Session/login/unlock integration and workspace-oriented shell startup.
- Window/application launching, file browsing, clipboard, notifications and background task runtime.
- Audio/microphone, networking, storage, display/input and power/session integration.
- Resource service coordinating browser, speech and local model workloads.
- Transactional/immutable system update strategy with A/B or equivalent rollback/recovery.
- Diagnostics/recovery mode independent of AI models.
- Secure credential/key storage integration and user data partitioning.
- Installer/image creation, reference hardware support matrix and migration from desktop-app profile.

## Architecture rules
- Supervisor, connectors, model workers and generated applications remain unprivileged user-space services.
- A broken/missing model cannot prevent login, files, network repair or OS rollback.
- OS distribution reuses the same contracts/workspaces rather than creating a second incompatible product state model.

## Acceptance criteria
- [ ] Reference hardware boots into the personal runtime and completes declared browser/workspace/file/voice workflows.
- [ ] Login, local files, network diagnostics and rollback work with inference entirely disabled/broken.
- [ ] Interrupted system update recovers transactionally without corrupting the personal workspace store.
- [ ] Desktop-app workspace export/migration is accepted by the OS runtime without losing declared portable state.
- [ ] Privileged OS components remain materially smaller than the AI/browser application stack.
- [ ] Hardware/driver limitations are documented in a tested support matrix.

## Dependencies
- CORE-03
- EVAL-04
- PC-03

**First phase:** P5
**Maturity target:** P8
**Owner:** os-systems

No files, tests, or entry points are named. Start by reviewing dependencies CORE-03, EVAL-04, and PC-03 and narrowing the P5 first phase; done means the listed boot, recovery, migration, update, and hardware-support acceptance criteria are met.

Written by the indexing model from the issue text.