Confirm installed K1 R11 runtime and authority availability

docs/audits/2026-09-07-k1-bluez-selection-r11.md

@@ -57,8 +57,7 @@ git diff --check pass. No agent-issued physical K1 commands or Bluetooth scans
 were used. Hardware connection and R10 live-preview acceptance remain pending
 an owner UI run after clearing the browser cache.
 
-Release hashes and installed readback follow when available. The prior Ops
-publication and remote full-journal-copy approval blocks remain unresolved;
+The prior Ops publication and remote full-journal-copy approval blocks remain unresolved;
 this report is local and contains no raw device identifiers or credentials.
 
 ## Release staged
@@ -67,7 +66,13 @@ Source: ad24518b71228544e6b8c78a050550f283199950. The private immutable artifact
 mission-core-xgrids-k1_0.1.8+private.1_amd64.deb is 318109768 bytes with SHA-256
 7fb0a5491140a358c815b2897214156f3e2bb10b87177f1851c9e82f142e1e00.
 The remote artifact, installer and release manifest hashes match. Apt simulation
-selects one K1 upgrade, zero new packages and zero removals. The GUI installer
-is open for the owner's Ubuntu sudo authentication. Installed R11 readback and
-fresh-cache UI acceptance remain pending. The canonical Core service is still
-running on port 8000.
+selects one K1 upgrade, zero new packages and zero removals.
+
+The owner completed the GUI installation. Subsequent read-only dpkg and
+provenance checks confirm K1 0.1.8+private.1 from the source commit above and
+unchanged Node 0.8.8. Both services are active/running with NRestarts=0; the
+K1 service started at 15:54:46 MSK. Fleet reports application_authority_available
+true and the canonical Core health endpoint on port 8000 reports ok. No new
+matching error entries were observed in the K1 journal after that start.
+Enrollment is idle and disconnected, allowing a new owner scan; this is not
+physical connection acceptance. The fresh-cache UI attempt remains pending.