# 2.1.22 beta update acceptance

Release source is frozen at `1c43d039ed3fbc993bc38ed193f77d469cc3a196`, annotated tag `v2.1.22`. The signed manifest SHA256 is `409574eda1883c3669b885b20aab1718cb06c275a608fa8d86fb262cb5adcef5`. The backend SHA256 is `17bb75426cecd91d7d4613681b8f648fa2865324a439d0c3e36e33e2b7cee80f`; the frontend archive SHA256 is `28af5daf3dcea4956236091ee2590444206671c71c997960eea6f77dbab5ed7e`.

## Correction and source qualification

An official historical ISO installed the signed web files without the complete `archipelago-runtime` directory included in the corresponding OTA archive. Version 2.1.21 rejected that legitimate layout before its owner transaction could begin. Its published payloads and tag remain immutable and its hold notice remains recorded.

Version 2.1.22 admits this precise ISO projection for the twelve authenticated historical versions 1.8.13-alpha through 1.8.22-alpha, 1.9.0-alpha and 1.9.1-alpha. Every remaining file must match the signed archive. Partial runtime directories, modified files, symlinks and other missing files remain rejected. The actual old layout is retained for recovery.

The focused adoption suite passed 74 checks and all twelve signed historical archives were audited. The full isolated backend suite passed 3,187 tests with zero failures and 29 explicit ignores. Production artifact and frontend boundary checks passed. The maintainer-approved dashboard changes remain unchanged in the frozen source; no new layout or payment flow is introduced by this feed promotion.

## Installed acceptance

An actual official-ISO 1.9.1-alpha installation completed the normal authenticated update to 2.1.22 and committed its owner transaction. Independent verification passed for signed installed code and frontend, owner/runtime state, protected wallet and identity data, app records, container preservation and custom routing. The temporary qualification selector was removed and normal service startup passed.

The existing security migration from legacy v0 sessions requires a one-time password sign-in after this upgrade. A normal post-upgrade password sign-in, authenticated read and logout passed. Legacy cookies are not claimed to survive that migration.

A separate existing-OTA 2.1.21 installation completed a single signed update to 2.1.22. Independent preservation checks passed, including all seven valid modern v2 sessions, protected data, app records, containers and peer state. Fresh desktop HTTP and phone-width HTTPS browser checks passed on both installations: the styled login was usable, assets loaded correctly and no startup placeholder remained.

These two installed profiles are distinct acceptance evidence. They do not prove every historical version or every hardware configuration. Earlier failed attempts and their recovery evidence remain retained.

Companion Bump28 is reused unchanged with its existing physical-phone acceptance. No new Android or USB acceptance is claimed.

## Publication

Public asset and historical compatibility verification must pass before promoting these exact signed bytes to both update feeds. Canonical release publication and matching reviewed main/tag refs on both source mirrors remain required. Publication completion is recorded separately from installed acceptance.

ISO build, clean installation and reboot remain separate gates. The proposed first-install account, password and Wi-Fi setup flow is deferred. This OTA acceptance does not claim an ISO release.