Phase 10.1: Registry protocol 2 (structured listing), migration 2, v1 refused explicitly

Listing (rates, modules, region, account provisioning), population with players and bots apart,
level cap and ruleset derived from the hash-checked capabilities. Realm records from protocol 1
keep their id, key and creation time and are republished in place. Host publishes the real
values: rates from the effective worldserver configuration, modules from the module catalog,
players/bots from the realm database.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
ДмитрийandClaude Sonnet 5.5 committed 2026-10-07 21:31:45 +05:00
1 parent 3e57d32c90
commit e39cecb333
28 files changed
+1012 -397

No files matched your search

+2 -2
View File
@@ -1788,9 +1788,9 @@ async fn registry_set_url(state: State<'_, AppState>, url: Option<String>) -> st
}
#[tauri::command]
async fn registry_publish(state: State<'_, AppState>, local_id: String, display_name: String, description: String, language: String) -> std::result::Result<(), UiError> {
async fn registry_publish(state: State<'_, AppState>, local_id: String, display_name: String, description: String, language: String, region: Option<String>) -> std::result::Result<(), UiError> {
let rt = realm_registry(&state)?;
tauri::async_runtime::spawn_blocking(move || rt.publish(&local_id, &display_name, &description, &language)).await.map_err(|e| Error::Invalid(e.to_string()))?.map_err(UiError::from)
tauri::async_runtime::spawn_blocking(move || rt.publish(&local_id, &display_name, &description, &language, region.as_deref())).await.map_err(|e| Error::Invalid(e.to_string()))?.map_err(UiError::from)
}
#[tauri::command]