Record project continuation changes

README.md

@@ -9,6 +9,9 @@ The project started as an RDP proxy, but the target architecture is broader:
 - service adapters for RDP now and VNC/SSH/VPN/file/video later
 - native Access Clients
 - future secure mesh / node-agent / updater / connector model
+- shared Fabric Service Channel runtime for working service data so VPN,
+  Remote Workspace, video, file, and future services request a common channel
+  instead of reimplementing transport, routing, and failover
 
 RDP is the first proven service baseline. RDP work is currently paused by
 product decision while the project moves to the Secure Access Fabric
@@ -57,6 +60,7 @@ See the current audit and baseline matrix before starting new work:
 - `workers/rdp-worker/` - active C++ RDP Adapter worker
 - `workers/rdp-service-csharp/` - inactive research scaffold, not current runtime
 - `clients/windows/` - Windows native Access Client
+- `clients/android/` - Android VPN client
 - `docs/architecture/` - target and staged architecture documents
 - `docs/codex/` - current Codex status and next-step prompts
 - `docs/audits/` - current audits and baseline matrices
@@ -64,6 +68,49 @@ See the current audit and baseline matrix before starting new work:
 - `deploy/` - deployment assets
 - `web-admin/` - future/admin UI area
 
+### Быстрый локальный билд Android APK после апдейта
+
+```powershell
+pwsh -ExecutionPolicy Bypass -File scripts\prepare-local-build-workstation.ps1 -SetEnvironment
+pwsh -ExecutionPolicy Bypass -File scripts\android\prepare-android-build-environment.ps1 -SetEnvironment
+pwsh -ExecutionPolicy Bypass -File scripts\android\rebuild-and-publish-android-apk.ps1
+```
+
+Для быстрого release (сборка + публикация + опциональная проверка манифеста):
+
+```powershell
+pwsh -ExecutionPolicy Bypass -File scripts\android\release-android-apk.ps1 `
+  -InstallMissing `
+  -PublishToTestDockerDownloads
+```
+
+Для одного шага «всё-в-одном»:
+
+```powershell
+pwsh -ExecutionPolicy Bypass -File scripts\android\fast-release-android-apk.ps1
+```
+
+Или через `.cmd` (Windows, двойной клик/ссылкой):
+
+```text
+scripts\android\fast-release-android-apk.cmd
+```
+
+После обновления Android-клиента выполните на машине сборки:
+
+```powershell
+pwsh -ExecutionPolicy Bypass -File scripts\android\rebuild-and-publish-android-apk.ps1 -InstallMissing -BuildType release
+```
+
+Скрипт сам проверит окружение, при необходимости поставит недостающие компоненты
+SDK (флаг `-InstallMissing`) и соберет APK. После этого артефакт сразу окажется в
+`web-admin/deploy/html/downloads` для скачивания из панели.
+
+Важно по процессу релиза: каждый новый номер версии должен проходить полный цикл
+`сборка → публикация → проверка manifest` и всегда попадать в `latest-release` +
+`releases/<version>` на стороне дистрибутива, чтобы узлы и пользователи всегда
+обновлялись с актуального билда.
+
 ## Read Order
 
 1. `CODEX_CONTEXT.md`
@@ -73,8 +120,9 @@ See the current audit and baseline matrix before starting new work:
 5. `docs/codex/ARCHITECTURE_GUARDRAILS.md`
 6. `docs/architecture/RDP_ADAPTER_RUNTIME.md`
 7. `docs/architecture/DATA_PLANE_V1.md`
-8. `docs/architecture/CLUSTER_NODE_ADMIN_FOUNDATION.md`
-9. `docs/codex/NEXT_STEP_PROMPT.md`
+8. `docs/architecture/FABRIC_SERVICE_CHANNEL_RUNTIME.md`
+9. `docs/architecture/CLUSTER_NODE_ADMIN_FOUNDATION.md`
+10. `docs/codex/NEXT_STEP_PROMPT.md`
 
 Do not use `docs/_legacy_v1` for implementation decisions. Legacy files are
 historical reference only.