From 8aa3c2095448a3e9e7ac5fa5d37158565462c841 Mon Sep 17 00:00:00 2001 From: fy59 Date: Thu, 17 Sep 2026 15:47:48 +0200 Subject: [PATCH] docs(sync): record rollout candidate provenance --- docs/current_state.md | 2 +- docs/sync_rollout_readiness.md | 8 +++++--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/current_state.md b/docs/current_state.md index 556bce4..de7e1c3 100644 --- a/docs/current_state.md +++ b/docs/current_state.md @@ -13,7 +13,7 @@ GCC 16.2.1 and Clang 22.1.8 builds now pass the same 81-test inventory, and the Clang ASan/UBSan build passes it with leak detection. Bounded path assembly and the Web sync accepted response reject insufficient capacity without publishing partial output. Fresh desktop, current-Android and schema-v17 bridge candidates -were rebuilt from commit `2c5a8be2827e31fc5be2accb65073bfeb79d6068`. +were rebuilt from code commit `dd8c91a946a9c836965818d8cc35b8f8bce74658`. The rollout packager now keeps the legacy request daemon and one-shot helper in the same relocatable, hashed bundle as the Web generation coordinator, avoiding mixed-checkout user-service execution during the controlled rollout. diff --git a/docs/sync_rollout_readiness.md b/docs/sync_rollout_readiness.md index f503981..eb1bc6b 100644 --- a/docs/sync_rollout_readiness.md +++ b/docs/sync_rollout_readiness.md @@ -54,10 +54,12 @@ This is a non-executed rollout checklist. The development branch implements the path; the daily installation still uses V3. The latest software-only candidate set was rebuilt under the private root -`/home/fy59/.cache/trainlog/native-build-candidate-v1.VbFjE9` from source commit -`2c5a8be2827e31fc5be2accb65073bfeb79d6068`. Its desktop inventory records every +`/home/fy59/.cache/trainlog/sync-rollout-candidate-v1.NEoMDx` from source commit +`dd8c91a946a9c836965818d8cc35b8f8bce74658`. Its desktop inventory records every packaged file digest plus schemas, protocols, entry points and runtime -dependencies. The current debug APK SHA-256 is +dependencies; the inventory file SHA-256 is +`800034b409824a68cef45e5251dd4d94f00bd9e13b3387a1a302b8e2e1136839`. The current +debug APK SHA-256 is `aca2f499ee9ff53ba5913a76a2a0117274e3e5545967ce361f6f126a6af497e1`; the non-installed bridge APK SHA-256 is `0a28d81cbb0818cdf2fee72d5024a4b706fcfda39f1182c682c12f000a026cb4`; and its