Bump version to 0.6.0-SNAPSHOT [skip ci]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.gitea/workflows/build.yaml

@@ -0,0 +1,7 @@
+name: build
+on:
+  push:
+jobs:
+  maven:
+    uses: self:KofTwentyTwo/ci-workflows/.gitea/workflows/maven.yaml@v1
+    secrets: inherit

.qqq-ci.yml

@@ -9,7 +9,7 @@ release_on_main: false
 release_tag_policy: stable
 test_branch_policy: all
 publish:
-  snapshot: false
+  snapshot: true
   release_candidate: false
   release: false
   feature: false

AGENTS.md

@@ -1,7 +1,7 @@
 # QQQ Mobile Scanners
 
-This is an application QBit and a separate local demo, using Java 21 and QQQ 4.1.0-RC.21.
-The Android host is maintained in [QRun-IO/qqq-android on Gitea](https://git.kof22.com/QRun-IO/qqq-android) (reviews: pulls/8 and pulls/10).
+This is an application QBit and a separate local demo, using Java 21 and QQQ 4.1.0-RC.21. Optional `examples/echo` (scan-to-print) uses released Printing 1.0.0; its Generation, Record Files and Scripting owner inputs are not yet public. Contract versions: UI API 1.10, `mobile-scanners` 1.6 (1.5 on the maintained local server), `printing` 2.3, `mobile-record-files` 1.0.
+The Android host is maintained in [QRun-IO/qqq-android on Gitea](https://git.kof22.com/QRun-IO/qqq-android) (reviews pulls/8 and pulls/10 are merged into `main`). Present status is in `docs/SESSION-STATE.md`; older logs are in `docs/history/`.
 
 ## Build and verify
 
@@ -28,4 +28,6 @@ The Android host is maintained in [QRun-IO/qqq-android on Gitea](https://git.kof
 - The primary forge for source, reviews and checks is Gitea (`git.kof22.com/QRun-IO`); GitHub is a shadow/archive, so make no ordinary GitHub writes.
 - The CircleCI manifest (central qbit profile, managed `0.8` track; keep the three version declarations identical) and the GitHub demo workflow are retained legacy definitions: preserve the existing managed files, but primary CI changes follow current Gitea policy and should not be directed into GitHub.
 - All publication switches start disabled. Creating a repo or pushing a branch is not permission to publish Maven artifacts or cut a release.
-- Preserve unrelated work. Update `docs/SESSION-STATE.md` and `docs/TODO.md` when project state changes. Commit, push, release, deployment and external communication require authorization in the active task.
+- The local demo must keep working independent of any shared CI redesign. `docs/LOCAL-DEMO.md` distinguishes the basic Scan Capture demo (`scripts/Start-Demo.ps1`) from the full Echo server (`examples/echo/demo`); do not invent port defaults (the Echo launcher has none). Never print or paste demo passwords: use `scripts/Copy-DemoPassword.ps1`. Keep device identifiers, addresses, credentials, workstation paths and vault IDs out of the repository.
+- Do not claim a manual or hardware test beyond what the operator actually reported or what an artifact shows; do not request the already-reported TC22 manual tests again, and do not claim barcode fidelity beyond the documented Echo profiles.
+- Preserve unrelated work. Keep `docs/SESSION-STATE.md` (present status, short), `docs/TODO.md` (open items only) and `docs/PRODUCTION-READINESS.md` current when project state changes, and move superseded detail to `docs/history/` rather than deleting it. Commit, push, release, deployment and external communication require authorization in the active task.

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing
 
-Use Java 21 and the checked-in Maven wrapper. Clone this repository and the companion [qqq-android](https://github.com/QRun-IO/qqq-android) when changing the mobile/server contract. No Android SDK is needed for server-only changes.
+Use Java 21 and the checked-in Maven wrapper. Clone this repository and the companion [qqq-android](https://git.kof22.com/QRun-IO/qqq-android) on Gitea (the primary forge; GitHub is a shadow/archive) when changing the mobile/server contract. No Android SDK is needed for server-only changes.
 
 Create `feature/`, `fix/`, `docs/` or `chore/` branches from `develop` and open pull requests into `develop`. Use Conventional Commit subjects and describe the resulting behavior, relevant verification and compatibility changes. Request review from the code owner; do not merge with failing required checks.
 

README.md

@@ -1,64 +1,91 @@
 # QQQ Mobile Scanners
 
-Server support for approved Android handhelds running native QQQ apps. The first app, **Scan Capture**, stores barcode events in a QQQ table. The companion Android application is [QQQ Android's scanner host](https://git.kof22.com/QRun-IO/qqq-android) (`scanner-host` directory), reviewed in [pull request 8](https://git.kof22.com/QRun-IO/qqq-android/pulls/8) and [pull request 10](https://git.kof22.com/QRun-IO/qqq-android/pulls/10). Gitea is primary; the GitHub copy is a shadow/archive.
+Server support for approved Android handhelds running native QQQ apps. The first app, **Scan Capture**, stores barcode events in a QQQ table. An optional example, **Echo**, scans a barcode and prints a copy of it ([Echo](examples/echo/README.md)).
 
-Version one is online only. Devices require an authenticated user and administrator approval. Android renders existing QQQ app, process, frontend-step and widget metadata; this qbit adds the scanner widget and enrollment lifecycle.
+Version one is online only. Devices require an authenticated user and administrator approval. Android renders existing QQQ app, process, frontend-step and widget metadata; this qbit adds the scanner widget and the device enrollment lifecycle. Not released as production 1.0.
 
-App discovery and process execution use the versioned semantic UI/UX API at `/qqq/v1`. Enrollment, branding and status are registered operations in the independently versioned `mobile-scanners` extension at `/qqq/v1/qbit/mobile-scanners`. The Android host checks core and extension compatibility before login. See [the semantic API contract](docs/UI-API.md). Metadata changes using supported native components can be delivered by the server; new required component types need a shared Android client update. This contract does not imply full web-client feature coverage.
+## Where things live
 
-## Project layout
+Gitea is the primary forge for source, reviews and checks. GitHub is a shadow/archive that receives no ordinary writes; any GitHub link in an older document is history only.
 
-- `src/main`: reusable qbit, device enrollment routes, device approval/revocation, scan process and table metadata.
-- `src/test`: server behavior and permission checks.
-- `demo`: local QQQ server with persistent H2 storage, native administration UI and password login.
-- `e2e`: browser acceptance tests against the packaged frontend and isolated real demo server.
-- `docs/TC22-ACCEPTANCE.md`: build, install and hardware verification.
+- Server (this repository): [git.kof22.com/QRun-IO/qbit-mobile-scanners](https://git.kof22.com/QRun-IO/qbit-mobile-scanners), development branch `develop`.
+- Android host: [git.kof22.com/QRun-IO/qqq-android](https://git.kof22.com/QRun-IO/qqq-android) (`scanner-host` module). Its reviews 8 and 10 are merged into `main`.
+- Current status: [session state](docs/SESSION-STATE.md), [TODO](docs/TODO.md), [production readiness](docs/PRODUCTION-READINESS.md). Older logs are in [history](docs/history/README.md).
 
-## Build
+## Current versions
 
-Use Java 21 and Maven 3.9+. The implementation targets QQQ `4.1.0-RC.21`; QQQ `4.0.0` does not provide the password session exchange needed by this demo.
+| Component | Version |
+| --- | --- |
+| Java / Maven | 21 / wrapper-pinned 3.9.9 |
+| QQQ | `4.1.0-RC.21` (public) |
+| QQQ semantic UI/UX API | 1.10 |
+| `mobile-scanners` extension | 1.5 |
+| `printing` extension (Echo) | 2.3, released Printing `1.0.0` |
+| `mobile-record-files` vocabulary | 1.0 |
+| Development snapshot | `0.1.0-20261103.233448-3645` (Central; development only) |
+
+The 198-test cohort for this set passes with Checkstyle (scanner 53, demo 8, mobile Record Files 18, Printing bridge 16, Echo 68, Echo demo 35). The document, Record Files and Scripting owner artifacts used by Echo are not yet public; see [session state](docs/SESSION-STATE.md).
+
+## Quick start
 
 ```powershell
 .\mvnw.cmd verify install
 .\mvnw.cmd -f demo/pom.xml verify
+pwsh -File scripts/Start-Demo.ps1
 ```
 
-The wrapper pins Maven 3.9.9. On Unix, use `./mvnw` in place of `mvnw.cmd`. This is an initial implementation, with no published Maven artifact. Consult [session state](docs/SESSION-STATE.md) for actual verification status.
+On Unix use `./mvnw`. The last command starts the basic Scan Capture demo on loopback. [Local demo](docs/LOCAL-DEMO.md) explains the two launchers (basic Scan Capture versus the full Echo server), signing in without displaying passwords, connecting a device or emulator, and the enroll, approve, scan and revoke walkthrough. For a physical handheld follow [TC22 acceptance](docs/TC22-ACCEPTANCE.md); for test runners see [testing](docs/TESTING.md). Checkstyle runs during `validate`; do not disable it or skip tests.
 
-For the Windows demo, follow [local startup and credentials](docs/LOCAL-DEMO.md). For the scanner, follow [TC22 installation and acceptance](docs/TC22-ACCEPTANCE.md).
+## Architecture
 
-See [process acceptance tests](docs/TESTING.md) for server, browser, and native Android E2E commands. Approval and revocation support record actions and bulk selections with a confirmation and visible result.
+The server uses QQQ's existing, versioned semantic UI/UX API; nothing parallel is added.
 
-## Customer branding and connection diagnostics
+- App discovery and process execution go through `/qqq/v1`.
+- Enrollment, branding and status are registered operations of the independently versioned `mobile-scanners` extension at `/qqq/v1/qbit/mobile-scanners`, with discovery, stable operation IDs and typed OpenAPI schemas. The Android host checks core and extension compatibility before login. See the [semantic API contract](docs/UI-API.md).
+- The qbit contributes `mobileDevice`, private device credential storage, `mobileScan`, `mobileScanCapture`, the scanner widget and the device approve/revoke processes. Device sessions, live activity and consented screen viewing are in [device sessions](docs/DEVICE-SESSIONS.md) and [screen viewing](docs/DEVICE-SCREEN-VIEWING.md).
+- Metadata changes that use supported native components reach devices from the server; a new required component type needs a shared Android update. This does not imply full web-client feature coverage.
 
-Configure the customer name, primary color and optional HTTPS logo on the server; the same Android APK applies them before login and throughout the mobile screens. See [branding configuration](docs/BRANDING.md). The shared launcher remains QQQ Mobile.
+```text
+Android host --(/qqq/v1 + mobile-scanners extension)--> QQQ server + this qbit --> H2/RDBMS
+                                                         |-- optional: Echo, Record Files, Document Generation, Printing
+```
 
-The app footer checks server reachability while foregrounded. Tap it to inspect and copy recent safe diagnostic events. The public status endpoint reports reachability independently of user authentication and device approval.
+## Project layout
 
-## Contributing and CI
+- `pom.xml`: the `qbit-mobile-scanners-reactor` aggregator (packaging pom, single `<revision>` source) of the two published modules, `base` and `integrations/record-files`; `demo` and `examples/echo` are not part of it. One root `mvn deploy` publishes the reactor POM, `qbit-mobile-scanners` and `qbit-mobile-scanners-record-files` at the same version.
+- `base/src/main`, `base/src/test`: the reusable qbit (enrollment routes, approval/revocation, scan process, table metadata) and its H2 behavior and permission tests.
+- `demo`: basic local QQQ server with persistent H2 storage, native administration UI and password login. QQQ `4.0.0` lacks the password session exchange it needs.
+- `e2e`: browser acceptance tests against the packaged frontend and an isolated real demo server.
+- `examples/echo` and `examples/echo/demo`: the optional Echo library and its runnable composed server.
+- `integrations/record-files`: optional camera/gallery upload bridge.
+- `scripts`: Windows launcher and the password-copy helper.
 
-The primary forge is Gitea (`git.kof22.com/QRun-IO`); GitHub is a shadow/archive and receives no ordinary writes. Development pull requests target `develop`. The CircleCI and GitHub workflow files in this repository describe the legacy shared QBit pipeline and demo HTTP/browser/CodeQL checks; see [CI and release operation](docs/CI-CD.md) for how to run the same checks locally. All Maven publication switches start disabled. Current progress and dependency status live in [session state](docs/SESSION-STATE.md), not here. See [contributing](CONTRIBUTING.md), [CI and release operation](docs/CI-CD.md), [security reporting](SECURITY.md) and the [code of conduct](CODE_OF_CONDUCT.md). This project is licensed under [Apache 2.0](LICENSE).
+## Supported features
+
+- Single-barcode capture (Zebra EMDK service on the Android host, no DataWedge profile) and manual entry for Scan Capture, with QQQ table-based login.
+- Device enrollment, approval and revocation from a record or from bulk selection (checked rows, select-all, first N up to 100), with confirmation and visible results.
+- Idempotent scan events, device/session records, online activity, administrator session termination, own-app screen viewing, optional foreground location, and customer branding with connection diagnostics ([branding](docs/BRANDING.md)).
+- Optional operator-consented device-screen viewing (extension 1.2), camera/gallery record uploads through the optional [Record Files bridge](integrations/record-files/README.md), and the Echo scan-to-print example.
+- Additional apps are ordinary QQQ app/process/widget metadata; their server-side permission rules must explicitly protect their actions.
 
 ## Embed in a QQQ application
 
-Enable `instance.setEnforcePermissionsInCoreActions(true)`, register `MobileScannersQBitProducer` with a host-owned persistent backend, and attach `MobileScannersRouteProvider` to the QQQ Javalin server. The qbit requires core permission enforcement so direct table actions cannot bypass its protections. Grant `mobile.scan` to operators and `mobile.admin` to administrators through the host's identity provider/permission integration. The demo's fixed account roles are confined to the demo application.
+Enable `instance.setEnforcePermissionsInCoreActions(true)`, register `MobileScannersQBitProducer` with a host-owned persistent backend, and attach `MobileScannersRouteProvider` to the QQQ Javalin server. The qbit requires core permission enforcement so direct table actions cannot bypass its protections. Grant `mobile.scan` to operators and `mobile.admin` to administrators through the host's identity provider. The demo's fixed account roles stay inside the demo application.
 
-The qbit contributes `mobileDevice`, private device credential storage, `mobileScan`, `mobileScanCapture`, and device approve/revoke processes. Generic table mutations are blocked; device lifecycle and capture go through guarded operations. An installation identifier is descriptive, not an authentication credential.
-
-The API uses the normal QQQ user session plus `X-QQQ-Device-Id` and `X-QQQ-Device-Token`. Device credentials are not process input fields. Enrollment creates a pending device; approval enables app access, and revocation prevents subsequent captures. Lost local app data requires fresh enrollment and administrator review.
+Generic table mutations are blocked; device lifecycle and capture go through guarded operations. The API uses the normal QQQ user session plus `X-QQQ-Device-Id` and `X-QQQ-Device-Token`; device credentials appear only in those scoped headers and in private hashed storage, never in process inputs, responses beyond enrollment, fixtures or logs. Enrollment creates a pending device, approval enables app access and revocation prevents later captures. An installation identifier is descriptive, not a credential. Lost app data requires fresh enrollment and administrator review.
 
 ## Scan semantics
 
-Each physical scan receives a new event UUID. A retry of that event uses the same UUID and returns the original receipt rather than inserting a second record. Scanning the same barcode twice intentionally produces two events.
+Each physical scan gets a new event UUID. A retry reuses that UUID and returns the original receipt; scanning the same barcode twice deliberately creates two events. Stored data includes barcode text (leading zeroes preserved), symbology, source, capture and receipt times, authenticated user, approved device, app and process, and reported hardware/app versions; extension 1.5 can add the scanner's AIM identifier and exact raw bytes. Client-reported timestamps and hardware details are provenance, not identity. The app shows success only after server acknowledgement, a timeout is an uncertain outcome to retry, and there is no offline queue.
 
-Stored data includes barcode text, symbology, source, device capture time, server receipt time, authenticated user, approved device, app/process and reported hardware/app versions. Barcode text is preserved, including leading zeroes. Client-reported timestamps and hardware information are provenance, not trusted identity.
+## Limits and release status
 
-The app must show server acknowledgement before reporting a save. A network timeout has an uncertain outcome; retry the retained event. There is no persistent offline queue in this version.
+- **Not production-ready.** The local demo works and the TC22 manual tests are operator-reported as passing; a QRun-signed Android 1.0 APK and its direct/MDM channel exist locally, but signed-build qualification on a device against an HTTPS server, distribution, HTTPS deployment and the other [readiness gates](docs/PRODUCTION-READINESS.md) are open. The HTTP loopback demo and an HTTPS production deployment are separate things.
+- **Barcode fidelity.** Echo supports a documented set of symbologies and refuses GS1, ECI, structured and binary payloads ([limits](examples/echo/README.md#fidelity-and-limits)); no universal reproduction or all-symbology claim is made. Hardware AIM output has no separate evidence beyond the operator's group report.
+- **Dependencies.** The development snapshot is published, but the document/files/scripting owner artifacts are not; Echo and the Record Files integration need a coherent local cohort until they are.
+- **Outside this version:** offline workflows, camera-based decoding, a visual app designer and applied MDM rollout. The Android host implements managed configuration, a profile generator and a live wallpaper, but applied rollout is not qualified. Native OAuth2 login exists only for servers that advertise the semantic UI API 1.10 native-session and nonce-validation features; no native handheld test against a configured provider (such as Authentik) is claimed, and that acceptance plus production ingress hardening remain gates.
+- **Database.** The supplied schema targets H2; migrations for other databases belong to the host application.
 
-## Scope
+## Contributing and CI
 
-The tested handheld path uses single-barcode capture through the Zebra EMDK service on the Android host (no DataWedge profile) and QQQ table-based login. The host conditionally configures AIM output and reads back the configuration before extracting an AIM identifier. SDK raw bytes can accompany either plain or AIM capture (mobile-scanners 1.5). Actual hardware AIM output, print and rescan fidelity is not yet qualified, so no exact-AIM or all-symbology claim is made. The Android client also implements metadata-advertised native OAuth2 login for servers providing the explicit UI API 1.9 contract; configured-provider acceptance and production scanner-ingress hardening remain release gates. See the client repository's authentication guide (`docs/AUTHENTICATION.md` in [the Gitea repository](https://git.kof22.com/QRun-IO/qqq-android)).
-
-Device/session records, online activity, administrator session termination, own-app screen viewing and optional foreground location are implemented. Extension1.2 adds optional [operator-consented device-screen viewing](docs/DEVICE-SCREEN-VIEWING.md); actual Android projection acceptance remains open. Camera/gallery record uploads use the optional Record Files bridge and require its compatible dependency tuple; production publication and actual camera acceptance remain open. Additional apps use QQQ's native process/widget metadata, and their server-side permission rules must explicitly protect their actions.
-
-A visual mobile app designer, offline workflows, camera-based barcode decoding and applied MDM rollout remain outside this version. The Android host implements company managed configuration, a profile generator and a live wallpaper (see `docs/` in the client repository); applied MDM/device-owner rollout of them is not yet qualified. The supplied SQL schema targets H2; other database migrations belong to the host application.
+Development pull requests target `develop`; `main` is reserved for reviewed releases. All Maven publication switches other than development snapshots stay disabled, and creating a repository or pushing a branch is not permission to publish. The CircleCI and GitHub workflow files describe the retained legacy shared QBit pipeline; [CI and release operation](docs/CI-CD.md) explains how to run the same checks locally, and the local demo does not depend on that pipeline. See [contributing](CONTRIBUTING.md), [security reporting](SECURITY.md) and the [code of conduct](CODE_OF_CONDUCT.md). Licensed under [Apache 2.0](LICENSE).

base/pom.xml

@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="utf-8"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
+   <modelVersion>4.0.0</modelVersion>
+   <parent>
+      <groupId>com.kingsrook.qbits</groupId>
+      <artifactId>qbit-mobile-scanners-reactor</artifactId>
+      <version>${revision}</version>
+      <relativePath>../pom.xml</relativePath>
+   </parent>
+   <groupId>com.kingsrook.qbits</groupId>
+   <artifactId>qbit-mobile-scanners</artifactId>
+   <version>${revision}</version>
+   <name>QQQ Mobile Scanners</name>
+   <description>Approved mobile devices and native QQQ barcode capture processes.</description>
+   <url>https://git.kof22.com/QRun-IO/qbit-mobile-scanners</url>
+   <scm>
+      <connection>scm:git:https://git.kof22.com/QRun-IO/qbit-mobile-scanners.git</connection>
+      <developerConnection>scm:git:ssh://git@git.kof22.com:22/QRun-IO/qbit-mobile-scanners.git</developerConnection>
+      <url>https://git.kof22.com/QRun-IO/qbit-mobile-scanners</url>
+      <tag>HEAD</tag>
+   </scm>
+   <issueManagement>
+      <system>Gitea</system>
+      <url>https://git.kof22.com/QRun-IO/qbit-mobile-scanners/issues</url>
+   </issueManagement>
+   <licenses>
+      <license>
+         <name>Apache License, Version 2.0</name>
+         <url>https://www.apache.org/licenses/LICENSE-2.0</url>
+         <distribution>repo</distribution>
+      </license>
+   </licenses>
+   <dependencyManagement>
+      <dependencies>
+         <dependency>
+            <groupId>com.kingsrook.qqq</groupId>
+            <artifactId>qqq-bom-pom</artifactId>
+            <version>${qqq.version}</version>
+            <type>pom</type>
+            <scope>import</scope>
+         </dependency>
+      </dependencies>
+   </dependencyManagement>
+   <dependencies>
+      <dependency>
+         <groupId>com.kingsrook.qqq</groupId>
+         <artifactId>qqq-backend-core</artifactId>
+      </dependency>
+      <dependency>
+         <groupId>com.kingsrook.qqq</groupId>
+         <artifactId>qqq-middleware-javalin</artifactId>
+      </dependency>
+      <dependency>
+         <groupId>com.kingsrook.qqq</groupId>
+         <artifactId>qqq-backend-module-rdbms</artifactId>
+         <scope>test</scope>
+      </dependency>
+      <dependency>
+         <groupId>com.h2database</groupId>
+         <artifactId>h2</artifactId>
+         <version>2.2.224</version>
+         <scope>test</scope>
+      </dependency>
+      <dependency>
+         <groupId>com.kingsrook.qqq</groupId>
+         <artifactId>qqq-backend-module-postgres</artifactId>
+         <scope>test</scope>
+      </dependency>
+      <dependency>
+         <groupId>org.testcontainers</groupId>
+         <artifactId>postgresql</artifactId>
+         <version>1.21.4</version>
+         <scope>test</scope>
+      </dependency>
+      <dependency>
+         <groupId>org.postgresql</groupId>
+         <artifactId>postgresql</artifactId>
+         <version>42.7.14</version>
+         <scope>test</scope>
+      </dependency>
+      <dependency>
+         <groupId>org.junit.jupiter</groupId>
+         <artifactId>junit-jupiter</artifactId>
+         <version>5.11.4</version>
+         <scope>test</scope>
+      </dependency>
+   </dependencies>
+   <build>
+      <plugins>
+         <plugin>
+            <groupId>org.apache.maven.plugins</groupId>
+            <artifactId>maven-checkstyle-plugin</artifactId>
+            <version>3.6.0</version>
+            <dependencies>
+               <dependency>
+                  <groupId>com.puppycrawl.tools</groupId>
+                  <artifactId>checkstyle</artifactId>
+                  <version>14.3.0</version>
+               </dependency>
+            </dependencies>
+            <configuration>
+               <configLocation>${maven.multiModuleProjectDirectory}/checkstyle/checkstyle.xml</configLocation>
+               <consoleOutput>true</consoleOutput>
+               <includeTestSourceDirectory>true</includeTestSourceDirectory>
+               <failOnViolation>true</failOnViolation>
+               <violationSeverity>warning</violationSeverity>
+            </configuration>
+            <executions>
+               <execution>
+                  <id>checkstyle</id>
+                  <phase>validate</phase>
+                  <goals>
+                     <goal>check</goal>
+                  </goals>
+               </execution>
+            </executions>
+         </plugin>
+      </plugins>
+   </build>
+</project>

base/src/main/java/com/kingsrook/qbits/mobilescanners/MobileDeviceActivity.java

@@ -69,11 +69,13 @@ final class MobileDeviceActivity
 
 
    /***************************************************************************
-    ** Preserve last known coordinates with explicit availability and timestamps.
+    ** Preserve last known coordinates with explicit availability and timestamps,
+    ** and refresh reported software versions in the same presence write.
     ***************************************************************************/
-   static void heartbeat(String id, Map<String, Object> input, boolean foreground) throws QException
+   static void heartbeat(QRecord device, Map<String, Object> input, boolean foreground) throws QException
    {
-      QRecord changes = new QRecord().withValue("id", id).withValue("lastSeenAt", Instant.now());
+      QRecord changes = new QRecord().withValue("id", device.getValueString("id")).withValue("lastSeenAt", Instant.now());
+      MobileService.refreshDeviceInfo(device, input, changes);
       String status = MobileService.optional(input, "locationStatus", 30);
       if(status != null && !List.of("AVAILABLE", "PERMISSION_DENIED", "DISABLED", "UNAVAILABLE").contains(status))
       {

base/src/main/java/com/kingsrook/qbits/mobilescanners/MobileScannersUiApi.java

@@ -46,7 +46,7 @@ public final class MobileScannersUiApi
     ***************************************************************************/
    public static MiddlewareSpecExtension extension()
    {
-      return new MiddlewareSpecExtension().withName("mobile-scanners").withSemanticVersion("1.5.0")
+      return new MiddlewareSpecExtension().withName("mobile-scanners").withSemanticVersion("1.6.0")
          .withDescription("Native scanner devices, customer branding and SCANNER process widget contract.")
          .withSpec(MobileBrandingSpec.class).withSpec(MobileStatusSpec.class)
          .withSpec(MobileEnrollSpec.class).withSpec(MobileCurrentDeviceSpec.class)

base/src/main/java/com/kingsrook/qbits/mobilescanners/MobileService.java

@@ -44,6 +44,7 @@ public final class MobileService
 {
    static final ThreadLocal<QBackendTransaction> TRANSACTION = new ThreadLocal<>();
 
+   static final List<String> DEVICE_INFO_FIELDS = List.of("manufacturer", "model", "osVersion", "appVersion");
    static final int AIM_IDENTIFIER_LENGTH = 3;
    static final int RAW_DATA_MAXIMUM_BYTES = 8192;
    static final int RAW_DATA_MAXIMUM_CHARACTERS = 10924;
@@ -78,7 +79,8 @@ public final class MobileService
       QRecord credential = new QRecord().withValue("id", id).withValue("tokenHash", hash(token));
       QRecord device = new QRecord().withValue("id", id).withValue("installationId", id).withValue("status", "PENDING")
          .withValue("enrolledBy", userId()).withValue("enrolledAt", Instant.now());
-      for(String name : new String[] { "displayName", "manufacturer", "model", "osVersion", "appVersion" })
+      device.setValue("displayName", optional(input, "displayName", 200));
+      for(String name : DEVICE_INFO_FIELDS)
       {
          device.setValue(name, optional(input, name, 200));
       }
@@ -567,6 +569,25 @@ public final class MobileService
 
 
 
+   /***************************************************************************
+    ** An updated app or OS reports new versions after enrollment; copy only
+    ** changed, bounded values so scans record the software that produced them.
+    ** Absent, null or blank values never erase what enrollment recorded.
+    ***************************************************************************/
+   static void refreshDeviceInfo(QRecord device, Map<String, ?> input, QRecord changes) throws QException
+   {
+      for(String name : DEVICE_INFO_FIELDS)
+      {
+         String value = optional(input, name, 200);
+         if(value != null && !value.isBlank() && !value.equals(device.getValueString(name)))
+         {
+            changes.setValue(name, value);
+         }
+      }
+   }
+
+
+
    /***************************************************************************
     ** Enforce canonical UUIDs before using them as identifiers.
     ***************************************************************************/

base/src/main/java/com/kingsrook/qbits/mobilescanners/MobileSessionHeartbeatSpec.java

@@ -24,7 +24,7 @@ public class MobileSessionHeartbeatSpec extends MobileDeviceJsonSpec
    {
       return new BasicOperation().withHttpMethod(HttpMethod.POST).withPath(MobileScannersUiApi.PREFIX + "/sessions/heartbeat")
          .withOperationId("mobileScannersSessionHeartbeat").withShortSummary("Report current handheld session activity")
-         .withLongDescription("Binds the current QQQ sign-in to the verified device. Nullable display metadata never grants permissions. Ended sign-ins return 401 and cannot start another mobile session. screenAvailable=false immediately removes the retained frame. Lease duration is expiresAt minus serverTime, not the device clock.");
+         .withLongDescription("Binds the current QQQ sign-in to the verified device. Nullable display metadata never grants permissions. Ended sign-ins return 401 and cannot start another mobile session. screenAvailable=false immediately removes the retained frame. Lease duration is expiresAt minus serverTime, not the device clock. Optional manufacturer, model, osVersion and appVersion refresh the enrolled device record when they differ (1.6); scans recorded afterwards carry the refreshed values.");
    }
 
 

base/src/main/java/com/kingsrook/qbits/mobilescanners/MobileSessionSchemas.java

@@ -52,10 +52,14 @@ final class MobileSessionSchemas
       activity.put("traceId", nullableText(100));
       activity.put("locationStatus", text(30).withEnumValues(List.of("AVAILABLE", "PERMISSION_DENIED", "DISABLED", "UNAVAILABLE")));
       activity.put("location", ref("MobileScannersLocationV1").withNullable(true));
+      for(String field : MobileService.DEVICE_INFO_FIELDS)
+      {
+         activity.put(field, text(200));
+      }
       schemas.put("MobileScannersLocationV1", object("Optional foreground observation with runtime permission. Coordinates are last known, not a guarantee of current position; the server separately records receipt time.", Map.of(
          "latitude", new BoundedIntegerSchema(-90, 90).withType(Type.NUMBER), "longitude", new BoundedIntegerSchema(-180, 180).withType(Type.NUMBER),
          "accuracyMeters", new BoundedIntegerSchema(0, 10000000).withType(Type.NUMBER), "capturedAt", timestamp()), "latitude", "longitude", "accuracyMeters", "capturedAt"));
-      schemas.put("MobileScannersHeartbeatRequestV1", object("Display activity only. Never include form values, barcodes, passwords or raw error messages. JSON maximum 4096 bytes. Omitted captureMode means APP_CONTENT, requiring foreground eligible app pixels. DEVICE_SCREEN requires explicit per-session Android operator consent and may remain available in background. False screenAvailable clears pixels and lease; changing mode invalidates old demand.", activity, "foreground", "screenAvailable"));
+      schemas.put("MobileScannersHeartbeatRequestV1", object("Display activity only. Never include form values, barcodes, passwords or raw error messages. JSON maximum 4096 bytes. Omitted captureMode means APP_CONTENT, requiring foreground eligible app pixels. DEVICE_SCREEN requires explicit per-session Android operator consent and may remain available in background. False screenAvailable clears pixels and lease; changing mode invalidates old demand. Optional manufacturer, model, osVersion and appVersion (1.6) refresh the enrolled device record when they differ, so later scans carry the installed software; omitted or blank values leave stored values unchanged.", activity, "foreground", "screenAvailable"));
       schemas.put("MobileScannersScreenLeaseV1", object("Server-authorized capture demand. Compute remaining duration from expiresAt minus heartbeat serverTime. Sequence is scoped to this lease and resumes at nextSequence after client restart.", Map.of(
          "leaseId", uuid(), "expiresAt", timestamp(), "frameIntervalMillis", integer(1000, 1000), "maxWidth", integer(640, 640),
          "maxHeight", integer(1280, 1280), "maxBytes", integer(262144, 262144), "nextSequence", integer(0, 9007199254740990L), "captureMode", captureMode()),

base/src/main/java/com/kingsrook/qbits/mobilescanners/MobileSessionService.java

@@ -153,7 +153,7 @@ final class MobileSessionService
       String deviceId = currentDevice();
       synchronized(current())
       {
-         MobileService.requireApproved(deviceId);
+         QRecord device = MobileService.requireApproved(deviceId);
          QRecord session = observe(deviceId);
          boolean foreground = bool(input, "foreground");
          MobileCaptureMode mode = MobileCaptureMode.parse(input.get("captureMode"));
@@ -173,7 +173,7 @@ final class MobileSessionService
             changes.setValue(name, MobileService.optional(input, name, 80));
          }
          changes.setValue("traceId", MobileService.optional(input, "traceId", 100));
-         MobileDeviceActivity.heartbeat(deviceId, input, foreground);
+         MobileDeviceActivity.heartbeat(device, input, foreground);
          update(changes);
          String id = session.getValueString("id");
          if(!available)

base/src/main/resources/db/mobile-scanners-postgres.sql

@@ -0,0 +1,92 @@
+-- Copyright (c) 2026 Kingsrook, LLC
+-- SPDX-License-Identifier: Apache-2.0
+
+-- PostgreSQL 17 fresh-install schema for Mobile Scanners: the final state of db/mobile-scanners-h2.sql (the H2 file carries
+-- the upgrade history of older installs, written with H2-only syntax). Physical names are the metadata names, quoted,
+-- and quoted, because QQQ quotes every identifier it issues (case preserved). Idempotent, run by the schema owner
+-- (never the runtime role), which then needs SELECT, INSERT, UPDATE and DELETE on these tables.
+-- mobileScan.aimIdentifier and rawDataBase64 are the Extension 1.5 optional exact capture metadata (NULL = absent).
+
+CREATE TABLE IF NOT EXISTS "mobileDevice" (
+   id VARCHAR(36) PRIMARY KEY,
+   "installationId" VARCHAR(200) NOT NULL,
+   "displayName" VARCHAR(200),
+   manufacturer VARCHAR(200),
+   model VARCHAR(200),
+   "osVersion" VARCHAR(200),
+   "appVersion" VARCHAR(200),
+   status VARCHAR(200) NOT NULL CHECK (status IN ('PENDING', 'APPROVED', 'REVOKED')),
+   "enrolledBy" VARCHAR(200) NOT NULL,
+   "approvedBy" VARCHAR(200),
+   "enrolledAt" TIMESTAMP WITH TIME ZONE NOT NULL,
+   "approvedAt" TIMESTAMP WITH TIME ZONE,
+   "shortName" VARCHAR(32) NOT NULL,
+   description VARCHAR(2000),
+   "lastSeenAt" TIMESTAMP WITH TIME ZONE,
+   "locationStatus" VARCHAR(30),
+   latitude NUMERIC(12,8),
+   longitude NUMERIC(12,8),
+   "accuracyMeters" NUMERIC(18,4),
+   "locationCapturedAt" TIMESTAMP WITH TIME ZONE,
+   "locationReceivedAt" TIMESTAMP WITH TIME ZONE
+);
+CREATE UNIQUE INDEX IF NOT EXISTS mobileDevice_shortName ON "mobileDevice"("shortName");
+CREATE INDEX IF NOT EXISTS mobileDevice_lastSeenAt ON "mobileDevice"("lastSeenAt");
+
+CREATE TABLE IF NOT EXISTS "mobileDeviceCredential" (
+   id VARCHAR(36) PRIMARY KEY,
+   "tokenHash" VARCHAR(64) NOT NULL
+);
+
+CREATE TABLE IF NOT EXISTS "mobileScan" (
+   id VARCHAR(64) PRIMARY KEY,
+   "deviceId" VARCHAR(200) NOT NULL REFERENCES "mobileDevice"(id),
+   "eventId" VARCHAR(200) NOT NULL,
+   "userId" VARCHAR(200) NOT NULL,
+   "appId" VARCHAR(200) NOT NULL,
+   "processName" VARCHAR(200) NOT NULL,
+   barcode VARCHAR(4096) NOT NULL,
+   symbology VARCHAR(200),
+   "scanSource" VARCHAR(200),
+   manufacturer VARCHAR(200),
+   model VARCHAR(200),
+   "osVersion" VARCHAR(200),
+   "appVersion" VARCHAR(200),
+   "capturedAt" TIMESTAMP WITH TIME ZONE NOT NULL,
+   "receivedAt" TIMESTAMP WITH TIME ZONE NOT NULL,
+   "aimIdentifier" VARCHAR(3),
+   "rawDataBase64" VARCHAR(10924)
+);
+
+CREATE TABLE IF NOT EXISTS "mobileSession" (
+   id VARCHAR(36) PRIMARY KEY,
+   "deviceId" VARCHAR(36) NOT NULL REFERENCES "mobileDevice"(id),
+   "userId" VARCHAR(200) NOT NULL,
+   status VARCHAR(20) NOT NULL CHECK (status IN ('ACTIVE', 'ENDED')),
+   "startedAt" TIMESTAMP WITH TIME ZONE NOT NULL,
+   "lastSeenAt" TIMESTAMP WITH TIME ZONE NOT NULL,
+   "endedAt" TIMESTAMP WITH TIME ZONE,
+   "endedBy" VARCHAR(200),
+   "endReason" VARCHAR(200),
+   foreground BOOLEAN,
+   "screenAvailable" BOOLEAN,
+   "captureBlockedReason" VARCHAR(80),
+   "appName" VARCHAR(200),
+   "processName" VARCHAR(200),
+   "processInstanceId" VARCHAR(200),
+   "stepName" VARCHAR(200),
+   "screenLabel" VARCHAR(200),
+   "lastAction" VARCHAR(80),
+   "errorCode" VARCHAR(80),
+   "traceId" VARCHAR(100),
+   "authCleanupStatus" VARCHAR(80),
+   "authCleanupAt" TIMESTAMP WITH TIME ZONE,
+   "captureMode" VARCHAR(20) DEFAULT 'APP_CONTENT'
+);
+CREATE INDEX IF NOT EXISTS mobileSession_device ON "mobileSession"("deviceId", "startedAt");
+
+CREATE TABLE IF NOT EXISTS "mobileSessionBinding" (
+   id VARCHAR(64) PRIMARY KEY,
+   "sessionId" VARCHAR(36) NOT NULL UNIQUE REFERENCES "mobileSession"(id),
+   "coreSessionUuid" VARCHAR(200) NOT NULL
+);

base/src/test/java/com/kingsrook/qbits/mobilescanners/MobileScannersApiContractTest.java

@@ -64,9 +64,19 @@ class MobileScannersApiContractTest
          assertTrue(model.getComponents().getSchemas().containsKey(schema), schema);
       }
       assertEquals(7, extension.getSpecs().size());
-      assertEquals("1.5.0", extension.getSemanticVersion());
-      assertEquals(java.util.List.of(), UiApiContract.check(generated, Files.readString(contract), Files.readString(Path.of("src/test/resources/openapi/mobile-scanners-1.4.0.yaml")), 1,
-         "Regenerate the current extension contract."));
+      assertEquals("1.6.0", extension.getSemanticVersion());
+      for(String previous : java.util.List.of("1.4.0", "1.5.0", "1.6.0"))
+      {
+         assertEquals(java.util.List.of(), UiApiContract.check(generated, Files.readString(contract), Files.readString(Path.of("src/test/resources/openapi/mobile-scanners-" + previous + ".yaml")), 1,
+            "Regenerate the current extension contract."));
+      }
+      var heartbeatRequest = model.getComponents().getSchemas().get("MobileScannersHeartbeatRequestV1");
+      for(String optional : MobileService.DEVICE_INFO_FIELDS)
+      {
+         assertTrue(heartbeatRequest.getProperties().containsKey(optional), optional);
+         assertEquals(200, heartbeatRequest.getProperties().get(optional).getMaxLength(), optional);
+         assertFalse(generated.contains("- \"" + optional + "\""), optional + " must stay optional, never a required key.");
+      }
       var scanEvent = model.getComponents().getSchemas().get("MobileScannersScanEventV1");
       var scanContext = model.getComponents().getSchemas().get("MobileScannersScanContextV1");
       for(String optional : java.util.List.of("aimIdentifier", "rawDataBase64"))

base/src/test/java/com/kingsrook/qbits/mobilescanners/MobileScannersTest.java

@@ -26,6 +26,7 @@ import com.kingsrook.qqq.backend.core.actions.tables.InsertAction;
 import com.kingsrook.qqq.backend.core.actions.tables.QueryAction;
 import com.kingsrook.qqq.backend.core.actions.tables.UpdateAction;
 import com.kingsrook.qqq.backend.core.context.QContext;
+import com.kingsrook.qqq.backend.core.exceptions.QBadRequestException;
 import com.kingsrook.qqq.backend.core.exceptions.QException;
 import com.kingsrook.qqq.backend.core.instances.QInstanceValidator;
 import com.kingsrook.qqq.backend.core.model.actions.processes.RunBackendStepInput;
@@ -75,6 +76,86 @@ class MobileScannersTest
 
 
 
+   /***************************************************************************
+    ** Each test receives an isolated database using the shipped schema.
+    ***************************************************************************/
+   /***************************************************************************
+    ** PostgreSQL 17 variant (opt-in with -Dmobile.pg=true): one fresh database per test in a
+    ** Testcontainers PostgreSQL; the schema is the shipped PostgreSQL file.
+    ***************************************************************************/
+   private static org.testcontainers.containers.PostgreSQLContainer<?> postgres;
+   private String dbUser = "sa";
+   private String dbPassword = "";
+   private String schemaResource = "/db/mobile-scanners-h2.sql";
+   private boolean pg;
+
+   /***************************************************************************
+    ** QQQ quotes every identifier it issues, so direct SQL against the PostgreSQL schema
+    ** must quote the camelCase names too (string literals are left alone).
+    ***************************************************************************/
+   private String q(String statement)
+   {
+      if(!pg)
+      {
+         return (statement);
+      }
+      java.util.regex.Matcher literals = java.util.regex.Pattern.compile("('(?:[^']|'')*')|\\b([a-z]+(?:[A-Z][A-Za-z0-9]*)+)\\b").matcher(statement);
+      StringBuilder result = new StringBuilder();
+      while(literals.find())
+      {
+         literals.appendReplacement(result, java.util.regex.Matcher.quoteReplacement(literals.group(1) != null ? literals.group(1) : "\"" + literals.group(2) + "\""));
+      }
+      literals.appendTail(result);
+      return (result.toString());
+   }
+
+   /***************************************************************************
+    ** Choose H2 or the PostgreSQL container for this test.
+    ***************************************************************************/
+   private void selectDatabase() throws Exception
+   {
+      pg = "true".equals(System.getProperty("mobile.pg"));
+      if(!pg)
+      {
+         jdbcUrl = "jdbc:h2:mem:mobile_" + UUID.randomUUID().toString().replace("-", "") + ";DATABASE_TO_UPPER=FALSE;DB_CLOSE_DELAY=-1";
+         return;
+      }
+      synchronized(MobileScannersTest.class)
+      {
+         if(postgres == null)
+         {
+            postgres = new org.testcontainers.containers.PostgreSQLContainer<>("postgres:17-alpine");
+            postgres.start();
+         }
+      }
+      String database = "mobile_" + UUID.randomUUID().toString().replace("-", "");
+      try(Connection admin = DriverManager.getConnection(postgres.getJdbcUrl(), postgres.getUsername(), postgres.getPassword()))
+      {
+         admin.createStatement().execute("CREATE DATABASE " + database);
+      }
+      jdbcUrl = postgres.getJdbcUrl().replaceFirst("/[^/?]+(\\?|$)", "/" + database + "$1");
+      dbUser = postgres.getUsername();
+      dbPassword = postgres.getPassword();
+      schemaResource = "/db/mobile-scanners-postgres.sql";
+   }
+
+   /***************************************************************************
+    ** The backend metadata for the selected database.
+    ***************************************************************************/
+   private com.kingsrook.qqq.backend.core.model.metadata.QBackendMetaData backendMetaData()
+   {
+      if(!pg)
+      {
+         return (new RDBMSBackendMetaData().withName("db").withVendor("h2").withJdbcUrl(jdbcUrl).withUsername("sa"));
+      }
+      var backend = new com.kingsrook.qqq.backend.module.postgres.model.metadata.PostgreSQLBackendMetaData();
+      backend.setName("db");
+      backend.setJdbcUrl(jdbcUrl);
+      backend.setUsername(dbUser);
+      backend.setPassword(dbPassword);
+      return (backend);
+   }
+
    /***************************************************************************
     ** Each test receives an isolated database using the shipped schema.
     ***************************************************************************/
@@ -82,20 +163,20 @@ class MobileScannersTest
    void setup() throws Exception
    {
       com.kingsrook.qqq.backend.module.rdbms.jdbc.ConnectionManager.resetConnectionProviders();
-      jdbcUrl = "jdbc:h2:mem:mobile_" + UUID.randomUUID().toString().replace("-", "") + ";DATABASE_TO_UPPER=FALSE;DB_CLOSE_DELAY=-1";
+      selectDatabase();
       instance = new QInstance();
       instance.setEnforcePermissionsInCoreActions(true);
       instance.registerAuthenticationProvider(AuthScope.instanceDefault(), new QAuthenticationMetaData().withName("test").withType(QAuthenticationType.MOCK));
-      instance.addBackend(new RDBMSBackendMetaData().withName("db").withVendor("h2").withJdbcUrl(jdbcUrl).withUsername("sa"));
+      instance.addBackend(backendMetaData());
       new MobileScannersQBitProducer().withConfig(new MobileScannersQBitConfig().withBackendName("db")).produce(instance, "mobile");
       for(var table : instance.getTables().values())
       {
          table.setBackendDetails(new RDBMSTableBackendDetails().withTableName(table.getName()));
       }
       new QInstanceValidator().validate(instance);
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
       {
-         String schema = new String(getClass().getResourceAsStream("/db/mobile-scanners-h2.sql").readAllBytes(), StandardCharsets.UTF_8);
+         String schema = new String(getClass().getResourceAsStream(schemaResource).readAllBytes(), StandardCharsets.UTF_8);
          for(String statement : schema.split(";"))
          {
             if(!statement.isBlank())
@@ -426,9 +507,9 @@ class MobileScannersTest
       assertThrows(QException.class, () -> MobileService.capture(input));
       input.put("eventId", UUID.randomUUID().toString());
       assertNotEquals(first.getValueString("id"), MobileService.capture(input).getValueString("id"));
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
       {
-         var result = connection.createStatement().executeQuery("SELECT COUNT(*) FROM mobileScan");
+         var result = connection.createStatement().executeQuery(q("SELECT COUNT(*) FROM mobileScan"));
          assertTrue(result.next());
          assertEquals(2, result.getInt(1));
       }
@@ -473,8 +554,8 @@ class MobileScannersTest
       QRecord saved = MobileService.capture(input);
       assertEquals("UNKNOWN", saved.getValueString("symbology"));
       assertEquals("UNKNOWN", saved.getValueString("scanSource"));
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", "");
-         var statement = connection.prepareStatement("UPDATE mobileScan SET symbology = NULL, scanSource = NULL WHERE id = ?"))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword);
+         var statement = connection.prepareStatement(q("UPDATE mobileScan SET symbology = NULL, scanSource = NULL WHERE id = ?")))
       {
          statement.setString(1, saved.getValueString("id"));
          assertEquals(1, statement.executeUpdate());
@@ -664,8 +745,8 @@ class MobileScannersTest
     ***************************************************************************/
    private int scanRows() throws Exception
    {
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", "");
-         var statement = connection.createStatement(); var rows = statement.executeQuery("SELECT COUNT(*) FROM mobileScan"))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword);
+         var statement = connection.createStatement(); var rows = statement.executeQuery(q("SELECT COUNT(*) FROM mobileScan")))
       {
          assertTrue(rows.next());
          return rows.getInt(1);
@@ -687,8 +768,8 @@ class MobileScannersTest
       input.addValue("symbology", "QR_CODE");
       assertTrue(assertThrows(QException.class, () -> MobileScannerActions.capture(input)).getMessage().contains("Restart the scanner process"));
       assertThrows(QException.class, () -> MobileScannerActions.capture(input));
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", "");
-         var statement = connection.createStatement(); var rows = statement.executeQuery("SELECT COUNT(*) FROM mobileScan"))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword);
+         var statement = connection.createStatement(); var rows = statement.executeQuery(q("SELECT COUNT(*) FROM mobileScan")))
       {
          assertTrue(rows.next());
          assertEquals(0, rows.getInt(1));
@@ -811,9 +892,9 @@ class MobileScannersTest
       {
          assertEquals(savedId, future.get());
       }
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
       {
-         var result = connection.createStatement().executeQuery("SELECT COUNT(*) FROM mobileScan");
+         var result = connection.createStatement().executeQuery(q("SELECT COUNT(*) FROM mobileScan"));
          assertTrue(result.next());
          assertEquals(1, result.getInt(1));
       }
@@ -850,9 +931,9 @@ class MobileScannersTest
    void interruptedEnrollmentRequiresNewInstallationIdentity() throws Exception
    {
       String id = UUID.randomUUID().toString();
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
       {
-         var statement = connection.prepareStatement("INSERT INTO mobileDeviceCredential(id, tokenHash) VALUES (?, ?)");
+         var statement = connection.prepareStatement(q("INSERT INTO mobileDeviceCredential(id, tokenHash) VALUES (?, ?)"));
          statement.setString(1, id);
          statement.setString(2, "0".repeat(64));
          statement.executeUpdate();
@@ -862,6 +943,93 @@ class MobileScannersTest
 
 
 
+   /***************************************************************************
+    ** Enrollment records the installed software; heartbeats without versions,
+    ** or with blank ones, leave it unchanged and scans copy it.
+    ***************************************************************************/
+   @Test
+   void enrollmentStoresVersionsAndHeartbeatWithoutThemLeavesThemUnchanged() throws Exception
+   {
+      String device = approvedDevice(Map.of("osVersion", "14", "appVersion", "1.0.0"));
+      QRecord enrolled = MobileService.get(MobileScannersQBitProducer.DEVICE, device);
+      assertEquals("Zebra", enrolled.getValueString("manufacturer"));
+      assertEquals("TC22", enrolled.getValueString("model"));
+      assertEquals("14", enrolled.getValueString("osVersion"));
+      assertEquals("1.0.0", enrolled.getValueString("appVersion"));
+      bind(device);
+      MobileSessionService.heartbeat(Map.of("foreground", true, "screenAvailable", false));
+      MobileSessionService.heartbeat(new HashMap<>(Map.of("foreground", true, "screenAvailable", false, "appVersion", "", "osVersion", " ")));
+      QRecord unchanged = MobileService.get(MobileScannersQBitProducer.DEVICE, device);
+      for(String field : MobileService.DEVICE_INFO_FIELDS)
+      {
+         assertEquals(enrolled.getValueString(field), unchanged.getValueString(field), field);
+      }
+      QRecord scan = MobileService.capture(scan());
+      assertEquals("1.0.0", scan.getValueString("appVersion"));
+      assertEquals("14", scan.getValueString("osVersion"));
+      assertEquals("Zebra", scan.getValueString("manufacturer"));
+      assertEquals("TC22", scan.getValueString("model"));
+   }
+
+
+
+   /***************************************************************************
+    ** An in-place app update reports its new version on the next heartbeat and
+    ** every later scan carries it; earlier scans keep the version that made them.
+    ***************************************************************************/
+   @Test
+   void heartbeatRefreshesDeviceVersionsForLaterScans() throws Exception
+   {
+      String device = approvedDevice(Map.of("osVersion", "14", "appVersion", "1.0.0"));
+      bind(device);
+      QRecord before = MobileService.capture(scan());
+      assertEquals("1.0.0", before.getValueString("appVersion"));
+      MobileSessionService.heartbeat(Map.of("foreground", true, "screenAvailable", false, "appVersion", "1.0.1", "osVersion", "15"));
+      QRecord updated = MobileService.get(MobileScannersQBitProducer.DEVICE, device);
+      assertEquals("1.0.1", updated.getValueString("appVersion"));
+      assertEquals("15", updated.getValueString("osVersion"));
+      assertEquals("Zebra", updated.getValueString("manufacturer"));
+      assertEquals("TC22", updated.getValueString("model"));
+      assertEquals("APPROVED", updated.getValueString("status"));
+      QRecord after = MobileService.capture(scan());
+      assertEquals("1.0.1", after.getValueString("appVersion"));
+      assertEquals("15", after.getValueString("osVersion"));
+      assertEquals("1.0.0", MobileService.get(MobileScannersQBitProducer.SCAN, before.getValueString("id")).getValueString("appVersion"));
+      MobileSessionService.heartbeat(Map.of("foreground", true, "screenAvailable", false, "manufacturer", "Zebra Technologies", "model", "MC9400"));
+      QRecord hardware = MobileService.get(MobileScannersQBitProducer.DEVICE, device);
+      assertEquals("Zebra Technologies", hardware.getValueString("manufacturer"));
+      assertEquals("MC9400", hardware.getValueString("model"));
+      assertEquals("1.0.1", hardware.getValueString("appVersion"));
+      assertEquals("MC9400", MobileService.capture(scan()).getValueString("model"));
+   }
+
+
+
+   /***************************************************************************
+    ** Heartbeat versions obey the enrollment limits: strings of at most 200
+    ** characters; anything else is a 400 and the device record is untouched.
+    ***************************************************************************/
+   @Test
+   void heartbeatRejectsInvalidDeviceVersionsLikeEnrollment() throws Exception
+   {
+      String tooLong = "v".repeat(201);
+      String longest = "v".repeat(200);
+      assertThrows(QBadRequestException.class, () -> MobileService.enroll(Map.of("installationId", UUID.randomUUID().toString(), "appVersion", tooLong)));
+      String device = approvedDevice(Map.of("osVersion", "14", "appVersion", "1.0.0"));
+      bind(device);
+      assertThrows(QBadRequestException.class, () -> MobileSessionService.heartbeat(Map.of("foreground", true, "screenAvailable", false, "appVersion", tooLong)));
+      assertThrows(QBadRequestException.class, () -> MobileSessionService.heartbeat(Map.of("foreground", true, "screenAvailable", false, "osVersion", 15)));
+      QRecord unchanged = MobileService.get(MobileScannersQBitProducer.DEVICE, device);
+      assertEquals("1.0.0", unchanged.getValueString("appVersion"));
+      assertEquals("14", unchanged.getValueString("osVersion"));
+      assertEquals("1.0.0", MobileService.capture(scan()).getValueString("appVersion"));
+      MobileSessionService.heartbeat(Map.of("foreground", true, "screenAvailable", false, "appVersion", longest));
+      assertEquals(longest, MobileService.get(MobileScannersQBitProducer.DEVICE, device).getValueString("appVersion"));
+      assertEquals(longest, MobileService.capture(scan()).getValueString("appVersion"));
+   }
+
+
+
    /***************************************************************************
     ** A realistic installation, with no hardware identifier requirement.
     ***************************************************************************/
@@ -1066,9 +1234,9 @@ class MobileScannersTest
     ***************************************************************************/
    private String deviceStatus(String id) throws Exception
    {
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
       {
-         var statement = connection.prepareStatement("SELECT status FROM mobileDevice WHERE id = ?");
+         var statement = connection.prepareStatement(q("SELECT status FROM mobileDevice WHERE id = ?"));
          statement.setString(1, id);
          var rows = statement.executeQuery();
          assertTrue(rows.next());
@@ -1083,7 +1251,19 @@ class MobileScannersTest
     ***************************************************************************/
    private String approvedDevice() throws QException
    {
-      String id = (String) enroll().get("deviceId");
+      return approvedDevice(Map.of());
+   }
+
+
+
+   /***************************************************************************
+    ** Approve an enrollment that also reported its software versions.
+    ***************************************************************************/
+   private String approvedDevice(Map<String, Object> versions) throws QException
+   {
+      Map<String, Object> enrollment = new HashMap<>(Map.of("installationId", UUID.randomUUID().toString(), "displayName", "Test TC22", "manufacturer", "Zebra", "model", "TC22"));
+      enrollment.putAll(versions);
+      String id = (String) MobileService.enroll(enrollment).get("deviceId");
       QContext.init(instance, admin);
       MobileService.setApproval(id, true);
       QContext.init(instance, scanner);
@@ -1280,9 +1460,9 @@ class MobileScannersTest
       var selected = new QueryInput().withTableName(MobileScannersQBitProducer.DEVICE)
          .withFieldNamesToInclude(java.util.Set.of("id", "online"));
       assertEquals(true, new QueryAction().execute(selected).getRecords().getFirst().getValueBoolean("online"));
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
       {
-         connection.createStatement().executeUpdate("UPDATE mobileDevice SET lastSeenAt = TIMESTAMP WITH TIME ZONE '2000-01-01 00:00:00+00:00'");
+         connection.createStatement().executeUpdate(q("UPDATE mobileDevice SET lastSeenAt = TIMESTAMP WITH TIME ZONE '2000-01-01 00:00:00+00:00'"));
       }
       QContext.init(instance, admin);
       var query = new QueryInput().withTableName(MobileScannersQBitProducer.DEVICE)
@@ -1336,12 +1516,13 @@ class MobileScannersTest
    @Test
    void migrationRemovesOnlyOrphanedCredentials() throws Exception
    {
+      org.junit.jupiter.api.Assumptions.assumeFalse(pg, "H2 upgrade-history migration; the PostgreSQL schema is a fresh install only");
       Map<String, Object> valid = enroll();
       String orphan = UUID.randomUUID().toString();
       MobileService.insert(MobileScannersQBitProducer.CREDENTIAL, new QRecord().withValue("id", orphan).withValue("tokenHash", MobileService.hash("never-returned")));
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
       {
-         String schema = new String(getClass().getResourceAsStream("/db/mobile-scanners-h2.sql").readAllBytes(), StandardCharsets.UTF_8);
+         String schema = new String(getClass().getResourceAsStream(schemaResource).readAllBytes(), StandardCharsets.UTF_8);
          for(String statement : schema.split(";"))
          {
             if(!statement.isBlank())
@@ -1363,17 +1544,18 @@ class MobileScannersTest
    @Test
    void generatedNamesAndMigrationSurvivePrefixCollisions() throws Exception
    {
+      org.junit.jupiter.api.Assumptions.assumeFalse(pg, "H2 upgrade-history migration; the PostgreSQL schema is a fresh install only");
       String firstId = "12345678-1234-4234-8234-123400000001";
       String secondId = "12345678-1234-4234-8234-123400000002";
       Map<String, Object> first = MobileService.enroll(Map.of("installationId", firstId));
       Map<String, Object> second = MobileService.enroll(Map.of("installationId", secondId));
       assertNotEquals(first.get("shortName"), second.get("shortName"));
       Map<String, Object> custom = MobileService.enroll(Map.of("installationId", UUID.randomUUID().toString(), "shortName", "scanner-1"));
-      try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""); var sql = connection.createStatement())
+      try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword); var sql = connection.createStatement())
       {
-         sql.execute("DROP INDEX mobileDevice_shortName");
-         sql.execute("UPDATE mobileDevice SET shortName = 'scanner-123456781234423482341234' WHERE id IN ('" + firstId + "', '" + secondId + "')");
-         String schema = new String(getClass().getResourceAsStream("/db/mobile-scanners-h2.sql").readAllBytes(), StandardCharsets.UTF_8);
+         sql.execute(q("DROP INDEX mobileDevice_shortName"));
+         sql.execute(q("UPDATE mobileDevice SET shortName = 'scanner-123456781234423482341234' WHERE id IN ('") + firstId + "', '" + secondId + "')");
+         String schema = new String(getClass().getResourceAsStream(schemaResource).readAllBytes(), StandardCharsets.UTF_8);
          for(int pass = 0; pass < 2; pass++)
          {
             for(String statement : schema.split(";"))
@@ -1400,6 +1582,7 @@ class MobileScannersTest
    @Test
    void timestampRoundTripsOutsideUtcAndPresenceExpires() throws Exception
    {
+      org.junit.jupiter.api.Assumptions.assumeFalse(pg, "changes the JVM default zone; a PostgreSQL deployment must run a UTC JVM (the owner PostgreSQL qualifiers require it) and the host refuses to start otherwise");
       java.util.TimeZone previous = java.util.TimeZone.getDefault();
       try
       {
@@ -1413,9 +1596,9 @@ class MobileScannersTest
          QRecord record = MobileService.get(MobileScannersQBitProducer.DEVICE, device);
          assertEquals(captured, record.getValueInstant("locationCapturedAt"));
          assertTrue(java.time.Duration.between(record.getValueInstant("lastSeenAt"), java.time.Instant.now()).abs().getSeconds() < 2);
-         try(Connection connection = DriverManager.getConnection(jdbcUrl, "sa", ""))
+         try(Connection connection = DriverManager.getConnection(jdbcUrl, dbUser, dbPassword))
          {
-            connection.createStatement().executeUpdate("UPDATE mobileDevice SET lastSeenAt = TIMESTAMP '2000-01-01 00:00:00'");
+            connection.createStatement().executeUpdate(q("UPDATE mobileDevice SET lastSeenAt = TIMESTAMP '2000-01-01 00:00:00'"));
          }
          assertEquals(false, MobileService.get(MobileScannersQBitProducer.DEVICE, device).getValueBoolean("online"));
       }

demo/pom.xml

@@ -7,7 +7,7 @@
    <properties>
       <maven.compiler.release>21</maven.compiler.release>
       <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-      <qqq.version>4.1.0-RC.21</qqq.version>
+      <qqq.version>4.1.0-RC.26</qqq.version>
    </properties>
    <dependencyManagement>
       <dependencies>
@@ -34,7 +34,7 @@
       <dependency>
          <groupId>com.kingsrook.qqq</groupId>
          <artifactId>qqq-frontend-next</artifactId>
-         <version>1.0.0-RC.35</version>
+         <version>1.0.0-RC.38</version>
       </dependency>
       <dependency>
          <groupId>com.h2database</groupId>
@@ -78,7 +78,7 @@
          <plugin>
             <groupId>org.apache.maven.plugins</groupId>
             <artifactId>maven-surefire-plugin</artifactId>
-            <version>3.5.2</version>
+            <version>3.5.6</version>
             <configuration>
                <systemPropertyVariables>
                   <qqq.logger.logSessionId.disabled>true</qqq.logger.logSessionId.disabled>

demo/src/test/java/com/kingsrook/qbits/mobilescanners/demo/MobileHttpAcceptanceTest.java

@@ -773,7 +773,7 @@ class MobileHttpAcceptanceTest
          }
       }
       assertNotNull(mobile);
-      assertEquals("1.5.0", mobile.getString("version"));
+      assertEquals("1.6.0", mobile.getString("version"));
       assertEquals("/qbit/mobile-scanners", mobile.getString("pathPrefix"));
       var openApiResponse = request("GET", "/qqq/v1/openapi.json", null, null, device);
       assertEquals(200, openApiResponse.statusCode());

docs/CI-CD.md

@@ -22,11 +22,17 @@ Run the same project checks locally with `./mvnw verify install` and `./mvnw -f
 
 For workflow syntax, run `actionlint .github/workflows/codeql.yml .github/workflows/demo-acceptance.yml`. Validate the setup caller with `circleci config validate --org gh/QRun-IO .circleci/config.yml`, using your existing CircleCI authentication. The shared orb is private; without organization scope and authorization, the compiler can report that it cannot find the orb. Do not place tokens in config files or command arguments.
 
-## Initial publishing policy
+## Development snapshot publication (enabled, November 3)
 
-Every `publish` switch and `release_completion` is explicitly false. Branch pushes, including initial `main`/`develop` pushes, and `vX.Y.Z` tags perform verification without deploying Maven artifacts. There is no automatic RC-cut workflow in this bootstrap configuration. GitHub test-report artifacts are diagnostic outputs, not releases.
+PR 7 merged as `795a0a2`; its post-merge run 3607 on `develop` passed but captured nothing because `publish.snapshot` was false. PR 12 set only `publish.snapshot: true` in `.qqq-ci.yml` and merged as `286e2e0`. Run 3645 succeeded and the snapshot `0.1.0-20261103.233448-3645` was read back anonymously from Central (JAR, POM, sources and Javadocs; the 37 published Java source files match the reviewed source). PR 13 (`1345197`, Echo defaults to released Printing `1.0.0`) then passed CI runs 4157 and 4158.
 
-To enable publishing later, submit a reviewed change to the manifest after TC22 acceptance and production readiness work are complete. Choose the intended snapshot/RC/GA policy; verify the organization registry context, signing configuration and Maven coordinates. Add the then-current shared `qbit-release-rc.yml` caller pinned to an immutable commit before enabling `release_completion`. Update protections and documentation using observed checks from successful hosted runs. Creating a repository does not itself authorize artifact publication.
+`develop` builds therefore publish development snapshots. Every other publication value is unchanged: `publish.release_candidate`, `release`, `feature`, `hotfix` and `asciidoc`, `release_on_main` and `release_completion` stay false, and the orb stays on `0.8`. A snapshot is not a stable release or a promotion to `main`, and source publication does not equal production 1.0.
+
+## Initial publishing policy (historical bootstrap)
+
+At bootstrap, every `publish` switch and `release_completion` was explicitly false; only the snapshot switch has since changed (above). Branch pushes, including initial `main`/`develop` pushes, and `vX.Y.Z` tags perform verification without deploying Maven artifacts. There is no automatic RC-cut workflow in this bootstrap configuration. GitHub test-report artifacts are diagnostic outputs, not releases.
+
+RC and stable publication still require a reviewed manifest change after TC22 acceptance and production readiness work are complete. Verify the organization registry context, signing configuration and Maven coordinates. Add the then-current shared `qbit-release-rc.yml` caller pinned to an immutable commit before enabling `release_completion`. Update protections and documentation using observed checks from successful hosted runs. The development-snapshot change above does not enable these release paths. The local demo does not depend on any of this pipeline.
 
 ## Repository settings
 

docs/GS1-RECORD-PHOTOS-PLAN.md

@@ -0,0 +1,51 @@
+# GS1 duplication and mobile records
+
+Active work requested November 4, 2026. Implementation and isolated acceptance are underway; deployment and physical qualification remain separate.
+
+## First delivery: GS1-128 duplication
+
+- Preserve the original scanned payload, AIM identifier and available raw evidence.
+- Convert supported GS1 element strings to the renderer's canonical GS1 input without guessing missing separators.
+- Print a GS1-128 symbol and its human-readable interpretation underneath, preserving leading zeroes and application identifiers.
+- Verify independent decoding of the rendered output, retry behavior, permissions and refusal of ambiguous inputs.
+- Qualify the actual label/media/printer and handheld path before claiming tomorrow's workflow ready.
+
+## Native records and photos
+
+- Discover permitted tables through existing semantic metadata.
+- Browse records and open record details through existing versioned query/read operations.
+- Offer camera/gallery attachment only when Record Files authorizes that exact record.
+- Reuse the native upload implementation and committed receipt checks; cover denied records, cancellation and retries with isolated native/server E2E tests.
+
+## Remaining readiness work
+
+1. Establish the intended HTTPS host and standalone connectivity.
+2. Qualify the existing signed APK and an enrollment-preserving update path.
+3. Verify an actual MC9400 trigger and persisted record (operator action required).
+4. Adopt published, coherent owner dependencies when available; do not invent versions.
+5. Qualify native provider login, logout and account switching against the configured provider.
+6. Document and exercise database migration, backup/recovery and retention for the selected deployment.
+7. Run final server/browser/native gates on the resulting revision and reconcile release documentation.
+8. Deliver the GS1 profile above before considering broader barcode profiles.
+
+## Constraints
+
+Preserve the user's database, accounts, enrollment and printer setup. Use isolated test databases and application IDs. No offline queue or replacement screen framework. Source checks cannot establish physical scanning/printing. Do not publish artifacts or promote a stable release as part of a test run.
+
+## Verified November 4
+
+- Scanner/base-demo/Echo reactor: 135 tests passed, including GS1 raw evidence, retry identity, derived HRI, metadata discovery and read-only permission regressions. Checkstyle passed.
+- Final composed cohort: 188 tests passed (scanner 53, base demo 8, Record Files 18, Echo 74, Echo demo 35), with Checkstyle, using the previously qualified owner dependency versions in an isolated copy. No POM publication coordinates were changed.
+- Android core/mobileapp/host unit tests, lint and debug/E2E APK builds passed; eight test-runner guard tests passed.
+- Disposable MC9400 native Echo acceptance passed with synthetic Code128, QR and GS1-128 events, one job per event, rotation/recreation, run cancellation and saved-record browsing. All requests matched the published semantic API. Printing was simulated; this does not qualify the physical trigger.
+- Disposable MC9400 record-details acceptance saved synthetic camera and gallery photos to the selected record through the real Record Files APIs. Pending-photo rotation, navigation blocking and remote-logout cleanup passed. The existing process-based photo flow also passed the same camera/gallery and lifecycle regression.
+- Actual renderer output independently decoded for synthetic GTIN/date/serial and separator-bearing batch/serial examples on 4-by-1-inch, 300-dpi media; HRI matched and did not overlap the symbol.
+
+## Deployment and migration gate
+
+Before updating the maintained demo, stop its owning process cleanly and back up the closed database, attachment files and configuration together. Preserve accounts, device enrollment, printer settings and template revisions. Apply the additive nullable `rendererValue` and `humanReadable` columns in `echo-h2.sql`; existing scans keep their original values and are not backfilled or reprinted. Verify the backup can be restored into an isolated directory and start only that restored copy for the recovery check.
+
+Publish a separately named GS1 document using `EchoTemplatePublisher.publishGs1` for the printer's reported media profile. Existing plain documents remain valid for their original profiles. Use the matching GS1 document for the sample label, print one copy, then scan that output and compare exact GS1 data and visible HRI. Do not declare physical acceptance from a synthetic broadcast or renderer-only result. Printer/media confirmation, deployment authorization, HTTPS configuration and the remaining readiness gates above are outstanding.
+## Forge source publication
+
+Server source commit `1874c64` merged through PR 15 as `f9b0eb2` after Gitea checks 4318 and 4319 succeeded. Signed tag `echo-gs1-source-20261104` pins that exact merged tree. The Gitea prerelease includes a source archive, checksum and verification receipt. Forge must include `examples/echo` explicitly; publishing the root scanner JAR alone does not include GS1 duplication. This is a source integration release, not an Echo Maven or APK release. No Forge or handheld deployment was performed.

docs/LOCAL-DEMO.md

@@ -1,46 +1,72 @@
 # Run the local demo on Windows
 
-Install Java 21, PowerShell 7, and the Android SDK. Start the server from this repository:
+The local demo runs on your workstation, binds only to loopback and is independent of the shared CI pipeline. There are two launchers; pick by what you want to try.
+
+| | Basic Scan Capture demo | Full Echo demo (all qbits) |
+| --- | --- | --- |
+| Starts | `scripts/Start-Demo.ps1` | `EchoDemo` or `TrustedLocalEchoDemo` from [`examples/echo/demo`](../examples/echo/demo/README.md) |
+| Contains | Mobile Scanners only: enrollment, approval, the **Scan Capture** app, device sessions, barcode scan table | Mobile Scanners plus Echo, Collaboration/Record Files, Document Generation and Printing in one server |
+| Try it for | Login, device approval, scanning and storing barcodes | Scan, render and print a label (the Echo app), scan photos |
+| Port | `-Port` parameter, script default `8080` | No default: pass a port argument or set `ECHO_DEMO_PORT` |
+| Setup | Java 21 and PowerShell 7 | Also a Printing tenant, a printing agent and printer, Docker for the renderer and published Echo templates; see its README |
+| Accounts | Generated on first start, kept in a per-user protected file | Reuses the basic demo's accounts when started on an existing database |
+
+The maintained local server in this project uses the full Echo launcher in its existing-database mode. That mode is the only one that accepts host port `57832`; fresh demos refuse it. See [adopting the existing local server](../examples/echo/demo/docs/LOCAL-SERVER-ADOPTION.md).
+
+## Basic Scan Capture demo
+
+Install Java 21, PowerShell 7 and the Android SDK, then from this repository:
 
 ```powershell
 pwsh -File scripts/Start-Demo.ps1
 ```
 
-The launcher verifies both Maven projects, then keeps the server running at <http://127.0.0.1:8080/>. Stop it with Ctrl+C. After a successful build, `-SkipBuild` starts it directly. If port 8080 is unavailable, use `-Port 18080` and open <http://127.0.0.1:18080/>. The database persists under `demo/data`; the server binds only to loopback.
+The launcher verifies both Maven projects, then keeps the server running at <http://127.0.0.1:8080/>. Stop it with Ctrl+C. After a successful build, `-SkipBuild` starts it directly. If port 8080 is unavailable, use `-Port 18080` (or another port) and open that address. The database persists under `demo/data`.
 
-Before upgrading an existing demo database, stop its JVM gracefully and back up the closed `demo/data` directory together with its protected credential file. The shared H2 schema begins with `SET TIME ZONE 'UTC'` before converting legacy `TIMESTAMP WITH TIME ZONE` columns to the current UTC `TIMESTAMP` representation. This protects both the demo initializer and hosts executing the supplied schema directly. It preserves the original instants independently of the workstation time zone; rerunning initialization preserves existing accounts, passwords, device approval and scans. Do not copy over an open H2 database or use an account reset as an upgrade step. The schema leaves its migration connection in UTC; hosts should use a dedicated migration connection or restore their desired connection zone after the entire script completes.
+First startup creates random passwords for the `admin` and `scanner` accounts. They are protected with Windows DPAPI under `%LOCALAPPDATA%/QRunIO/MobileScannersDemo/credentials.clixml`, readable only by the same Windows user, and are never written to the repository or printed. The launcher never changes existing passwords. If a database exists without its credential file, it refuses to start rather than reset accounts.
 
-Use the matching Android build with the [mobile-scanners semantic API extension](UI-API.md). Public discovery is at `/qqq/v1/version`; the extension's connectivity endpoint is `/qqq/v1/qbit/mobile-scanners/status`. This migration removes the former standalone mobile routes, so upgrade the local server and APK together. Installing the APK with `adb install -r` and restarting the server preserves the existing application data and database; no account or device reset is required.
-
-First startup creates random passwords for the `admin` and `scanner` accounts. The launcher stores them using Windows DPAPI under `%LOCALAPPDATA%/QRunIO/MobileScannersDemo/credentials.clixml`, readable only through the same Windows user/machine protection. They are never written to the repository or printed. Keep that credential file with this local database; the launcher never changes existing account passwords.
-
-In another PowerShell window, copy the admin password when ready to log into the browser:
+To sign in without ever displaying a password, use the helper from another PowerShell window:
 
 ```powershell
 pwsh -File scripts/Copy-DemoPassword.ps1 -Account admin
 ```
 
-Sign in with username `admin`, paste the password, then clear the clipboard with `Set-Clipboard -Value ''`. Use `-Account scanner` to copy the scanner password for the Android login. These accounts belong only to this local demo. For another operating system, supply your own password environment variables as described in [TC22 acceptance](TC22-ACCEPTANCE.md).
+Paste into the browser login for user `admin`, then clear the clipboard with `Set-Clipboard -Value ''`. Use `-Account scanner` for the handheld login. Never paste passwords into an issue, chat or log. These accounts belong only to the local demo; on another operating system, supply your own password environment variables as described in [TC22 acceptance](TC22-ACCEPTANCE.md).
 
-## Emulator walkthrough
+## Connect a device or emulator
 
-Follow the Android repository's [emulator guide](https://github.com/QRun-IO/qqq-android/blob/feature/mobile-scanner-host/docs/EMULATOR.md) to start a virtual device and install the debug APK. Forward its port to the host:
+Install the matching debug build of the [Android scanner host](https://git.kof22.com/QRun-IO/qqq-android) (the `scanner-host` module; its `docs/EMULATOR.md` covers the emulator). Always pick the target explicitly when more than one device is attached. USB or paired wireless ADB both work; do not put device serials or addresses in notes or commits.
 
 ```powershell
-adb reverse tcp:8080 tcp:8080
+adb devices -l
+$serial = '<serial or address from adb devices>'
+adb -s $serial install -r <path to scanner-host-debug.apk>
+adb -s $serial reverse tcp:8080 tcp:<host port>
 ```
 
-If the host server uses `-Port 18080`, use `adb reverse tcp:8080 tcp:18080` instead; the Android server URL still uses port 8080.
+`install -r` updates the app without clearing its login or enrollment. Use the host port the server actually listens on (8080, the `-Port` value, or the Echo launcher's port). The app URL on the device stays `http://127.0.0.1:8080` because the forward maps device port 8080 to the host port. The debug build permits HTTP only for this local use; deployed builds require HTTPS.
 
-1. Open **QQQ Mobile** on the emulator and use server `http://127.0.0.1:8080`.
-2. Sign in as `scanner` and enroll the device. It starts pending approval.
-3. In the browser as `admin`, open **Mobile Scanner Administration → Mobile Devices**, open the device record, and choose **Actions → Approve Device**. Review the selected device, continue, and check the success result. For several devices, select their rows in the device list and run the same action from the bulk menu. The standalone sidebar process also accepts device IDs.
-4. Refresh approval on Android, open **Scan Capture**, type a barcode such as `000123456789`, and submit it.
+## Walkthrough: enroll, approve, scan, revoke
+
+1. Open **QQQ Mobile** on the device and use server `http://127.0.0.1:8080`.
+2. Sign in as `scanner` and enroll. The device starts pending approval.
+3. In the browser as `admin`, open **Mobile Scanner Administration → Mobile Devices**, open the device record and choose **Actions → Approve Device**. Review the selected device, continue and check the success result. For several devices, select their rows and run the same action from the bulk menu; the standalone sidebar process also accepts device IDs.
+4. Refresh approval on the device, open **Scan Capture**, scan or type a barcode such as `000123456789` and submit it.
 5. Inspect **Barcode Scans** in the browser and verify the exact text, user, device and timestamps.
-6. Choose **Revoke Device** from the device record or bulk selection, confirm the selection, and verify subsequent capture is refused.
+6. Choose **Revoke Device** from the record or a bulk selection, confirm, and verify that later capture is refused.
 
-The emulator exercises native screens, login, approval, manual capture and persistence. Verify the physical trigger, DataWedge delivery and barcode decoding on the Zebra TC22 using [the hardware checklist](TC22-ACCEPTANCE.md).
+Approval and revocation accept checked rows, select-all matching rows and first-N selections, up to 100 devices per run. The confirmation fixes the selected IDs for that run, so a device that enrolls afterwards is not included; larger selections fail explicitly, and nothing changes until you continue past confirmation.
 
-Approval and revocation support checked rows, select-all matching rows, and first-N selections, up to 100 devices per run. The confirmation fixes the selected device IDs for that run, so a newly enrolled matching device is not unexpectedly included. Larger selections fail explicitly; choose a smaller batch. No approval changes occur until you continue past confirmation.
+An emulator exercises native screens, login, approval, manual capture and persistence. The physical trigger, Zebra scanner delivery and decoding need real hardware: use the [hardware checklist](TC22-ACCEPTANCE.md).
 
-See [branding configuration](BRANDING.md) to test customer names, colors and logos with the same APK. Tap the Android connection footer to view or copy diagnostic events.
+## Full Echo demo
+
+Follow the [Echo demo README](../examples/echo/demo/README.md) for build, environment variables (set in the environment, never on the command line), accounts and permissions, and operator order. Use the trusted-local launcher for a developer machine and the production `EchoDemo` only with the owner's qualified renderer sandbox. The Android flow is the same as above, then open **Echo**, choose the printer, paper size, document and optional copies, and scan.
+
+## Upgrading an existing demo database
+
+Stop its JVM gracefully and back up the closed `demo/data` directory together with its protected credential file. The shared H2 schema begins with `SET TIME ZONE 'UTC'` before converting legacy `TIMESTAMP WITH TIME ZONE` columns to the current UTC `TIMESTAMP`, preserving original instants regardless of the workstation time zone. Re-running initialization preserves accounts, passwords, device approval and scans. Do not copy over an open H2 database, and do not use an account reset as an upgrade step. The schema leaves its migration connection in UTC, so hosts should use a dedicated migration connection or restore their own zone afterwards.
+
+Use the matching Android build with the [mobile-scanners semantic API extension](UI-API.md). Public discovery is at `/qqq/v1/version`; the connectivity endpoint is `/qqq/v1/qbit/mobile-scanners/status`. Upgrade the server and the app together: the former standalone mobile routes are gone.
+
+See [branding configuration](BRANDING.md) to try customer names, colors and logos with the same APK. Tap the Android connection footer to view or copy diagnostic events.

docs/MOBILE-TEST-DATA.md

@@ -0,0 +1,21 @@
+# Mobile browsing test data
+
+The composed Echo demo includes **Test Data → Test Orders** for testing the existing mobile app. These are synthetic records, separate from scanner captures and printer jobs.
+
+| Table | Rows | Contents |
+| --- | ---: | --- |
+| Test Orders | 1,000 | 39 fields across Order overview, Customer, Shipping, Amounts, Warehouse, and Notes and audit |
+| Order Items | 12,000 | 12 related items per order, grouped item and handling fields |
+| Order History | 3,000 | Three related history entries per order |
+
+Values exercise dates, timestamps, numbers, decimals, booleans, leading zeros, Unicode, multiline notes, long descriptions and empty optional fields. All customer information is fictional.
+
+Search or filter the table, open an order, and use Details, Items, History or Photos. Details groups collapse and can be selected directly. Table pages contain 25 records; related tabs contain 10 records per page. Back preserves the table page and search/filter state.
+
+Use **Actions → Add photo → Take photo / Choose photo** to attach an image to the displayed record. Photos lists saved attachments, including those awaiting server review; available images have thumbnails and previews. Normal Record Files permissions, quarantine and upload lifecycle still apply.
+
+The native preview uses standard QQQ metadata sections and direct association joins through the existing semantic query/get API. It supports read-only browsing; arbitrary widgets, nested editing and unsupported relationship definitions are not added by this fixture.
+
+`MobileTestData` belongs only to `examples/echo/demo`. Startup adds missing H2 tables and missing synthetic rows without replacing existing rows or attachments. The scanner account can read these tables and attach photos; raw table edits remain refused. The basic Scan Capture demo does not install this dataset.
+
+Verification uses separate databases, accounts and disposable application IDs. Updating the maintained demo must preserve its database, accounts, printer configuration and existing device enrollment.

docs/MOBILE-UX-PLAN.md

@@ -0,0 +1,15 @@
+# Mobile record UX improvements
+
+User direction: Add photo belongs in the record's Actions menu, alongside other actions. Address the full TC22 visual review in the existing app and maintained demo.
+
+1. Preserve table page, scroll, search and filter state across record navigation and recreation.
+2. Keep record identity visible; add Details, related-record and Photos navigation, collapsible field groups, compact summaries and formatted values.
+3. Put capture/selection behind Actions → Add photo; retain pending-upload guards. Browse saved attachments with lifecycle status and authorized previews.
+4. Use standard semantic metadata, query/count/process and owner attachment/download APIs. Preserve existing permissions and quarantine.
+5. Verify unit/build/lint, isolated real native flows, and actual TC22 layout; update the same app/server with preserved data.
+
+The user subsequently authorized committing, pushing and merging the completed scanner and Android work through Gitea. No new artifact release is requested.
+
+## Progress
+
+All five steps are complete. The maintained server and existing TC22 app were updated with preserved data and enrollment. Native search/filter/Back, related-record and photo acceptance passed. Actual TC22 inspection confirmed the Actions menu, capture chooser, tabs, formatting and page-two restoration. Evidence and remaining hardware/release limits are in [the completion record](history/MOBILE-UX-2026-11-05.md).

docs/OPERATIONS.md

@@ -0,0 +1,56 @@
+# Single-instance deployment and recovery
+
+Written 2026-11-05 from the static final review of source base `a9eae04` (see [review reconciliation](REVIEW-RECONCILIATION-2026-11-05.md)). The procedure below is for the host/operator in a real incident. The only executed evidence is the automated [isolated local-demo recovery acceptance](#isolated-local-demo-recovery-acceptance-automated-passed), which covers the demo's stopped H2 database plus object snapshot and restore. No production storage, enterprise object-store or high-availability deployment is supported or qualified, and those are not tasks of this scanner release. The supported model is one server process per database.
+
+## Topology
+
+- Run exactly **one server JVM per database**, with no overlap during an upgrade (stop the old process before starting the new one). Revocation and capture-commit exclusion use a per-JVM monitor, screen-mirror frames are held in memory only, and Echo job admission relies on a row lock in that one database.
+- H2 must be used single-process. Do not point two servers at one database.
+- The host owns HTTPS and the identity provider; the loopback HTTP demo is not a deployment ([production readiness](PRODUCTION-READINESS.md)).
+
+## Backup and restore
+
+- Take one **consistent snapshot of the database and any file storage together** (same moment, or with the server stopped). A database restored without its matching files, or the reverse, leaves dangling references.
+- Treat bindings and backups as **sensitive**. `mobileSessionBinding.coreSessionUuid` is stored in plaintext at rest (reads are blocked by the application, not by the backup). Anyone holding a backup holds live session identifiers until they expire or end. Backups also contain barcode payloads and last-known device location.
+- After any restore, before reopening to users:
+  1. Stop all server processes, then restore the database and files from the same snapshot. Nothing can be done through the application while every server is stopped, so steps 2 and 3 need a running server.
+  2. **Restart in controlled, admin-only access** (for example, reachable only by administrators, with scanner clients and other users kept off the network path) and keep it that way through steps 3 to 6. Do not reopen to users first: a device revoked after the snapshot may be approved again and a session ended after it may be active again.
+  3. **Re-audit device approvals.** A restore reverts revocations, approvals and enrollments made after the snapshot, so a device revoked later may be approved again. Review every device and re-revoke as needed.
+  4. **End or reconcile active sessions.** Tombstones written after the snapshot are lost. With the server running in that controlled state, apply the End Session process to the restored sessions so cleanup runs against the restored state, and check the cleanup status below.
+  5. Devices enrolled after the snapshot no longer exist and must re-enroll.
+  6. **Echo:** jobs accepted after the snapshot may be absent from the database although a print was already queued. Manually reconcile the physical or Printing queue against the restored jobs **before authorizing any retry**, and retry only what that comparison shows was not printed. This is a manual check; there is **no exactly-once physical print guarantee**, and a retry can still produce a duplicate or a missing print if the queue or printer state is unknown.
+  7. Reopen to users only after the above are done.
+
+### Isolated local-demo recovery acceptance (automated, passed)
+
+`EchoDemoAcceptanceTest.restoredSnapshotKeepsScanAndRetainedFileAndRevertedApprovalStateIsReaudited` (Echo composed demo) exercises this procedure on private temporary directories only.
+
+**Verification (2026-11-05):** the combined five-module `verify` on the merged source (`develop` `9e8685f` plus the storage fixes) passed with qualified private owner dependencies: 196 tests (root 53, demo 8, Record Files 22, Echo 74, Echo demo 39), 0 failures, 0 errors, 0 skips, and zero Checkstyle violations in every module. The qualified owner inputs are private, so this is not public-dependency qualification.
+
+The case restores H2 scan rows, the exact leading-zero value and symbology, and the Record Files owner's own `RecordFilesTables.FILE` row. It asserts that row's exact table, record and attachment relationship and the SHA-256 of the object bytes. It shows that a revocation and session end made after the snapshot are reverted by the restore, then reapplies the normal Revoke and End Session processes and shows that a valid in-flight run and a new initialization are denied. No physical printer, service or demo data was changed.
+
+Flow: it enrolls and approves a synthetic device, scans over real HTTP, and lets the real Record Files service retain the generated original in the demo local-file adapter. With the servers stopped and H2 shut down, it copies the database and object directory together, makes later changes (a second scan and file, a revocation and an ended session), restores only those two temporary directories and reads them without the application. It then restarts on a new ephemeral loopback port and applies the existing Revoke and End Session processes.
+
+What this is **not**: it covers the local demo's H2 database and local files only, using private coherent fixture inputs. It is not published-cohort qualification (that is repeated when the final public dependencies are adopted), and enterprise object-store and high-availability recovery are unsupported and unqualified. In a real incident the full procedure above still requires an operator-owned audit of approvals, sessions and the print queue before a restored service returns to users.
+
+Storage regressions in `PrivateObjectFilesTest` (part of the Echo demo's 39 tests): `concurrentSameKeyWritersLeaveOneWinnersBytesAndMetadata` (concurrent same-key writers leave one winner's bytes and metadata), `dotBucketsAreRefusedAndValidBucketsStillWork` (`.` and `..` buckets refused), plus `existingObjectIsNeverReplaced` and `keysCannotTraverseOrAlias`.
+
+Limits: the file store is the single-host demo adapter and the database is the demo's H2 file, so this does not qualify production storage, an object store, encryption or high availability. Other database backends are not supported or tested here. The renderer is controlled and the printer is a database fixture; no job is physically printed and no normal demo data is changed. The file check reads the Record Files rows and object bytes directly, not through a product service.
+
+## Session cleanup status
+
+Ending a session (`MobileSessionService`) first persists the ended state with `authCleanupStatus = PENDING`. Cleanup then sets `REQUESTED` (with `authCleanupAt`) **before** calling the logout executor and removing the stored core session. If that call throws a `QException`, the status becomes `RETRY_NEEDED`. So `REQUESTED` means cleanup was attempted and no failure was reported; it is not independent proof that the provider session is gone. Cleanup is skipped when a binding does not exist, and for a single end inside an open transaction; a status left at `PENDING` also needs a retry. The bulk End Session process commits all tombstones first and runs cleanup afterwards.
+
+To retry: find sessions with `authCleanupStatus` of `RETRY_NEEDED` or `PENDING` (admin view of the session table), then run End Session again for them. Ending an already ended session does not change its end time and reruns cleanup when a binding exists. Confirm the status reaches `REQUESTED`. There is no automatic monitor in this repository; the operator must check for these statuses.
+
+## Retention
+
+Scans, sessions, bindings and Echo scans are **kept indefinitely** by default. Table deletes are blocked by permissions and foreign keys tie history to devices. Barcode payloads and last-known location are retained, so a different retention period is a host-owned policy, not a feature of this release: any purge is a host DBA procedure, taken with a snapshot first and respecting the foreign keys. Audit is current-state only; revoking overwrites the previous approver and time.
+
+## Database migration beyond H2
+
+The supplied, tested scripts are H2: `base/src/main/resources/db/mobile-scanners-h2.sql` and the Echo `echo-h2.sql`. Other backends are unsupported and untested here; a host that uses one **owns the equivalent migration**; do not assume `ADD COLUMN IF NOT EXISTS` or the column types. Additive columns that older databases need before running current servers: on `mobileScan`, nullable `aimIdentifier` (`VARCHAR(3)`) and `rawDataBase64`; on Echo, nullable `echo_scan.aimIdentifier`, `rendererValue` and `humanReadable`, and **`echo_run.copies`, which is `INT NOT NULL DEFAULT 1`** (existing runs keep one copy), so it is not nullable and the equivalent migration must supply the default. Echo also has nullable template columns (`templateId`, `templateRevisionId`) in `echo-h2.sql`. Test the migration on a copy, and snapshot first.
+
+## Demo-only file adapters
+
+`LocalFilesystemAttachmentStorage` and `LocalStagingChunkStorage` (Echo demo) are single-host local-file adapters for the demo. They are not production storage; photo and record-file storage for a deployment is not qualified here. `ECHO_RELEASE_GENERATED_FILES=true` turns off generated-file quarantine and exists for the demo only; leave it off unless every producer permitted to keep generated output is trusted ([Echo demo README](../examples/echo/demo/README.md)).

docs/PRODUCTION-READINESS.md

@@ -1,105 +1,37 @@
-# Mobile scanners 1.0 release gates
+# Production readiness
 
-Status: not release-ready. The user requested a full client/server audit and production-ready 1.0. This is an evidence ledger; a numerical quality score does not replace the gates below.
+**Status (2026-11-05): not released as production 1.0.** The local demo works and is accepted by the operator; the gates below decide whether the project can be called production-ready. This is a checklist, not a score. The detailed evidence ledger, with per-gate tables and the architecture review findings A1–A11, is archived in [history](history/PRODUCTION-READINESS-through-2026-11-04.md); present status is in [session state](SESSION-STATE.md).
 
-## Current checkpoint — November 2
+## Delivered and verified
 
-Server `e3b775e` (Gitea PR 7) fixes the Generation/renderer output-limit mismatch and passes 45 Echo library plus 29 composed demo tests with zero Checkstyle violations. Android implementation `fb3cc5d`, published with documentation at `ffc5b49` (Gitea PR 10), passes 174 JVM tests, lint with zero errors and warnings, and the debug APK build. One local server on host port 57832 runs Echo, Record Files, Document Generation and Printing together (API 1.10.0, mobile 1.4.0, printing 2.3.0). The normal TC22 and the installed print client work against it, and the real 4x1 stock, media revision and Echo document are published and selectable. The earlier native acceptance (7 stages, 112 requests) used simulated printing and inputs.
-
-The synthetic HTTP event `ECHO-HTTP-TEST-001` has one matching scan and one actual ZPL print job in `SPOOLED`, with a Windows spooler job assigned and its process closed. A read-only recheck at 16:31 UTC confirmed that receipt, server HTTP 200, the running print service, and the TC22 showing Echo / Scanner ready / Connected. No Windows administrator prompt or printer pairing is pending. Paper output and physical TC22 print/rescan remain unconfirmed; see the [delivery receipt](../examples/echo/demo/docs/echo-delivery-acceptance.json).
-
-Still not release-ready. Open: physical Code128 and leading-zero QR scan, print and rescan; extended barcode fidelity beyond the currently admitted types; full provider, camera, GPS, projection and device qualification; public coherent artifacts; primary Gitea CI; and final signing and distribution, which is deliberately last. Core PR 1337 was reviewed with its 57 focused tests verified, but normal CI and publication are not established and default dependencies are not repinned. Where dated checkpoints below describe the same-origin fix, printer connection, media, document or server composition as pending, this section supersedes them.
-
-## Superseded checkpoint — November 1, 17:34 UTC
-
-Server standards checkpoint0b53f34 is signed/pushed and all eight hosted checks pass; a fresh private API1.10 cohort passes39 server, six demo HTTP and18 Record Files consumer cases with Checkstyle. Client strict compilation and163 JVM tests pass; final TC22 native acceptance is running and the Query artwork density warning is being corrected before installation. About includes bundled Query artwork and the exact public Dogfooding/Query links.
-
-Actual Authentik desktop acceptance now passes real negative nonce rejection, A login, explicit company logout, old-cookie rejection, fresh B credentials and B principal in the same retained browser context, followed by B local logout/rejection. HTTPS verification remained enabled with profile-only fixture trust. The owned provider required its documented company invalidation flow; no global flow or default client sign-out policy changed. This closes the earlier desktop A-to-B handoff failure for the qualified API1.10 fixture, not the actual Android external-browser callback gate. The normal server remains API1.9/mobile1.1 and operator data is preserved.
-
-CorePR1369's new hosted run exposed a missing explicit architecture allow-list entry for extracted private-session logout plumbing; a narrow policy-conforming correction is under verification. Do not call final core CI green. Remaining physical GPS/camera/projection/lifecycle/retry, immutable files-owner handoff, deployment and owner-deferred signing/distribution gates remain open. Dated matrix rows below retain their earlier source/runtime scope and are superseded by this checkpoint where stated.
-## Current release ledger — November 1
-
-This is the current acceptance matrix; dated checkpoints below remain historical evidence. Android portrait-default source `7de2b5088fa376cb161ed5ac7e5358d2a2145d92` passes all eleven hosted checks. Documentation/QR fixture checkpoint `2e0fd962a7ece0f81328e5f9f05e4c1e2d77a853` does not establish physical QR acceptance. Server implementation `10416938724c9663d66f7848ff2b1a63fe635794` has qualified API1.9/mobile1.2 source evidence. Source publication, private consumer qualification and the installed operator runtime are distinct; no production APK or immutable dependency release is claimed.
-
-| Requirement | Accepted evidence and scope | Remaining release gate |
-| --- | --- | --- |
-| Current Android and CI | All eleven hosted checks pass at published Android8d8 (portrait implementation7de), including native navigation/input, PixelCopy and semantic E2E. The subsequent optional provider-logout working patch passes148 JVM tests, lint and debug build; its native tests compile but have not run. The completed-logout/enabled-action guard retains fresh-login/new-session assertions. Portrait default preserves explicit saved choices. | Physical operator navigation, lifecycle, ownership, outage/retry and leave/cancel walkthrough. Any later executable source needs its own verification. |
-| Trusted scanner ingress and hardware | Ordinary-UID/distinct-signer rejection of eight forged scans plus manual positive control; actual EMDK Code128 source/model/event proof: eight deliberate events on prior F3AF APK and one on the installed portrait-default C891 APK. Historical DataWedge evidence is separately retained. | Current leading-zero QR, repeated-intent/lifecycle/ownership matrix, connection failure and uncertain receipt/retry/leave acceptance. Code128 success does not qualify QR or every lifecycle path. |
-| Running operator deployment | Preserving coreecf/serverb14 UI API1.9/mobile1.1 runtime on127.0.0.1:57832; normal TC22 uses development APK C89161C522AA7DFFE09C009ABDE769C1BADB7E6C64BFCE699857062A1CEC6340 with signer/data backup preserved and portrait requested. | Supported production deployment, HTTPS/authentication, migration/recovery and release upgrade acceptance. No normal1.2/RF installation is implied. |
-| Source-pinned server/admin APIs | Server104 source:39 server/six demo/all15 browser cases,195 hashed JARs/2,441 unique QQQ classes/zero duplicates; record/bulk administration, profiles, presence, sessions and screen controls covered. Coreecf selected closure:4,507 discovered/16 existing skips/zero failures/errors. | Coherent immutable dependency publication and final supported deployment configuration. Default Maven dependencies still select RC.20; passing source-pinned consumers do not change that default. |
-| Authentik | Real Authentik2026.8.5 browser PKCE login established operator A; QQQ local logout invalidated its old cookie. With retained browser SSO, the next prompt=login silently reused A, so operator handoff failed. Optional semantic API1.10 RP logout and Android AppAuth handling are implemented but unqualified; the first core build found an API mismatch and review found an alternate-authentication-source gap under correction. | Correct and qualify the optional logout implementation, then prove real A→provider logout→B identity isolation. Native browser callback/lifecycle and user-selected sign-out policy remain pending. Existing failed retained-SSO evidence must remain failed. |
-| Optional whole-device viewing | Additive mobile1.2 server and consent-based Android source built/reviewed; mode/session-bound leases and bounded image ownership verified automatically. Normal server remains mobile1.1 and does not expose device-screen mode. | Actual OS consent/notification, Home/other-app pixels, Stop/lock/rotation, lease expiry and remote logout on the refined candidate. Separately preserve normal data before any coordinated1.2 upgrade. |
-| Camera/gallery and Record Files | Filesystem portability142 discovered/138 passed/four existing skips; metadata symlink-parent regression fixed and independently closed. Final coherent core32/scanner1a3 qualification passes39 scanner, six demo,18 Record Files and15 browser cases (78 total), with214 JARs/3,163 unique QQQ classes/zero duplicates and no separate filesystem override. Synthetic native camera/gallery/receipt cases remain separate evidence. | Coherent immutable supported RF/attachment-owner/core/RDBMS/filesystem tuple and default adoption, then actual TC22 lens/gallery permissions and durable authorized record association. The isolated coherent qualification does not establish the files owner full-suite/default publication gate or change the normal runtime. |
-| GPS and customer appearance | Foreground-only location/state/age controls and automated permission-denial/schema coverage; current basic operator display/navigation observed. | Real GPS permission/fix/disabled-provider behavior and customer-specific logo/physical appearance. |
-| Security, architecture and standards | Historical scoped security reports/remediations retained; independent architecture closure maps A1–A11 controls/tests. Whole-device changed-file review and follow-up found no concrete introduced issue; filesystem finding closed against corrected source/test evidence. | Final revision/scope reconciliation and unresolved external-provider/deployment gates. These reports do not become a new exhaustive scan or blanket production clearance. |
-| Release and operations | Release automation/source packaging independently reviewed; normal preserving migration/login checks passed. | Reviewed GitHub environment/tag protections, organization signing identity/recovery, actual signed APK upgrade/physical qualification and distribution decision. Signing/distribution remains owner-deferred until the final step. |
-
-The local emulator remains off because of workstation stalls. Disposable QA and private fixtures must not replace the normal package/runtime or clear operator data. No numerical quality score replaces the remaining gates.
-
-Historical November1 display observation retained: the handheld's black desktop mirror was not proof of a crash. Direct inspection found the normal process alive/resumed, no crash-buffer entries and connected sign-in; login reached Scan Capture without clearing data or running disposable instrumentation over the operator.
-
-## Historical checkpoints
-
-Latest correction: hosted Android testing found revoked heartbeats remained successful. Approval now precedes all heartbeat activity observation, including accepted trailing-slash aliases. Independent red reproductions and final 37-root/four-demo green tests are retained; new hosted native verification remains pending. Scanner authentication must follow configured Authentik through explicit native semantic authentication metadata; that implementation and real-provider acceptance are now required release gates.
-
-The optional consumer has subsequently qualified frozen0515 with37 fresh base and18 integration tests, including the matched core logging correction and runtime integrity checks. This remains an isolated private candidate; immutable dependency publication and optional hosted CI are required before production adoption. Separate OAuth2 log-redaction work in the native-auth core branch is not included in0515.
-
-## Scope and checkpoints
-
-Latest verified checkpoint: server `0926550` includes the standalone file-backed presence regression and the passing browser-to-native
-viewing regression after guarded-upload commit `84ffd7c`. Base 37, demo HTTP two,
-browser 15 and optional guarded integration 18 cases pass. Android's local reports
-show 91 JVM tests; TC22 navigation (12 cases), orientation, offline licenses,
-synthetic camera/gallery/rotation/logout, and the complete real-screen/session-end
-scenario pass. Native photo/session requests match published semantic operations.
-The full server deep static security review of `0926550` is sealed with no reportable findings. It does not inspect external dependencies or production configuration and does not replace runtime acceptance. Android's full scan and the later single-hamburger UX correction remain pending.
-These are checkpoint results; final Android audits, fresh Android hosted CI,
-production provider/immutable dependency qualification and actual lens acceptance
-remain open. Signing/distribution is owner-deferred until the final step.
-
-- Server semantic baseline: `7dd02b8874882ca2edcdcd89109b3dee6b4b0c88`, with all hosted checks passing. Documentation checkpoint: `a49724384f569a4b4b66ce2cd4aa69332ee1e0e8`.
-- Android semantic baseline: `6574ec4991dbb859b60c3a0be462af96918aee32`; hosted JVM/lint/APK, CodeQL and CircleCI checks passed, but both hosted native E2E jobs failed at compatible login before any credential request reached the server. Login/form reachability fixes are under verification; this baseline is not fully green.
-- Active implementation: [device/session history, live activity, actual app screen viewing, session termination, identity/presence/location and Record Files integration](DEVICE-SESSIONS.md).
-- Final audit scope: both complete repositories, including shared Android core/mobileapp libraries, scanner host, qbit, demo, build/release configuration, tests and documentation. Exclude local secrets and operator data from published evidence.
-
-## Required gates
-
-| Gate | Status / required evidence |
+| Area | Evidence (see session state for revisions and counts) |
 | --- | --- |
-| Feature completion | Session administration, screen viewing and device naming/presence/location have passing server/browser coverage. Native navigation/session and Record Files photo integration are in progress. Actual ingestion routes exist; atomic revocation/commit protection and compatible runtime qualification remain open. |
-| Security | Independent multi-pass full scans of the frozen client and server; validate findings, fix release blockers, verify fixes and retain coverage/limitations. |
-| Architecture | Review boundaries, coupling/cohesion, session ownership, semantic API evolution, concurrency, resource limits and deployment assumptions. |
-| Coding standards | Repository conventions, public API compatibility, lifecycle/error handling, duplication, dead code and maintainability review. |
-| Automated tests | Unit, HTTP contract, schema/version compatibility, browser record/bulk processes and native UI-to-real-server tests on the final revision. |
-| Physical acceptance | TC22 capture, mirroring, remote logout, failure/retry, restart, data preservation, location permission/age, camera capture and gallery upload to an authorized record. |
-| Delivery | Release build, signing/update approach, reproducible artifacts, dependencies/licenses, secrets checks and final hosted CI. |
-| Operations | Supported deployment/database migration, HTTPS/authentication, retention/resource limits, diagnostics and recovery documentation. |
-| Final review | No unresolved release-blocking findings; evidence identifies exact revisions and remaining supported-use boundaries. |
+| Server source and development publication | PR 19 merged as `9e8685f`, including record/photo UX support and earlier PR 17/18 changes; the storage/recovery patch is based on that source. Earlier PR 12 snapshot `0.1.0-20261103.233448-3645` was read back anonymously and matched its reviewed source. |
+| Android host libraries | Published development libraries from source `0ae2101`: SDK run 3634 passed and artifacts verified. The scanner application's newer source and signed candidate are recorded below. |
+| Current cohort tests | Combined five-module `verify` (2026-11-05): 196 server tests (53 / 8 / 22 / 74 / 39), zero failures, errors and skips, zero Checkstyle violations, with qualified private owner dependencies. Android 232 unit tests and lint pass. Inherited report-only guardrail findings remain visible. |
+| Storage integrity and recovery | `PrivateObjectFilesTest` concurrent-writer and dot-bucket regressions; `EchoDemoAcceptanceTest.restoredSnapshotKeepsScanAndRetainedFileAndRevertedApprovalStateIsReaudited` is the isolated local-demo recovery acceptance (stopped H2 plus object snapshot/restore, `RecordFilesTables.FILE` relationship and byte hashes). See [operations](OPERATIONS.md). |
+| Local runtime | One server using the tested development aggregate: public QQQ SNAPSHOT, current Collaboration, scoped local Record Files and qualified document inputs, plus Printing 1.0.0. API 1.10, mobile 1.5, printing 2.3, mobile-record-files 1.0; existing data preserved. Final immutable public-cohort qualification remains open. |
+| Device and admin processes | Enrollment, approval and revocation work from a single record and from bulk selection (checked rows, select-all, first N), with confirmation and visible results, covered by HTTP and browser E2E tests. Earlier browser run: 15 cases. |
+| Approved-scanner photos | Host-only `quarantineCapturedFiles=false` makes an approved device's captured JPEG/PNG `AVAILABLE`; other intake stays `QUARANTINED`. `record-files.release` is admin-only. Root-reported: 69 owner and 197 scanner/Echo tests passed, 13 focused Android tests passed, Checkstyle passed. A synthetic gallery PNG from the signed MC9400 app was `AVAILABLE` with exact parent/type/size/SHA-256. No camera-hardware or new full-preview proof. Depends on the unmerged Record Files owner PR 1. |
+| Hardware | TC22 manual tests: operator-reported pass on November 4 (no per-case artifacts). MC9400 physical trigger done: Saved scan with backend EMDK CODE128/AIM/raw bytes and attribution confirmed (the barcode was not the requested literal). |
 
-## Verified baseline evidence
+## Open gates
 
-October 31 working-source evidence: 37 root tests, two real HTTP acceptance tests and all 15 browser E2E cases pass. Browser cases include single/selected-bulk/full-query session end, cancellation, live image/clear, device profile edits, location timestamps and online expiry/filtering. The full browser run completed in 59.4 seconds after correcting file-H2 connection lifetime. A subsequent virtual-online projection fix passes the 37-test suite; its combined native acceptance remains pending. Android's intermediate 76 JVM tests and zero-error/zero-warning lint pass; shared native and real-server session tests remain in progress. These are local intermediate results, not a frozen release or fresh hosted qualification.
+The maintained server and existing TC22 app now run the GS1, rich test-data and record UX changes. Actions → Add photo, grouped/related records, search/filter/Back state and the saved-photo gallery are implemented and verified by isolated native acceptance plus an actual TC22 visual pass. Existing data and enrollment were preserved. See [current evidence](history/MOBILE-UX-2026-11-05.md). This supersedes the earlier undeployed status; physical GS1 print/rescan and signed-build production deployment remain open. The user authorized the final release, signing and publication for this bounded goal; Android PR 15 (`c782aaaaba3f62422232436a9000af9d4b38fc82`) merged after all CI.
 
-Server: 23 root tests plus the real HTTP lifecycle scenario and six packaged-frontend browser E2E scenarios. Android: 53 JVM tests, six shared native UI tests, lint with zero errors/six warnings, debug/E2E APK builds, and six semantic native scenarios across focused runs. The final admin scenario passed in 255.917 seconds; 31 of 31 requests matched 13 published operations, including cancellation. These results are baseline evidence and must not be represented as verification of later session/mirroring changes.
-
-Physical TC22 (Android 14, DataWedge 13.0.325, app 0.1.0): installed with existing state preserved, signed in and approved through the actual device-record process. A dedicated DataWedge profile uses barcode input, explicit broadcast delivery and package/signature verification, with keyboard output disabled. Two deliberate Code128 trigger scans produced two records. One QR trigger scan preserved `001234567890`; backend records confirmed symbology, source, user/device/app/process and timestamps. Outage/retry and remote-session controls remain to be tested on the completed feature.
-
-## Review findings
-
-The initial full-source architecture/maintainability review covered Android `6574ec4` and server `7dd02b8`; it does not cover the later session/device features. Findings are being remediated, with final independent review still required:
-
-| Finding | Remediation owner / evidence pending |
+| Gate | What is still required |
 | --- | --- |
-| A1: scan retry cleared on an incomplete receipt | Android host: require matching acknowledgement ID, `scanSaved=true` and nonblank scan ID. |
-| A2: invalid scanner length metadata silently defaulted/truncated | Android host: reject invalid or out-of-range metadata. |
-| A3: legacy INPUT_FIELD bypassed typed field semantics and interpreted input as action code | Shared client: typed field handling and explicit action capability. |
-| A4: ordinary asynchronous status failures lacked a safe retry | Shared client: retry status GET without replaying submission. |
-| A5: cancellation during initialization could leave a late process orphaned | Shared client: retain cancellation intent and cancel a returned process ID. |
-| A6: login/forms could place actions outside the viewport or behind the keyboard | Shared client: scrolling/IME handling and constrained-viewport native tests. Hosted failure cause remains unproven until the regression evidence is complete. |
-| A7: explicit null displayed a default while submitting null | Shared client: distinguish absent keys from explicit null consistently. |
-| A8: business JSON collided with class-based serialization envelopes | Shared client: ordinary JSON values without class loading. |
-| A9: multi-record mutations and enrollment could persist partially | Server: transactions for credential/device and session/binding pairs and bulk state changes; provider logout after durable tombstones with explicit cleanup outcome. |
-| A10: media ownership/disposal could leak resources | Shared client: sound/image lifecycle ownership. |
-| A11: navigation title/state and native back stack could drift | Android host: derive navigation state from the active NavController. |
+| Public dependency cohort | Public, coherent Generation/bridges/Record Files/Scripting artifacts from their owner; adoption of the Core/Collaboration/Next UI foundations when released. Today these are qualified owner inputs, and the current local aggregate uses public Core SNAPSHOT, current Collaboration and a local Record Files change, not a final public cohort. |
+| Release | Retest the full gate when the final public dependency cohort is adopted, with a reviewed release manifest; Maven publication stays disabled until then. Redesign of the shared CI pipeline is outside this scope. |
+| Signing and distribution | Done: QRun key with backup, signed Android 1.0.1 (code 3) built from the merged PR 15 source tree and installed in place on an MC9400 (installed bytes match; login/enrollment preserved; Scan Capture reopened; HTTPS connected). Open: public dependencies, signing-APK download publication and final distribution. No signing CI. |
+| Deployment | HTTPS and the host's identity provider. Single-instance procedure, recovery and default-indefinite, host-owned retention guidance is in [operations](OPERATIONS.md); isolated local-demo recovery acceptance has passed. Enterprise object-store/HA and non-H2 databases are unsupported and unqualified options, not release tasks. The HTTP loopback demo is not a production deployment. |
+| Provider authentication | Native OAuth2 requires UI API 1.10 native-session and nonce-validation support on the server (verified in the Android source). Shared Authenticator server configuration is verified (trusted HTTPS, API 1.10, scanner and printing extensions and channels, exact callbacks, REQUIRED nonce). Still open: native Authentik login, logout and account switching on a handheld (needs the MC9400 wireless-debugging endpoint). No native-auth pass is claimed. The Printing client nonce fix (PR 11, `443f642`; 352 tests and build passed) awaits hosted Core. |
+| Further device qualification | MDM-applied managed configuration remain unverified. Company profile/wallpaper is separate tracked scope, not a blocker for this release goal. The TC22 camera, GPS and screen-viewing checks are covered by the accepted operator group report; no separate per-case evidence is claimed or required again for that demo. |
+| Barcode fidelity | Echo's supported profiles are documented ([limits](../examples/echo/README.md#fidelity-and-limits)); The committed source supports bounded GS1-128; physical print/rescan remains open. Other GS1, ECI, structured and binary profiles remain refused. No universal barcode-reproduction claim. |
+| Final reviews | Reconcile the dated security, architecture and standards reports to the final revision; they are scoped historical reviews, not a fresh exhaustive scan. A dated static review of base `a9eae04`, its supplement and its scope and limits are in [review reconciliation](REVIEW-RECONCILIATION-2026-11-05.md); it is not an audit rating. |
 
-The completed TC22 session scenario delivered and decoded real application JPEG pixels, cleared background frames, renewed viewing on resume, honored operator Stop viewing, ended the session remotely and accepted a fresh login. Android packaging now verifies 130 notice entries, nine license texts and eight native binary hashes in each host variant. The full server static scan is complete; Android review, external core logging remediation/adoption, production signing/update path, supported database migration and final hosted checks remain required before 1.0.
+## Rules that stay in force
+
+- Do not describe a passing build, an emulator run or a demo as production acceptance.
+- Never reset or overwrite the user's demo or scanner data to run a test; use isolated accounts, databases and application IDs.
+- Keep device credentials, passwords, device identifiers and workstation paths out of the repository.

docs/REVIEW-RECONCILIATION-2026-11-05.md

@@ -0,0 +1,40 @@
+# Final review reconciliation, 2026-11-05
+
+**Source base:** `a9eae04` (merge of PR 17, record-files publication metadata), branch `docs/release-readiness-reconciliation`. Present status is in [session state](SESSION-STATE.md).
+
+This records what one static review covered. It is not an audit rating and not a release or production claim.
+
+## Scope and limits
+
+- Method: a source and test **read** of the server and Echo at the base above. Nothing was built, run or deployed for the review itself.
+- Validation of the resulting patch: on the working tree, root `./mvnw verify install` passed 53 tests with zero errors, failures or skips and 0 Checkstyle violations, and the frozen 1.5.0 YAML's SHA-256 equals the runtime YAML. Base demo verification also passed all 8 HTTP/presence/migration tests, zero failures/errors/skips and 0 Checkstyle violations (61 tests total). Earlier cohort counts in [session state](SESSION-STATE.md) remain historical and were not rerun on final public inputs; no whole-cohort or public-release verification is claimed.
+- Found no actionable source blocker among the traced paths: admin single/bulk processes, device approval and revocation, session end, scan idempotency, session mirroring, Echo copies and retry, and the optional file-integration guard.
+- Not verifiable here: Android-source items (A3, A5, A6, A8, A10, A11), which rely on the Android repository's own closure report.
+- Not read in that pass: the GS1 renderer-side classes (`EchoGs1`, `EchoTemplates`, `EchoTemplatePublisher`, `EchoOwnerAdapters`), `EchoDemoAuthentication`, `LocalStagingChunkStorage`, `PrivateObjectFiles`, and the Record Files and Echo test sources.
+- Not covered: physical output (copies, GS1 print and rescan), the owner Generation/Printing behavior, browser E2E re-run, MC9400, HTTPS and the identity provider. These remain pending as listed in [production readiness](PRODUCTION-READINESS.md). The three earlier dated reviews predate GS1, copies, photo capture and the 1.5 raw metadata.
+
+## Actions taken from the review
+
+- Status documents reconciled to the committed GS1 source and PR 17.
+- [Operations and recovery](OPERATIONS.md) added; it is a procedure, not an executed drill.
+- A frozen 1.5.0 OpenAPI baseline added to the contract test; the existing baselines and assertions remain. No runtime or contract change.
+- `UI-API.md` operation table now lists all seven operations; root `pom.xml` url, scm and issue tracker point at Gitea.
+- Deferred: the screen-upload 409 and every other operation's 409 share the generic text "Installation already enrolled" in `MobileJsonSpec`. Correcting it is a contract text change needing a patch version bump and regenerated YAML, so it is not done here.
+
+## Supplement: findings checked after the review
+
+Scope: the four findings raised after the static review. This is not an audit rating or a score.
+
+- **F1, concurrent metadata overwrite:** fixed in `PrivateObjectFiles` and regression-tested by `PrivateObjectFilesTest.lateSecondWriterIsRefusedAndFirstWritersBytesAndMetadataRemain` (also `existingObjectIsNeverReplaced`). The controlled interleaving reproduced mismatched metadata on the old implementation; all eight storage tests then passed with the fix.
+- **F2, dot bucket traversal:** fixed and regression-tested by `PrivateObjectFilesTest.dotBucketsAreRefusedAndValidBucketsStillWork` (also `keysCannotTraverseOrAlias`).
+- **F3, ZPL command injection:** disproven at source. In the owner Generation renderer, `ZplRenderer.java` lines 326-331 encode every UTF-8 byte under `^FH`. `RendererTest.typedZplEscapesCommandsAndEmitsRasterBarcodes` covers `^XA`, `~JA` and underscore input. That source is owner-held; the exact published artifacts are still pending qualification.
+- **F4, label clipping:** the assumption is guarded by renderer placement bounds, which refuse overwide text. No universal media-fidelity claim is made.
+
+The fixes were verified by the 2026-11-05 combined five-module `verify` (196 tests, zero failures, errors and skips, zero Checkstyle violations) on qualified private owner dependencies, not on published artifacts. Pending: owner artifact qualification, physical output and any enterprise object-store or high-availability recovery (unsupported, not tasks of this release).
+
+## Inherited guardrail heuristics (visible, not disabled)
+
+Two generic guardrail reports are heuristic mismatches, not missing behavior. They stay visible as existing signals; no check was disabled and no test marker was added to satisfy them.
+
+- **Cross-QBit references.** Root `src` imports no other QBit's package and its POM depends only on core, Javalin and test libraries. The references are in the separate Echo and Record Files modules, where they are the purpose. Any allowlist belongs at the guardrail, not here.
+- **OpenAPI and test markers.** The contract is covered by `MobileScannersApiContractTest` (generated against committed YAML and the 1.0.0, 1.1.0, 1.4.0 and 1.5.0 baselines, exact path set and schemas) and real discovery in `MobileHttpAcceptanceTest`. A generic string-marker scan cannot see this.

docs/SESSION-STATE.md

@@ -1,258 +1,51 @@
-## November 3 — current checkpoint (supersedes everything below)
+# Session state
 
-- **Server source:** `45f9cbddb14999d28add02dd9a37e4ce018e282e` is signed and pushed on Gitea PR 7 (earlier "uncommitted" statements below are historical). The five `qqq.version` POM pins to public **QQQ 4.1.0-RC.21** (root, demo, Echo, Echo demo, record-files) and the record-files POM test fix below are included in this verified dependency update.
-- **Final RC.21 gate: PASS** (`C:/Users/james/.cache/qqq-rc21-copies-gate-076d059d8d0641d9a85874ec64008def/verified-summary.json`). 377 unique tests with zero failures, errors or skips and Checkstyle PASS: Generation 179 and Printing bridge 16 (`verify-recovery.log`); scanner 53, demo 8, mobile Record Files 18, Echo 68 and Echo demo 35 (`verify-consumers-junit-fixed.log`). Plus 15 real admin-browser E2E cases on public RC.21 (single, checked and query selection, first-N approve, revoke, end session, display name/description, location/online, screenshot widget). The three earlier MySQL network timeouts did not recur in the focused 31 or the full 179 runs; the original failure reports are retained.
-- **Owned source fix:** `integrations/record-files/pom.xml` drops the aggregate Jupiter 5.11.4 and uses the BOM-managed engine and params; the XML test classpath shows API, engine, params and platform all at 6.0.2.
-- **Dependency honesty:** the five owned scanner consumer modules resolve only public QQQ artifacts (core, rdbms, middleware, filesystem, openapi RC.21; frontend-next RC.35), and Generation's core is RC.21 too, so all 182 scanner-consumer tests use public QQQ modules. The 16 Printing-bridge owner tests still resolve three private `pu507` QQQ libraries (filesystem, Javalin, OpenAPI) transitively through the existing owner Printing POM, and the other owner qbits remain qualified private inputs. So: **377 pass with public core RC.21 plus qualified owner inputs; this is not a fully public or released cohort.** No normal-runtime core upgrade was performed.
-- **Generation copies:** canonical Git source is now `Website-Backend/third-party-src/qbit-document-generation`. Signed `aac68907e67906aeef4e0cd687d28bc98b738f8c` is pushed on `feature/echo-generation-copies`, based on the actual PR 343 head `8f473fa`. The isolated clone `C:/Users/james/.cache/qqq-generation-copies-git-20261103` has 13 paths (including the PostgreSQL migration and provenance); the 21/21 module manifest matches. Qualified: 179 Generation + 16 bridge tests (prior cohort) and a fresh real PostgreSQL 17 migration pass. Owner integration and public artifact publication are not acknowledged and remain pending. No peer active checkout was edited.
-- **Android:** `f72b90d08cf29d2785cef1d5c5e7eeaf75f9afd2` is signed and pushed to the existing AGit PR 10 head (read back independently over SSH). Gitea CI 3480 **succeeded** on it (unit-test, device-test, package, secrets, gate; root read the UI); root also verified a clean git merge-tree of f72b90d with actual `main` b75fdac and merged nothing. Pull requests #8 and #10 remain open; nothing is released. The updated normal APK (SHA-256 `4AAB6951D3B0ABDDD4F5A8DC6790DCD84233EE08179B68DB108BF77909AB850E`) is installed with the same signer and no data clear; Connected, Apps, Settings, portrait, location on and the system-wallpaper brand-only preview were verified. No wallpaper or profile was applied. Fresh: 222 JVM tests, lint 0 errors/0 warnings (2 info), APK builds, 23 Node tests, 255-file standards pass. A fresh disposable TC22 Echo ten-stage run passed 109/109 semantic requests (simulated inputs and printing).
-- **Authentik:** a fresh real desktop acceptance passed against the same isolated TLS fixture (nonce, A login, logout with old-cookie replay rejected, fresh B without clearing cookies, logout). The opt-in native harness is integrated and compiled and its 8 launcher guards pass. Native TC22 execution still needs the temporary CA and PIN interaction (pending); no trust bypass. The normal server on 57832 is unchanged and ready.
-- **Still open (not claimed):** Generation canonical owner integration and public reproducible inputs for the owner qbits; primary source CI, merge and release; the manual TC22 trigger, value/type, AIM, label count, rescan, photo, GPS, projection and profile checks (the operator is still remote); native Authentik CA, PIN and callback; and signing/distribution, deliberately last by user decision. The normal TC22 currently shows Echo setup, Copies 1, Connected.
+Current as of **2026-11-05**. Open work is in [TODO](TODO.md), release gates in [production readiness](PRODUCTION-READINESS.md), and prior evidence in [history](history/README.md).
 
-## November 3 — publication preparation (historical; superseded by the current checkpoint above)
+## Source and publication
 
-The scanner/Echo/demo sources for copies per scan, AIM/EAN/UPC fidelity and photo composition are in the working tree of `feature/echo-example`, ready for one signed commit and review (not yet committed). They declare no private artifact coordinates: Echo's POM states that copies need a Generation build with the print-copies change, and `integrations/record-files` now takes `qqq.version`, `mobile.version`, `recordfiles.version` and `collaboration.version` with the demo's defaults. The Generation copies change is ten hash-checked files; its eight existing files match the Kof22 release reactor's `third-party-src/qbit-document-generation` byte for byte (SHA-256 listed in `qqq-finish-server-ready-20261103.md`). No Git repository for Generation exists in these local directories: adoption belongs to the Kof22 release repository, so the change is a hash-verified file set, not a commit here. Nothing was built or pushed in this step.
+GS1-128 duplication, including barcode and printed HRI, is merged through [PR 15](https://git.kof22.com/QRun-IO/qbit-mobile-scanners/pulls/15), commit `f9b0eb2`, and included in the [Forge source prerelease](https://git.kof22.com/QRun-IO/qbit-mobile-scanners/releases/tag/echo-gs1-source-20261104). This is source publication, not a published Echo Maven dependency. PRs 17 and 18 add publication metadata, the frozen contract baseline and recovery guidance; those changes are retained in this feature branch.
 
-## November 2 — Echo copies adopted in the normal local server
+The [rich demo fixture](MOBILE-TEST-DATA.md) and [record UX improvements](history/MOBILE-UX-2026-11-05.md) are implemented. Native browsing, record Actions and photo presentation belong to the companion Android repository. The user authorized the final release, signing and publication for this bounded goal. Android [PR 15](https://git.kof22.com/QRun-IO/qqq-android/pulls/15) merged as `c782aaaaba3f62422232436a9000af9d4b38fc82` after all CI. Maven publication switches stay disabled until the public dependency cohort is adopted.
 
-Optional **Copies per scan** defaults to 1 and accepts 1–100. Omitted/null/blank setup uses 1. The run pins the quantity; scan payloads cannot change it. Each scan creates one retained job with options.copies, with retries preserving quantity and job identity. Existing records migrate to 1. The normal server on port 57832 now runs this feature, mobile-scanners 1.5 and mobile-record-files 1.0 using the original database, approval, accounts and printer configuration. The unchanged normal TC22 APK is connected and shows the setup field with 1.
+| Item | State |
+| --- | --- |
+| Primary forge | Gitea `QRun-IO/qbit-mobile-scanners`, default `develop`; Android uses protected `main`. GitHub is a shadow/archive. |
+| Scanner development snapshot | PR 12 merged; run 3645 published `0.1.0-20261103.233448-3645`, anonymously read back and compared to its reviewed source. |
+| Printing | PR 13 merged; Echo defaults to released Printing `1.0.0`. |
+| Android libraries and signed preview | PRs 8/10 merged at `0ae2101`, documentation through PR 14 (`464814f`); SDK run 3634 verified. `scanner-v1.0.0` is a signed preview, not production qualification. |
+| Production 1.0 | Not released. Publication policy and switches are unchanged. |
 
-Verified gates: Generation 179, Printing bridge 16, scanner 53, base demo 8, mobile Record Files 18, Echo 68 and composed demo 35 tests (377 unique tests across module runs, no failures/errors/skips). Native TC22 acceptance passed ten stages and 116/116 semantic requests, including default 1, range rejection, chosen 3 across two scans, recreation and Leave. Scanner inputs/printing are simulated; physical count remains unconfirmed. Android source also passes 222 JVM tests, lint and APK builds; 15 Node tests pass.
+## Local runtime
 
-Generation's ten-file copies contract is verified in C:/Users/james/.cache/qqq-generation-copies-20261102 with handoff qqq-generation-copies-handoff.md; canonical owner adoption/publication is still pending. Echo photo composition is running and its authorization tests pass; actual capture/upload is unqualified. Native Authentik and physical trigger/print/rescan, camera/GPS/projection checks are deferred while the operator is remote. No certificate installation is confirmed. Public coherent artifacts/CI and final signing/distribution remain open. Earlier checkpoints below are historical.
+The maintained composed Echo server and **existing TC22 app** were updated in place on November 5. Database and attachment objects were backed up first; accounts, enrollment, app data and printer configuration were preserved. Live reads verified 1,000 test orders, 12,000 items and 3,000 history entries; orders have 39 fields, six groups and two associations.
 
-## November 2 — current checkpoint
+Use **Test Data → Test Orders → a record → Actions → Add photo**. Details, Items, History and Photos tabs provide direct access. Search/filter/count and Back preserve table context. Approved photos have thumbnails/previews; quarantined uploads remain listed as awaiting review. Ordinary read/attach permissions still apply.
 
-Source candidate: mobile-scanners 1.5 adds optional `aimIdentifier` and exact SDK `rawDataBase64` to persisted scans and backend `scanContext`. Changed metadata on an existing event is rejected; identical retries retain the original row, and omitted metadata cannot leak from the preceding event. The generated semantic contract remains compatible with the unchanged 1.0, 1.1 and newly preserved 1.4 baselines. The isolated four-module reactor passes 135 tests (53 scanner, 8 native HTTP demo, 45 Echo, 29 composed demo), zero failures/errors/skips and Checkstyle clean. Independent Claude diff review found no actionable correctness, security or compatibility defect; a whitespace-only review correction followed verification. This candidate is not installed in the running demo; hardware AIM extraction and extended Echo fidelity remain open.
+**Approved-scanner photos.** The Echo host sets Record Files `quarantineCapturedFiles=false`, so a JPEG/PNG captured by a currently approved device is `AVAILABLE` at once. Uploads, imports and attachment-panel files stay `QUARANTINED`. Parent tables are Echo scans plus the test orders, items and events; the scanner's existing `.attach` grants are retained. Only `admin` gains `record-files.release`; scanner grants are unchanged. Three earlier quarantined photos were released through the audited admin Release process. The server's current aggregate was built from public Core SNAPSHOT, current Collaboration, the scoped local Record Files change and qualified private document inputs, not a final public cohort. The scoped Record Files change is [owner PR 1](https://git.kof22.com/QRun-IO/qbit-record-files/pulls/1) (policy commit `3f08c584`), open and unmerged; its public CI currently fails an enrollment check that the coordinator owns, so neither the check nor its merge gates are changed here. No version or POM was guessed.
 
-The first actual Echo native HTTP event exposed a composition defect: Generation requested its default 20 MiB allowance from a renderer capped at 1 MiB. Both demo launchers now propagate their configured cap into Generation. Restoring the old wiring produces three regression failures; the fixed library/demo reactor passes all 74 tests (45 + 29), with no failures, errors or skips and Checkstyle clean. The preserving local server restart uses these tested artifacts. A new, clearly synthetic `ECHO-HTTP-TEST-001` Code128 event completed real rendering, retention and printing: one job reached `SPOOLED` with a spooler job assigned, and native Cancel closed the process. The earlier failed event remains `ATTENTION` without a print job and was also cancellable. Neither event is a physical TC22 scan. Paper output and rescan confirmation remain pending; see [delivery receipt](../examples/echo/demo/docs/echo-delivery-acceptance.json).
-
-The real trusted-local renderer has produced Code128 `QQQ-TEST-123456` and QR `001234567890` from the actual published 4x1 revision. Independent ZXing pixel decoding and stock/margin/fit checks pass; a fresh native read confirms the same published revision and stock. See [rendering evidence and test images](../examples/echo/demo/docs/ECHO-RENDERER-ACCEPTANCE.md). That earlier rendering-only check submitted no printer job; the subsequent synthetic delivery is recorded above. Physical acceptance remains open.
-
-The primary CI secret-scan failure was reproduced locally as five findings in inert test-token literals. The fixtures now generate tokens at runtime; `.gitleaksignore` names only the five exact historical commit/file/rule/line fingerprints. There are no rule or path exclusions and no production validation changes. Historical and staged Gitleaks scans pass, and all 27 composed demo tests pass with zero failures, errors or skips and zero Checkstyle violations. Current hosted CI still needs verification after publication.
-
-Completed and verified:
-
-- Server source `e3b775e` is signed and published as Gitea PR 7. The Echo library and composed demo pass 74 tests with zero Checkstyle violations. Host forwarding accepts `localhost` and `127.0.0.1` with a valid explicit port, and foreign Host and Origin values are denied.
-- One local QQQ demo server on host port 57832 runs Mobile Scanners/Echo, Collaboration/Record Files, Document Generation and Printing (API 1.10.0, mobile 1.4.0, printing 2.3.0). On this workstation, device port 8080 forwards to host port 57832. The original accounts, enrollment and approval are retained.
-- Android `fb3cc5d` (Gitea PR 10) adds the native same-origin fix. The normal TC22 was updated without clearing data, and existing login and approval, heartbeat, real printer, media and document selection, and Cancel then Leave were verified. The emulator is off because it stalls this workstation.
-- The installed print client (RC4) is signed in, enrolled and connected to this server, and its native-approved ZPL printer is available. The Printing owner has aligned the loaded 4x1 stock (101600 x 25400 microns at 300 dpi) and updated the real media revision. No UAC prompt or printer setup is pending.
-- A real Echo 4x1 barcode document is published through native authoring, with a matching immutable revision 1. The TC22 selected the actual printer, the fresh 4x1 media and that document. Next succeeded and the device shows Scanner ready and Connected.
-
-Not yet done:
-
-- No physical Echo print or rescan has been proven. The synthetic event has exactly one matching scan and one actual ZPL job in `SPOOLED`, rechecked at 16:31 UTC. The same read-only check confirmed server HTTP 200, print service Running, and the normal TC22 showing Echo / Scanner ready / Connected. One physical scan of QQQ-TEST-123456 has been requested from the user; no UAC or setup action is pending.
-- The earlier native end-to-end run (7 stages, 112 semantic requests) used simulated printing and inputs. It is not physical evidence.
-- Still open for 1.0: physical Code128 and leading-zero QR scan, print and rescan; the full original provider, camera, GPS, projection and device qualification; public coherent artifacts; primary Gitea CI; and final signing and distribution. Signing is deliberately last, by the user's decision. A working first demo does not collapse these requirements, and nothing here claims release readiness.
-- Core native API merge continuation PR 1337 (a42f9e5) was reviewed with no actionable conflict regression, and its 57 focused tests were verified. Normal CI and publication are not established, and default dependencies are not repinned.
-
-The entries below are historical. Where they describe same-origin login, printer connection, media, document publication or server composition as pending, this checkpoint supersedes them.
-
-## November 2 — one local QQQ server and installed print client connected
-
-The canonical local server on57832 now runs Mobile Scanners/Echo, Collaboration/Record Files, Document Generation and Printing together, using the existing development database. Both original accounts authenticated. Live discovery advertises API1.10/mobile1.4/printing2.3; authenticated administration metadata exposes the composed modules. This is greenfield local development: no backup, cutover or cross-server bridge is required.
-
-The full demo gate passes27 tests with zero failures/errors/skips and zero Checkstyle violations. It includes file-backed existing-data acceptance and the USB-forwarded loopback Host regression. Actual running HTTP checks accept Host127.0.0.1:8080 through57832 and reject foreign hosts/origins. The TC22 retains its original app data, approved device and8080 USB connection; no emulator runs.
-
-The existing RC4 print client is now natively signed in, enrolled and connected to57832. It reports five printers/two exposed. The sole available ZPL printer was approved through the ordinary printingEnablePrinter process; the persisted native query confirms enabled/available. No physical job was sent and printer defaults were unchanged.
-
-(Superseded by the current checkpoint above: the same-origin header, 4x1 media report and document publication are done. Only the physical TC22 scan, print and rescan remains for the demo, and the full production release gates remain open. Earlier separate 53118 pairing and Windows-prompt status below are historical.)
-
-## November 1 — corrected setup verified on TC22 and published
-
-Server source8da274e and Android test-only source47a923a are signed/pushed; Android's actual Gitea PR10 review topic was advanced to47a923a via SSH AGit (the source feature branch alone does not advance an AGit review ref). Required printer/media/INTEGER Document selection, dependency clearing, two accepted synthetic scans with the same selections, recreation and Apps/Leave all passed on real TC22:7 stages,112/112 published semantic requests,15 operations. Normal app/data preserved; emulator off; printing/scanner qualification flags remain false. Server45/library24/demo and Android99focused/host tests+8Nodeguards/lint0errors0warnings pass. Live private server53118 is still101efc8/EchoRetry pending document-choice rollout, and actual printer pairing awaits the current Windows consent in existing session73437. No root physical print has occurred. Normal57832 stays unchanged.
-## November 1 — operator chooses the Document at setup (server verified)
-
-User-confirmed flow: choose printer, Document template and paper/label size once, then repeat scan -> server render -> accepted print job until Leave. The Android client remains a generic semantic QQQ process client; it has no printer-device integration. `templateId` is required INTEGER with an authorized dependent PVS, not a hidden server default. The run pins selected template/revision; changed documents are refused rather than substituted. Migration preserves existing rows. Root:45 Echo library/24 full composed demo tests PASS, Checkstyle0. Tests include two document choices, forged retarget refusal, republish refusal with native Leave/CLOSED and repeated scan rendering. Expected errors use existing output.setException to retain process ownership after core step failure. Native Android tests99 + Node8 + lint0errors0warnings/testAPK compile pass; updated TC22 UI acceptance remains in progress. No physical print claim. Private live53118 remains filtered source101efc8/EchoRetry until this rollout, and printer retry awaits Windows consent; normal57832/TC22data are preserved.
-## November 1 — shared device headers scoped per extension registry (verified)
-
-`MobileScannersRouteProvider` interpreted every `X-QQQ-Device-*` header as a scanner credential, so a native Printing agent's own proof got 403 on `/qqq/v1/qbit/printing/*`. It now leaves a request to another extension's own authenticator only when the path is another extension's `/qqq/v1/qbit/*` route (not scanner routes, metadata, process or widget calls) and QQQ already validated a registered, non-`android`, non-`web`, non-token client channel. Android and unmarked requests keep scanner verification everywhere, ended-session and approval checks are unchanged, and no scanner device is bound for the foreign route, so the marker grants nothing. New composed demo regression `printerDeviceProofIsAuthorizedByPrintingAndNeverByScannerAuthentication` passed against the new immutable private scanner artifact. Root verification:50 scanner tests,7 base-demo HTTP tests and23 composed Echo-demo tests, Checkstyle0. The corrected regression fails403 at printer binding on the old artifact and passes on the fixed artifact; wrong proof/actor and scanner-boundary denials remain enforced. Live update and physical printing are separate.
-
-## November 1 — independent review corrections verified
-
-The scoped independent review of Echo4bc88a4/Androida2f0080 found a pre-pin recovery gap, an unchecked atomic pin result and a late-revocation receipt-audit gap. The fixes preserve authorization checks and lookup-only recovery after a pin. Five meaningful regressions now pass: Echo38 and full composed demo22, Checkstyle0. See ECHO-RELEASE-REVIEW-2026-11-01.md. The running private backend remains on the earlier qualified Echo artifact until an owned rollout; no running SDK or normal operator database was overwritten. Physical print/rescan and public release gates remain open.
-## November 1 — Echo composed pipeline verified and private backend live
-
-Echo's 33 tests and the runnable demo's full22 tests pass with zero failures/errors/skips and Checkstyle0. The clean native HTTP acceptance uses the real Generation, Record Files and Printing owners: two scans create two retained originals and two accepted jobs; retry preserves one job, and Leave closes the run. Renderer output is controlled and printer inventory simulated in this test, so physical printing remains unqualified. The Echo source checker now accepts core's exact bare READ capability probe while preserving user/permission checks, actor row locks and concrete write denial. The demo enriches complete QQQ metadata, establishes attachment capability, and derives the printing tenant idempotently. Host tests reset JVM-local RDBMS providers between fixtures.
-
-The local launcher uses the renderer owner's explicit TrustedLocalDockerExchange public factory (unique private renderer0.1.0-echo.gen64c9pu507.tl1); no copied transport or production fallback remains. Owner52 tests and real Docker smoke qualify development use only. A fresh private instance is live with successful scanner/admin semantic login and metadata; no printer or template is configured yet. Normal operator data/runtime remain preserved.
-
-Next required path: native Windows printing connection/current4x1stock handoff, publish and pin a real media-matched template, actual TC22 scan/print/rescan, and primary Gitea CI/public dependency publication. Full1.0 physical provider/GPS/photo/screen gates and broader AIM/EAN/UPC/GS1/raw barcode fidelity remain open. Production signing/distribution is deferred as requested. Passing private SDK/source gates is not a production release claim.
-## November 1 — coherent scanner and Record Files regression verified
-
-Security-key snapshots compare effective membership as sets, allowing identical repeated grants and reordering while rejecting new or changed authority. Optional Record Files authentication applies the owner's CollaborationSecurity.applyToSession during login/revalidation before the first verified capture. Scanner50 and native Record Files18 (16 integration +2 contract) pass with zero failures/errors/skips and Checkstyle0 against the complete private gen64c9pu507/PU dependency cohort. This supersedes the prior pending/failed native18 checkpoint; it does not declare private dependencies published or production-qualified.
-
-Echo32 and runnable demo12 also pass on that cohort. The demo startup test uses a refusing renderer; actual live cold renderer configuration and physical print/rescan remain pending. Android169 JVM and five-stage TC22 native semantic Echo acceptance passed with simulated printing. Gitea is primary for further source publication; previous GitHub PR links are historical shadow references. Preserve the normal scanner/server/data and printer installation. Signing/distribution remains deferred.
-## November 1 — verified capture identity retained without authority drift
-
-Claude's scanner fix preserves the same already-verified session only after current approval/binding/authentication and unchanged session reference/authority checks. First capture still wraps. Tests cover repeated object identity, current permission/credential ceilings/selectors, device and user binding, revocation, and real post-query-hook mutations during validation. Mutable opaque authority values refuse retention. Full scanner49 and real demoHTTP7 cases pass with Checkstyle0 against the frozen privatePU/f708 core.
-
-The files owner still must qualify its strict native upload/finalize18 against this exact patch; no per-instance enrichment policy or global registry is adopted. Normal server/data remain unchanged. Echo native TC22 now passes all5stages/86documentedrequests with client3bec46d; real renderer/printer output and final host integration remain open. Production signing is deferred.
-# QQQ Mobile Scanners session state
-
-## November 1 typed scan context implementation
-
-Extension 1.3 defines accepted `scanContext` for backend actions, preserving exact symbology and server-derived attribution. Legacy omissions are explicit UNKNOWN/MANUAL; event inputs are consumed, changed retry types/apps/processes are rejected, and pre-context state requires reopening the process. The default scanner loop remains while appended host steps can consume context. Qualified private API 1.10 verification passes 44 root, seven real-HTTP demo and 18 optional integration tests with normal Checkstyle; canonical contract generation passes two additional tests and preserves both release baselines. The source cohort is `qqq-server-typed-context-843fa0ee69b34535b1890cf7347492ee`; no normal runtime adoption is implied.
-
-## Echo implementation scope
-
-User requested example QQQ application Echo: first select printer and paper/label size, then continuously scan → render the same value/symbology → print until leaving. User chose one in-flight job and delegated first real printer/media choice to the printing master. Team implements the optional examples/echo host, ordinary semantic QQQ process metadata and server per-scan context; no new Android screen engine, barcode encoder, attachment framework or print queue.
-
-Owner coordination requests are posted in our shared mailbox. Source discovery found missing authorized media discovery/job options, worker barcode fit-to-stock, least-privilege printing submission and an immutable retained-print adapter handoff. These are concrete integration gates, not permission to change the other masters' source or live printer/service. Implementation and isolated tests can proceed while owners respond; no physical print or final working Echo claim yet.
-
-## November 1 standards implementation and API 1.10 qualification
-
-Copyright/SPDX, member layout and optional PowerShell tooling fixes are applied. Unexpected server failures now produce fixed structured diagnostics without private values. The attachment test fixture closes its metadata-before-stream ownership gap. Fresh Checkstyle/compilation, 39 root tests and six real HTTP tests pass against the qualified private API1.10 cohort; optional integration verification is tracked in the standards review. These are source gates, not a normal-server deployment.
-
-Core native API1.10 is signed and published as e1e45b29f in draft PR1369. Its real Authentik fixture is upgraded and actual retained-browser account switching is under test. Android1127 is published; the installed normal APK is the diagnostics/location3fee build, preserving sign-in and data. Prior installed1c Code128, leading-zero QR and menu/reopen were physically confirmed. Default-on location, existing fine/coarse grants and system location are verified; an actual GPS fix remains open. Historical entries below retain their original scope. See [standards review](CODING-STANDARDS-REVIEW-2026-11-01.md).
-
-
-## November 1 provider logout implementation in progress
-
-Core32 passes all ten hosted checks, including corrected1000-test sample acceptance; Android8d8 passes all eleven checks. The final coherent core32/scanner1a3 cohort passes39 scanner/six demo/18 Record Files/15 browser cases and is recorded in the published qualification document.
-
-Real Authentik now passes a desktop-browser PKCE callback through the native-session exchange contract, principal A, QQQ logout and old-cookie rejection. This does not establish Android external-browser acceptance. A subsequent login with provider SSO retained silently reused A despite prompt=login. The pinned provider also ignores max_age=0. This is an open operator-handoff issue, not a passed two-operator test. Optional standard RP-initiated logout is being implemented in core branch feature/mobile-native-provider-logout (based on core32) and the Android client, with explicit API1.10 capability, encrypted session-bound hint storage, local logout independent of provider failures, and a separately correlated AppAuth end-session attempt. The user policy choice (automatic company sign-out versus retained SSO with account confirmation/Switch account) remains pending; default sign-out behavior has not changed.
-
-The optional Android provider-logout working patch passes148 JVM tests, lint and debug build; native cases compile but have not run. The first isolated core package failed at an UpdateOutput API mismatch before tests. Independent review also found the optional hint gate must reject alternate in-process/code-state authentication sources; corrections and an HTTP regression are in progress. Initial failed candidate evidence is preserved.
-
-The isolated localhost-CA E2E APK built from signed Android8d8 passes63 unit cases/zero lint errors and packaged CA/callback/signature inspection. It is not installed; no device trust changed. Normal TC22 remains portrait C891 and its API1.9/mobile1.1 server remains untouched. Current QR, camera/gallery, projection, GPS and failure/navigation operator acceptance remain open. Files-owner immutable handoff/default adoption and final signing/distribution remain separate.
-
-Updated: 2026-11-01
-
-## November 1 release reconciliation
-
-Published server1041693 retains its qualified source-pinned API1.9/mobile1.2 server/demo/browser/provenance evidence. Android portrait-default7de passes all eleven hosted checks; QR documentation2e0fd962 does not establish physical QR acceptance. The normal runtime remains coreecf/serverb14 API1.9/mobile1.1 on57832, with normal portrait-default C891 development APK installed preserving signer/data. Trusted EMDK Code128 evidence comprises eight priorF3AF events and oneC891 event; QR, lifecycle/ownership and failure/retry/leave operator paths remain pending. Whole-device1.2 is qualified source, not installed normal-server behavior.
-
-Filesystem portability passes142 discovered/138 passed/four existing skips, including the corrected invalid-reference exception contract; its metadata symlink-parent and NUL-reference findings are independently closed. The final coherent core32/scanner1a3 cohort passes78 consumer cases, including18 Record Files cases, with no separate filesystem override. Matching files-owner immutable/default adoption remains open. Actual Authentik flow remains pending; strict proxy TLS now works, while provider configuration returned a validation error under diagnosis; physical projection, camera/gallery and GPS acceptance remain open. Signing/distribution stays owner-deferred until the final step. [PRODUCTION-READINESS.md](PRODUCTION-READINESS.md) is the current matrix; older entries below retain historical scope and are superseded where their then-open state has changed.
-
-Cross-chat coordination uses `R:\agent-comms\README.md` and the mobile master's owned `R:\agent-comms\qqq-mobile-scanner.md`, explicitly requested by the user. Record Files and Printing acknowledged the directory. Read the current summary at the top of each owner's mailbox before changing shared contracts.
-
-## November 1 Record Files consumer checkpoint
-
-The isolated core32/scanner1a3 cohort passes all 78 consumer cases (39 scanner,
-six demo HTTP, 18 Record Files and 15 real-browser process tests), with coherent
-backend versions, 214 optional runtime JARs and zero duplicate QQQ/QBit classes.
-Core verification combines the prior full reactor gate, the corrected filesystem
-full gate and an exhaustive final artifact class comparison; see the precise
-[qualification scope](../integrations/record-files/docs/CORE-32DF-CONSUMER-QUALIFICATION.md).
-The files-owner matching immutable handoff, optional default adoption and actual
-camera/gallery acceptance remain open. This cohort did not change the normal
-runtime, device or historical optional default.
-
-## October 31 current checkpoint
-
-The normal local demo is now running the qualified `ecf0f550`/`b14d925` API1.9/mobile1.1 TABLE runtime at its existing loopback address. This supersedes the unchanged-runtime statements in the historical acceptance entries below. Read-only inspection froze its actual old classpath; old-runtime and old-after-new HTTP/login checks passed on historical and fresh closed backups before startup. Fresh copied invariants preserved every original column, row count, password/device-credential hash, barcode and UTC timestamp. Both original accounts passed live login, authenticated metadata and logout; ordinary semantic queries confirmed two devices and three scans, including the leading-zero barcode. The normal Android installation and peer services were preserved. Private backup/runtime evidence is retained in the task cache; old PID-specific maintenance helpers must never target the replacement JVM.
-
-Optional consent-based whole-device viewing is under implementation as an additive extension1.2 contract; it is not part of that running, qualified1.1 runtime. Android diagnostic checkpoint `6f25562` is published to its existing PR after instrumentation compilation; fresh hosted results remain pending. The actual trusted-scanner trigger attempt is unverified. Production signing/distribution remains the final owner decision.
-
-The initial1.2 reactor now passes39 server and six real-HTTP demo tests with normal Checkstyle, no failures/errors/skips, unchanged qualified-core hashes and unchanged1.0/1.1 baselines. Independent changed-file source review found no concrete introduced security finding; Android consent and projection acceptance remain open. The diagnostic Android checkpoint subsequently passed CircleCI37 native tests and unit tests; its earlier intermittent focus-owner cause remains unproven.
-
-Exact-source core `ecf0f550a0357cec6387c2b54efca128a405a629` with server `b14d925b741e815d1cfa4f62301f19207f25b03f` now passes fresh37 server/five demo tests, strict runtime provenance and all15 browser cases (zero skips/flaky/failures). The runtime has195 hashed JARs,2,440 unique QQQ classes, zero duplicate QQQ classes, patched Guava33.7.2-jre and H2 2.2.224. Core's full selected closure separately passes4,507 discovered/16 existing skips/zero failures/errors. See [qualification scope](API19-CONSUMER-ACCEPTANCE.md). No operator runtime was upgraded by this acceptance.
-
-The demo now imports the QQQ BOM using its own `qqq.version`, so an explicit version selection governs its complete transitive QQQ runtime. Private source qualification caught the prior mismatch: the scanner's installed POM retained its default RC.20 property, while the demo override selected a newer direct RDBMS dependency. The strict runtime verifier rejected the mixed core/Javalin/OpenAPI versions and older Guava despite passing tests. The first BOM-aligned run then exposed the demo's explicit JUnit 5.11.4 aggregate mixing an older API with the BOM's JUnit 6 engine; the demo now uses the BOM-managed test engine and its matching API/platform. The coherent candidate's fresh acceptance is recorded above; passing tests from the earlier mixed runtime did not establish that result. No operator runtime or shared Maven repository was changed.
-
-The normal operator demo was upgraded in place to mobile extension1.1 with a closed owner-only backup: two accounts, two devices (one approved), three scans, credential hashes and timestamp instants were preserved. Both original passwords authenticated after startup. Its JVM currently uses UTC because the copied upgrade exposed H2 converting legacy zoned timestamps using the workstation zone. The canonical H2 schema now begins by setting its migration connection to UTC, protecting both direct schema consumers and the demo initializer. A no-install reactor verifies the freshly packaged base resource: 37 base tests and five demo tests pass, with zero Checkstyle violations, including a file-backed America/Chicago child-JVM regression over all eleven converted timestamp columns, multiple source offsets, preserved passwords/approval/barcodes and an idempotent second startup. The isolated old-schema resource without the UTC statement fails with the expected six-hour winter timestamp shift; the tested jar resource hash matches the canonical source. This source change does not restart the operator runtime; it remains safely mitigated with UTC.
-
-The optional Record Files consumer now explicitly defaults to frozen0515 and its separate isolated-m2-0515 cache. Fresh normalized-heartbeat base37 and optional18 pass, with214 runtime jars/3180 classes/zero duplicates. Immutable evidence is retained under integrations/record-files/evidence/20261031-124632Z. Earlier0352 native acceptance remains historical;0515 is a new server consumer qualification, not an operator upgrade. Published dependency coordinates and hosted optional CI remain blocked on the upstream handoff recorded in HOSTED-CI-DEPENDENCIES.md. New API1.9 native Authentik metadata is being developed in an isolated core worktree and is not part of this server's adopted dependencies.
-
-Hosted Android acceptance exposed a heartbeat revocation defect after the published checkpoint: pending/revoked devices could keep receiving successful heartbeats and remain signed in. The fix checks approval under the existing activity lock before observing activity, and the route filter avoids pre-observation for canonical and accepted trailing-slash heartbeat paths. Both defects were independently reproduced before correction. Final root verification/install passes 37 tests and demo verification passes four tests, including the real HTTP no-side-effects regression and standalone presence case. Native hosted confirmation on the new server revision is still required; earlier static zero-findings results do not prove absence of this defect.
-
-Server checkpoint `0926550` includes 37 passing root tests, two HTTP acceptance cases, a passing standalone file-backed presence regression and 15 passing browser cases. The optional Record Files module adopts frozen bundle `retained-contract-20261031-0352`; 18 guarded integration/contract tests pass. TC22 navigation (12 cases), orientation, offline licenses, synthetic photos and the complete screen-viewing/session-end scenario pass on Android checkpoint `d5b5580`. These do not imply an operator-runtime upgrade or actual camera-lens acceptance.
-
-The full server deep static security scan of `0926550` completed and its canonical report was sealed on October 31 with no reportable findings. Coverage excludes external dependency implementations and production configuration; no new runtime tests were executed by the scan. The known external core DEBUG session logging issue, immutable Record Files publication/CI and production provider qualification remain open. Android's final full scan is still pending. A user-requested single-hamburger navigation correction is now being implemented after the published Android checkpoint; its new tests are not yet run.
-
-The normal operator demo and normal TC22 package remain unchanged. A separate temporary visual demo showed the new menu on the TC22; the user stopped computer control and retains the device. Do not restart, uninstall or drive that demo until coordinated. Signing/distribution remains deferred to the final step.
-
-The local emulator is closed after the user confirmed it caused workstation-wide stutters. TC22 is connected; do not restart the emulator automatically. Builds are serialized with bounded workers. Existing operator demo and handheld state remain preserved. Android85 JVM tests and zero-error/zero-warning lint pass at the last compiled checkpoint; newer changes must be verified again.
-
-The active goal authorizes completing and publishing the project, superseding historical artifact-publication deferrals below. However, on October31 the owner explicitly deferred signing and distribution until the final step because the channel is undecided. Complete implementation, final audits, tests, documentation and ordinary hosted CI first. No signing key, production release, merge or deployment is claimed.
-
-## Active: device sessions, live screen viewing and 1.0 audit
-
-Additional user scope: unique short device names assigned at setup/approval, editable names/descriptions, independent approval/presence, online fleet view and foreground GPS with age/accuracy. Camera/gallery photos use the separately developed Record Files qbit. The Build QQQ Documentation agent owns it and `qbit-record-files/docs/INGESTION-CONTRACT.md` documents the implemented record-files1.0 semantic capabilities/create/status/chunk/finalize/cancel operations and durable receipts. The October31 checkpoint above supersedes earlier proposed-only contract status. Native photo acceptance and the final authorization guard remain pending; unavailable capabilities stay hidden.
-
-The user requires all device/session history, live activity and actual application-screen viewing in QQQ administration, plus session termination. Implementation follows [DEVICE-SESSIONS.md](DEVICE-SESSIONS.md): ordinary QQQ tables/widgets/processes, server-owned authenticated bindings, an additive 1.1 semantic extension and demand-based bounded screen frames. Native and browser actions require full E2E coverage, including record and bulk entry points.
-
-The user also requires independent in-depth security, architecture, coding-standards and coupling/cohesion reviews of both complete repositories before a production-ready 1.0. [PRODUCTION-READINESS.md](PRODUCTION-READINESS.md) tracks the gates and exact baseline evidence. Plan: complete the session feature and tests; freeze final revisions for independent audits; remediate and verify findings; complete physical and release/operations acceptance. Deployment/distribution details have been requested. No 1.0 readiness or release is claimed.
-
-## Current: semantic API migration
-
-The qbit registers mobile-scanners 1.0.0 through QQQ's extension registry. Device enrollment/current status, branding and connectivity use `/qqq/v1/qbit/mobile-scanners`; discovery advertises the relative prefix `/qbit/mobile-scanners`. The generated OpenAPI includes typed device and scanner event/acknowledgment schemas, stable operation IDs and standard errors. Legacy standalone mobile routes are removed. [UI-API.md](UI-API.md) describes the contract and versioning policy.
-
-Root `verify install` passed 23 tests, including the extension contract baseline checks; demo `verify` passed one real HTTP discovery/schema/error/lifecycle scenario. All six migrated browser E2E scenarios passed in 2.9 minutes. Native integration exposed an unregistered Android client channel returning HTTP400; the qbit now registers `android` without replacing existing channel policies. The real HTTP regression sends `X-QQQ-Client: android/qqq-mobile` on all requests and passes. Android requires `android` in discovery's `clientChannels`; its combined JVM suites passed 53 tests (core 21/mobileapp 23/scanner 9), with six shared native UI tests also passing. Final lint passed with zero errors and six warnings; debug and E2E APK builds passed. Five native scanner scenarios passed with the OpenAPI request audit: incompatible core version, missing extension, missing Android channel, baseline scan flow and additive future metadata. The final native administration form scenario passed in 255.917 seconds after correcting completion handling for a COMPLETE response without `nextStep`: approval, revocation and cancellation completed, with all 31 requests matched to 13 published operations. All six native scenarios passed across the original and focused reruns; this is not a claim of one uninterrupted six-case run. All hosted checks passed for published server commit `7dd02b8874882ca2edcdcd89109b3dee6b4b0c88`: CircleCI setup/verify, CodeQL, Windows helpers and the demo HTTP/browser E2E job.
-
-Active plan: publish the companion Android checkpoint pinned to verified server code `7dd02b8`, then add the requested device/session activity, session termination and on-demand app-screen viewing. Physical connection-loss/retry and revoke-denial checks are deferred to acceptance with those session controls; the persistent server and USB forwarding are restored. The local server and emulator restarted after the workstation crash with data preserved; the backend administration UI was visibly signed in. The physical TC22 is identified through authorized USB debugging, running Android 14 and DataWedge 13.0.325. The debug app is installed and signed in. Approval from the browser record's Actions menu visibly reported one device approved; the handheld then opened the native app catalog and Scan Capture process. Updating the APK preserved its login. DataWedge is configured for package `io.qrun.mobile.scanner`, activity `*`, barcode input enabled, keystroke output disabled and Intent Output enabled. Intent delivery uses Broadcast, action `io.qrun.mobile.scanner.SCAN`, category `android.intent.category.DEFAULT`, and an explicit target package with signature checking enabled. Two deliberate physical trigger presses were confirmed by the user and produced two persisted records visible in Barcode Scans. A stored row matched the TC22 receipt for `QQQ-TEST-123456`, CODE128, source `scanner`, user `scanner`, TC22/Android 14/app 0.1.0, app `mobileScanApp`, process `mobileScanCapture`, and capture/receipt timestamps. Basic physical Code128 delivery and persistence passed. A subsequent physical QR scan was acknowledged on the handheld and independently visible in the backend as `001234567890`, `LABEL-TYPE-QRCODE`, source `scanner`, with matching TC22/user/app/process and capture/receipt metadata. Three physical records are verified: two deliberate Code128 captures and one QR capture. Physical QR delivery and leading-zero preservation passed; physical connection-loss/retry and revoke-denial checks remain pending. The old semantic-gap note below is superseded by this implementation status and the current TODO.
-
-## Verified: record and bulk device administration
-
-- User reported Approve Device did not work from a device record and required proper E2E coverage for every process, including single-record and bulk entry points.
-- Root and real HTTP regressions reproduced the missing selected device ID. Approval/revocation now prepare a stable selection, show confirmation, apply only after confirmation, and display a result/count. Explicit selected IDs and native select-all/first-N filters are supported up to 100 devices; oversized selections fail explicitly.
-- The process stores selected IDs in native process records, ignores replacement IDs submitted at confirmation, rechecks administrator permission, and validates all targets before changing any. Standalone manual ID entry remains supported.
-- Root verification/install passed 21 tests and Checkstyle. Demo verification passed the real HTTP scenario covering single-record approval, both bulk selection modes for approve/revoke, unselected-device isolation, visible results, scanner permission denial, scan persistence/retry, and revoked-device denial.
-- Restarted the persistent local demo on port 57832; public status returned `ok`. Accounts, database and emulator forwarding were preserved. Dedicated scanner-host native E2E passed (one complete real-server scenario, 50.932 seconds); Android verification also passed 28 JVM tests, lint/build and workflow syntax. Test APKs were removed and the normal scanner restored.
-- Browser E2E passed all six scenarios in 2.7 minutes: record approve/revoke with results and return navigation, checked-row bulk with untouched-device assertions, standalone manual entry, cancellation, full-query selection, and first-N selection with independent persisted-state checks. Tests use the packaged frontend and a temporary real backend. The fixture authenticates through the real API and supplies the nonsecret `qqq.sessionHint` marker so the UI resumes and validates its HttpOnly cookie. Browser checks now run inside the existing required demo CI job; native E2E runs in the Android push/PR emulator lane. New-head hosted results remain separate from these local passes.
-- UI/UX API clarification: the Android app uses `/qqq/v1` metadata/process operations, but full semantic-client conformance is unfinished. Version/feature negotiation, broader native component handling and migration of separate `/mobile/v1` routes into a registered UI API extension are tracked in TODO; do not describe the current client as fully conformant.
-
-2026-10-30 correction: native authentication metadata is served at `/qqq/v1/metaData/authentication`. The device-header guard now exempts that exact public path; the previous legacy-only exemption caused HTTP403 on app restart after enrollment when device headers were present before a user session was restored. A real HTTP regression failed before the fix and passed afterward with stale, pending, invalid-token and revoked device headers. Protected metadata/process/scan authorization still fails appropriately. Root13 tests, Checkstyle and demo HTTP acceptance passed; the local demo was restarted on57832 with its persistent database and accounts preserved.
-
-## Current repository and demo state
-
-- GitHub repository created at https://github.com/QRun-IO/qbit-mobile-scanners with `develop` as default. Initial signed commit `abbcc39` is published. Companion Android implementation is in https://github.com/QRun-IO/qqq-android/pull/8.
-- Hosted initial-commit checks passed: CircleCI `setup`/`verify`, CodeQL `analyze / Analyze branch source`, demo HTTP acceptance and Windows helper analysis. CircleCI dynamic configuration is enabled. Maven artifact publication remains disabled.
-- Runtime branding is configurable on the server before login; the shared Android APK uses the customer name, primary color and optional HTTPS logo. Public branding/status endpoints carry no credentials. Root tests now pass 13 cases; demo HTTP acceptance also passes.
-- Windows demo helpers store generated demo passwords using per-user Windows DPAPI outside the repository. An Android 15/API35 emulator is running with WHPX; six native UI instrumentation tests passed. Physical TC22 acceptance is still pending.
-- The current workstation demo uses loopback port 57832 because other services occupy the conventional ports. `adb reverse tcp:8080 tcp:57832` preserves the Android server URL `http://127.0.0.1:8080/`. Start it again with `pwsh -File scripts/Start-Demo.ps1 -SkipBuild -Port 57832` after stopping the existing instance. See `LOCAL-DEMO.md` for login helpers.
-- The earlier verification/handoff notes below describe the initial implementation before repository publication and emulator setup.
-
-## Confirmed scope
-
-- Native Android host for Zebra TC22 and other handheld scanners, extending `qqq-android`.
-- Server-defined native screens and QQQ process actions, using existing QQQ metadata.
-- Online only for version one; no offline scan queue.
-- Local demo server with real QQQ login and required administrator device approval.
-- First app: barcode capture into a QQQ table with scan, user, device and timestamp metadata.
-- User authorized Codex agents for implementation and subsequently requested GitHub repositories and standard project files. Repository creation and pushes are authorized; artifact publication remains disabled.
-
-## Completed plan
-
-1. Established enrollment and scan contract using existing QQQ APIs.
-2. Implemented qbit tables, native metadata/processes, approval/revocation and guarded routes.
-3. Added Android scanner host, table-based login/enrollment gate and Zebra DataWedge input.
-4. Added a file-backed H2 demo and verified native login, approval, scan, retry and revocation over HTTP.
-5. Built the Android debug APK and documented TC22 hardware acceptance.
-6. Added standard repository/community files, current shared CircleCI QBit configuration, CodeQL, Dependabot, demo HTTP and Windows-script CI, and a documented publishing policy.
-
-## Baseline and ownership
-
-- QQQ baseline: 4.1.0-RC.21 (public Maven Central; adopted 2026-11-03, gate pending). The local 4.0.0 middleware does not support Basic sign-in through `manageSession`; RC.20 and later do.
-- Backend agent: qbit main source, unit/integration tests and root POM.
-- Android agent: `qqq-android` source and scanner application module.
-- Toolchain agent: Android SDK installed after explicit user approval of required Google terms.
-- Parent: local demo, cross-component verification and documentation.
+The [local demo](LOCAL-DEMO.md) source defaults remain QQQ `4.1.0-RC.21` and Printing `1.0.0` pending the public-cohort update; the maintained runtime uses the verified development aggregate described above. Host port is `57832`. The TC22 development app retains its loopback forwarding; the signed MC9400 app connects through trusted HTTPS. Contract versions remain UI API 1.10, mobile-scanners 1.5, printing 2.3 and mobile-record-files 1.0. This is local development qualification, not a customer production deployment.
 
 ## Verification
 
-- Qbit: `./mvnw.cmd -q verify install` passed 11 tests (7 H2 behavioral/security tests and 4 inherited guardrails), with Checkstyle passing.
-- Demo: `../mvnw.cmd -B verify` passed Checkstyle and one real HTTP acceptance scenario. It verifies QQQ login, anonymous and pending-device denial, operator/admin separation, approval, async native process capture, same-event deduplication, SQL provenance, bad/missing device credentials, revocation while a process is open, logout and session replay rejection.
-- HTTP fixtures verify the actual native `composite`/`SCANNER` widget payload. The Android tests deserialize these real metadata/process/init responses.
-- Android: core/mobileapp/scanner JVM suites passed 19 tests, no failures or skips. `lintDebug` and `assembleDebug` passed. Lint has 0 errors and 5 warnings: 3 inherited Navigation custom checks skipped due to API incompatibility and 2 dependency/version notices.
-- Debug APK signature verified. Path: `../../qqq-android/scanner-host/build/outputs/apk/debug/scanner-host-debug.apk`.
-- APK SHA256: `B3E160CE3279C369CEDB425AC6E777A2729CE8A2E430E7D6F46D35C6376F8214`.
-- Android SDK location: `C:/Users/james/AppData/Local/Android/Sdk`; SDK 35, build-tools 34/35, Gradle 8.7.
-- `adb devices -l` returned no attached devices. No physical TC22, camera, or emulator acceptance performed.
-- Repository bootstrap verification: CircleCI setup validated against the private QRun-IO orb with explicit organization scope; Actionlint passed for both workflows. Current shared generator accepted the manifest and selected verification only for seven branch/tag cases. All publication switches are false. Root 11 tests and demo one scenario were rerun successfully after repository metadata changes.
+- Photo/admin change set (root-reported, not rerun in this review): 69 owner tests and 197 scanner/Echo tests passed (runs of 31, 158 and 8), 13 focused Android tests passed, and the relevant Checkstyle passed. These groupings differ from the module split below, so no per-module counts are claimed. Public immutable dependency qualification is still pending.
+- Live evidence: a fresh synthetic gallery PNG uploaded from the production-signed MC9400 app returned "Saved photo", and the server showed `AVAILABLE` with the exact parent, type, size and SHA-256. An older photo's Available state, thumbnail and Preview control were observed. The new photo's full preview was not clicked because ADB disconnected. No camera-hardware or full-preview proof is claimed.
+- The earlier combined five-module `verify` (2026-11-05, base `9e8685f` plus the storage fixes) passed **196 server tests** with zero failures, errors and skips and zero Checkstyle violations: scanner 53, base demo 8, mobile Record Files 22, Echo 74, Echo demo 39. It used qualified private owner dependencies; there is no public-dependency or physical-output qualification, and the gate must be repeated when the public cohort is adopted. The new build parent's report-only schema-location/contract-test findings remain visible.
+- Storage/recovery PR 21 is merged (`59959247`), with bounded cold-restore and race proof complete. Website 0.1.17 is complete. Evidence: `PrivateObjectFilesTest.concurrentSameKeyWritersLeaveOneWinnersBytesAndMetadata` and `dotBucketsAreRefusedAndValidBucketsStillWork`; recovery acceptance `EchoDemoAcceptanceTest.restoredSnapshotKeepsScanAndRetainedFileAndRevertedApprovalStateIsReaudited` (details in [OPERATIONS](OPERATIONS.md#isolated-local-demo-recovery-acceptance-automated-passed)).
+- Android passed **232 unit tests**, lint with **0 errors/0 warnings**, and the debug APK build. E2E APK/instrumentation builds and eight runner guard tests also passed.
+- Isolated MC9400 native acceptance passed search/filter/paging/Back, grouped/related records, camera/gallery upload, parent-scoped saved-photo list, approved preview, rotation, pending-upload navigation protection and forced-logout cleanup. All requests matched the semantic API. Process-photo regression also passed.
+- The final date-only correction received unit/lint/build checks and actual TC22 verification. Actual-device screenshots confirm Actions → Add photo, dates/timezones, currency, related tabs, photo empty state and return to page two. Synthetic camera/gallery inputs in automated acceptance are not a new operator camera report.
+- Earlier 135/188/198/377-test cohorts and 15 browser E2E cases are historical evidence, not a fresh run against future public dependencies. The snapshot source comparison applies to its original revision only.
+- 2026-11-06, branch `fix/refresh-device-versions`: the MC9400 in-place 1.0.0 to 1.0.1 update left the device record and every later scan reporting `appVersion` 1.0.0, because only enrollment ever wrote `manufacturer`/`model`/`osVersion`/`appVersion` and no later client request carried them. Extension 1.6 adds the same optional fields to `MobileScannersHeartbeatRequestV1`; the heartbeat refreshes the device record when a value differs and scans copy the refreshed record (see [UI-API](UI-API.md)). The Android host change (send `osVersion`/`appVersion` on heartbeat) is on the same-named branch in the Android repository; devices need that client build before their versions refresh. Root module: 56 tests, zero Checkstyle violations, new baseline `mobile-scanners-1.6.0.yaml`.
 
-## Handoff and remaining scope
+## Handhelds and remaining limits
 
-- Follow `TC22-ACCEPTANCE.md` for local credentials, loopback demo, USB forwarding, DataWedge profile and device tests.
-- Runtime demo server is not left running. No user credentials were created outside temporary test databases.
-- First host supports QQQ table-based authentication; other providers show an explicit unsupported message pending configuration.
-- Server enforces approved device plus authenticated user, including async execution. Enable QQQ core permission enforcement when embedding the qbit.
-- Only a current unacknowledged scan is retained in memory for explicit retry. Closing/resetting the app is not an offline queue.
-- The H2 schema is supplied; migrations for other databases and deployment authentication remain host-owned.
-- Pending physical acceptance is tracked in TODO. GitHub bootstrap and hosted checks are separate from artifact release or production deployment; use `CI-CD.md` for the repository settings and release enablement policy.
+Previous TC22 APK SHA-256: `F71033C835AC3EB361A04D78C842947C5A04C85CE1AB1B999AA8CEFBFC9D7A95`; prior preview hashes are in [history](history/RICH-RECORDS-2026-11-05.md).
 
-## Native authentication review follow-up
-The first optional provider-logout compile failure and alternate authentication-source hint gate are corrected in a new frozen source candidate; its isolated focused build is running. Independently, native login does not currently carry/validate the original request nonce against the provider ID token. PKCE code binding is present; no account-takeover exploit is claimed. Explicit provider-bound claim/nonce validation and real-provider acceptance remain required before production authentication closure.
+Signed Android `1.0.1` (code 3) was built from the identical merged source tree (PR 15) and installed in place on the MC9400. The installed bytes match the built APK, login and enrollment were preserved, the authorized Scan Capture screen reopened, and the HTTPS connection was established. The MC9400 physical trigger is **done**: an actual operator trigger produced a Saved scan, and the backend confirmed EMDK CODE128, AIM and raw bytes with server-derived attribution. The barcode scanned was not the literal string requested, so no exact-test-string claim is made.
 
-Android nonce/logout working source now passes151 JVM tests, zero lint errors/warnings and APK/native-test compilation. Independent26-file diff review is completed/sealed as c358cde3-b51d-4451-b07d-8d1afe6c4485 with no findings; this is source-scoped and does not establish native/browser/provider execution. Core combined nonce/test corrections remain in progress; initial diagnostic failures stay failed.
+Shared Authenticator server configuration is verified: real trusted HTTPS, UI API 1.10, both scanner and printing extensions and channels, exact callbacks and a REQUIRED nonce. Native client login, logout and account switching are **not yet tested** (this needs the MC9400 wireless-debugging endpoint), so no native-auth pass is claimed. The Printing client required-nonce fix (PR 11, `443f642`; 352 Windows/CLI tests and build passed) awaits hosted Core. Pending: native Authentik login/logout/account switching, the final public Core/Collaboration/document/files/scripting/bridge artifacts, a public-cohort rerun, GS1 physical print/rescan, signing-APK download publication and owned cleanup.
+
+The November 4 TC22 operator group pass remains accepted and is not requested again. Physical GS1 print/rescan, provider callback acceptance and fleet rollout remain open. Echo supports only its documented [barcode profiles](../examples/echo/README.md#fidelity-and-limits). Company profile/wallpaper is separate tracked scope, not a blocker for this release goal.
+
+Operations and recovery guidance is in [OPERATIONS](OPERATIONS.md). The automated stopped-H2 plus object snapshot/restore case passed as isolated local-demo recovery acceptance (no physical printing, no normal demo data changed). Enterprise object-store/HA and non-H2 databases are unsupported and unqualified, not release tasks. The [dated review](REVIEW-RECONCILIATION-2026-11-05.md) records its scope and supplement. Public owner dependencies require a separate reviewed adoption and a new gate.

docs/TC22-ACCEPTANCE.md

@@ -2,6 +2,20 @@
 
 This checklist records steps to run on physical hardware. A passing JVM test or APK build does not establish that a TC22 scan succeeded.
 
+## Operator acceptance — November 4, 2026
+
+**PASS — operator reported.** The user confirmed in the project conversation: "i have ran the manual tests - it all works". This closes the outstanding manual acceptance group for the installed local demo. The user did not supply separate per-case logs or output samples; this entry records their acceptance without inventing those artifacts. No repeat of the same manual checks is requested.
+
+The last recorded installed configuration was the normal TC22 APK with SHA-256 `38A11155BF6A9C089A1EE6D9E44401E8FF39497B7150B51A85F1F916148BE60D`, connected to the local composed server on port 57832 with public QQQ RC.21 and Printing 1.0.0. This identifies our last deployment record, not a new device inspection at the time of the user's tests.
+
+Release packaging/publication and the documented unsupported barcode profiles remain separate from this manual acceptance. Signed-build HTTPS device qualification and distribution remain deferred by the user. The procedures below are retained for future deployments and regressions.
+
+The development APK used for this acceptance is version 0.1.0 (code 1). The server it connected to is the local composed server described in [session state](SESSION-STATE.md).
+
+## Second handheld: Zebra MC9400 (Android 13)
+
+The MC9400 was installed and launched with a signed 1.0 release build. At the user's request it was then configured like the TC22 for now: the same development APK as the TC22, device port 8080 forwarded to the host server over paired wireless ADB, signed in as the `scanner` account, and approved through the ordinary **Approve Device** process. The original TC22 is unchanged. **Pending:** one physical trigger scan and the matching backend scan record. Run the acceptance sequence below on it when convenient; the November 4 operator pass above covered the TC22 only.
+
 ## Start the server
 
 From `qbit-mobile-scanners`, build and install the qbit, then build the demo:
@@ -44,7 +58,7 @@ Create a dedicated profile associated with package `io.qrun.mobile.scanner` and
 
 In Intent Output's Component Information, restrict delivery to `io.qrun.mobile.scanner` and enable its application signature check. Use single-decode mode. Zebra documents barcode text, symbology and source in its [DataWedge 13 Intent Output guide](https://techdocs.zebra.com/datawedge/13-0/guide/output/intent/).
 
-## Observed hardware results, 2026-10-30
+## Observed hardware results, 2026-10-30 (historical record)
 
 The attached TC22 runs Android 14, DataWedge 13.0.325 and QQQ Mobile 0.1.0. Installation, sign-in, pending enrollment, approval from the browser record Actions menu, native app discovery and opening Scan Capture passed. Updating the APK preserved login. The profile uses the package/activity, input/output and explicit package/signature settings above.
 
@@ -52,7 +66,7 @@ The user confirmed two deliberate physical trigger presses; two scan records wer
 
 The user then confirmed a saved physical QR scan; the backend record preserved `001234567890` exactly, with `LABEL-TYPE-QRCODE`, source `scanner`, and matching TC22/user/app/process and capture/receipt metadata. Three physical records are now verified: two deliberate Code128 captures and one QR capture. Physical QR delivery and leading-zero preservation passed.
 
-Physical connection-loss/retry and revocation-denial cases remain pending. Complete the remaining sequence below before claiming full hardware acceptance.
+The connection-loss/retry and revocation-denial cases were still open when this was written; the operator's November 4 report above covers them as part of the outstanding manual group, without separate per-case artifacts.
 
 ## Acceptance sequence
 
@@ -67,4 +81,4 @@ Physical connection-loss/retry and revocation-denial cases remain pending. Compl
 9. Sign out. Confirm the scanner cannot save under the previous user and the previous user session is ended.
 10. Restart the server and application. Confirm saved scans and device approval persist. Reinstallation/data reset must not silently inherit approval.
 
-Record pass/fail and observations in `SESSION-STATE.md`. Hardware acceptance remains pending until these steps are actually performed on the TC22.
+For a new device or a regression run, record pass/fail and observations in [session state](SESSION-STATE.md) without device serials, addresses or credentials. A device is not accepted until its own steps have actually been performed or reported.

docs/TC22-UIUX-REVIEW-2026-11-05.md

@@ -0,0 +1,30 @@
+# TC22 visual and interaction review
+
+Follow-up: all eight findings were addressed in the existing app and maintained demo. See [implementation and verification](history/MOBILE-UX-2026-11-05.md). The review below preserves the original observations.
+
+Reviewed November 5 on the actual TC22 running the existing app and maintained demo, using synthetic Test Orders. Directly inspected the first and second table pages, all six order groups, photo controls, related items, an item detail, history links and Back navigation. This is a visual/interaction review, not a new camera, printer or hardware acceptance claim. No records or photos were changed.
+
+## Assessment
+
+Readable and functional, but the current presentation is inefficient for repeated handheld work. Large text and buttons help readability; hierarchy, navigation and access to frequent actions need improvement. The data volume exposes limitations that smaller records concealed.
+
+## Prioritized changes
+
+| Priority | Observed issue | Recommendation |
+| --- | --- | --- |
+| P1 | Page two → order 26 → Android Back returns to page one. | Preserve table page, scroll position and filters per navigation entry. Verify Back after multiple record visits. |
+| P1 | Reaching photo buttons required five long swipes from the top of order 1. Items/history follow all 39 fields. | Add direct Details, Items, Photos and History navigation, with a prominent Add photo action. Make detail groups collapsible and provide a section selector. |
+| P1 | Toolbar says only “Record”; order identity disappears while scrolling. Child records use the same title. | Keep a compact record reference and record type visible. Show a parent-order link on item details; keep record labels out of telemetry. |
+| P1 | A 1,000-row list has Previous/Next/Refresh but no visible search, filters, count or page indication. | Add server-backed search, relevant filters and “26–50 of 1,000.” Consider scan-to-find where declared metadata supports it. |
+| P2 | Table entries are centered blue links with uneven wrapping; child descriptions occupy three lines. History shows only event identifiers. | Use left-aligned rows with a strong reference, concise secondary text, status and a clear navigation affordance. Show item quantity/SKU and history timestamp/status through metadata-defined summaries. |
+| P2 | Item heading repeats the full description in very large type, then repeats it as a field. Persistent branding/header and diagnostic footer consume substantial space. | Use a short reference heading and secondary description. Consolidate the header and reduce connected status to a compact indicator; retain accessible text and touch targets. |
+| P2 | Dates/timestamps and money read like raw values; timestamp example includes `T` and `Z`. | Apply metadata-aware currency, units and localized date/time formatting with timezone context. Preserve leading zeros. Show an explicit empty-value indicator. |
+| P2 | Photo controls offer capture/select but this screen provides no visible saved-photo gallery or attachment count. | Add thumbnails/count, preview, upload progress and clear pending-review/retry states. Keep the destination record visible near photo actions. |
+
+## What works
+
+Text is legible, field labels are distinguishable, sections have clear headings, and the blue photo buttons are easy to identify. Leading zeros, Unicode and multiline values displayed correctly. Parent-to-item navigation worked. Table pagination is available without scrolling the whole page.
+
+## Suggested order
+
+Fix navigation state first. Then add persistent record identity and direct photo/related-record access. Next improve list summaries/search and reduce repeated content. Finish with formatting and attachment presentation. Implement generic metadata-driven controls rather than order-specific layouts. No UI fixes were made during this review.

docs/TESTING.md

@@ -19,6 +19,15 @@ With Java 21:
 .\mvnw.cmd -f demo/pom.xml verify
 ```
 
+The optional Echo modules sit outside the root lifecycle and have their own gates (68 library and 35 composed-demo tests in the current cohort, plus 18 mobile Record Files and 16 Printing-bridge tests):
+
+```powershell
+.\mvnw.cmd -f examples/echo/pom.xml verify
+.\mvnw.cmd -f examples/echo/demo/pom.xml verify
+```
+
+They resolve the owner Generation/bridges/Record Files artifacts from a coherent local Maven repository; see the [Echo README](../examples/echo/README.md#build-and-acceptance).
+
 The HTTP suite uses an isolated H2 database and generated accounts. It sends the Android client-channel header on every request and exercises real login and process endpoints, asynchronous polling, confirmation/result steps, scan retry idempotency and authorization. Discovery must advertise the Android channel and the registered mobile-scanners extension. SQL assertions independently check persisted values and unaffected devices. Root process tests additionally cover malformed/oversized selections, first-N limits, and stable selection snapshots despite later enrollment or changed submitted values.
 
 ## Browser E2E
@@ -48,6 +57,6 @@ node scripts/ci/scanner-e2e.mjs ..\qbit-mobile-scanners
 
 The runner uses a separate `io.qrun.mobile.scanner.e2e` package, a temporary server database and generated credentials. It preserves the normal scanner app's data and refuses physical devices. The test drives the actual login, pending approval, app picker and Scan Capture screens, then independently checks the saved row and revocation denial.
 
-The semantic migration expands this to six scenarios: incompatible core version, missing extension, missing Android channel, baseline scan flow, additive future metadata, and native approval/revocation/cancellation forms. A test-only forwarding proxy matches requests to the real server's published OpenAPI operations and checks that rejected servers receive no credentials. Current verification results and remaining hardware checks are recorded in [session state](SESSION-STATE.md).
+The semantic migration expands this to six scenarios: incompatible core version, missing extension, missing Android channel, baseline scan flow, additive future metadata, and native approval/revocation/cancellation forms. A test-only forwarding proxy matches requests to the real server's published OpenAPI operations and checks that rejected servers receive no credentials. Current verification results and remaining hardware checks are recorded in [session state](SESSION-STATE.md). Isolated test accounts, databases and application IDs are required; never reset the demo or scanner data to run tests.
 
 Hardware trigger, decoding and DataWedge delivery still require [TC22 acceptance](TC22-ACCEPTANCE.md). Emulator success does not establish physical scanner acceptance.

docs/TODO.md

@@ -1,114 +1,38 @@
-# QQQ Mobile Scanners TODO
+# TODO
 
-Current checkpoint (November 3; supersedes the notes below where they differ):
+Open work only, as of **2026-11-05**. Present status is in [session state](SESSION-STATE.md); release gates are in [production readiness](PRODUCTION-READINESS.md). The earlier ledger, including every completed item, is archived in [history](history/TODO-through-2026-11-04.md).
 
-- [x] Server `45f9cbd` is signed and pushed (Gitea PR 7). Android `f72b90d` is signed and pushed to the existing AGit PR 10 head and Gitea CI 3480 succeeded on it (pull requests #8 and #10 still open; not merged, not released). Updated normal APK installed without clearing data; fresh disposable TC22 Echo run passed 109/109 semantic requests (simulated inputs/printing).
-- [x] Final RC.21 gate PASS: 377 unique tests (Generation 179, Printing bridge 16, scanner 53, demo 8, mobile Record Files 18, Echo 68, Echo demo 35), zero failures/errors/skips, Checkstyle PASS, plus 15 real admin-browser E2E on public RC.21. The earlier MySQL timeouts did not recur (focused 31, full 179). Evidence: `C:/Users/james/.cache/qqq-rc21-copies-gate-076d059d8d0641d9a85874ec64008def/verified-summary.json`.
-- [x] Verified dependency update: five RC.21 POM pins and the record-files POM test fix (BOM-managed Jupiter engine/params, all 6.0.2).
-- [ ] This is public core RC.21 plus qualified owner inputs, not a fully public or released cohort: the 16 Printing-bridge tests still resolve three private `pu507` QQQ libraries through the owner Printing POM, and the other owner qbits remain qualified private inputs. Public reproducible owner inputs, primary source CI, merge and release remain open. No normal-runtime core upgrade was done.
-- [x] Generation copies: signed `aac68907e67906aeef4e0cd687d28bc98b738f8c` on `feature/echo-generation-copies` (base PR 343 head `8f473fa`) in `Website-Backend/third-party-src/qbit-document-generation`; 13 paths, 21/21 manifest match; real PostgreSQL 17 migration passes. [ ] Owner integration and public artifact publication not yet acknowledged.
-- [x] Fresh real Authentik desktop acceptance passes; native harness integrated (8 guards pass). [ ] Native TC22 run needs the temporary CA and PIN (pending); no trust bypass.
-- [ ] Manual physical checks: trigger, AIM, fidelity, label count, photo, GPS, projection. [ ] Signing and distribution last, by user decision.
+## Needs an owner outside this repository
 
-Previous checkpoint (November 2; historical, superseded by the current checkpoint above):
+- [ ] **Public document/files/scripting artifacts.** The document owner publishes a coherent set (Generation, its Printing and Record Files bridges including copies support, Record Files, Scripting) as public Maven artifacts. Until then the Echo modules and the optional Record Files integration build against qualified owner inputs and only `qqq.version` and `printing.version` resolve publicly. The owner's packaging is in progress; no completed version is known, so do not invent coordinates or change POMs ahead of it.
+- [ ] **Core, Collaboration and Next UI foundations.** Adopt the public versions when the owner releases them, as a normal reviewed dependency change with a fresh full gate.
 
-- [x] Optional Copies per scan defaults to 1, accepts 1–100 and remains server-pinned for every scan/retry. Live on the original local server57832; normal TC22 setup shows 1.
-- [x] Verify 377 unique server/owner tests across the module runs, plus real TC22 ten-stage/116-request semantic acceptance with simulated scans/printing.
-- [x] Adopt mobile-scanners1.5 and actual mobile-record-files1.0/Echo photo composition locally, preserving the original database and printer settings. Photo authorization tests pass.
-- [ ] Confirm physical label count/fidelity and real camera/GPS/projection/provider behavior; operator currently remote. Temporary Authentik CA installation is unconfirmed.
-- [ ] Obtain canonical owner adoption/publication of the verified Generation copies handoff: ten hash-checked files for the Kof22 release repository's `third-party-src/qbit-document-generation` (base verified identical), then a published Generation coherent with Echo's `generation.version`; complete coherent artifacts/CI. Signing/distribution stays last.
+Note: redesign of the shared CI pipeline is outside this scanner/local Echo scope and is not tracked here; the local demo does not depend on it.
 
-Current demo path (November2; supersedes historical runtime/pairing notes below):
+- [ ] **Record Files `quarantineCapturedFiles`.** The Echo host (`EchoDemo`) and the optional integration test already call/require `RecordFilesQBitConfig.withQuarantineCapturedFiles(Boolean)` (nullable, null inherits `quarantineNewFiles`; applies only to CAPTURE intake with a provider-verified device identity). The owner's scoped change (policy commit `3f08c584`, PR 1) is open and unmerged, and its CI currently fails a not-enrolled check owned by the coordinator; do not change CI or weaken merge gates. Adopt the released version as a reviewed pin once public; no coordinate is known, so none was guessed and this source builds only against the local owner input until then.
 
-- [x] Implement and verify additive mobile1.5 raw-byte/AIM transport, exact retry binding, optional context and preserving H2 migration:135 scanner/demo/Echo tests pass. Android counterpart is implemented; native capture and installed-runtime adoption remain open.
-- [ ] Qualify actual TC22 raw-byte delivery, AIM extraction and decoder settings; finish renderer scanner-mode/extended-symbology integration. Transport support alone does not establish same-symbol reproduction.
-- [x] Fix and adopt the Generation/renderer byte-limit mismatch in both demo launchers; three failures with old wiring, 74 passing library/demo tests with the fix. One clearly synthetic native HTTP event now reaches the actual Windows printer spooler through Echo, with process cancellation verified after failure and acceptance. Paper output, TC22 trigger capture and rescan remain separate open checks.
-- [x] Render the actual published 4x1 document through the real renderer and independently decode its Code128 and leading-zero QR pixels; both preserve exact value/symbology and fit the configured stock. See [evidence and test images](../examples/echo/demo/docs/ECHO-RENDERER-ACCEPTANCE.md). Physical printing remains unverified.
-- [x] Correct the five inert test-token secret-scan findings using generated fixtures and exact historical fingerprints; local historical/staged scans and all 27 demo tests pass. Current primary CI remains an open gate.
-- [x] Run all real scanner/Echo, files, document and printing qbits in the single local server57832; original accounts work; full demo27 and live forwarded-host checks pass.
-- [x] Connect the existing installed print client to57832 and approve its available ZPL printer through the native QQQ process; no job/default changes.
-- [x] Verify the Android same-origin header (Android `fb3cc5d`, 174 JVM tests) and TC22 sign-in, heartbeat, printer/media/document selection and Cancel/Leave against the strict local host, preserving data.
-- [x] Resolve the earlier 4x6 media report versus loaded 4x1 stock with the Printing owner (101600 x 25400 microns, 300 dpi) and publish the real Echo 4x1 barcode document with its matching immutable revision 1.
-- [ ] Complete one physical Code128 (QQQ-TEST-123456) scan, print and rescan on the TC22, then leading-zero QR. One synthetic HTTP test job reached `SPOOLED`; physical paper output and handheld acceptance are not yet proven.
-- [ ] Finish the existing production-readiness matrix and publication gates; local demo acceptance alone does not complete 1.0. Public coherent artifacts, primary Gitea CI and final signing remain open, with signing last by user decision.
+## This repository
 
-- [x] Implement explicit required INTEGER Document choice with printer/media dependency, server-pinned revision and recoverable errors:45 library/24 composed tests and real TC22 seven-stage/112-request semantic acceptance pass (simulated printing).
-- [x] Roll out the document-selection feature and connect the installed print client to the canonical local server. Real4x1 publication and physical scan/print/rescan remain tracked above.
+- [ ] Qualify GS1 template/media setup and **physical print/rescan** of the requested label profile. Software duplication, native acceptance and maintained-demo adoption are complete.
+Retention stays indefinite by default and any change is a host-owned policy ([operations](OPERATIONS.md#retention)). Enterprise object-store and high-availability recovery, and database backends other than H2, are unsupported/unqualified deployment options, not tasks of this release. The 2026-11-05 gate (196 tests, zero failures/errors/skips, zero Checkstyle violations) used qualified private owner dependencies; the required public-cohort rerun remains listed below.
+- [ ] Optionally correct the generic 409 text in `MobileJsonSpec` (screen upload is a stale-frame conflict) with a patch version bump and regenerated contract; deferred.
+- [ ] Complete the authorized readiness work in [the active plan](GS1-RECORD-PHOTOS-PLAN.md), retaining explicit external/hardware gates.
 
-- [x] Verify the per-extension device-header scope fix (50 base,7 base-demo and composed HTTP regressions), then complete actual native printer enrollment/binding on the local server.
+- [ ] Re-run the full gate (root, demo, Echo, Echo demo, Record Files, browser E2E) on whatever dependency set is adopted next, and record the actual counts.
+- [ ] Qualify the bounded GS1-128 profile and keep explicit refusals for other GS1, ECI, structured and binary scanner profiles in Echo ([limits](../examples/echo/README.md#fidelity-and-limits)).
 
-- [x] Publish reviewed Echo retry/receipt fixes as signed Gitea commit912040d;38 library/22 demo tests pass. (Historical: the then-pending Windows approval of printer pairing is superseded; the print client is now connected to the single local server.) Physical output and public CI/artifacts are still open.
+## Hardware and device follow-up
 
-- [x] Verify real composed Echo native HTTP pipeline:38example/22demo, retained files, accepted jobs, retry identity and Leave closure; simulated printer/controlled renderer only.
-- [x] Complete native printer connection on the current loaded stock (done on the single local server). Physical scan/print/rescan is tracked above; published dependencies and primary CI remain open.
+- [ ] Native Authentik login, logout and account switching on a handheld (not yet tested; needs the MC9400 wireless-debugging endpoint). The shared Authenticator server configuration is verified; the Printing client nonce fix (PR 11) awaits hosted Core. The MC9400 physical trigger check is done ([session state](SESSION-STATE.md#handhelds-and-remaining-limits)).
+- [ ] Optional: click the full preview of the newly uploaded gallery photo on a handheld (not observed because ADB disconnected). No camera-hardware proof is claimed.
+- [ ] Optional: capture per-case evidence (photos, logs, a scanned-back label) on a future run. The November 4 operator pass is accepted as is and is not to be requested again.
 
-- [x] Verify effective security-key set comparison and early Collaboration authentication initialization: scanner50/native Record Files18, Checkstyle0 on private coherent cohort.
-- [x] Compose the live Echo renderer, Printing and document publication in the single local server. Physical TC22 print/rescan is tracked above; startup smoke and simulated printing do not close that gate.
+## Release (deliberately last)
 
-- [ ] Deliver Echo example: choose an authorized printer, media and Document (all three required) once, then one scan/render/accepted-print job at a time until leave; reproduce exact value and symbology with worker-owned integer-module fitting and quiet zones. Source, composition, Document choice and native setup are done. Still open: the physical print and rescan above, and full-fidelity work beyond the six admitted printable-ASCII types (EAN/UPC, GS1, AIM identifier and raw payloads), tracked in `examples/echo/README.md`.
-- [ ] Coordinate qualified renderer fit, authorized printer/media discovery, least-privilege submit and retained-print adapter contracts with their owners via shared communications.
-- [x] Verify scanContext 1.3 with root44/demo7/optional18 and Checkstyle: following-step QR/Code 128 branching, legacy omission isolation, trusted attribution and exact retry binding; physical scanner acceptance remains separate.
+- [ ] Final distribution of the signed 1.0.1 build and the public dependencies it waits on. Signing is done: the build was installed in place on an MC9400 through ADB, preserved enrollment, and reopened Scan Capture against the HTTPS server. Remaining device checks are listed above; no automatic APK-signing CI is qualified. Also open: signing-APK download publication, owned cleanup, and a rerun of the public cohort with the final public Core/Collaboration/document/files/scripting/bridge artifacts.
+- [ ] Company profile/wallpaper is a separate tracked scope and not a blocker for this bounded release goal.
+- [ ] HTTPS deployment by the host (any non-H2 migration is host-owned and unsupported here) and the remaining gates in [production readiness](PRODUCTION-READINESS.md).
 
-- [x] Apply the full scoped standards review corrections and verify server39/demo6 with Checkstyle; see [review](CODING-STANDARDS-REVIEW-2026-11-01.md).
-- [ ] Finish final hosted checks and remaining physical/provider acceptance; source compliance is not production release approval.
+## Not in version one
 
-- [x] Upgrade the normal local demo to qualified API1.9/mobile1.1 with fresh closed backup, original-data invariants, recovery qualification and live verification of both existing accounts and preserved devices/scans.
-- [x] Implement/review additive extension1.2 whole-device source with explicit Android consent, mode-bound leases and automated controls, preserving1.1 app-content compatibility.
-- [ ] Complete actual Android projection/notification/Home/Stop/lock/rotation/expiry/remote-logout acceptance; normal server remains mobile1.1.
-
-- [x] Qualify the demo BOM import and managed JUnit engine with fresh37 server/five demo tests, exact runtime module/Guava/H2 provenance and all15 single-record/bulk browser cases; see [acceptance evidence](API19-CONSUMER-ACCEPTANCE.md). The operator runtime remains separate.
-- [x] Preserve legacy timestamp instants in the canonical supplied H2 schema with an explicit UTC migration connection; verify non-UTC file-backed upgrade, unchanged passwords/approval/scans and repeated initialization. The operator upgrade is preserved with UTC; a no-install reactor passes 37 base tests and five demo tests using the freshly built schema.
-- [x] Implement unique short names, editable names/descriptions, additive H2 migration and protected profile editing; qualify the preserving upgrade of the operator database before deployment.
-- [x] Implement separate approval/presence states, online-only fleet query and foreground location with accuracy/age and permission-denied behavior; actual GPS-fix acceptance remains in the release gates.
-- [x] Implement the optional Record Files contract/native capture/association path and qualify the final coherent core32/scanner1a3 consumer cohort: 39 scanner, six demo HTTP, 18 Record Files and 15 browser cases. See [qualification scope](../integrations/record-files/docs/CORE-32DF-CONSUMER-QUALIFICATION.md); this is not a files-owner full-suite or default-adoption claim.
-- [ ] Qualify coherent immutable/default RF dependencies and actual TC22 camera/gallery permissions and durable authorized association; no normal-runtime adoption is implied.
-
-- [x] Device/session history, live activity and demand-based actual app-screen viewing through native QQQ administration and semantic extension 1.1.
-- [x] Single-record and bulk End Session process with server-enforced invalidation, audit and browser/native E2E coverage.
-- [x] Complete and seal the full server deep static security review of `0926550`; no reportable findings, with external implementation/deployment limitations retained.
-- [ ] Complete final revision/scope reconciliation of historical security reports and remaining external deployment/provider gates. Independent architecture A1–A11 source closure and the filesystem regression correction are recorded; do not relabel partial/historical reports as a new exhaustive scan.
-- [ ] Complete production 1.0 gates in [PRODUCTION-READINESS.md](PRODUCTION-READINESS.md), including physical acceptance and deployment/release requirements.
-
-- [x] Native qbit device/scan tables and permission boundaries.
-- [x] Authenticated enrollment, approval and revocation.
-- [x] Native Scan Capture process and idempotent scan storage.
-- [x] Android login, device gate, app picker and current trusted EMDK scanner path; prior DataWedge handling is historical.
-- [x] Persistent local demo with separate scanner/admin accounts.
-- [x] Automated HTTP acceptance: pending denial, approval, capture, duplicate retry, revoke denial.
-- [x] Android build and meaningful unit checks.
-- [x] Standard repository files, current shared CircleCI profile, demo/Windows CI, CodeQL and Dependabot.
-- [x] Validate CircleCI, workflow syntax and verification-only publication policy locally.
-- [x] Connect hosted CI and confirm actual successful status checks.
-- [x] Define branch protection policy from observed hosted checks; enforcement lives in GitHub settings.
-- [x] Server-configured customer branding for one shared APK.
-- [x] Public status endpoint for the Android connection footer and diagnostics.
-- [x] Android emulator installed; native UI tests passed.
-- [x] Single-record and bulk approval/revocation with confirmation, stable selection and visible results.
-- [x] HTTP acceptance for checked rows, filtered bulk selection, persisted results and unselected-device isolation.
-- [x] Browser E2E acceptance for all administration processes from record and bulk menus (six scenarios passed).
-- [x] Scanner-host native E2E acceptance against an isolated real demo server.
-- [x] Register enrollment, branding and status as the documented mobile-scanners 1.0.0 semantic UI API extension; generate OpenAPI and check the versioned contract baseline.
-- [x] Verify extension discovery, real HTTP payload schemas, standard errors, public stale-credential behavior and rejection of legacy routes (root 23 tests and demo HTTP verification passed).
-- [x] Coordinate Android core/extension compatibility checks before login and native semantic process/form updates.
-- [x] Register the Android client channel while preserving host channel policies; verify the real HTTP suite sends Android-channel requests successfully.
-- [x] Rerun all six browser E2E scenarios against the migrated server (passed in 2.9 minutes).
-- [x] Verify the migrated client/server pair's incompatible-version, missing-extension, missing-channel, baseline scan and additive-metadata native scenarios with the OpenAPI request audit.
-- [x] Verify Android's 53 JVM tests, six shared native UI tests, lint and debug/E2E APK builds.
-- [x] Complete native approval/revocation/cancellation forms after the completion-state fix (255.917 seconds; all 31 requests matched to 13 published operations).
-- [x] Publish server semantic API migration commit `7dd02b8` and verify its hosted CircleCI, CodeQL, Windows helper and demo HTTP/browser checks all pass.
-- [ ] Finish current EMDK physical acceptance: Code128 positive controls pass; current QR, lifecycle/ownership and failure/retry/leave matrix remain open.
-- [x] Identify the physical TC22, install the debug app, sign in and enroll through USB forwarding.
-- [x] Approve the TC22 through its browser record Actions menu and open its native app catalog and Scan Capture process; preserve login across APK update.
-- [x] Configure the TC22 DataWedge profile with explicit package/signature delivery; verify two deliberate Code128 hardware captures persist with matching metadata.
-- [x] Verify physical QR delivery and exact preservation of leading zeroes in `001234567890`, with matching persisted scan metadata.
-- [ ] Finish physical connection-loss/retry and revocation-denial acceptance alongside the requested device/session controls.
-- [x] TC22 install and DataWedge acceptance guide written and updated with observed results.
-
-Future scope (not version one): offline queue, camera-based barcode decoding, kiosk/MDM provisioning, broader native screen coverage, fleet rollout. Optional record-photo capture is implemented; its remaining qualification is tracked above.
-
-- [ ] Complete the optional semantic API1.10 provider-logout capability and client AppAuth end-session handling; keep local cleanup reliable on provider failure, qualify real A-to-B handoff, and apply the user's pending sign-out policy. Existing prompt-only retained-SSO handoff is not accepted.
-
-- [ ] Validate native OIDC ID-token claims and original request nonce before creating the QQQ session. Review confirmed request continuity and S256 PKCE exist, but expected nonce is not currently carried to the server exchange. Add explicit semantic capability/wire compatibility and rejection tests; retain real-provider nonce acceptance as pending.
-
-- [x] Retain unchanged verified capture session identity with explicit current authority/reference checks;49root+7demo tests andCheckstylepass.
-- [ ] Qualify exact ownerRF18 upload/finalize using the frozen identity patch before final coherent host adoption.
+Offline queue, camera-based barcode decoding, kiosk/MDM provisioning beyond the implemented managed configuration, broader native screen coverage and fleet rollout.

docs/UI-API.md

@@ -1,6 +1,6 @@
 # Mobile Scanners semantic UI API
 
-Mobile Scanners is an independently versioned QQQ UI API extension. `MobileScannersQBitProducer` registers the `mobile-scanners` contract, currently **1.4.0**, through `MiddlewareSpecExtensionsMetaData`. The framework generates its routes, discovery advertisement and merged OpenAPI from the same endpoint specs. Optional operator-consented device-screen viewing is described in [DEVICE-SCREEN-VIEWING.md](DEVICE-SCREEN-VIEWING.md); app-content remains the default. There is no separate `/mobile/v1` API or legacy alias.
+Mobile Scanners is an independently versioned QQQ UI API extension. `MobileScannersQBitProducer` registers the `mobile-scanners` contract, currently **1.6.0** (core UI API 1.10 on the maintained local server), through `MiddlewareSpecExtensionsMetaData`. The framework generates its routes, discovery advertisement and merged OpenAPI from the same endpoint specs. Optional operator-consented device-screen viewing is described in [DEVICE-SCREEN-VIEWING.md](DEVICE-SCREEN-VIEWING.md); app-content remains the default. There is no separate `/mobile/v1` API or legacy alias.
 
 The host must also install `MobileScannersRouteProvider` on the same server. This provider binds verified device headers to the current request; it does not register additional business routes. Keep the versioned QQQ routes enabled. The qbit registers the `android` client channel while preserving the host's existing channel policies. The demo disables legacy unversioned middleware routes.
 
@@ -26,11 +26,18 @@ Every path below is relative to `/qqq/v1/qbit/mobile-scanners`.
 | `GET /status` | `mobileScannersStatus` | Public | 200, `MobileScannersStatusV1` |
 | `POST /devices/enroll` | `mobileScannersEnrollDevice` | QQQ user session, `mobile.scan` | 201, `MobileScannersEnrollmentV1` |
 | `GET /devices/current` | `mobileScannersCurrentDevice` | QQQ user session, `mobile.scan`, both device headers | 200, `MobileScannersDeviceV1` |
+| `POST /sessions/heartbeat` | `mobileScannersSessionHeartbeat` | QQQ user session (cookie, bearer or OAuth2), both device headers | 200, `MobileScannersHeartbeatV1` |
+| `POST /sessions/current/end` | `mobileScannersEndCurrentSession` | QQQ user session (cookie, bearer or OAuth2), both device headers | 200, `MobileScannersSessionEndedV1` |
+| `POST /sessions/current/screen` | `mobileScannersUploadSessionScreen` | QQQ user session (cookie, bearer or OAuth2), both device headers | 204, no body; its 409 means a stale frame or sequence, not an enrollment conflict |
+
+All seven operations also declare 400, 401, 403, 404, 429 and 500 error responses (`BasicErrorResponseV1`). The published YAML labels every operation's 409 "Installation already enrolled"; that text is accurate only for enrollment. Session behavior is in [device sessions](DEVICE-SESSIONS.md) and [screen viewing](DEVICE-SCREEN-VIEWING.md).
 
 Public discovery, OpenAPI, branding and connectivity ignore stale device headers. Authentication discovery/session/logout also remain available when a previously enrolled credential is no longer valid. Responses from extension handlers use `Cache-Control: no-store`.
 
 Enrollment takes `MobileScannersEnrollRequestV1`: required canonical UUID `installationId`, optional `displayName`, `manufacturer`, `model`, `osVersion` and `appVersion` strings, each at most 200 characters. The JSON request body is limited to 4096 characters. A duplicate installation returns HTTP 409 and never rotates or discloses its existing credential. A new installation starts `PENDING` and receives its private `deviceToken` once.
 
+Since extension 1.6, `MobileScannersHeartbeatRequestV1` also accepts the same optional `manufacturer`, `model`, `osVersion` and `appVersion` strings (at most 200 characters, 400 otherwise). An approved device's record is updated only when a sent value differs; omitted, null or blank values leave the enrolled values unchanged. Scan events copy the device record at save time, so an in-place app or OS update is reflected on the next heartbeat and every later scan, while earlier scans keep the versions that produced them. The Android host sends `osVersion` and `appVersion` on every heartbeat.
+
 Send `X-QQQ-Device-Id` and `X-QQQ-Device-Token` on authenticated device/core metadata, widget and process requests to this same origin. The device ID is a UUID; the token is private and at most 128 characters. These headers supplement the authenticated user session. They never replace user permission checks. Never put a token in metadata, URLs, process values, screenshots, logs or fixtures; never forward credentials to a branding asset origin. Store the issued credential privately. Only its digest is stored server-side.
 
 `devices/current` returns `deviceId`, `displayName` and `status`, never a token. `PENDING` and `REVOKED` devices may read their status. Scanner access still requires `APPROVED`, checked when launching and saving, including asynchronous/resumed execution. Device approval/revocation uses the ordinary QQQ processes, including single-record and bulk selections.
@@ -76,7 +83,7 @@ Schema migration (H2, idempotent, nullable): `ALTER TABLE mobileScan ADD COLUMN
 
 ## Contract checks and compatibility
 
-The published fragment is [mobile-scanners.yaml](../src/main/resources/openapi/qqq-v1/mobile-scanners.yaml); the initial release baseline is [mobile-scanners-1.0.0.yaml](../src/test/resources/openapi/mobile-scanners-1.0.0.yaml), with additional frozen baselines such as [mobile-scanners-1.4.0.yaml](../src/test/resources/openapi/mobile-scanners-1.4.0.yaml) (the contract immediately before the 1.5.0 capture metadata). `MobileScannersApiContractTest` rejects generated-document drift, unresolved contract structure, incompatible baseline changes and missing version bumps using QQQ's shared contract checker. Object required fields and scanner numeric bounds are standard OpenAPI keywords, added by small Schema subclasses because RC20's base model does not expose those setters.
+The published fragment is [mobile-scanners.yaml](../base/src/main/resources/openapi/qqq-v1/mobile-scanners.yaml); the initial release baseline is [mobile-scanners-1.0.0.yaml](../base/src/test/resources/openapi/mobile-scanners-1.0.0.yaml), with additional frozen baselines such as [mobile-scanners-1.4.0.yaml](../base/src/test/resources/openapi/mobile-scanners-1.4.0.yaml) (the contract immediately before the 1.5.0 capture metadata) and [mobile-scanners-1.5.0.yaml](../base/src/test/resources/openapi/mobile-scanners-1.5.0.yaml), the frozen 1.5.0 release snapshot that later changes are checked against. `MobileScannersApiContractTest` rejects generated-document drift, unresolved contract structure, incompatible baseline changes and missing version bumps using QQQ's shared contract checker. Object required fields and scanner numeric bounds are standard OpenAPI keywords, added by small Schema subclasses because RC20's base model does not expose those setters.
 
 For an intentional contract edit, update specs/schemas and the extension semantic version, then regenerate only the current fragment:
 

docs/history/ECHO-SESSION-STATE-through-2026-11-04.md

@@ -0,0 +1,25 @@
+> Historical record, superseded by [current status](../SESSION-STATE.md). Do not treat as current.
+
+# Echo session state
+
+November 1, 2026: optional example source is being implemented under this directory only. Echo registers ordinary setup and scanner-loop process metadata, uses current approved-device attribution and canonical persisted scan context, and delegates generation/retention/printing to existing QBits. Its state store admits one event, preserves uncertain identities and refuses silent reprint. Core protected process identity, exact media/template revision and owner read-only acceptance seams are under coordinated implementation; no physical printer or peer service has been touched.
+
+Initial private offline build stopped on an unavailable aggregate JUnit artifact; dependency declarations now use the already available split API/engine. Current compilation and focused H2/process tests remain pending. There is no runnable fully wired demo or production-release claim. See [TODO](../../examples/echo/docs/TODO.md) for remaining acceptance.
+
+Verification now passes14 real QQQ USER process/mobile-approval/H2 tests, zero failures/errors/skips, and zero Checkstyle violations, against the qualified protected-process SDK4.1.0-pu.507b0d21e09d7eebb76782d14660483c45c77b11 and scanner facade JAR9A5728B7…. Tests cover setup once, two-type exact-value loop, canonical receipt, changed-type retry refusal, uncertain/crashed read-only receipt adoption without re-enqueue, deterministic in-flight concurrency, post-setup cancellation, same-user run substitution, media drift/too-small plan and enforced native source reads including forged reserved keys. Destination/layout/generation fixtures are synthetic; no real renderer, owner adapter, Android or physical-print acceptance is implied. Private evidence is under Ccache/qqq-echo-final-verify-e3929445f6a144e889ba12d90e4c7efb. The unqualified generation API dependency is compile-only provenance, not release adoption.
+
+Final packaging follow-up: module-directory wrapper verification passes15 tests (including canonical cross-run replay refusal), zero failures/errors/skips, zero Checkstyle violations and deprecation/unchecked warnings-as-errors. Apache license metadata is present in the POM; the JAR contains byte-identical existing repository LICENSE/NOTICE under META-INF/qqq-echo and unchanged db/echo-h2.sql. No duplicate license source files were introduced. Real adapters, hosted integration and physical printing remain pending.
+
+## Semantic scanner presentation companion
+
+Echo now supplies acknowledgmentLabel=Print queued and manualEntryEnabled=false through the registered scanner extension 1.4. The companion Android implementation passes 167 JVM cases, strict compilation and lint with zero errors/warnings. The server passes 69 consumer cases plus two contract-generation cases. Echo's 15 strict process/state tests also pass against the qualified 1.4 scanner artifact. This remains synthetic owner-port qualification; actual pinned rendering, media/profile propagation, native Echo UI and physical output still require owner handoffs and acceptance.
+
+2026-11-01: Added test-scope EchoHttpFixture + actual semantic HTTP smoke, reusing the qualified demo artifact, TABLE auth and mobile routes. No production row lock or service changed. UI fixture has random in-memory state and unmistakable simulated printing branding. Real HTTP retry exposed database precision changes in server receivedAt; removed that observation timestamp from print intent comparison while preserving the first persisted observation. Canonical scan identity, payload/type/source/capture/run bindings remain enforced. Final fixture verification pending; old qualified Echo15 proof is retained.
+
+Fixture verification: private qqq-echo-http-fixture-e66c4b1bc35a434a8e668fa7cff49dd8, strict16/0/0/0 +Checkstyle0 PASS. Snapshot includes compiled test/main classes, fixture-java.args and source provenance. HTTP test stops its listener cleanly; no device or physical print run. Native execution is the next independent gate.
+
+2026-11-01 13:15 local: Split only EchoScan reads from approved-device capture. EchoSourceReadPermissions admits current nonblank actor + echo.use for native Get/Query/Count/Aggregate and metadata discovery; native actor RecordSecurityLock remains unchanged and direct writes remain denied. Echo app/widget/process/capture and test-only run inspection retain the approved-device checker. Original-actor desktop read after run close succeeds without mobile.scan/device scope; revoked Echo grant, anonymous actor, different actor with spoofed reserved security key, direct update/delete and desktop capture/process attempts fail. EchoTest17/0fail/0error/0skip, Checkstyle0 and strict Java21 package PASS against core pu.507b0d21 + mobile1.4 FDDB118A; evidence source-read-split.log in the private Echo HTTP fixture cache. Frozen native fixture classes/args were not replaced.
+
+Critical path: qualify this split's HTTP companion, finish frozen native TC22 UI gate, then compose a production adapter only after reviewed owner media-capability/adoption + exact-pinned template/stock/media + read-only acceptance lookup handoffs. Printing must qualify current original-actor/source reauthorization before pending delivery/retry bytes release. Actual rendering/physical label fidelity and rescan are still unqualified; simulated fixture receipts do not satisfy them.
+
+Companion semantic HTTP smoke1/0/0/0 +Checkstyle0 PASS after the split (source-read-http.log). Combined bounded cohort18 tests passes; original frozen UI fixture bundle is unchanged.

docs/history/ECHO-TODO-through-2026-11-04.md

@@ -0,0 +1,46 @@
+> Historical record, superseded by [current status](../SESSION-STATE.md). Do not treat as current.
+
+# Echo remaining work
+
+## Current checkpoint — November 2, copies live
+
+- [x] Printer, paper/label size and Document selection, real installed Printing client connection and 4x1 document publication are complete on the normal local server57832.
+- [x] Copies per scan is optional, defaults to 1 and accepts 1–100; pinned for the run and carried as one job's copy quantity. Null/blank/default, selected 3, mutation refusal, retry identity and additive migration tests pass.
+- [x] Root gates pass: 68 Echo and 35 composed demo tests; 377 unique tests including the Generation/Printing/scanner/files dependencies across verified module runs.
+- [x] Real TC22 semantic acceptance passes ten stages/116 requests using simulated scans and printing. The normal connected TC22 is left on setup showing Copies per scan = 1; normal server advertises mobile1.5.
+- [ ] Physical quantity, trigger/print/rescan and AIM/EAN/UPC fidelity checks remain unqualified. The operator is remote.
+- [ ] Canonical Generation copies adoption/publication and coherent public CI remain pending; qualified local source/handoff lives in C:/Users/james/.cache/qqq-generation-copies-20261102 and qqq-generation-copies-handoff.md.
+
+The older ledger below is historical; its unrun-test, setup and mobile1.4 notes are superseded by this checkpoint.
+
+- [ ] Root gate for the required Document choice (printer, paper or label size, then Document at run start; see DOCUMENT-CHOICE-HANDOFF.md): module and demo verify, then on-device check that the generic form shows the dependent Document field.
+
+Verified by root (2026-11-02): module `verify` 33 tests, Checkstyle 0, against the complete private cohort `0.1.0-echo.gen64c9pu507`. Runnable demo `verify` 22 tests, Checkstyle 0, including the composed acceptance below, with the real new Echo read checker and the renderer owner's TL1 factory (52 owner tests pass, no copied transport). A local demo run was observed live on an ephemeral loopback port (scanner and admin native login and metadata 200). No printer or template on it, and no physical printing.
+
+## Done
+
+- [x] Process, state, mobile-approval and H2 tests against the protected-process-identity core API; concurrency, crash recovery, cancellation and run-substitution regressions.
+- [x] Test-only isolated semantic HTTP fixture (simulated printing) and split read-only `echoScan` permission with actor-lock, revoked, anonymous and write negatives; the read rule also accepts Collaboration's and Record Files' plain capability probe for sessions with `echo.use`.
+- [x] Owner adapters from actual public APIs: authorized printer/media from Printing, exact pinned template/revision/stock/media generation, read-only accepted-print lookup, `QUEUED` only for a durable available receipt.
+- [x] Media choices filtered by the selected printer through the semantic dependency value.
+- [x] Host composition `EchoHost.install` using `PrintingDispatch.forOwnerMediaEnforcement(source)`.
+- [x] Publisher scene reviewed against the worker source and owner fixture shape; EAN13/EAN8/UPCA/UPCE0 refused before admission; six types admitted.
+- [x] Runnable demo module and the owner's trusted-local renderer factory integration.
+- [x] **Clean composed acceptance** (demo `EchoDemoAcceptanceTest`): authenticated approved scanner, real `echoPrint`, real Generation, Record Files retention and Printing job acceptance; two scans give two retained originals and two accepted jobs on one printer, a retry gives the same job, and leaving closes the run. Controlled synthetic renderer and simulated Printing queue; not physical.
+
+## Open
+
+- [ ] Actual native Printing client (Windows agent) connection to the composed server and the current stock/media handoff.
+- [ ] Publish the ZPL template through the real renderer, then preview and independently decode Code 128 and a leading-zero QR (`001234567890`) at 4 x 6 in / 300 dpi.
+- [ ] Real-server native TC22 run: setup once, scan twice, rotate/recreate, leave; one stable print identity after transport loss.
+- [ ] Physical print and TC22 rescan with exact value, symbology, quiet zones and stock dimensions; native Printing acceptance. A queue acknowledgment is not paper.
+- [x] Source: AIM persistence (`echo_scan.aimIdentifier`), EAN13/EAN8/UPCA/UPCE0 validation, and a scanner-fidelity document through the renderer's scanner mode; candidate Android AIM output profile (`AimOutputProfile`, driver config/readback/restore). Not yet run (root builds) and not physically qualified.
+- [x] Source: Copies per scan (setup field, server-pinned `echo_run.copies`, scan-stage forgery refusal, widget text). Library tests added, not run.
+- [x] Source: copies reach Generation's request and the accepted-lookup binding (needs the Generation copies cohort from `C:/Users/james/.cache/qqq-generation-copies-handoff.md`, unbuilt). Optional field with 1..100 core limits and real HTTP tests for default 1, chosen 3 and mutation rejection; not run.
+- [ ] Root gate with the Generation copies cohort, the `20261102-print-copies-h2.sql` migration in the demo's `GENERATION_MIGRATIONS`, a Printing owner that honors `options.copies`, and a physical count check on the printer.
+- [ ] TC22 pulls proving what `getData()` and `getRawData()` contain under `codeIdType=AIM`, then a physical EAN/UPC scan, print and rescan on the scanner-fidelity document. Normal server 1.5 adoption (the live server is 1.4 and drops AIM and raw bytes).
+- [ ] GS1, ECI, structured, binary and non-ASCII payloads stay refused: the existing public renderer has no scanner-mode profile for them (see `C:/Users/james/.cache/qqq-finish-barcode-handoff.md`).
+- [ ] Original-actor source reauthorization policy confirmed for delayed byte release (Printing retained source authority).
+- [ ] Deployment: Windows agent exposing `printer-media-v1`, ZPL printer, tenant, operator permissions without `printing_admin` (the scanner never receives it).
+- [ ] Public immutable SDK publication, Gitea CI and distribution, then signing, last. The private cohort is unpublished; PR 7 is on Gitea and earlier GitHub references are historical.
+- [ ] Release and production readiness: not done and not claimed.

docs/history/MOBILE-UX-2026-11-05.md

@@ -0,0 +1,28 @@
+# Mobile record UX completion — November 5
+
+The [TC22 review](../TC22-UIUX-REVIEW-2026-11-05.md) identified eight usability issues. All are addressed in the companion Android application and this demo's ordinary metadata:
+
+- Table page/scroll/search/filter state survives record navigation and recreation; search, exact text filters and counts use the semantic query/count APIs.
+- Record identity stays visible above Details, related-record and Photos tabs. Groups collapse; a section selector and child-to-parent navigation shorten large records.
+- Left-aligned summaries, short item labels, localized dates/timezones, currency/units and explicit empty values improve readability. Diagnostic detail is behind Connected.
+- **Actions → Add photo** opens the existing camera/gallery upload flow. Saved photos are scoped to the parent, show lifecycle status and use the owner's authorized tracked download for available-image previews. Quarantined originals remain unavailable.
+
+Record Files deliberately refuses aggregate counts: the gallery uses bounded pages with one lookahead row, without weakening permissions. Images have bounded byte/bitmap memory, exact length/hash checks, same-origin authenticated delivery and no image disk cache. Navigation guards remain active during pending uploads, including rotation; logout removes owned temporary staging.
+
+## Verification and adoption
+
+The composed feature cohort passed 189 tests (scanner 53, base demo 8, mobile Record Files 18, Echo 74, Echo demo 36) with Checkstyle. Android passed 232 unit tests and lint (0 errors/0 warnings), plus debug/E2E/instrumentation builds and eight native runner guard tests. Isolated MC9400 rich-record acceptance passed grouping, related paging, search/filter/Back preservation, camera/gallery persistence, parent-scoped gallery, approved preview, rotation, blocked navigation and forced-logout cleanup. Process-photo regression passed separately. All native requests matched the published semantic API.
+
+The date fallback needed to recognize the server's default `%s` metadata and differing raw/display JSON representations. Regression tests and a final unit/lint/APK gate cover that correction; actual TC22 screenshots show formatted dates and timezone context. The final date-only change did not repeat the full native suite.
+
+The maintained server was updated with a database/object backup and no reset. The ordinary TC22 application was replaced in place after matching its signer; the installed bytes match SHA-256 `F71033C835AC3EB361A04D78C842947C5A04C85CE1AB1B999AA8CEFBFC9D7A95`. Login, enrollment, server address and existing data survived. Actual TC22 inspection confirmed Actions, Take photo/Choose photo, Details/Items/History/Photos, formatted values and order 26 → Android Back → 26–50 of 1,000. No real camera capture or print was submitted during this visual check.
+
+Earlier UX-build hashes `23BA59F0EEE34D5B9ABBE5D45158A57C98416A5D7D69337090129AB6C853EABC` and `25DAB25D92FF709E4DA5DAA9949A501113E71DC050FF12E07C17C06EE06514E5` were superseded by the date correction. The preceding rich-record preview is preserved [separately](RICH-RECORDS-2026-11-05.md).
+
+## Source and remaining limits
+
+The user authorized commit, push and merge after the local update. Latest upstream scanner PRs 17/18 are retained. Reviews: [scanner/server PR 19](https://git.kof22.com/QRun-IO/qbit-mobile-scanners/pulls/19) and [Android PR 15](https://git.kof22.com/QRun-IO/qqq-android/pulls/15), which includes actual TC22 screenshots. Publication switches and repository dependency defaults are unchanged.
+
+The combined source passed a fresh **193-test** server gate: 53 scanner, 8 base demo, 22 mobile Record Files, 74 Echo and 36 Echo demo, zero failures/errors/skips and passing Checkstyle. The inherited build parent adds four guardrail cases; report-only extension schema-location/contract-test findings remain visible. Every source/resource file in the isolated build was matched to the merged working tree by count and SHA-256. Owner-coordinate and Checkstyle-path overrides existed only in that verification copy. A direct build against the old default Record Files snapshot failed because its authorization API is missing; the qualified running-demo cohort passes. Public owner-dependency adoption remains separate work.
+
+The November 4 TC22 operator pass remains accepted. Physical GS1 print/rescan, MC9400 trigger acceptance, HTTPS/signed-build qualification and public owner-dependency adoption remain distinct open gates. No production release or new Maven artifact publication is claimed.

docs/history/PRODUCTION-READINESS-through-2026-11-04.md

@@ -0,0 +1,107 @@
+> Historical record, superseded by [current status](../SESSION-STATE.md). Do not treat as current.
+
+# Mobile scanners 1.0 release gates
+
+Status: not release-ready. The user requested a full client/server audit and production-ready 1.0. This is an evidence ledger; a numerical quality score does not replace the gates below.
+
+## Current checkpoint — November 2
+
+Server `e3b775e` (Gitea PR 7) fixes the Generation/renderer output-limit mismatch and passes 45 Echo library plus 29 composed demo tests with zero Checkstyle violations. Android implementation `fb3cc5d`, published with documentation at `ffc5b49` (Gitea PR 10), passes 174 JVM tests, lint with zero errors and warnings, and the debug APK build. One local server on host port 57832 runs Echo, Record Files, Document Generation and Printing together (API 1.10.0, mobile 1.4.0, printing 2.3.0). The normal TC22 and the installed print client work against it, and the real 4x1 stock, media revision and Echo document are published and selectable. The earlier native acceptance (7 stages, 112 requests) used simulated printing and inputs.
+
+The synthetic HTTP event `ECHO-HTTP-TEST-001` has one matching scan and one actual ZPL print job in `SPOOLED`, with a Windows spooler job assigned and its process closed. A read-only recheck at 16:31 UTC confirmed that receipt, server HTTP 200, the running print service, and the TC22 showing Echo / Scanner ready / Connected. No Windows administrator prompt or printer pairing is pending. Paper output and physical TC22 print/rescan remain unconfirmed; see the [delivery receipt](../../examples/echo/demo/docs/echo-delivery-acceptance.json).
+
+Still not release-ready. Open: physical Code128 and leading-zero QR scan, print and rescan; extended barcode fidelity beyond the currently admitted types; full provider, camera, GPS, projection and device qualification; public coherent artifacts; primary Gitea CI; and final signing and distribution, which is deliberately last. Core PR 1337 was reviewed with its 57 focused tests verified, but normal CI and publication are not established and default dependencies are not repinned. Where dated checkpoints below describe the same-origin fix, printer connection, media, document or server composition as pending, this section supersedes them.
+
+## Superseded checkpoint — November 1, 17:34 UTC
+
+Server standards checkpoint0b53f34 is signed/pushed and all eight hosted checks pass; a fresh private API1.10 cohort passes39 server, six demo HTTP and18 Record Files consumer cases with Checkstyle. Client strict compilation and163 JVM tests pass; final TC22 native acceptance is running and the Query artwork density warning is being corrected before installation. About includes bundled Query artwork and the exact public Dogfooding/Query links.
+
+Actual Authentik desktop acceptance now passes real negative nonce rejection, A login, explicit company logout, old-cookie rejection, fresh B credentials and B principal in the same retained browser context, followed by B local logout/rejection. HTTPS verification remained enabled with profile-only fixture trust. The owned provider required its documented company invalidation flow; no global flow or default client sign-out policy changed. This closes the earlier desktop A-to-B handoff failure for the qualified API1.10 fixture, not the actual Android external-browser callback gate. The normal server remains API1.9/mobile1.1 and operator data is preserved.
+
+CorePR1369's new hosted run exposed a missing explicit architecture allow-list entry for extracted private-session logout plumbing; a narrow policy-conforming correction is under verification. Do not call final core CI green. Remaining physical GPS/camera/projection/lifecycle/retry, immutable files-owner handoff, deployment and owner-deferred signing/distribution gates remain open. Dated matrix rows below retain their earlier source/runtime scope and are superseded by this checkpoint where stated.
+## Current release ledger — November 1
+
+This is the current acceptance matrix; dated checkpoints below remain historical evidence. Android portrait-default source `7de2b5088fa376cb161ed5ac7e5358d2a2145d92` passes all eleven hosted checks. Documentation/QR fixture checkpoint `2e0fd962a7ece0f81328e5f9f05e4c1e2d77a853` does not establish physical QR acceptance. Server implementation `10416938724c9663d66f7848ff2b1a63fe635794` has qualified API1.9/mobile1.2 source evidence. Source publication, private consumer qualification and the installed operator runtime are distinct; no production APK or immutable dependency release is claimed.
+
+| Requirement | Accepted evidence and scope | Remaining release gate |
+| --- | --- | --- |
+| Current Android and CI | All eleven hosted checks pass at published Android8d8 (portrait implementation7de), including native navigation/input, PixelCopy and semantic E2E. The subsequent optional provider-logout working patch passes148 JVM tests, lint and debug build; its native tests compile but have not run. The completed-logout/enabled-action guard retains fresh-login/new-session assertions. Portrait default preserves explicit saved choices. | Physical operator navigation, lifecycle, ownership, outage/retry and leave/cancel walkthrough. Any later executable source needs its own verification. |
+| Trusted scanner ingress and hardware | Ordinary-UID/distinct-signer rejection of eight forged scans plus manual positive control; actual EMDK Code128 source/model/event proof: eight deliberate events on prior F3AF APK and one on the installed portrait-default C891 APK. Historical DataWedge evidence is separately retained. | Current leading-zero QR, repeated-intent/lifecycle/ownership matrix, connection failure and uncertain receipt/retry/leave acceptance. Code128 success does not qualify QR or every lifecycle path. |
+| Running operator deployment | Preserving coreecf/serverb14 UI API1.9/mobile1.1 runtime on127.0.0.1:57832; normal TC22 uses development APK C89161C522AA7DFFE09C009ABDE769C1BADB7E6C64BFCE699857062A1CEC6340 with signer/data backup preserved and portrait requested. | Supported production deployment, HTTPS/authentication, migration/recovery and release upgrade acceptance. No normal1.2/RF installation is implied. |
+| Source-pinned server/admin APIs | Server104 source:39 server/six demo/all15 browser cases,195 hashed JARs/2,441 unique QQQ classes/zero duplicates; record/bulk administration, profiles, presence, sessions and screen controls covered. Coreecf selected closure:4,507 discovered/16 existing skips/zero failures/errors. | Coherent immutable dependency publication and final supported deployment configuration. Default Maven dependencies still select RC.20; passing source-pinned consumers do not change that default. |
+| Authentik | Real Authentik2026.8.5 browser PKCE login established operator A; QQQ local logout invalidated its old cookie. With retained browser SSO, the next prompt=login silently reused A, so operator handoff failed. Optional semantic API1.10 RP logout and Android AppAuth handling are implemented but unqualified; the first core build found an API mismatch and review found an alternate-authentication-source gap under correction. | Correct and qualify the optional logout implementation, then prove real A→provider logout→B identity isolation. Native browser callback/lifecycle and user-selected sign-out policy remain pending. Existing failed retained-SSO evidence must remain failed. |
+| Optional whole-device viewing | Additive mobile1.2 server and consent-based Android source built/reviewed; mode/session-bound leases and bounded image ownership verified automatically. Normal server remains mobile1.1 and does not expose device-screen mode. | Actual OS consent/notification, Home/other-app pixels, Stop/lock/rotation, lease expiry and remote logout on the refined candidate. Separately preserve normal data before any coordinated1.2 upgrade. |
+| Camera/gallery and Record Files | Filesystem portability142 discovered/138 passed/four existing skips; metadata symlink-parent regression fixed and independently closed. Final coherent core32/scanner1a3 qualification passes39 scanner, six demo,18 Record Files and15 browser cases (78 total), with214 JARs/3,163 unique QQQ classes/zero duplicates and no separate filesystem override. Synthetic native camera/gallery/receipt cases remain separate evidence. | Coherent immutable supported RF/attachment-owner/core/RDBMS/filesystem tuple and default adoption, then actual TC22 lens/gallery permissions and durable authorized record association. The isolated coherent qualification does not establish the files owner full-suite/default publication gate or change the normal runtime. |
+| GPS and customer appearance | Foreground-only location/state/age controls and automated permission-denial/schema coverage; current basic operator display/navigation observed. | Real GPS permission/fix/disabled-provider behavior and customer-specific logo/physical appearance. |
+| Security, architecture and standards | Historical scoped security reports/remediations retained; independent architecture closure maps A1–A11 controls/tests. Whole-device changed-file review and follow-up found no concrete introduced issue; filesystem finding closed against corrected source/test evidence. | Final revision/scope reconciliation and unresolved external-provider/deployment gates. These reports do not become a new exhaustive scan or blanket production clearance. |
+| Release and operations | Release automation/source packaging independently reviewed; normal preserving migration/login checks passed. | Reviewed GitHub environment/tag protections, organization signing identity/recovery, actual signed APK upgrade/physical qualification and distribution decision. Signing/distribution remains owner-deferred until the final step. |
+
+The local emulator remains off because of workstation stalls. Disposable QA and private fixtures must not replace the normal package/runtime or clear operator data. No numerical quality score replaces the remaining gates.
+
+Historical November1 display observation retained: the handheld's black desktop mirror was not proof of a crash. Direct inspection found the normal process alive/resumed, no crash-buffer entries and connected sign-in; login reached Scan Capture without clearing data or running disposable instrumentation over the operator.
+
+## Historical checkpoints
+
+Latest correction: hosted Android testing found revoked heartbeats remained successful. Approval now precedes all heartbeat activity observation, including accepted trailing-slash aliases. Independent red reproductions and final 37-root/four-demo green tests are retained; new hosted native verification remains pending. Scanner authentication must follow configured Authentik through explicit native semantic authentication metadata; that implementation and real-provider acceptance are now required release gates.
+
+The optional consumer has subsequently qualified frozen0515 with37 fresh base and18 integration tests, including the matched core logging correction and runtime integrity checks. This remains an isolated private candidate; immutable dependency publication and optional hosted CI are required before production adoption. Separate OAuth2 log-redaction work in the native-auth core branch is not included in0515.
+
+## Scope and checkpoints
+
+Latest verified checkpoint: server `0926550` includes the standalone file-backed presence regression and the passing browser-to-native
+viewing regression after guarded-upload commit `84ffd7c`. Base 37, demo HTTP two,
+browser 15 and optional guarded integration 18 cases pass. Android's local reports
+show 91 JVM tests; TC22 navigation (12 cases), orientation, offline licenses,
+synthetic camera/gallery/rotation/logout, and the complete real-screen/session-end
+scenario pass. Native photo/session requests match published semantic operations.
+The full server deep static security review of `0926550` is sealed with no reportable findings. It does not inspect external dependencies or production configuration and does not replace runtime acceptance. Android's full scan and the later single-hamburger UX correction remain pending.
+These are checkpoint results; final Android audits, fresh Android hosted CI,
+production provider/immutable dependency qualification and actual lens acceptance
+remain open. Signing/distribution is owner-deferred until the final step.
+
+- Server semantic baseline: `7dd02b8874882ca2edcdcd89109b3dee6b4b0c88`, with all hosted checks passing. Documentation checkpoint: `a49724384f569a4b4b66ce2cd4aa69332ee1e0e8`.
+- Android semantic baseline: `6574ec4991dbb859b60c3a0be462af96918aee32`; hosted JVM/lint/APK, CodeQL and CircleCI checks passed, but both hosted native E2E jobs failed at compatible login before any credential request reached the server. Login/form reachability fixes are under verification; this baseline is not fully green.
+- Active implementation: [device/session history, live activity, actual app screen viewing, session termination, identity/presence/location and Record Files integration](../DEVICE-SESSIONS.md).
+- Final audit scope: both complete repositories, including shared Android core/mobileapp libraries, scanner host, qbit, demo, build/release configuration, tests and documentation. Exclude local secrets and operator data from published evidence.
+
+## Required gates
+
+| Gate | Status / required evidence |
+| --- | --- |
+| Feature completion | Session administration, screen viewing and device naming/presence/location have passing server/browser coverage. Native navigation/session and Record Files photo integration are in progress. Actual ingestion routes exist; atomic revocation/commit protection and compatible runtime qualification remain open. |
+| Security | Independent multi-pass full scans of the frozen client and server; validate findings, fix release blockers, verify fixes and retain coverage/limitations. |
+| Architecture | Review boundaries, coupling/cohesion, session ownership, semantic API evolution, concurrency, resource limits and deployment assumptions. |
+| Coding standards | Repository conventions, public API compatibility, lifecycle/error handling, duplication, dead code and maintainability review. |
+| Automated tests | Unit, HTTP contract, schema/version compatibility, browser record/bulk processes and native UI-to-real-server tests on the final revision. |
+| Physical acceptance | TC22 capture, mirroring, remote logout, failure/retry, restart, data preservation, location permission/age, camera capture and gallery upload to an authorized record. |
+| Delivery | Release build, signing/update approach, reproducible artifacts, dependencies/licenses, secrets checks and final hosted CI. |
+| Operations | Supported deployment/database migration, HTTPS/authentication, retention/resource limits, diagnostics and recovery documentation. |
+| Final review | No unresolved release-blocking findings; evidence identifies exact revisions and remaining supported-use boundaries. |
+
+## Verified baseline evidence
+
+October 31 working-source evidence: 37 root tests, two real HTTP acceptance tests and all 15 browser E2E cases pass. Browser cases include single/selected-bulk/full-query session end, cancellation, live image/clear, device profile edits, location timestamps and online expiry/filtering. The full browser run completed in 59.4 seconds after correcting file-H2 connection lifetime. A subsequent virtual-online projection fix passes the 37-test suite; its combined native acceptance remains pending. Android's intermediate 76 JVM tests and zero-error/zero-warning lint pass; shared native and real-server session tests remain in progress. These are local intermediate results, not a frozen release or fresh hosted qualification.
+
+Server: 23 root tests plus the real HTTP lifecycle scenario and six packaged-frontend browser E2E scenarios. Android: 53 JVM tests, six shared native UI tests, lint with zero errors/six warnings, debug/E2E APK builds, and six semantic native scenarios across focused runs. The final admin scenario passed in 255.917 seconds; 31 of 31 requests matched 13 published operations, including cancellation. These results are baseline evidence and must not be represented as verification of later session/mirroring changes.
+
+Physical TC22 (Android 14, DataWedge 13.0.325, app 0.1.0): installed with existing state preserved, signed in and approved through the actual device-record process. A dedicated DataWedge profile uses barcode input, explicit broadcast delivery and package/signature verification, with keyboard output disabled. Two deliberate Code128 trigger scans produced two records. One QR trigger scan preserved `001234567890`; backend records confirmed symbology, source, user/device/app/process and timestamps. Outage/retry and remote-session controls remain to be tested on the completed feature.
+
+## Review findings
+
+The initial full-source architecture/maintainability review covered Android `6574ec4` and server `7dd02b8`; it does not cover the later session/device features. Findings are being remediated, with final independent review still required:
+
+| Finding | Remediation owner / evidence pending |
+| --- | --- |
+| A1: scan retry cleared on an incomplete receipt | Android host: require matching acknowledgement ID, `scanSaved=true` and nonblank scan ID. |
+| A2: invalid scanner length metadata silently defaulted/truncated | Android host: reject invalid or out-of-range metadata. |
+| A3: legacy INPUT_FIELD bypassed typed field semantics and interpreted input as action code | Shared client: typed field handling and explicit action capability. |
+| A4: ordinary asynchronous status failures lacked a safe retry | Shared client: retry status GET without replaying submission. |
+| A5: cancellation during initialization could leave a late process orphaned | Shared client: retain cancellation intent and cancel a returned process ID. |
+| A6: login/forms could place actions outside the viewport or behind the keyboard | Shared client: scrolling/IME handling and constrained-viewport native tests. Hosted failure cause remains unproven until the regression evidence is complete. |
+| A7: explicit null displayed a default while submitting null | Shared client: distinguish absent keys from explicit null consistently. |
+| A8: business JSON collided with class-based serialization envelopes | Shared client: ordinary JSON values without class loading. |
+| A9: multi-record mutations and enrollment could persist partially | Server: transactions for credential/device and session/binding pairs and bulk state changes; provider logout after durable tombstones with explicit cleanup outcome. |
+| A10: media ownership/disposal could leak resources | Shared client: sound/image lifecycle ownership. |
+| A11: navigation title/state and native back stack could drift | Android host: derive navigation state from the active NavController. |
+
+The completed TC22 session scenario delivered and decoded real application JPEG pixels, cleared background frames, renewed viewing on resume, honored operator Stop viewing, ended the session remotely and accepted a fresh login. Android packaging now verifies 130 notice entries, nine license texts and eight native binary hashes in each host variant. The full server static scan is complete; Android review, external core logging remediation/adoption, production signing/update path, supported database migration and final hosted checks remain required before 1.0.

docs/history/README.md

@@ -0,0 +1,23 @@
+# Documentation history
+
+Latest checkpoint: [record UX completion, November 5](MOBILE-UX-2026-11-05.md). Earlier preview: [rich record fixture](RICH-RECORDS-2026-11-05.md).
+
+Superseded rolling logs, preserved verbatim as evidence. They are **not** current status: many entries describe work as pending that was later completed. Read the current entry points instead:
+
+- [Project README](../../README.md), [session state](../SESSION-STATE.md), [TODO](../TODO.md), [production readiness](../PRODUCTION-READINESS.md)
+- [Echo README](../../examples/echo/README.md), [Echo demo README](../../examples/echo/demo/README.md)
+
+| File | What it is | Covers |
+| --- | --- | --- |
+| [SESSION-STATE-through-2026-11-04.md](SESSION-STATE-through-2026-11-04.md) | The former `docs/SESSION-STATE.md` rolling log, newest checkpoint first | 2026-10-29 to 2026-11-04 |
+| [TODO-through-2026-11-04.md](TODO-through-2026-11-04.md) | The former `docs/TODO.md` ledger | 2026-10-29 to 2026-11-04 |
+| [PRODUCTION-READINESS-through-2026-11-04.md](PRODUCTION-READINESS-through-2026-11-04.md) | The former release-gate ledger, including per-gate evidence tables | 2026-10-29 to 2026-11-04 |
+| [ECHO-SESSION-STATE-through-2026-11-04.md](ECHO-SESSION-STATE-through-2026-11-04.md) | The former `examples/echo/docs/SESSION-STATE.md` | 2026-11-01 |
+| [ECHO-TODO-through-2026-11-04.md](ECHO-TODO-through-2026-11-04.md) | The former `examples/echo/docs/TODO.md` | 2026-11-01 to 2026-11-02 |
+
+## Reading notes
+
+- Entries are dated and were true when written. Where an entry says an item is pending, check the current documents before relying on it.
+- Gitea (`git.kof22.com/QRun-IO`) is the primary forge. Pull request and repository links to GitHub in these files are historical shadow references.
+- The content was moved without rewording; only a banner and relative links were adjusted. It contains workstation-local evidence locations and earlier version coordinates that do not apply to a fresh checkout.
+- The dated hand-off and review documents under `docs/` and `examples/echo/` (for example `CLAUDE-CI-HANDOFF.md`, `CLAUDE-SCANNER-AUTH-HANDOFF.md`, `ECHO-RELEASE-REVIEW-2026-11-01.md`, `ADAPTERS-HANDOFF.md`, `DOCUMENT-CHOICE-HANDOFF.md`, `examples/echo/demo/CLAUDE-HANDOFF.md`) stay in place with their original dates. Treat them as historical unless a current document links to them.

docs/history/RICH-RECORDS-2026-11-05.md

@@ -0,0 +1,7 @@
+# Rich record preview — November 5
+
+Before this update, the maintained demo ran the earlier 198-test public RC.21/Printing 1.0 cohort. The first TC22 records/photo preview was installed in place with SHA-256 `79E6CD0559419E059EC253DD0364C13BDDB3C27F566F0DA9A478FBB70D99A038`; the user then clarified that the existing app and existing server should be used, without a separate manual QA application.
+
+The rich-record update added demo-only synthetic tables, ordinary metadata sections/associations, read-only permissions and explicit attachment grants. Native grouping and child queries use the versioned semantic API. Verification caught missing section tiers in metadata serialization and missing Origin headers in the composed-server test helper; both were corrected without weakening server guards. The final gate passed 189 tests and Android unit/lint/build checks. Isolated MC9400 native acceptance passed before adoption.
+
+The maintained database and objects were backed up; the server restarted with the new application JARs and the same owner dependency cohort. Scanner-account reads verified all fixture counts and layout metadata. The existing TC22 app was updated with matching signer and installed bytes verified; its data and connection remained intact. Current details are in [session state](../SESSION-STATE.md).

docs/history/SESSION-STATE-through-2026-11-04.md

@@ -0,0 +1,275 @@
+> Historical record, superseded by [current status](../SESSION-STATE.md). Do not treat as current.
+
+## November 4 — current checkpoint
+
+This section supersedes the historical checkpoints below. The operator reports that the manual tests all passed. Release packaging and publication remain incomplete.
+
+- **Scanner publication complete:** PR 12 merged normally as `286e2e0`; run 3645 succeeded. Anonymous Central readback verified the JAR, POM, sources and Javadocs for `com.kingsrook.qbits:qbit-mobile-scanners:0.1.0-20261103.233448-3645`. All 37 published Java source files match the reviewed source.
+- **Android publication complete:** PRs 10 and 8 merged into `main` at `0ae2101`. Main lifecycle 3634 succeeded; the shared CI owner's independent registry readback matched all ten primary files, including both AARs, at timestamp `0.1.1-20261103.232145-3634`. This publishes development libraries, not a signed production APK.
+- **Local runtime updated:** the server on port 57832 now uses public QQQ `4.1.0-RC.21` and released Printing `1.0.0`. The existing database and settings were retained. A fresh identity and health check confirms API `1.10.0`, mobile extension `1.5.0` and printing extension `2.3.0`. The normal TC22 remains signed in, shows Echo setup with Copies 1 and Connected; the existing Print Agent shows Connected and ready against this server. No physical print was submitted during this update.
+- **Exact updated cohort qualified:** 198 tests passed with no failures, errors or skips and Checkstyle passed. All 94 scanner Java inputs match reviewed source; all five QQQ backend dependencies resolve to public RC.21. Released Printing removes the three private QQQ transitive dependencies from the prior gate. Other document/files components still use qualified local owner artifacts.
+- **Echo Printing default implemented and reviewed:** both Echo POMs now select released Printing `1.0.0`; the dependency comment and READMEs match. Both modules pass Maven validation and Checkstyle. The version pin is the only semantic POM change, and all 94 Java files match the prior 198-test qualification. Remaining owner package versions are unchanged; normal source review/publication is next.
+- **Remaining source/publication work:** commit, review and publish the two Echo POM defaults for Printing `1.0.0` (prepared above), and obtain the document owner's coherent standalone Generation/bridges/Record Files/Scripting artifacts, including copies. The owner's website image pipeline does not publish these Maven artifacts. The owner verified that the local standalone directories are not Git repositories and have no release workflows; reviewed code lives in host candidate `b6fb238`, using private coordinates. The remaining work is source extraction with provenance, public dependency pins and standard standalone release wiring. No new domain feature is required for this publication step. Claude access is restored, and the dependency owner's actual Claude standalone packaging is active as of November 4; no claim of completion is made.
+- **Manual acceptance passed, operator reported:** on November 4 the user stated, "i have ran the manual tests - it all works". Accept this as completion of the outstanding manual acceptance group and do not request the same checks again. See [TC22 acceptance](../TC22-ACCEPTANCE.md). This is the operator's report, not a newly instrumented run or separate per-case evidence.
+- **Remaining scope/distribution decisions:** Echo's documented scanner profile still explicitly refuses unsupported GS1/ECI/binary variants; the manual pass does not add encoder support. Production Android signing and distribution remain deferred by the user.
+
+Evidence: local `qqq-scanner-published-3645/anonymous-readback.json`, `qrun-android-3634-readback/registry-readback-proof.json`, `qqq-printing100-echo-gate-20261103/verified-summary.json`, and the runtime pointer `qqq-public-core-printing-runtime-current.txt` under the user's cache directory.
+
+## November 3 — historical checkpoint
+
+- **Server source:** `45f9cbddb14999d28add02dd9a37e4ce018e282e` is signed and pushed on Gitea PR 7 (earlier "uncommitted" statements below are historical). The five `qqq.version` POM pins to public **QQQ 4.1.0-RC.21** (root, demo, Echo, Echo demo, record-files) and the record-files POM test fix below are included in this verified dependency update.
+- **Final RC.21 gate: PASS** (`C:/Users/james/.cache/qqq-rc21-copies-gate-076d059d8d0641d9a85874ec64008def/verified-summary.json`). 377 unique tests with zero failures, errors or skips and Checkstyle PASS: Generation 179 and Printing bridge 16 (`verify-recovery.log`); scanner 53, demo 8, mobile Record Files 18, Echo 68 and Echo demo 35 (`verify-consumers-junit-fixed.log`). Plus 15 real admin-browser E2E cases on public RC.21 (single, checked and query selection, first-N approve, revoke, end session, display name/description, location/online, screenshot widget). The three earlier MySQL network timeouts did not recur in the focused 31 or the full 179 runs; the original failure reports are retained.
+- **Owned source fix:** `integrations/record-files/pom.xml` drops the aggregate Jupiter 5.11.4 and uses the BOM-managed engine and params; the XML test classpath shows API, engine, params and platform all at 6.0.2.
+- **Dependency honesty:** the five owned scanner consumer modules resolve only public QQQ artifacts (core, rdbms, middleware, filesystem, openapi RC.21; frontend-next RC.35), and Generation's core is RC.21 too, so all 182 scanner-consumer tests use public QQQ modules. The 16 Printing-bridge owner tests still resolve three private `pu507` QQQ libraries (filesystem, Javalin, OpenAPI) transitively through the existing owner Printing POM, and the other owner qbits remain qualified private inputs. So: **377 pass with public core RC.21 plus qualified owner inputs; this is not a fully public or released cohort.** No normal-runtime core upgrade was performed.
+- **Generation copies:** canonical Git source is now `Website-Backend/third-party-src/qbit-document-generation`. Signed `aac68907e67906aeef4e0cd687d28bc98b738f8c` is pushed on `feature/echo-generation-copies`, based on the actual PR 343 head `8f473fa`. The isolated clone `C:/Users/james/.cache/qqq-generation-copies-git-20261103` has 13 paths (including the PostgreSQL migration and provenance); the 21/21 module manifest matches. Qualified: 179 Generation + 16 bridge tests (prior cohort) and a fresh real PostgreSQL 17 migration pass. Owner integration and public artifact publication are not acknowledged and remain pending. No peer active checkout was edited.
+- **Android:** `f72b90d08cf29d2785cef1d5c5e7eeaf75f9afd2` is signed and pushed to the existing AGit PR 10 head (read back independently over SSH). Gitea CI 3480 **succeeded** on it (unit-test, device-test, package, secrets, gate; root read the UI); root also verified a clean git merge-tree of f72b90d with actual `main` b75fdac and merged nothing. Pull requests #8 and #10 remain open; nothing is released. The updated normal APK (SHA-256 `4AAB6951D3B0ABDDD4F5A8DC6790DCD84233EE08179B68DB108BF77909AB850E`) is installed with the same signer and no data clear; Connected, Apps, Settings, portrait, location on and the system-wallpaper brand-only preview were verified. No wallpaper or profile was applied. Fresh: 222 JVM tests, lint 0 errors/0 warnings (2 info), APK builds, 23 Node tests, 255-file standards pass. A fresh disposable TC22 Echo ten-stage run passed 109/109 semantic requests (simulated inputs and printing).
+- **Authentik:** a fresh real desktop acceptance passed against the same isolated TLS fixture (nonce, A login, logout with old-cookie replay rejected, fresh B without clearing cookies, logout). The opt-in native harness is integrated and compiled and its 8 launcher guards pass. Native TC22 execution still needs the temporary CA and PIN interaction (pending); no trust bypass. The normal server on 57832 is unchanged and ready.
+- **Still open (not claimed):** Generation canonical owner integration and public reproducible inputs for the owner qbits; primary source CI, merge and release; the manual TC22 trigger, value/type, AIM, label count, rescan, photo, GPS, projection and profile checks (the operator is still remote); native Authentik CA, PIN and callback; and signing/distribution, deliberately last by user decision. The normal TC22 currently shows Echo setup, Copies 1, Connected.
+
+## November 3 — publication preparation (historical; superseded by the current checkpoint above)
+
+The scanner/Echo/demo sources for copies per scan, AIM/EAN/UPC fidelity and photo composition are in the working tree of `feature/echo-example`, ready for one signed commit and review (not yet committed). They declare no private artifact coordinates: Echo's POM states that copies need a Generation build with the print-copies change, and `integrations/record-files` now takes `qqq.version`, `mobile.version`, `recordfiles.version` and `collaboration.version` with the demo's defaults. The Generation copies change is ten hash-checked files; its eight existing files match the Kof22 release reactor's `third-party-src/qbit-document-generation` byte for byte (SHA-256 listed in `qqq-finish-server-ready-20261103.md`). No Git repository for Generation exists in these local directories: adoption belongs to the Kof22 release repository, so the change is a hash-verified file set, not a commit here. Nothing was built or pushed in this step.
+
+## November 2 — Echo copies adopted in the normal local server
+
+Optional **Copies per scan** defaults to 1 and accepts 1–100. Omitted/null/blank setup uses 1. The run pins the quantity; scan payloads cannot change it. Each scan creates one retained job with options.copies, with retries preserving quantity and job identity. Existing records migrate to 1. The normal server on port 57832 now runs this feature, mobile-scanners 1.5 and mobile-record-files 1.0 using the original database, approval, accounts and printer configuration. The unchanged normal TC22 APK is connected and shows the setup field with 1.
+
+Verified gates: Generation 179, Printing bridge 16, scanner 53, base demo 8, mobile Record Files 18, Echo 68 and composed demo 35 tests (377 unique tests across module runs, no failures/errors/skips). Native TC22 acceptance passed ten stages and 116/116 semantic requests, including default 1, range rejection, chosen 3 across two scans, recreation and Leave. Scanner inputs/printing are simulated; physical count remains unconfirmed. Android source also passes 222 JVM tests, lint and APK builds; 15 Node tests pass.
+
+Generation's ten-file copies contract is verified in C:/Users/james/.cache/qqq-generation-copies-20261102 with handoff qqq-generation-copies-handoff.md; canonical owner adoption/publication is still pending. Echo photo composition is running and its authorization tests pass; actual capture/upload is unqualified. Native Authentik and physical trigger/print/rescan, camera/GPS/projection checks are deferred while the operator is remote. No certificate installation is confirmed. Public coherent artifacts/CI and final signing/distribution remain open. Earlier checkpoints below are historical.
+
+## November 2 — current checkpoint
+
+Source candidate: mobile-scanners 1.5 adds optional `aimIdentifier` and exact SDK `rawDataBase64` to persisted scans and backend `scanContext`. Changed metadata on an existing event is rejected; identical retries retain the original row, and omitted metadata cannot leak from the preceding event. The generated semantic contract remains compatible with the unchanged 1.0, 1.1 and newly preserved 1.4 baselines. The isolated four-module reactor passes 135 tests (53 scanner, 8 native HTTP demo, 45 Echo, 29 composed demo), zero failures/errors/skips and Checkstyle clean. Independent Claude diff review found no actionable correctness, security or compatibility defect; a whitespace-only review correction followed verification. This candidate is not installed in the running demo; hardware AIM extraction and extended Echo fidelity remain open.
+
+The first actual Echo native HTTP event exposed a composition defect: Generation requested its default 20 MiB allowance from a renderer capped at 1 MiB. Both demo launchers now propagate their configured cap into Generation. Restoring the old wiring produces three regression failures; the fixed library/demo reactor passes all 74 tests (45 + 29), with no failures, errors or skips and Checkstyle clean. The preserving local server restart uses these tested artifacts. A new, clearly synthetic `ECHO-HTTP-TEST-001` Code128 event completed real rendering, retention and printing: one job reached `SPOOLED` with a spooler job assigned, and native Cancel closed the process. The earlier failed event remains `ATTENTION` without a print job and was also cancellable. Neither event is a physical TC22 scan. Paper output and rescan confirmation remain pending; see [delivery receipt](../../examples/echo/demo/docs/echo-delivery-acceptance.json).
+
+The real trusted-local renderer has produced Code128 `QQQ-TEST-123456` and QR `001234567890` from the actual published 4x1 revision. Independent ZXing pixel decoding and stock/margin/fit checks pass; a fresh native read confirms the same published revision and stock. See [rendering evidence and test images](../../examples/echo/demo/docs/ECHO-RENDERER-ACCEPTANCE.md). That earlier rendering-only check submitted no printer job; the subsequent synthetic delivery is recorded above. Physical acceptance remains open.
+
+The primary CI secret-scan failure was reproduced locally as five findings in inert test-token literals. The fixtures now generate tokens at runtime; `.gitleaksignore` names only the five exact historical commit/file/rule/line fingerprints. There are no rule or path exclusions and no production validation changes. Historical and staged Gitleaks scans pass, and all 27 composed demo tests pass with zero failures, errors or skips and zero Checkstyle violations. Current hosted CI still needs verification after publication.
+
+Completed and verified:
+
+- Server source `e3b775e` is signed and published as Gitea PR 7. The Echo library and composed demo pass 74 tests with zero Checkstyle violations. Host forwarding accepts `localhost` and `127.0.0.1` with a valid explicit port, and foreign Host and Origin values are denied.
+- One local QQQ demo server on host port 57832 runs Mobile Scanners/Echo, Collaboration/Record Files, Document Generation and Printing (API 1.10.0, mobile 1.4.0, printing 2.3.0). On this workstation, device port 8080 forwards to host port 57832. The original accounts, enrollment and approval are retained.
+- Android `fb3cc5d` (Gitea PR 10) adds the native same-origin fix. The normal TC22 was updated without clearing data, and existing login and approval, heartbeat, real printer, media and document selection, and Cancel then Leave were verified. The emulator is off because it stalls this workstation.
+- The installed print client (RC4) is signed in, enrolled and connected to this server, and its native-approved ZPL printer is available. The Printing owner has aligned the loaded 4x1 stock (101600 x 25400 microns at 300 dpi) and updated the real media revision. No UAC prompt or printer setup is pending.
+- A real Echo 4x1 barcode document is published through native authoring, with a matching immutable revision 1. The TC22 selected the actual printer, the fresh 4x1 media and that document. Next succeeded and the device shows Scanner ready and Connected.
+
+Not yet done:
+
+- No physical Echo print or rescan has been proven. The synthetic event has exactly one matching scan and one actual ZPL job in `SPOOLED`, rechecked at 16:31 UTC. The same read-only check confirmed server HTTP 200, print service Running, and the normal TC22 showing Echo / Scanner ready / Connected. One physical scan of QQQ-TEST-123456 has been requested from the user; no UAC or setup action is pending.
+- The earlier native end-to-end run (7 stages, 112 semantic requests) used simulated printing and inputs. It is not physical evidence.
+- Still open for 1.0: physical Code128 and leading-zero QR scan, print and rescan; the full original provider, camera, GPS, projection and device qualification; public coherent artifacts; primary Gitea CI; and final signing and distribution. Signing is deliberately last, by the user's decision. A working first demo does not collapse these requirements, and nothing here claims release readiness.
+- Core native API merge continuation PR 1337 (a42f9e5) was reviewed with no actionable conflict regression, and its 57 focused tests were verified. Normal CI and publication are not established, and default dependencies are not repinned.
+
+The entries below are historical. Where they describe same-origin login, printer connection, media, document publication or server composition as pending, this checkpoint supersedes them.
+
+## November 2 — one local QQQ server and installed print client connected
+
+The canonical local server on57832 now runs Mobile Scanners/Echo, Collaboration/Record Files, Document Generation and Printing together, using the existing development database. Both original accounts authenticated. Live discovery advertises API1.10/mobile1.4/printing2.3; authenticated administration metadata exposes the composed modules. This is greenfield local development: no backup, cutover or cross-server bridge is required.
+
+The full demo gate passes27 tests with zero failures/errors/skips and zero Checkstyle violations. It includes file-backed existing-data acceptance and the USB-forwarded loopback Host regression. Actual running HTTP checks accept Host127.0.0.1:8080 through57832 and reject foreign hosts/origins. The TC22 retains its original app data, approved device and8080 USB connection; no emulator runs.
+
+The existing RC4 print client is now natively signed in, enrolled and connected to57832. It reports five printers/two exposed. The sole available ZPL printer was approved through the ordinary printingEnablePrinter process; the persisted native query confirms enabled/available. No physical job was sent and printer defaults were unchanged.
+
+(Superseded by the current checkpoint above: the same-origin header, 4x1 media report and document publication are done. Only the physical TC22 scan, print and rescan remains for the demo, and the full production release gates remain open. Earlier separate 53118 pairing and Windows-prompt status below are historical.)
+
+## November 1 — corrected setup verified on TC22 and published
+
+Server source8da274e and Android test-only source47a923a are signed/pushed; Android's actual Gitea PR10 review topic was advanced to47a923a via SSH AGit (the source feature branch alone does not advance an AGit review ref). Required printer/media/INTEGER Document selection, dependency clearing, two accepted synthetic scans with the same selections, recreation and Apps/Leave all passed on real TC22:7 stages,112/112 published semantic requests,15 operations. Normal app/data preserved; emulator off; printing/scanner qualification flags remain false. Server45/library24/demo and Android99focused/host tests+8Nodeguards/lint0errors0warnings pass. Live private server53118 is still101efc8/EchoRetry pending document-choice rollout, and actual printer pairing awaits the current Windows consent in existing session73437. No root physical print has occurred. Normal57832 stays unchanged.
+## November 1 — operator chooses the Document at setup (server verified)
+
+User-confirmed flow: choose printer, Document template and paper/label size once, then repeat scan -> server render -> accepted print job until Leave. The Android client remains a generic semantic QQQ process client; it has no printer-device integration. `templateId` is required INTEGER with an authorized dependent PVS, not a hidden server default. The run pins selected template/revision; changed documents are refused rather than substituted. Migration preserves existing rows. Root:45 Echo library/24 full composed demo tests PASS, Checkstyle0. Tests include two document choices, forged retarget refusal, republish refusal with native Leave/CLOSED and repeated scan rendering. Expected errors use existing output.setException to retain process ownership after core step failure. Native Android tests99 + Node8 + lint0errors0warnings/testAPK compile pass; updated TC22 UI acceptance remains in progress. No physical print claim. Private live53118 remains filtered source101efc8/EchoRetry until this rollout, and printer retry awaits Windows consent; normal57832/TC22data are preserved.
+## November 1 — shared device headers scoped per extension registry (verified)
+
+`MobileScannersRouteProvider` interpreted every `X-QQQ-Device-*` header as a scanner credential, so a native Printing agent's own proof got 403 on `/qqq/v1/qbit/printing/*`. It now leaves a request to another extension's own authenticator only when the path is another extension's `/qqq/v1/qbit/*` route (not scanner routes, metadata, process or widget calls) and QQQ already validated a registered, non-`android`, non-`web`, non-token client channel. Android and unmarked requests keep scanner verification everywhere, ended-session and approval checks are unchanged, and no scanner device is bound for the foreign route, so the marker grants nothing. New composed demo regression `printerDeviceProofIsAuthorizedByPrintingAndNeverByScannerAuthentication` passed against the new immutable private scanner artifact. Root verification:50 scanner tests,7 base-demo HTTP tests and23 composed Echo-demo tests, Checkstyle0. The corrected regression fails403 at printer binding on the old artifact and passes on the fixed artifact; wrong proof/actor and scanner-boundary denials remain enforced. Live update and physical printing are separate.
+
+## November 1 — independent review corrections verified
+
+The scoped independent review of Echo4bc88a4/Androida2f0080 found a pre-pin recovery gap, an unchecked atomic pin result and a late-revocation receipt-audit gap. The fixes preserve authorization checks and lookup-only recovery after a pin. Five meaningful regressions now pass: Echo38 and full composed demo22, Checkstyle0. See ECHO-RELEASE-REVIEW-2026-11-01.md. The running private backend remains on the earlier qualified Echo artifact until an owned rollout; no running SDK or normal operator database was overwritten. Physical print/rescan and public release gates remain open.
+## November 1 — Echo composed pipeline verified and private backend live
+
+Echo's 33 tests and the runnable demo's full22 tests pass with zero failures/errors/skips and Checkstyle0. The clean native HTTP acceptance uses the real Generation, Record Files and Printing owners: two scans create two retained originals and two accepted jobs; retry preserves one job, and Leave closes the run. Renderer output is controlled and printer inventory simulated in this test, so physical printing remains unqualified. The Echo source checker now accepts core's exact bare READ capability probe while preserving user/permission checks, actor row locks and concrete write denial. The demo enriches complete QQQ metadata, establishes attachment capability, and derives the printing tenant idempotently. Host tests reset JVM-local RDBMS providers between fixtures.
+
+The local launcher uses the renderer owner's explicit TrustedLocalDockerExchange public factory (unique private renderer0.1.0-echo.gen64c9pu507.tl1); no copied transport or production fallback remains. Owner52 tests and real Docker smoke qualify development use only. A fresh private instance is live with successful scanner/admin semantic login and metadata; no printer or template is configured yet. Normal operator data/runtime remain preserved.
+
+Next required path: native Windows printing connection/current4x1stock handoff, publish and pin a real media-matched template, actual TC22 scan/print/rescan, and primary Gitea CI/public dependency publication. Full1.0 physical provider/GPS/photo/screen gates and broader AIM/EAN/UPC/GS1/raw barcode fidelity remain open. Production signing/distribution is deferred as requested. Passing private SDK/source gates is not a production release claim.
+## November 1 — coherent scanner and Record Files regression verified
+
+Security-key snapshots compare effective membership as sets, allowing identical repeated grants and reordering while rejecting new or changed authority. Optional Record Files authentication applies the owner's CollaborationSecurity.applyToSession during login/revalidation before the first verified capture. Scanner50 and native Record Files18 (16 integration +2 contract) pass with zero failures/errors/skips and Checkstyle0 against the complete private gen64c9pu507/PU dependency cohort. This supersedes the prior pending/failed native18 checkpoint; it does not declare private dependencies published or production-qualified.
+
+Echo32 and runnable demo12 also pass on that cohort. The demo startup test uses a refusing renderer; actual live cold renderer configuration and physical print/rescan remain pending. Android169 JVM and five-stage TC22 native semantic Echo acceptance passed with simulated printing. Gitea is primary for further source publication; previous GitHub PR links are historical shadow references. Preserve the normal scanner/server/data and printer installation. Signing/distribution remains deferred.
+## November 1 — verified capture identity retained without authority drift
+
+Claude's scanner fix preserves the same already-verified session only after current approval/binding/authentication and unchanged session reference/authority checks. First capture still wraps. Tests cover repeated object identity, current permission/credential ceilings/selectors, device and user binding, revocation, and real post-query-hook mutations during validation. Mutable opaque authority values refuse retention. Full scanner49 and real demoHTTP7 cases pass with Checkstyle0 against the frozen privatePU/f708 core.
+
+The files owner still must qualify its strict native upload/finalize18 against this exact patch; no per-instance enrichment policy or global registry is adopted. Normal server/data remain unchanged. Echo native TC22 now passes all5stages/86documentedrequests with client3bec46d; real renderer/printer output and final host integration remain open. Production signing is deferred.
+# QQQ Mobile Scanners session state
+
+## November 1 typed scan context implementation
+
+Extension 1.3 defines accepted `scanContext` for backend actions, preserving exact symbology and server-derived attribution. Legacy omissions are explicit UNKNOWN/MANUAL; event inputs are consumed, changed retry types/apps/processes are rejected, and pre-context state requires reopening the process. The default scanner loop remains while appended host steps can consume context. Qualified private API 1.10 verification passes 44 root, seven real-HTTP demo and 18 optional integration tests with normal Checkstyle; canonical contract generation passes two additional tests and preserves both release baselines. The source cohort is `qqq-server-typed-context-843fa0ee69b34535b1890cf7347492ee`; no normal runtime adoption is implied.
+
+## Echo implementation scope
+
+User requested example QQQ application Echo: first select printer and paper/label size, then continuously scan → render the same value/symbology → print until leaving. User chose one in-flight job and delegated first real printer/media choice to the printing master. Team implements the optional examples/echo host, ordinary semantic QQQ process metadata and server per-scan context; no new Android screen engine, barcode encoder, attachment framework or print queue.
+
+Owner coordination requests are posted in our shared mailbox. Source discovery found missing authorized media discovery/job options, worker barcode fit-to-stock, least-privilege printing submission and an immutable retained-print adapter handoff. These are concrete integration gates, not permission to change the other masters' source or live printer/service. Implementation and isolated tests can proceed while owners respond; no physical print or final working Echo claim yet.
+
+## November 1 standards implementation and API 1.10 qualification
+
+Copyright/SPDX, member layout and optional PowerShell tooling fixes are applied. Unexpected server failures now produce fixed structured diagnostics without private values. The attachment test fixture closes its metadata-before-stream ownership gap. Fresh Checkstyle/compilation, 39 root tests and six real HTTP tests pass against the qualified private API1.10 cohort; optional integration verification is tracked in the standards review. These are source gates, not a normal-server deployment.
+
+Core native API1.10 is signed and published as e1e45b29f in draft PR1369. Its real Authentik fixture is upgraded and actual retained-browser account switching is under test. Android1127 is published; the installed normal APK is the diagnostics/location3fee build, preserving sign-in and data. Prior installed1c Code128, leading-zero QR and menu/reopen were physically confirmed. Default-on location, existing fine/coarse grants and system location are verified; an actual GPS fix remains open. Historical entries below retain their original scope. See [standards review](../CODING-STANDARDS-REVIEW-2026-11-01.md).
+
+
+## November 1 provider logout implementation in progress
+
+Core32 passes all ten hosted checks, including corrected1000-test sample acceptance; Android8d8 passes all eleven checks. The final coherent core32/scanner1a3 cohort passes39 scanner/six demo/18 Record Files/15 browser cases and is recorded in the published qualification document.
+
+Real Authentik now passes a desktop-browser PKCE callback through the native-session exchange contract, principal A, QQQ logout and old-cookie rejection. This does not establish Android external-browser acceptance. A subsequent login with provider SSO retained silently reused A despite prompt=login. The pinned provider also ignores max_age=0. This is an open operator-handoff issue, not a passed two-operator test. Optional standard RP-initiated logout is being implemented in core branch feature/mobile-native-provider-logout (based on core32) and the Android client, with explicit API1.10 capability, encrypted session-bound hint storage, local logout independent of provider failures, and a separately correlated AppAuth end-session attempt. The user policy choice (automatic company sign-out versus retained SSO with account confirmation/Switch account) remains pending; default sign-out behavior has not changed.
+
+The optional Android provider-logout working patch passes148 JVM tests, lint and debug build; native cases compile but have not run. The first isolated core package failed at an UpdateOutput API mismatch before tests. Independent review also found the optional hint gate must reject alternate in-process/code-state authentication sources; corrections and an HTTP regression are in progress. Initial failed candidate evidence is preserved.
+
+The isolated localhost-CA E2E APK built from signed Android8d8 passes63 unit cases/zero lint errors and packaged CA/callback/signature inspection. It is not installed; no device trust changed. Normal TC22 remains portrait C891 and its API1.9/mobile1.1 server remains untouched. Current QR, camera/gallery, projection, GPS and failure/navigation operator acceptance remain open. Files-owner immutable handoff/default adoption and final signing/distribution remain separate.
+
+Updated: 2026-11-01
+
+## November 1 release reconciliation
+
+Published server1041693 retains its qualified source-pinned API1.9/mobile1.2 server/demo/browser/provenance evidence. Android portrait-default7de passes all eleven hosted checks; QR documentation2e0fd962 does not establish physical QR acceptance. The normal runtime remains coreecf/serverb14 API1.9/mobile1.1 on57832, with normal portrait-default C891 development APK installed preserving signer/data. Trusted EMDK Code128 evidence comprises eight priorF3AF events and oneC891 event; QR, lifecycle/ownership and failure/retry/leave operator paths remain pending. Whole-device1.2 is qualified source, not installed normal-server behavior.
+
+Filesystem portability passes142 discovered/138 passed/four existing skips, including the corrected invalid-reference exception contract; its metadata symlink-parent and NUL-reference findings are independently closed. The final coherent core32/scanner1a3 cohort passes78 consumer cases, including18 Record Files cases, with no separate filesystem override. Matching files-owner immutable/default adoption remains open. Actual Authentik flow remains pending; strict proxy TLS now works, while provider configuration returned a validation error under diagnosis; physical projection, camera/gallery and GPS acceptance remain open. Signing/distribution stays owner-deferred until the final step. [PRODUCTION-READINESS.md](../PRODUCTION-READINESS.md) is the current matrix; older entries below retain historical scope and are superseded where their then-open state has changed.
+
+Cross-chat coordination uses `R:\agent-comms\README.md` and the mobile master's owned `R:\agent-comms\qqq-mobile-scanner.md`, explicitly requested by the user. Record Files and Printing acknowledged the directory. Read the current summary at the top of each owner's mailbox before changing shared contracts.
+
+## November 1 Record Files consumer checkpoint
+
+The isolated core32/scanner1a3 cohort passes all 78 consumer cases (39 scanner,
+six demo HTTP, 18 Record Files and 15 real-browser process tests), with coherent
+backend versions, 214 optional runtime JARs and zero duplicate QQQ/QBit classes.
+Core verification combines the prior full reactor gate, the corrected filesystem
+full gate and an exhaustive final artifact class comparison; see the precise
+[qualification scope](../../integrations/record-files/docs/CORE-32DF-CONSUMER-QUALIFICATION.md).
+The files-owner matching immutable handoff, optional default adoption and actual
+camera/gallery acceptance remain open. This cohort did not change the normal
+runtime, device or historical optional default.
+
+## October 31 current checkpoint
+
+The normal local demo is now running the qualified `ecf0f550`/`b14d925` API1.9/mobile1.1 TABLE runtime at its existing loopback address. This supersedes the unchanged-runtime statements in the historical acceptance entries below. Read-only inspection froze its actual old classpath; old-runtime and old-after-new HTTP/login checks passed on historical and fresh closed backups before startup. Fresh copied invariants preserved every original column, row count, password/device-credential hash, barcode and UTC timestamp. Both original accounts passed live login, authenticated metadata and logout; ordinary semantic queries confirmed two devices and three scans, including the leading-zero barcode. The normal Android installation and peer services were preserved. Private backup/runtime evidence is retained in the task cache; old PID-specific maintenance helpers must never target the replacement JVM.
+
+Optional consent-based whole-device viewing is under implementation as an additive extension1.2 contract; it is not part of that running, qualified1.1 runtime. Android diagnostic checkpoint `6f25562` is published to its existing PR after instrumentation compilation; fresh hosted results remain pending. The actual trusted-scanner trigger attempt is unverified. Production signing/distribution remains the final owner decision.
+
+The initial1.2 reactor now passes39 server and six real-HTTP demo tests with normal Checkstyle, no failures/errors/skips, unchanged qualified-core hashes and unchanged1.0/1.1 baselines. Independent changed-file source review found no concrete introduced security finding; Android consent and projection acceptance remain open. The diagnostic Android checkpoint subsequently passed CircleCI37 native tests and unit tests; its earlier intermittent focus-owner cause remains unproven.
+
+Exact-source core `ecf0f550a0357cec6387c2b54efca128a405a629` with server `b14d925b741e815d1cfa4f62301f19207f25b03f` now passes fresh37 server/five demo tests, strict runtime provenance and all15 browser cases (zero skips/flaky/failures). The runtime has195 hashed JARs,2,440 unique QQQ classes, zero duplicate QQQ classes, patched Guava33.7.2-jre and H2 2.2.224. Core's full selected closure separately passes4,507 discovered/16 existing skips/zero failures/errors. See [qualification scope](../API19-CONSUMER-ACCEPTANCE.md). No operator runtime was upgraded by this acceptance.
+
+The demo now imports the QQQ BOM using its own `qqq.version`, so an explicit version selection governs its complete transitive QQQ runtime. Private source qualification caught the prior mismatch: the scanner's installed POM retained its default RC.20 property, while the demo override selected a newer direct RDBMS dependency. The strict runtime verifier rejected the mixed core/Javalin/OpenAPI versions and older Guava despite passing tests. The first BOM-aligned run then exposed the demo's explicit JUnit 5.11.4 aggregate mixing an older API with the BOM's JUnit 6 engine; the demo now uses the BOM-managed test engine and its matching API/platform. The coherent candidate's fresh acceptance is recorded above; passing tests from the earlier mixed runtime did not establish that result. No operator runtime or shared Maven repository was changed.
+
+The normal operator demo was upgraded in place to mobile extension1.1 with a closed owner-only backup: two accounts, two devices (one approved), three scans, credential hashes and timestamp instants were preserved. Both original passwords authenticated after startup. Its JVM currently uses UTC because the copied upgrade exposed H2 converting legacy zoned timestamps using the workstation zone. The canonical H2 schema now begins by setting its migration connection to UTC, protecting both direct schema consumers and the demo initializer. A no-install reactor verifies the freshly packaged base resource: 37 base tests and five demo tests pass, with zero Checkstyle violations, including a file-backed America/Chicago child-JVM regression over all eleven converted timestamp columns, multiple source offsets, preserved passwords/approval/barcodes and an idempotent second startup. The isolated old-schema resource without the UTC statement fails with the expected six-hour winter timestamp shift; the tested jar resource hash matches the canonical source. This source change does not restart the operator runtime; it remains safely mitigated with UTC.
+
+The optional Record Files consumer now explicitly defaults to frozen0515 and its separate isolated-m2-0515 cache. Fresh normalized-heartbeat base37 and optional18 pass, with214 runtime jars/3180 classes/zero duplicates. Immutable evidence is retained under integrations/record-files/evidence/20261031-124632Z. Earlier0352 native acceptance remains historical;0515 is a new server consumer qualification, not an operator upgrade. Published dependency coordinates and hosted optional CI remain blocked on the upstream handoff recorded in HOSTED-CI-DEPENDENCIES.md. New API1.9 native Authentik metadata is being developed in an isolated core worktree and is not part of this server's adopted dependencies.
+
+Hosted Android acceptance exposed a heartbeat revocation defect after the published checkpoint: pending/revoked devices could keep receiving successful heartbeats and remain signed in. The fix checks approval under the existing activity lock before observing activity, and the route filter avoids pre-observation for canonical and accepted trailing-slash heartbeat paths. Both defects were independently reproduced before correction. Final root verification/install passes 37 tests and demo verification passes four tests, including the real HTTP no-side-effects regression and standalone presence case. Native hosted confirmation on the new server revision is still required; earlier static zero-findings results do not prove absence of this defect.
+
+Server checkpoint `0926550` includes 37 passing root tests, two HTTP acceptance cases, a passing standalone file-backed presence regression and 15 passing browser cases. The optional Record Files module adopts frozen bundle `retained-contract-20261031-0352`; 18 guarded integration/contract tests pass. TC22 navigation (12 cases), orientation, offline licenses, synthetic photos and the complete screen-viewing/session-end scenario pass on Android checkpoint `d5b5580`. These do not imply an operator-runtime upgrade or actual camera-lens acceptance.
+
+The full server deep static security scan of `0926550` completed and its canonical report was sealed on October 31 with no reportable findings. Coverage excludes external dependency implementations and production configuration; no new runtime tests were executed by the scan. The known external core DEBUG session logging issue, immutable Record Files publication/CI and production provider qualification remain open. Android's final full scan is still pending. A user-requested single-hamburger navigation correction is now being implemented after the published Android checkpoint; its new tests are not yet run.
+
+The normal operator demo and normal TC22 package remain unchanged. A separate temporary visual demo showed the new menu on the TC22; the user stopped computer control and retains the device. Do not restart, uninstall or drive that demo until coordinated. Signing/distribution remains deferred to the final step.
+
+The local emulator is closed after the user confirmed it caused workstation-wide stutters. TC22 is connected; do not restart the emulator automatically. Builds are serialized with bounded workers. Existing operator demo and handheld state remain preserved. Android85 JVM tests and zero-error/zero-warning lint pass at the last compiled checkpoint; newer changes must be verified again.
+
+The active goal authorizes completing and publishing the project, superseding historical artifact-publication deferrals below. However, on October31 the owner explicitly deferred signing and distribution until the final step because the channel is undecided. Complete implementation, final audits, tests, documentation and ordinary hosted CI first. No signing key, production release, merge or deployment is claimed.
+
+## Active: device sessions, live screen viewing and 1.0 audit
+
+Additional user scope: unique short device names assigned at setup/approval, editable names/descriptions, independent approval/presence, online fleet view and foreground GPS with age/accuracy. Camera/gallery photos use the separately developed Record Files qbit. The Build QQQ Documentation agent owns it and `qbit-record-files/docs/INGESTION-CONTRACT.md` documents the implemented record-files1.0 semantic capabilities/create/status/chunk/finalize/cancel operations and durable receipts. The October31 checkpoint above supersedes earlier proposed-only contract status. Native photo acceptance and the final authorization guard remain pending; unavailable capabilities stay hidden.
+
+The user requires all device/session history, live activity and actual application-screen viewing in QQQ administration, plus session termination. Implementation follows [DEVICE-SESSIONS.md](../DEVICE-SESSIONS.md): ordinary QQQ tables/widgets/processes, server-owned authenticated bindings, an additive 1.1 semantic extension and demand-based bounded screen frames. Native and browser actions require full E2E coverage, including record and bulk entry points.
+
+The user also requires independent in-depth security, architecture, coding-standards and coupling/cohesion reviews of both complete repositories before a production-ready 1.0. [PRODUCTION-READINESS.md](../PRODUCTION-READINESS.md) tracks the gates and exact baseline evidence. Plan: complete the session feature and tests; freeze final revisions for independent audits; remediate and verify findings; complete physical and release/operations acceptance. Deployment/distribution details have been requested. No 1.0 readiness or release is claimed.
+
+## Current: semantic API migration
+
+The qbit registers mobile-scanners 1.0.0 through QQQ's extension registry. Device enrollment/current status, branding and connectivity use `/qqq/v1/qbit/mobile-scanners`; discovery advertises the relative prefix `/qbit/mobile-scanners`. The generated OpenAPI includes typed device and scanner event/acknowledgment schemas, stable operation IDs and standard errors. Legacy standalone mobile routes are removed. [UI-API.md](../UI-API.md) describes the contract and versioning policy.
+
+Root `verify install` passed 23 tests, including the extension contract baseline checks; demo `verify` passed one real HTTP discovery/schema/error/lifecycle scenario. All six migrated browser E2E scenarios passed in 2.9 minutes. Native integration exposed an unregistered Android client channel returning HTTP400; the qbit now registers `android` without replacing existing channel policies. The real HTTP regression sends `X-QQQ-Client: android/qqq-mobile` on all requests and passes. Android requires `android` in discovery's `clientChannels`; its combined JVM suites passed 53 tests (core 21/mobileapp 23/scanner 9), with six shared native UI tests also passing. Final lint passed with zero errors and six warnings; debug and E2E APK builds passed. Five native scanner scenarios passed with the OpenAPI request audit: incompatible core version, missing extension, missing Android channel, baseline scan flow and additive future metadata. The final native administration form scenario passed in 255.917 seconds after correcting completion handling for a COMPLETE response without `nextStep`: approval, revocation and cancellation completed, with all 31 requests matched to 13 published operations. All six native scenarios passed across the original and focused reruns; this is not a claim of one uninterrupted six-case run. All hosted checks passed for published server commit `7dd02b8874882ca2edcdcd89109b3dee6b4b0c88`: CircleCI setup/verify, CodeQL, Windows helpers and the demo HTTP/browser E2E job.
+
+Active plan: publish the companion Android checkpoint pinned to verified server code `7dd02b8`, then add the requested device/session activity, session termination and on-demand app-screen viewing. Physical connection-loss/retry and revoke-denial checks are deferred to acceptance with those session controls; the persistent server and USB forwarding are restored. The local server and emulator restarted after the workstation crash with data preserved; the backend administration UI was visibly signed in. The physical TC22 is identified through authorized USB debugging, running Android 14 and DataWedge 13.0.325. The debug app is installed and signed in. Approval from the browser record's Actions menu visibly reported one device approved; the handheld then opened the native app catalog and Scan Capture process. Updating the APK preserved its login. DataWedge is configured for package `io.qrun.mobile.scanner`, activity `*`, barcode input enabled, keystroke output disabled and Intent Output enabled. Intent delivery uses Broadcast, action `io.qrun.mobile.scanner.SCAN`, category `android.intent.category.DEFAULT`, and an explicit target package with signature checking enabled. Two deliberate physical trigger presses were confirmed by the user and produced two persisted records visible in Barcode Scans. A stored row matched the TC22 receipt for `QQQ-TEST-123456`, CODE128, source `scanner`, user `scanner`, TC22/Android 14/app 0.1.0, app `mobileScanApp`, process `mobileScanCapture`, and capture/receipt timestamps. Basic physical Code128 delivery and persistence passed. A subsequent physical QR scan was acknowledged on the handheld and independently visible in the backend as `001234567890`, `LABEL-TYPE-QRCODE`, source `scanner`, with matching TC22/user/app/process and capture/receipt metadata. Three physical records are verified: two deliberate Code128 captures and one QR capture. Physical QR delivery and leading-zero preservation passed; physical connection-loss/retry and revoke-denial checks remain pending. The old semantic-gap note below is superseded by this implementation status and the current TODO.
+
+## Verified: record and bulk device administration
+
+- User reported Approve Device did not work from a device record and required proper E2E coverage for every process, including single-record and bulk entry points.
+- Root and real HTTP regressions reproduced the missing selected device ID. Approval/revocation now prepare a stable selection, show confirmation, apply only after confirmation, and display a result/count. Explicit selected IDs and native select-all/first-N filters are supported up to 100 devices; oversized selections fail explicitly.
+- The process stores selected IDs in native process records, ignores replacement IDs submitted at confirmation, rechecks administrator permission, and validates all targets before changing any. Standalone manual ID entry remains supported.
+- Root verification/install passed 21 tests and Checkstyle. Demo verification passed the real HTTP scenario covering single-record approval, both bulk selection modes for approve/revoke, unselected-device isolation, visible results, scanner permission denial, scan persistence/retry, and revoked-device denial.
+- Restarted the persistent local demo on port 57832; public status returned `ok`. Accounts, database and emulator forwarding were preserved. Dedicated scanner-host native E2E passed (one complete real-server scenario, 50.932 seconds); Android verification also passed 28 JVM tests, lint/build and workflow syntax. Test APKs were removed and the normal scanner restored.
+- Browser E2E passed all six scenarios in 2.7 minutes: record approve/revoke with results and return navigation, checked-row bulk with untouched-device assertions, standalone manual entry, cancellation, full-query selection, and first-N selection with independent persisted-state checks. Tests use the packaged frontend and a temporary real backend. The fixture authenticates through the real API and supplies the nonsecret `qqq.sessionHint` marker so the UI resumes and validates its HttpOnly cookie. Browser checks now run inside the existing required demo CI job; native E2E runs in the Android push/PR emulator lane. New-head hosted results remain separate from these local passes.
+- UI/UX API clarification: the Android app uses `/qqq/v1` metadata/process operations, but full semantic-client conformance is unfinished. Version/feature negotiation, broader native component handling and migration of separate `/mobile/v1` routes into a registered UI API extension are tracked in TODO; do not describe the current client as fully conformant.
+
+2026-10-30 correction: native authentication metadata is served at `/qqq/v1/metaData/authentication`. The device-header guard now exempts that exact public path; the previous legacy-only exemption caused HTTP403 on app restart after enrollment when device headers were present before a user session was restored. A real HTTP regression failed before the fix and passed afterward with stale, pending, invalid-token and revoked device headers. Protected metadata/process/scan authorization still fails appropriately. Root13 tests, Checkstyle and demo HTTP acceptance passed; the local demo was restarted on57832 with its persistent database and accounts preserved.
+
+## Current repository and demo state
+
+- GitHub repository created at https://github.com/QRun-IO/qbit-mobile-scanners with `develop` as default. Initial signed commit `abbcc39` is published. Companion Android implementation is in https://github.com/QRun-IO/qqq-android/pull/8.
+- Hosted initial-commit checks passed: CircleCI `setup`/`verify`, CodeQL `analyze / Analyze branch source`, demo HTTP acceptance and Windows helper analysis. CircleCI dynamic configuration is enabled. Maven artifact publication remains disabled.
+- Runtime branding is configurable on the server before login; the shared Android APK uses the customer name, primary color and optional HTTPS logo. Public branding/status endpoints carry no credentials. Root tests now pass 13 cases; demo HTTP acceptance also passes.
+- Windows demo helpers store generated demo passwords using per-user Windows DPAPI outside the repository. An Android 15/API35 emulator is running with WHPX; six native UI instrumentation tests passed. Physical TC22 acceptance is still pending.
+- The current workstation demo uses loopback port 57832 because other services occupy the conventional ports. `adb reverse tcp:8080 tcp:57832` preserves the Android server URL `http://127.0.0.1:8080/`. Start it again with `pwsh -File scripts/Start-Demo.ps1 -SkipBuild -Port 57832` after stopping the existing instance. See `LOCAL-DEMO.md` for login helpers.
+- The earlier verification/handoff notes below describe the initial implementation before repository publication and emulator setup.
+
+## Confirmed scope
+
+- Native Android host for Zebra TC22 and other handheld scanners, extending `qqq-android`.
+- Server-defined native screens and QQQ process actions, using existing QQQ metadata.
+- Online only for version one; no offline scan queue.
+- Local demo server with real QQQ login and required administrator device approval.
+- First app: barcode capture into a QQQ table with scan, user, device and timestamp metadata.
+- User authorized Codex agents for implementation and subsequently requested GitHub repositories and standard project files. Repository creation and pushes are authorized; artifact publication remains disabled.
+
+## Completed plan
+
+1. Established enrollment and scan contract using existing QQQ APIs.
+2. Implemented qbit tables, native metadata/processes, approval/revocation and guarded routes.
+3. Added Android scanner host, table-based login/enrollment gate and Zebra DataWedge input.
+4. Added a file-backed H2 demo and verified native login, approval, scan, retry and revocation over HTTP.
+5. Built the Android debug APK and documented TC22 hardware acceptance.
+6. Added standard repository/community files, current shared CircleCI QBit configuration, CodeQL, Dependabot, demo HTTP and Windows-script CI, and a documented publishing policy.
+
+## Baseline and ownership
+
+- QQQ baseline: 4.1.0-RC.21 (public Maven Central; adopted 2026-11-03, gate pending). The local 4.0.0 middleware does not support Basic sign-in through `manageSession`; RC.20 and later do.
+- Backend agent: qbit main source, unit/integration tests and root POM.
+- Android agent: `qqq-android` source and scanner application module.
+- Toolchain agent: Android SDK installed after explicit user approval of required Google terms.
+- Parent: local demo, cross-component verification and documentation.
+
+## Verification
+
+- Qbit: `./mvnw.cmd -q verify install` passed 11 tests (7 H2 behavioral/security tests and 4 inherited guardrails), with Checkstyle passing.
+- Demo: `../mvnw.cmd -B verify` passed Checkstyle and one real HTTP acceptance scenario. It verifies QQQ login, anonymous and pending-device denial, operator/admin separation, approval, async native process capture, same-event deduplication, SQL provenance, bad/missing device credentials, revocation while a process is open, logout and session replay rejection.
+- HTTP fixtures verify the actual native `composite`/`SCANNER` widget payload. The Android tests deserialize these real metadata/process/init responses.
+- Android: core/mobileapp/scanner JVM suites passed 19 tests, no failures or skips. `lintDebug` and `assembleDebug` passed. Lint has 0 errors and 5 warnings: 3 inherited Navigation custom checks skipped due to API incompatibility and 2 dependency/version notices.
+- Debug APK signature verified. Path: `../../qqq-android/scanner-host/build/outputs/apk/debug/scanner-host-debug.apk`.
+- APK SHA256: `B3E160CE3279C369CEDB425AC6E777A2729CE8A2E430E7D6F46D35C6376F8214`.
+- Android SDK location: `C:/Users/james/AppData/Local/Android/Sdk`; SDK 35, build-tools 34/35, Gradle 8.7.
+- `adb devices -l` returned no attached devices. No physical TC22, camera, or emulator acceptance performed.
+- Repository bootstrap verification: CircleCI setup validated against the private QRun-IO orb with explicit organization scope; Actionlint passed for both workflows. Current shared generator accepted the manifest and selected verification only for seven branch/tag cases. All publication switches are false. Root 11 tests and demo one scenario were rerun successfully after repository metadata changes.
+
+## Handoff and remaining scope
+
+- Follow `TC22-ACCEPTANCE.md` for local credentials, loopback demo, USB forwarding, DataWedge profile and device tests.
+- Runtime demo server is not left running. No user credentials were created outside temporary test databases.
+- First host supports QQQ table-based authentication; other providers show an explicit unsupported message pending configuration.
+- Server enforces approved device plus authenticated user, including async execution. Enable QQQ core permission enforcement when embedding the qbit.
+- Only a current unacknowledged scan is retained in memory for explicit retry. Closing/resetting the app is not an offline queue.
+- The H2 schema is supplied; migrations for other databases and deployment authentication remain host-owned.
+- Pending physical acceptance is tracked in TODO. GitHub bootstrap and hosted checks are separate from artifact release or production deployment; use `CI-CD.md` for the repository settings and release enablement policy.
+
+## Native authentication review follow-up
+The first optional provider-logout compile failure and alternate authentication-source hint gate are corrected in a new frozen source candidate; its isolated focused build is running. Independently, native login does not currently carry/validate the original request nonce against the provider ID token. PKCE code binding is present; no account-takeover exploit is claimed. Explicit provider-bound claim/nonce validation and real-provider acceptance remain required before production authentication closure.
+
+Android nonce/logout working source now passes151 JVM tests, zero lint errors/warnings and APK/native-test compilation. Independent26-file diff review is completed/sealed as c358cde3-b51d-4451-b07d-8d1afe6c4485 with no findings; this is source-scoped and does not establish native/browser/provider execution. Core combined nonce/test corrections remain in progress; initial diagnostic failures stay failed.

docs/history/TODO-through-2026-11-04.md

@@ -0,0 +1,128 @@
+> Historical record, superseded by [current status](../SESSION-STATE.md). Do not treat as current.
+
+# QQQ Mobile Scanners TODO
+
+Current checkpoint (November 4; supersedes historical notes below):
+
+- [x] Scanner PR 12 merged `286e2e0`; full run 3645 succeeded. Central snapshot `0.1.0-20261103.233448-3645` verified anonymously, including all 37 published Java source files.
+- [x] Android PRs 10 and 8 merged into main `0ae2101`; full main lifecycle 3634 succeeded. Shared CI's independent registry readback matched all ten primary library files at `0.1.1-20261103.232145-3634`.
+- [x] Qualify released Printing `1.0.0` with public QQQ RC.21: 198 tests pass, Checkstyle passes, all 94 scanner Java files match reviewed source, and no private QQQ backend artifacts remain in that cohort.
+- [x] Adopt that cohort on local port 57832 while retaining the database/settings. Confirm API health, TC22 Echo setup/Copies 1/Connected and Print Agent Connected and ready after restart.
+- [x] Adopt and review Printing `1.0.0` in both Echo POMs and matching READMEs. Both Maven validate/Checkstyle checks pass; 94 Java inputs match the 198-test qualification.
+- [ ] Document owner: extract reviewed code from host candidate `b6fb238` with provenance, set public dependency pins and standard standalone release wiring, then publish coherent document/files/scripting Maven artifacts including Generation copies. The local standalone directories are not Git repositories and have no workflows; the website image pipeline does not publish these artifacts. Claude access is restored; the dependency owner's actual Claude standalone packaging is active as of November 4, not finished.
+- [x] Outstanding manual acceptance group: user reported on November 4, "i have ran the manual tests - it all works". Recorded as operator acceptance in [TC22 acceptance](../TC22-ACCEPTANCE.md); no duplicate manual checks requested. Separate per-case artifacts were not supplied.
+- [ ] Resolve or explicitly scope the unsupported GS1/ECI/binary scanner profiles before claiming universal barcode reproduction.
+- [ ] Production Android signing/distribution last, as requested. Development publication and demo availability are not production 1.0 acceptance.
+
+Historical checkpoint (November 3):
+
+- [x] Server `45f9cbd` is signed and pushed (Gitea PR 7). Android `f72b90d` is signed and pushed to the existing AGit PR 10 head and Gitea CI 3480 succeeded on it (pull requests #8 and #10 still open; not merged, not released). Updated normal APK installed without clearing data; fresh disposable TC22 Echo run passed 109/109 semantic requests (simulated inputs/printing).
+- [x] Final RC.21 gate PASS: 377 unique tests (Generation 179, Printing bridge 16, scanner 53, demo 8, mobile Record Files 18, Echo 68, Echo demo 35), zero failures/errors/skips, Checkstyle PASS, plus 15 real admin-browser E2E on public RC.21. The earlier MySQL timeouts did not recur (focused 31, full 179). Evidence: `C:/Users/james/.cache/qqq-rc21-copies-gate-076d059d8d0641d9a85874ec64008def/verified-summary.json`.
+- [x] Verified dependency update: five RC.21 POM pins and the record-files POM test fix (BOM-managed Jupiter engine/params, all 6.0.2).
+- [ ] This is public core RC.21 plus qualified owner inputs, not a fully public or released cohort: the 16 Printing-bridge tests still resolve three private `pu507` QQQ libraries through the owner Printing POM, and the other owner qbits remain qualified private inputs. Public reproducible owner inputs, primary source CI, merge and release remain open. No normal-runtime core upgrade was done.
+- [x] Generation copies: signed `aac68907e67906aeef4e0cd687d28bc98b738f8c` on `feature/echo-generation-copies` (base PR 343 head `8f473fa`) in `Website-Backend/third-party-src/qbit-document-generation`; 13 paths, 21/21 manifest match; real PostgreSQL 17 migration passes. [ ] Owner integration and public artifact publication not yet acknowledged.
+- [x] Fresh real Authentik desktop acceptance passes; native harness integrated (8 guards pass). [ ] Native TC22 run needs the temporary CA and PIN (pending); no trust bypass.
+- [ ] Manual physical checks: trigger, AIM, fidelity, label count, photo, GPS, projection. [ ] Signing and distribution last, by user decision.
+
+Previous checkpoint (November 2; historical, superseded by the current checkpoint above):
+
+- [x] Optional Copies per scan defaults to 1, accepts 1–100 and remains server-pinned for every scan/retry. Live on the original local server57832; normal TC22 setup shows 1.
+- [x] Verify 377 unique server/owner tests across the module runs, plus real TC22 ten-stage/116-request semantic acceptance with simulated scans/printing.
+- [x] Adopt mobile-scanners1.5 and actual mobile-record-files1.0/Echo photo composition locally, preserving the original database and printer settings. Photo authorization tests pass.
+- [ ] Confirm physical label count/fidelity and real camera/GPS/projection/provider behavior; operator currently remote. Temporary Authentik CA installation is unconfirmed.
+- [ ] Obtain canonical owner adoption/publication of the verified Generation copies handoff: ten hash-checked files for the Kof22 release repository's `third-party-src/qbit-document-generation` (base verified identical), then a published Generation coherent with Echo's `generation.version`; complete coherent artifacts/CI. Signing/distribution stays last.
+
+Current demo path (November2; supersedes historical runtime/pairing notes below):
+
+- [x] Implement and verify additive mobile1.5 raw-byte/AIM transport, exact retry binding, optional context and preserving H2 migration:135 scanner/demo/Echo tests pass. Android counterpart is implemented; native capture and installed-runtime adoption remain open.
+- [ ] Qualify actual TC22 raw-byte delivery, AIM extraction and decoder settings; finish renderer scanner-mode/extended-symbology integration. Transport support alone does not establish same-symbol reproduction.
+- [x] Fix and adopt the Generation/renderer byte-limit mismatch in both demo launchers; three failures with old wiring, 74 passing library/demo tests with the fix. One clearly synthetic native HTTP event now reaches the actual Windows printer spooler through Echo, with process cancellation verified after failure and acceptance. Paper output, TC22 trigger capture and rescan remain separate open checks.
+- [x] Render the actual published 4x1 document through the real renderer and independently decode its Code128 and leading-zero QR pixels; both preserve exact value/symbology and fit the configured stock. See [evidence and test images](../../examples/echo/demo/docs/ECHO-RENDERER-ACCEPTANCE.md). Physical printing remains unverified.
+- [x] Correct the five inert test-token secret-scan findings using generated fixtures and exact historical fingerprints; local historical/staged scans and all 27 demo tests pass. Current primary CI remains an open gate.
+- [x] Run all real scanner/Echo, files, document and printing qbits in the single local server57832; original accounts work; full demo27 and live forwarded-host checks pass.
+- [x] Connect the existing installed print client to57832 and approve its available ZPL printer through the native QQQ process; no job/default changes.
+- [x] Verify the Android same-origin header (Android `fb3cc5d`, 174 JVM tests) and TC22 sign-in, heartbeat, printer/media/document selection and Cancel/Leave against the strict local host, preserving data.
+- [x] Resolve the earlier 4x6 media report versus loaded 4x1 stock with the Printing owner (101600 x 25400 microns, 300 dpi) and publish the real Echo 4x1 barcode document with its matching immutable revision 1.
+- [ ] Complete one physical Code128 (QQQ-TEST-123456) scan, print and rescan on the TC22, then leading-zero QR. One synthetic HTTP test job reached `SPOOLED`; physical paper output and handheld acceptance are not yet proven.
+- [ ] Finish the existing production-readiness matrix and publication gates; local demo acceptance alone does not complete 1.0. Public coherent artifacts, primary Gitea CI and final signing remain open, with signing last by user decision.
+
+- [x] Implement explicit required INTEGER Document choice with printer/media dependency, server-pinned revision and recoverable errors:45 library/24 composed tests and real TC22 seven-stage/112-request semantic acceptance pass (simulated printing).
+- [x] Roll out the document-selection feature and connect the installed print client to the canonical local server. Real4x1 publication and physical scan/print/rescan remain tracked above.
+
+- [x] Verify the per-extension device-header scope fix (50 base,7 base-demo and composed HTTP regressions), then complete actual native printer enrollment/binding on the local server.
+
+- [x] Publish reviewed Echo retry/receipt fixes as signed Gitea commit912040d;38 library/22 demo tests pass. (Historical: the then-pending Windows approval of printer pairing is superseded; the print client is now connected to the single local server.) Physical output and public CI/artifacts are still open.
+
+- [x] Verify real composed Echo native HTTP pipeline:38example/22demo, retained files, accepted jobs, retry identity and Leave closure; simulated printer/controlled renderer only.
+- [x] Complete native printer connection on the current loaded stock (done on the single local server). Physical scan/print/rescan is tracked above; published dependencies and primary CI remain open.
+
+- [x] Verify effective security-key set comparison and early Collaboration authentication initialization: scanner50/native Record Files18, Checkstyle0 on private coherent cohort.
+- [x] Compose the live Echo renderer, Printing and document publication in the single local server. Physical TC22 print/rescan is tracked above; startup smoke and simulated printing do not close that gate.
+
+- [ ] Deliver Echo example: choose an authorized printer, media and Document (all three required) once, then one scan/render/accepted-print job at a time until leave; reproduce exact value and symbology with worker-owned integer-module fitting and quiet zones. Source, composition, Document choice and native setup are done. Still open: the physical print and rescan above, and full-fidelity work beyond the six admitted printable-ASCII types (EAN/UPC, GS1, AIM identifier and raw payloads), tracked in `examples/echo/README.md`.
+- [ ] Coordinate qualified renderer fit, authorized printer/media discovery, least-privilege submit and retained-print adapter contracts with their owners via shared communications.
+- [x] Verify scanContext 1.3 with root44/demo7/optional18 and Checkstyle: following-step QR/Code 128 branching, legacy omission isolation, trusted attribution and exact retry binding; physical scanner acceptance remains separate.
+
+- [x] Apply the full scoped standards review corrections and verify server39/demo6 with Checkstyle; see [review](../CODING-STANDARDS-REVIEW-2026-11-01.md).
+- [ ] Finish final hosted checks and remaining physical/provider acceptance; source compliance is not production release approval.
+
+- [x] Upgrade the normal local demo to qualified API1.9/mobile1.1 with fresh closed backup, original-data invariants, recovery qualification and live verification of both existing accounts and preserved devices/scans.
+- [x] Implement/review additive extension1.2 whole-device source with explicit Android consent, mode-bound leases and automated controls, preserving1.1 app-content compatibility.
+- [ ] Complete actual Android projection/notification/Home/Stop/lock/rotation/expiry/remote-logout acceptance; normal server remains mobile1.1.
+
+- [x] Qualify the demo BOM import and managed JUnit engine with fresh37 server/five demo tests, exact runtime module/Guava/H2 provenance and all15 single-record/bulk browser cases; see [acceptance evidence](../API19-CONSUMER-ACCEPTANCE.md). The operator runtime remains separate.
+- [x] Preserve legacy timestamp instants in the canonical supplied H2 schema with an explicit UTC migration connection; verify non-UTC file-backed upgrade, unchanged passwords/approval/scans and repeated initialization. The operator upgrade is preserved with UTC; a no-install reactor passes 37 base tests and five demo tests using the freshly built schema.
+- [x] Implement unique short names, editable names/descriptions, additive H2 migration and protected profile editing; qualify the preserving upgrade of the operator database before deployment.
+- [x] Implement separate approval/presence states, online-only fleet query and foreground location with accuracy/age and permission-denied behavior; actual GPS-fix acceptance remains in the release gates.
+- [x] Implement the optional Record Files contract/native capture/association path and qualify the final coherent core32/scanner1a3 consumer cohort: 39 scanner, six demo HTTP, 18 Record Files and 15 browser cases. See [qualification scope](../../integrations/record-files/docs/CORE-32DF-CONSUMER-QUALIFICATION.md); this is not a files-owner full-suite or default-adoption claim.
+- [ ] Qualify coherent immutable/default RF dependencies and actual TC22 camera/gallery permissions and durable authorized association; no normal-runtime adoption is implied.
+
+- [x] Device/session history, live activity and demand-based actual app-screen viewing through native QQQ administration and semantic extension 1.1.
+- [x] Single-record and bulk End Session process with server-enforced invalidation, audit and browser/native E2E coverage.
+- [x] Complete and seal the full server deep static security review of `0926550`; no reportable findings, with external implementation/deployment limitations retained.
+- [ ] Complete final revision/scope reconciliation of historical security reports and remaining external deployment/provider gates. Independent architecture A1–A11 source closure and the filesystem regression correction are recorded; do not relabel partial/historical reports as a new exhaustive scan.
+- [ ] Complete production 1.0 gates in [PRODUCTION-READINESS.md](../PRODUCTION-READINESS.md), including physical acceptance and deployment/release requirements.
+
+- [x] Native qbit device/scan tables and permission boundaries.
+- [x] Authenticated enrollment, approval and revocation.
+- [x] Native Scan Capture process and idempotent scan storage.
+- [x] Android login, device gate, app picker and current trusted EMDK scanner path; prior DataWedge handling is historical.
+- [x] Persistent local demo with separate scanner/admin accounts.
+- [x] Automated HTTP acceptance: pending denial, approval, capture, duplicate retry, revoke denial.
+- [x] Android build and meaningful unit checks.
+- [x] Standard repository files, current shared CircleCI profile, demo/Windows CI, CodeQL and Dependabot.
+- [x] Validate CircleCI, workflow syntax and verification-only publication policy locally.
+- [x] Connect hosted CI and confirm actual successful status checks.
+- [x] Define branch protection policy from observed hosted checks; enforcement lives in GitHub settings.
+- [x] Server-configured customer branding for one shared APK.
+- [x] Public status endpoint for the Android connection footer and diagnostics.
+- [x] Android emulator installed; native UI tests passed.
+- [x] Single-record and bulk approval/revocation with confirmation, stable selection and visible results.
+- [x] HTTP acceptance for checked rows, filtered bulk selection, persisted results and unselected-device isolation.
+- [x] Browser E2E acceptance for all administration processes from record and bulk menus (six scenarios passed).
+- [x] Scanner-host native E2E acceptance against an isolated real demo server.
+- [x] Register enrollment, branding and status as the documented mobile-scanners 1.0.0 semantic UI API extension; generate OpenAPI and check the versioned contract baseline.
+- [x] Verify extension discovery, real HTTP payload schemas, standard errors, public stale-credential behavior and rejection of legacy routes (root 23 tests and demo HTTP verification passed).
+- [x] Coordinate Android core/extension compatibility checks before login and native semantic process/form updates.
+- [x] Register the Android client channel while preserving host channel policies; verify the real HTTP suite sends Android-channel requests successfully.
+- [x] Rerun all six browser E2E scenarios against the migrated server (passed in 2.9 minutes).
+- [x] Verify the migrated client/server pair's incompatible-version, missing-extension, missing-channel, baseline scan and additive-metadata native scenarios with the OpenAPI request audit.
+- [x] Verify Android's 53 JVM tests, six shared native UI tests, lint and debug/E2E APK builds.
+- [x] Complete native approval/revocation/cancellation forms after the completion-state fix (255.917 seconds; all 31 requests matched to 13 published operations).
+- [x] Publish server semantic API migration commit `7dd02b8` and verify its hosted CircleCI, CodeQL, Windows helper and demo HTTP/browser checks all pass.
+- [ ] Finish current EMDK physical acceptance: Code128 positive controls pass; current QR, lifecycle/ownership and failure/retry/leave matrix remain open.
+- [x] Identify the physical TC22, install the debug app, sign in and enroll through USB forwarding.
+- [x] Approve the TC22 through its browser record Actions menu and open its native app catalog and Scan Capture process; preserve login across APK update.
+- [x] Configure the TC22 DataWedge profile with explicit package/signature delivery; verify two deliberate Code128 hardware captures persist with matching metadata.
+- [x] Verify physical QR delivery and exact preservation of leading zeroes in `001234567890`, with matching persisted scan metadata.
+- [ ] Finish physical connection-loss/retry and revocation-denial acceptance alongside the requested device/session controls.
+- [x] TC22 install and DataWedge acceptance guide written and updated with observed results.
+
+Future scope (not version one): offline queue, camera-based barcode decoding, kiosk/MDM provisioning, broader native screen coverage, fleet rollout. Optional record-photo capture is implemented; its remaining qualification is tracked above.
+
+- [ ] Complete the optional semantic API1.10 provider-logout capability and client AppAuth end-session handling; keep local cleanup reliable on provider failure, qualify real A-to-B handoff, and apply the user's pending sign-out policy. Existing prompt-only retained-SSO handoff is not accepted.
+
+- [ ] Validate native OIDC ID-token claims and original request nonce before creating the QQQ session. Review confirmed request continuity and S256 PKCE exist, but expected nonce is not currently carried to the server exchange. Add explicit semantic capability/wire compatibility and rejection tests; retain real-provider nonce acceptance as pending.
+
+- [x] Retain unchanged verified capture session identity with explicit current authority/reference checks;49root+7demo tests andCheckstylepass.
+- [ ] Qualify exact ownerRF18 upload/finalize using the frozen identity patch before final coherent host adoption.

examples/echo/README.md

@@ -4,11 +4,14 @@ Echo is an optional QQQ example application, using the shared Android scanner ho
 
 The source implements ordinary QQQ metadata and processes; no Echo-specific Android screen, business endpoint, barcode encoder or print queue is added. There is deliberately no fabricated printer, hardcoded stock, administrative-permission shortcut or in-process renderer fallback.
 
-**Status.** The owner adapters and host composition are source-complete and pass `verify` (Checkstyle clean) against the qualified owner inputs described under Build and acceptance, and the [runnable demo](#runnable-demo) passes its tests, including a complete composed acceptance (current counts and progress: [session state](../../docs/SESSION-STATE.md)): an authenticated approved scanner, two scans, two retained originals and two accepted Printing jobs on one printer, an idempotent retry and leaving. That automated acceptance uses a controlled synthetic renderer and a simulated Printing queue.
+## At a glance
 
-The composed demo runs as one local server with a real Printing client, printer and 4x1 media, and a published Echo barcode document. A TC22 completed setup against it (printer, media and document, then Next) and Cancel then Leave. A separate, explicitly synthetic native HTTP event now completes the real render/retain/print pipeline: one `ECHO-HTTP-TEST-001` Code128 job reached `SPOOLED` with a Windows spooler job assigned, and its Echo process closed successfully. This is printer delivery evidence, not physical trigger, paper output or rescan confirmation. See the [delivery receipt](demo/docs/echo-delivery-acceptance.json). Public Maven publication and full production acceptance remain open.
-
-The actual renderer's Code128 and leading-zero QR outputs now pass independent pixel decoding and 4x1 stock/fit checks. See the [rendering evidence and scannable test images](demo/docs/ECHO-RENDERER-ACCEPTANCE.md). This no-print check does not replace physical acceptance.
+- **Flow.** Choose a printer, its paper/label size and a published Document once; then every scan renders the same value and symbology and prints one job, until you leave. **Copies per scan** is optional (default 1, range 1–100) and fixed for the run.
+- **Where it runs.** The maintained local server composes Echo with Collaboration/Record Files, Document Generation and Printing on public QQQ `4.1.0-RC.21` and released Printing `1.0.0` (UI API 1.10, `mobile-scanners` 1.5, `printing` 2.3). Start it with the [runnable demo](demo/README.md); [local demo](../../docs/LOCAL-DEMO.md) explains how it differs from the basic Scan Capture demo.
+- **Verified.** In the current 198-test cohort Echo has 68 tests and the composed demo 35, with Checkstyle clean ([session state](../../docs/SESSION-STATE.md)). The automated composed acceptance (an approved scanner, two scans, two retained originals, two accepted jobs, an idempotent retry, leaving) uses a controlled synthetic renderer and a simulated Printing queue.
+- **Rendering evidence.** The real renderer's Code128 and leading-zero QR outputs pass independent pixel decoding and stock/fit checks ([evidence and test images](demo/docs/ECHO-RENDERER-ACCEPTANCE.md)). A separate synthetic HTTP event reached a real printer spooler ([delivery receipt](demo/docs/echo-delivery-acceptance.json)).
+- **Physical acceptance.** The TC22 trigger, paper output and rescan checks were reported by the operator as passing on November 4, as a group report without per-case artifacts. A queue acknowledgment still means *queued*, not confirmed paper.
+- **Not claimed.** Production readiness, signed distribution, public Maven coordinates for the document owner's qbits, or universal barcode fidelity ([limits](#fidelity-and-limits)).
 
 ## Host composition
 
@@ -28,9 +31,21 @@ Setup asks **Copies per scan**: an optional ordinary integer form field, default
 
 `EchoDocumentGenerator` builds `DocumentGenerationService.Request(..., mediaProfile, copies)` with the run's pinned count, so Generation binds it to the `echo:<scanId>` key and its printing bridge submits one job with `options.copies`; the accepted-print lookup compares the committed count with the pinned one before Echo adopts a job. This needs the Generation copies cohort (`GenerationPorts.PrintRequest`/`Request` with the appended `copies`, the request-table `copies` migration `20261102-print-copies-h2.sql`, and a Printing owner that honors `options.copies`); an owner without `supportsCopies()` refuses a count above 1 before any row, render or submit. Physical copy counts are not verified.
 
-## Fidelity and retries
+## Fidelity and limits
 
-The first explicit mapping covers CODE128, QRCODE, CODE39, Data Matrix, PDF417 and Aztec scanner identifiers and their documented legacy label aliases. Leading zeros are never parsed as numbers. EAN13/EAN8/UPCA/UPCE0 are admitted only with the scanner's AIM identifier (`]E0`, EAN-8 `]E4`), a full-length value of the exact length with a valid GS1 check digit (UPC-E number system 0 only), and a document published with `EchoTemplatePublisher.publishScannerFidelity`. That separate, clearly named **scanner-fidelity** document passes the recorded scanner label and AIM identifier (`echoScan.symbology`, new nullable `echoScan.aimIdentifier`) to the renderer's scanner mode, which verifies them again and converts the value. It requires an AIM identifier on every scan, so the original plain document stays the choice for older scanners and servers; an EAN/UPC scan on a plain document, or a scan without AIM on a scanner-fidelity document, is refused before any print and the operator leaves Echo to choose the other document. The AIM column is an additive, nullable migration in `echo-h2.sql` (other databases need the equivalent); a retry is bound to the stored AIM. UNKNOWN, manual input, unsupported variants and control/binary/GS1 payloads are refused until their exact metadata/encoder profile is qualified. When the canonical scan context carries the optional mobile-scanners 1.5 evidence, Echo checks it before admission: an `aimIdentifier` other than the renderer's plain-mode identifier for that type (for example `]C1`, `]Q3`, `]A4`) is refused as a GS1/ECI/structured mode, and `rawDataBase64` must decode to exactly the ASCII bytes of the display value. Absent evidence (legacy 1.4 servers, older clients, or a Zebra read where the host did not confirm its AIM output profile by configuration read-back) is admitted as before and proves nothing, and physical AIM output on the handheld is not yet qualified; no fidelity is inferred from the display string. No symbology is inferred from value or substituted with QR/Code128.
+| Input | Behavior |
+| --- | --- |
+| CODE128, QRCODE, CODE39, Data Matrix, PDF417, Aztec (printable ASCII) | Admitted on the plain document. |
+| EAN13, EAN8, UPCA, UPCE0 | Admitted only with the scanner's AIM identifier, an exact-length value with a valid check digit (UPC-E number system 0 only) and a document published with `publishScannerFidelity`; otherwise refused before any print. |
+| GS1-128 (`]C1`) | Bounded profile below; requires matching raw-byte evidence and a separate GS1 document with printed HRI. |
+| Other GS1, ECI and structured-append modes (for example `]Q3`, `]A4`) | Refused; no qualified profile. |
+| Control, binary or non-ASCII payloads | Refused. |
+| UNKNOWN symbology or manual entry | Refused. No symbology is inferred from the value or substituted with QR/Code128. |
+| Raw bytes (`rawDataBase64`, mobile-scanners 1.5) | Must decode to exactly the ASCII bytes of the displayed value, else refused. Required for GS1-128; absent evidence remains admitted for legacy plain profiles and proves nothing. |
+
+Independent decoding (ZXing on the rendered raster) is recorded only for Code128 `QQQ-TEST-123456` and QR `001234567890` on 4 x 1 in stock at 300 dpi. Hardware AIM output and physical copy counts are covered by the operator's accepted group report (not reopened), but have no separate instrumented evidence; no exact-AIM or all-symbology claim is made.
+
+The first explicit mapping covers CODE128, QRCODE, CODE39, Data Matrix, PDF417 and Aztec scanner identifiers and their documented legacy label aliases. Leading zeros are never parsed as numbers. EAN13/EAN8/UPCA/UPCE0 are admitted only with the scanner's AIM identifier (`]E0`, EAN-8 `]E4`), a full-length value of the exact length with a valid GS1 check digit (UPC-E number system 0 only), and a document published with `EchoTemplatePublisher.publishScannerFidelity`. That separate, clearly named **scanner-fidelity** document passes the recorded scanner label and AIM identifier (`echoScan.symbology`, new nullable `echoScan.aimIdentifier`) to the renderer's scanner mode, which verifies them again and converts the value. It requires an AIM identifier on every scan, so the original plain document stays the choice for older scanners and servers; an EAN/UPC scan on a plain document, or a scan without AIM on a scanner-fidelity document, is refused before any print and the operator leaves Echo to choose the other document. The AIM column is an additive, nullable migration in `echo-h2.sql` (other databases need the equivalent); a retry is bound to the stored AIM. UNKNOWN, manual input, unsupported variants and control/binary payloads outside the GS1-128 profile below are refused until their exact metadata/encoder profile is qualified. When the canonical scan context carries the optional mobile-scanners 1.5 evidence, Echo checks it before admission: outside the GS1-128 profile, an `aimIdentifier` other than the renderer's plain-mode identifier for that type (for example `]Q3`, `]A4`) is refused as a GS1/ECI/structured mode, and `rawDataBase64` must decode to exactly the ASCII bytes of the display value. Absent evidence (legacy 1.4 servers, older clients, or a Zebra read where the host did not confirm its AIM output profile by configuration read-back) is admitted as before and proves nothing, and physical AIM output on the handheld is not yet qualified; no fidelity is inferred from the display string. No symbology is inferred from value or substituted with QR/Code128.
 
 Each canonical mobile scan has one durable `echoScan` source with the same ID and a stable `echo:<scanId>` generation request key across every run. A duplicate accepted event in the same run returns its existing job; moving that event into another run is rejected. A deliberate new trigger event with the same value is a new print intent. A changed value/type/source/timestamp cannot reuse the event. An uncertain/crashed call never automatically renders or prints again: recovery requires read-only exact owner acceptance evidence; absent/unavailable evidence remains visibly unconfirmed and the user may leave. Independent decoding and physical scanner/printer acceptance remain mandatory for any claimed barcode profile.
 
@@ -44,15 +59,17 @@ From the repository root, use Java 21 and the included wrapper:
 
 On Windows, run `mvnw.cmd -f examples/echo/pom.xml verify` from the repository root. From `examples/echo`, use `../../mvnw -f pom.xml verify` (Windows: `..\..\mvnw.cmd -f pom.xml verify`). Both forms use the checked-in wrapper; Checkstyle and resource paths resolve from the module directory.
 
-This optional module is outside the root lifecycle. The POM's defaults are `qqq.version` 4.1.0-RC.21 (public), `mobile.version` and `generation.version` 0.1.0-SNAPSHOT, and `printing.version` 0.4.0-SNAPSHOT. The owner qbits (Generation and bridges, Printing, Collaboration, Record Files) are still qualified private inputs, not a fully public or released dependency cohort, so these snapshot defaults alone may not resolve or match what was verified. Copies per scan also needs the Generation copies change described above. Use a dedicated Maven repository and one coherent owner cohort; never install cross-chat snapshots over the shared cache. The source requires the narrow protected-process-identity API and current `MobileScannerActions.capture(input, appName)` API. These private artifacts are not published to a public Maven repository and are not a production handoff. The primary forge is Gitea; GitHub is a shadow/archive.
+This optional module is outside the root lifecycle. The POM's defaults are `qqq.version` 4.1.0-RC.21 (public), `printing.version` 1.0.0 (released Printing, qualified with public RC.21), and `mobile.version` and `generation.version` 0.1.0-SNAPSHOT. The other owner qbits (Generation and bridges, Collaboration, Record Files, Scripting) are still qualified owner inputs, not a public or released dependency cohort, so their snapshot defaults alone may not resolve or match what was verified. Copies per scan also needs the Generation copies change described above. Use a dedicated Maven repository and one coherent owner cohort; never install cross-chat snapshots over the shared cache. When the owner publishes public versions, adopt them in a reviewed dependency change; until then do not guess coordinates. The source requires the narrow protected-process-identity API and the current `MobileScannerActions.capture(input, appName)` API. The primary forge is Gitea; GitHub is a shadow/archive.
 
 Tests: core and HTTP-fixture tests (real QQQ process state, H2 persistence and the mobile QBit's approval and binding, with synthetic destination, layout and queue fixtures) and adapter tests (controlled owner facades for exact pins, receipts, lookup, media filtering, the published scene geometry and the absent-deployment refusals). They qualify orchestration, event identity, permission boundaries and adapter mapping, not render output or physical printing. The adapter tests do not run the renderer worker.
 
 ## Runnable demo
 
-[`demo/`](demo/README.md) is a separate optional module that composes the real owners into a startable server (tested, Checkstyle clean). Its production `EchoDemo` keeps the owner's cold bridge, which defaults to the `runsc` Docker runtime and fails closed on Windows Docker Desktop (`runc`). `TrustedLocalEchoDemo` is the explicit developer launcher over the renderer owner's public trusted-local factory (owner tests pass; the demo copies no transport) and is not a production sandbox qualification. An earlier local run on an ephemeral loopback port (November 1, historical) had no printer or template. A real combined setup now exists: one local server runs Echo, Record Files, Document Generation and Printing with a real Printing client, printer, 4x1 media and a published Echo barcode document, and a TC22 completes setup against it. Physical output remains unproven. Operator prerequisites, from its README: a Printing tenant and administration token, a Windows printing agent that reports printer media, an approved scanner enrolled through the mobile flow, published Echo-compatible ZPL templates for the reported media, chosen by the operator during process setup, and Record Files' generated-file release switch.
+[`demo/`](demo/README.md) is a separate optional module that composes the real owners into a startable server (tested, Checkstyle clean). Its production `EchoDemo` keeps the owner's cold bridge, which defaults to the `runsc` Docker runtime and fails closed on Windows Docker Desktop (`runc`). `TrustedLocalEchoDemo` is the explicit developer launcher over the renderer owner's public trusted-local factory (the demo copies no transport) and is not a production sandbox qualification. Operator prerequisites, from its README: a Printing tenant and administration token, a Windows printing agent that reports printer media, an approved scanner enrolled through the mobile flow, published Echo-compatible ZPL templates for the reported media (chosen by the operator during process setup), and Record Files' generated-file release switch. The demo README's first section says which launcher to use; the basic Scan Capture demo is a different, smaller server ([local demo](../../docs/LOCAL-DEMO.md)).
 
-What remains before any print claim: a TC22 scan against the real server that produces a physical print, independent decode of the output and a rescan of Code 128 and leading-zero QR labels. Beyond that: full AIM, EAN/UPC, GS1 and raw fidelity (the six admitted types are printable ASCII only, and the rest fail explicitly as unsupported), then public immutable SDK publication, Gitea CI and distribution, and signing. The source pull request is on Gitea (PR 7); earlier GitHub references are historical.
+## Release limits
+
+Echo is an example, not a released product. Source and development publication are done on Gitea (scanner `develop` snapshot from run 3645; Android `main` `0ae2101`, run 3634). Still open: public Generation/bridges/Record Files/Scripting artifacts from their owner, signed-build HTTPS device qualification and distribution (the signed Android APK and channel already exist locally), and any barcode profile beyond the [limits above](#fidelity-and-limits). Earlier GitHub references are historical.
 
 ## License packaging
 
@@ -67,3 +84,11 @@ Launch its test classpath with one unused loopback port argument and private env
 The printer/media choices are `fixture-printer` / `fixture-4x6`, labeled “Simulated printer” / “Simulated 4 x 6 in — 300 dpi”. Standard native queries of `echoScan` and test-only `echoFixtureRun` use the scanner session and approved device credentials, retaining actor locks. The HTTP smoke covers login, real enrollment/admin approval, metadata, setup, two symbologies, same-event retry, queued receipts, row inspection and cancellation. Android device acceptance remains a separate test; none of these fixture results qualify physical output.
 
 Retained Echo source reads use a separate read-only permission: the current authenticated actor must still have `echo.use`, and native actor row locks restrict results to that actor. Desktop source reads after leaving Echo do not reconstruct a scanner session or grant capture authority. Echo app/process/widget/capture operations still require the currently approved device. Direct source-table writes are denied. Accepted print delivery/retry also requires the printing owner's reviewed original-actor source-reauthorization policy; this table read rule alone does not qualify delayed byte release.
+
+### GS1-128 duplication profile
+
+Choose a separate document created with `EchoTemplatePublisher.publishGs1`; existing plain documents cannot print GS1 scans. This profile requires AIM `]C1`, a supported Code128/GS1 scanner label, and raw bytes matching the original payload (optionally including its AIM prefix). It preserves the original scan and derives `rendererValue` and `humanReadable` in additive nullable columns. Apply the H2 additions in `echo-h2.sql` before use; other database owners must supply equivalent migrations.
+
+Supported AIs: fixed-length `00`, `01`, `02`, `11`, `12`, `13`, `15`, `16`, `17`, `20`; variable-length `10`, `21`, `30`, `37`. ASCII group separators terminate variable fields; boundaries are never guessed. The bounded profile admits at most 48 payload characters and refuses unknown AIs and unsupported controls. Example: `01095011015300031120101421TEST000123` prints `(01)09501101530003(11)201014(21)TEST000123` below a GS1-128 barcode. The renderer checks the canonical data independently.
+
+Two synthetic 4-by-1-inch, 300-dpi outputs passed independent decoding with exact GS1 data, matching HRI and non-overlapping geometry. Native acceptance is in progress; physical print/rescan and suitability for the operator's actual media remain unverified.

examples/echo/demo/CLAUDE-HANDOFF.md

@@ -1,5 +1,7 @@
 # Echo runnable demo checkpoint
 
+> Historical checkpoint (2026-11-02). Its test counts and "Remaining" list are superseded: see the [demo README](README.md) and [session state](../../../docs/SESSION-STATE.md) for current status.
+
 Date: 2026-11-02. Scope: `examples/echo/demo/**`. Source checkpoint, not a release.
 
 ## Verified status
@@ -14,7 +16,7 @@ Date: 2026-11-02. Scope: `examples/echo/demo/**`. Source checkpoint, not a relea
 
 `EchoDemo` extends `MobileScannersDemo` (database, `scanner`/`admin` accounts, native server) and composes Collaboration, Record Files, Printing, Document Generation and `EchoHost.install` from their public classes on one private H2 file (`WRITE_DELAY=0`). Composition runs under a scoped system context that is restored afterwards, then `QInstanceEnricher` enriches the instance, because the server only validates and the enricher registers Collaboration's record-feature permissions. `LocalFilesystemAttachmentStorage` implements the attachment owner's storage SPI over `PrivateObjectFiles` (hashed keys, temp-file-then-link, no overwrite) and adds no policy. `TrustedLocalEchoDemo` is the explicit developer launcher; the production `EchoDemo` default fails closed. See `README.md` for build, run and environment.
 
-Authentication is the existing demo password/session module plus exact grants. `scanner`: `echo.use`, `printing_operator`, `document-generation.view|generate|print`, `record-files.view|manage`, `echoScan.attach` and the `printing_tenant` row key (replaced, never appended, on each validation); then `CollaborationSecurity.applyToSession`. `admin` additionally: `printing_admin`, `document-generation.configure|publish`. No Record Files release/configure/audit for anyone.
+Authentication is the existing demo password/session module plus exact grants. `scanner`: `echo.use`, `printing_operator`, `document-generation.view|generate|print`, `record-files.view|manage`, `echoScan.attach` and the `printing_tenant` row key (replaced, never appended, on each validation); then `CollaborationSecurity.applyToSession`. `admin` additionally: `printing_admin`, `document-generation.configure|publish`, `record-files.release` (so approved captured photos release through the normal audited process). The scanner never gets release; no Record Files configure/review/audit for anyone.
 
 ## Test isolation
 

examples/echo/demo/README.md

@@ -2,7 +2,20 @@
 
 Optional module (`qqq-echo-demo`) that turns the Echo example into a server you can start. The library module `examples/echo` does not depend on it. It reuses `MobileScannersDemo` (database, `scanner`/`admin` accounts, native server) and adds Collaboration, Record Files, Printing, Document Generation and Echo from their public production classes. Nothing is simulated: the renderer is the owner's cold Docker bridge, output is retained by Record Files, and printing is Printing's own service. The server binds `127.0.0.1` only.
 
-Status: the demo and Echo library tests pass with Checkstyle clean (current counts and progress: [session state](../../../docs/SESSION-STATE.md); the qqq version default is 4.1.0-RC.21 while owner qbits remain qualified private inputs). The composed acceptance test passes: an authenticated approved scanner, two scans, two retained originals and two accepted Printing jobs on one printer, an idempotent retry, and leaving closes the run. It uses a controlled synthetic renderer and a simulated Printing queue, so it is **not physical output**. The production `EchoDemo` default is unchanged and fails closed (the owner's cold bridge needs `runsc`; Windows Docker Desktop reports `runc`). A local run prints its URL in the startup log (`ECHO_DEMO_READY port=<port>`, then `http://127.0.0.1:<port>`; the port is chosen per run). Not production-ready and not a public SDK release. See `CLAUDE-HANDOFF.md` for status and what remains.
+## Which launcher?
+
+| Goal | Use |
+| --- | --- |
+| Try login, device approval and basic barcode capture only | The basic Scan Capture demo, `scripts/Start-Demo.ps1` ([local demo](../../../docs/LOCAL-DEMO.md)). Not this module. |
+| Run the full scan, render and print flow on a developer machine | `TrustedLocalEchoDemo` (below). |
+| Production-style cold renderer sandbox | `EchoDemo`; it fails closed unless the owner's `runsc` runtime is available. |
+| Keep using the maintained local server's existing database | Either launcher with `ECHO_EXISTING_DATABASE` set ([adoption notes](docs/LOCAL-SERVER-ADOPTION.md)). Only this mode accepts host port `57832`. |
+
+There is **no default port**: pass one as the argument or set `ECHO_DEMO_PORT`. A local run prints its URL in the startup log (`ECHO_DEMO_READY port=<port>`, then `http://127.0.0.1:<port>`).
+
+## Status
+
+The demo and Echo library tests pass with Checkstyle clean (counts change per run; see [session state](../../../docs/SESSION-STATE.md) for the latest reported results). The QQQ default is 4.1.0-RC.21 and Printing defaults to released 1.0.0; the other owner qbits remain qualified owner inputs until their public release. The composed acceptance test passes with a controlled synthetic renderer and a simulated Printing queue, so it is **not physical output**. TC22 physical acceptance is separately operator-reported as passing (November 4, group report). Not production-ready and not a public SDK release. The dated [`CLAUDE-HANDOFF.md`](CLAUDE-HANDOFF.md) is a historical checkpoint.
 
 ## Trusted local development launcher
 
@@ -44,7 +57,7 @@ Set the configuration below in the environment (never on the command line), then
 java -cp "examples\echo\demo\target\classes;$(Get-Content examples\echo\demo\target\classpath.txt)" com.kingsrook.examples.echo.demo.EchoDemo 48123
 ```
 
-The optional argument is the port; otherwise `ECHO_DEMO_PORT`. There is no default port. Ports 1024-65535 are accepted except the protected local runtimes listed in `EchoDemoSettings`. `mvnw.cmd -f examples\echo\demo\pom.xml exec:java` is equivalent when the environment is set.
+The optional argument is the port; otherwise `ECHO_DEMO_PORT`. There is no default port, and the sign-in passwords are never given on the command line (see below; to copy an existing demo account's password without displaying it, use `scripts/Copy-DemoPassword.ps1`). Ports 1024-65535 are accepted except the protected local runtimes listed in `EchoDemoSettings`. `mvnw.cmd -f examples\echo\demo\pom.xml exec:java` is equivalent when the environment is set.
 
 ## Configuration (environment only)
 
@@ -75,7 +88,7 @@ The legacy `ECHO_TEMPLATE_ID`, `ECHO_TEMPLATE_MEDIA_ID` and `ECHO_TEMPLATE_MEDIA
 
 ## Accounts and permissions
 
-`scanner` receives exactly: `echo.use`, `printing_operator`, `document-generation.view|generate|print`, `record-files.view|manage` (manage is the owner's intake permission) and the `printing_tenant` row key. `admin` receives the same plus `printing_admin` (Printing's native pairing/approval/setup processes) and `document-generation.configure|publish` to prepare templates. The scanner never gets these, and nobody gets Record Files release/configure/audit. Scans still need an enrolled and approved device, so use the existing mobile enrollment flow.
+`scanner` receives exactly: `echo.use`, `printing_operator`, `document-generation.view|generate|print`, `record-files.view|manage` (manage is the owner's intake permission), `.attach` on `echoScan` and the three mobile test-data tables (`testOrder`, `testOrderItem`, `testOrderEvent`) and the `printing_tenant` row key. `admin` receives the same plus `printing_admin` (Printing's native pairing/approval/setup processes) and `document-generation.configure|publish` to prepare templates. The scanner never gets these. Only `admin` also receives `record-files.release`, so approved captured photos can be released through the normal audited process; nobody gets Record Files configure/review/audit. Scans still need an enrolled and approved device, so use the existing mobile enrollment flow.
 
 ## Operator order
 
@@ -88,10 +101,11 @@ The legacy `ECHO_TEMPLATE_ID`, `ECHO_TEMPLATE_MEDIA_ID` and `ECHO_TEMPLATE_MEDIA
 The host also installs the existing `qbit-mobile-scanners-record-files` integration, so an approved scanner can attach photos to one of its own retained Echo scans. Nothing new is served: Record Files' registered, versioned `record-files` upload API (`/qqq/v1/qbit/record-files/...`) and the independently versioned `mobile-record-files` widget vocabulary are advertised in `/qqq/v1/version`, behind the same native auth and device guards.
 
 - **Process:** `echoScanPhotos` ("Echo scan photos"), listed in the Echo app. It requires `echo.use`, `echoScan.attach` and a verified approved device. The first step lists the actor's own scans (the table's record security lock decides; label is the barcode and type, never the record id). The server then re-reads the chosen scan through the collaboration owner's visibility and `attach` checks and builds the `RECORD_FILES_CAPTURE` widget from the record that check returned, on the fixed `echoScan` table. The client never supplies a table or record reference, and rendering the widget directly names no parent. Record Files authorizes the parent again on every upload operation.
-- **Policy:** JPEG/PNG only, 20 MiB per file, up to four files, 256 KiB chunks, private staging under the demo's `objects` directory (separate staging namespace). Retained originals follow the existing Record Files quarantine setting.
-- **Needs a real scan first:** the list is empty until the scanner has Echo scans. Nothing is seeded outside this module's tests.
+- **Policy:** JPEG/PNG only, 20 MiB per file, up to four files, 256 KiB chunks, private staging under the demo's `objects` directory (separate staging namespace). The Echo host sets Record Files' `quarantineCapturedFiles=false` (leaving `quarantineNewFiles=true` and the generated-file setting unchanged), so a JPEG/PNG saved from this process by a device that `MobileCaptureIdentityProvider` currently verifies as approved is registered `AVAILABLE` and can be previewed immediately. The same upload API on any other host, and every upload, import or attachment-panel file here, stay `QUARANTINED` until released. This is a host trust decision, not a content scan or human review; no release event is written and review status is unchanged. **Requires a Record Files version that contains `RecordFilesQBitConfig.withQuarantineCapturedFiles(Boolean)`. The owner's change is an open, unmerged PR; this checkout's dependency pin has not been updated and builds only against the local owner input until a public version is pinned.** Files already uploaded stay `QUARANTINED` until released through the normal `record_files_file_record_files_release` process.
+- **Test-data records:** the host also registers the test orders, items and events as Record Files parents, so a scanner can add photos from a record's Actions menu. The same approved-device policy and authorization re-check apply. Release of any quarantined file is admin-only (`record-files.release`).
+- **Needs a real scan first (for the `echoScanPhotos` process):** the list is empty until the scanner has Echo scans. Nothing is seeded outside this module's tests.
 - **Existing databases:** the Record Files upload tables are added by the same tolerated-reapply schema step; plan the migration for a database from another version.
-- **Not claimed:** no real photo upload, native capture or device run has been verified here. That needs the Android host against this server.
+- **Not claimed:** one synthetic gallery PNG uploaded from the signed MC9400 app was observed `AVAILABLE` with matching parent, type, size and SHA-256 (see [session state](../../../docs/SESSION-STATE.md)). No camera-hardware capture and no full preview of that photo are claimed.
 
 ## Existing databases
 

examples/echo/demo/docs/LOCAL-SERVER-ADOPTION.md

@@ -1,10 +1,12 @@
 # Running all qbits in the local test server
 
+> The combined server is the maintained local server (host port 57832 in this mode only; public QQQ RC.21, Printing 1.0.0; API 1.10, mobile 1.5, printing 2.3). The "now responds ... Mobile Scanners 1.4" sentence at the end is a November 2 note; see [session state](../../../../docs/SESSION-STATE.md) for the current versions.
+
 One server, one database: the existing `MobileScannersDemo` data file is opened in place by the combined `EchoDemo` (Mobile Scanners/Echo, Collaboration/Record Files, Document Generation, Printing). No second server, network bridge or reset.
 
 ## Environment contract (public values only; no secrets are read from or written to this file)
 Use the existing `TrustedLocalEchoDemo` (or `EchoDemo`) launcher plus the normal Echo variables, and add:
-- `ECHO_EXISTING_DATABASE` - absolute path of the existing H2 file, ending `.mv.db` (for the normal server: `R:\Git.Local\QRunIO\qbit-mobile-scanners\demo\data\mobile.mv.db`). Setting it is the explicit existing-local-server mode.
+- `ECHO_EXISTING_DATABASE` - absolute path of the existing H2 file, ending `.mv.db` (for the basic demo's database: `demo/data/mobile.mv.db` under your checkout, as an absolute path). Setting it is the explicit existing-local-server mode.
 - `ECHO_DEMO_PORT` - `57832` is accepted only in this mode. Every other protected port (including peer Printing 18081) is still refused, and fresh/private demos still refuse 57832.
 - `ECHO_DEMO_ROOT` - existing absolute directory for Record Files objects and renderer state (`objects`, `renderer-state`); the database is NOT taken from it in this mode.
 - Unchanged: `ECHO_PRINTING_TENANT`, `ECHO_PRINTING_ADMIN_TOKEN` (32+ chars), `ECHO_RELEASE_GENERATED_FILES`, renderer variables (`ECHO_LOCAL_RENDERER*` or `ECHO_RENDERER_*`), `MOBILE_BRAND_*`.

examples/echo/demo/pom.xml

@@ -16,15 +16,15 @@
    <properties>
       <maven.compiler.release>21</maven.compiler.release>
       <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-      <qqq.version>4.1.0-RC.21</qqq.version>
+      <qqq.version>4.1.0-RC.26</qqq.version>
       <mobile.version>0.1.0-SNAPSHOT</mobile.version>
       <echo.version>0.1.0-SNAPSHOT</echo.version>
-      <generation.version>0.1.0-SNAPSHOT</generation.version>
+      <generation.version>1.1.0-RC.1</generation.version>
       <renderer.version>${generation.version}</renderer.version>
-      <printing.version>0.4.0-SNAPSHOT</printing.version>
-      <recordfiles.version>0.1.0-SNAPSHOT</recordfiles.version>
+      <printing.version>1.2.0-RC.1</printing.version>
+      <recordfiles.version>0.4.0-RC.1</recordfiles.version>
       <mobilerecordfiles.version>0.1.0-SNAPSHOT</mobilerecordfiles.version>
-      <collaboration.version>0.1.0-record-files-SNAPSHOT</collaboration.version>
+      <collaboration.version>1.2.0-RC.1</collaboration.version>
    </properties>
    <dependencyManagement><dependencies>
       <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-bom-pom</artifactId><version>${qqq.version}</version><type>pom</type><scope>import</scope></dependency>
@@ -40,14 +40,14 @@
       <dependency><groupId>com.kingsrook.qbits</groupId><artifactId>qbit-mobile-scanners-record-files</artifactId><version>${mobilerecordfiles.version}</version></dependency>
       <dependency><groupId>com.kingsrook.qbits</groupId><artifactId>qbit-collaboration</artifactId><version>${collaboration.version}</version></dependency>
       <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-backend-module-rdbms</artifactId></dependency>
-      <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-frontend-next</artifactId><version>1.0.0-RC.35</version></dependency>
+      <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-frontend-next</artifactId><version>1.0.0-RC.38</version></dependency>
       <dependency><groupId>com.h2database</groupId><artifactId>h2</artifactId><version>2.2.224</version></dependency>
       <dependency><groupId>org.junit.jupiter</groupId><artifactId>junit-jupiter-api</artifactId><version>6.0.2</version><scope>test</scope></dependency>
       <dependency><groupId>org.junit.jupiter</groupId><artifactId>junit-jupiter-engine</artifactId><version>6.0.2</version><scope>test</scope></dependency>
    </dependencies>
    <build><plugins>
       <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-compiler-plugin</artifactId><version>3.13.0</version><configuration><showWarnings>true</showWarnings><failOnWarning>true</failOnWarning><proc>none</proc><compilerArgs><arg>-Xlint:deprecation</arg><arg>-Xlint:unchecked</arg><arg>-Werror</arg></compilerArgs></configuration></plugin>
-      <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId><version>3.5.2</version><configuration><systemPropertyVariables><qqq.logger.logSessionId.disabled>true</qqq.logger.logSessionId.disabled></systemPropertyVariables></configuration></plugin>
+      <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId><version>3.5.6</version><configuration><systemPropertyVariables><qqq.logger.logSessionId.disabled>true</qqq.logger.logSessionId.disabled></systemPropertyVariables></configuration></plugin>
       <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-dependency-plugin</artifactId><version>3.8.1</version></plugin>
       <plugin><groupId>org.codehaus.mojo</groupId><artifactId>exec-maven-plugin</artifactId><version>3.5.0</version><configuration><mainClass>com.kingsrook.examples.echo.demo.EchoDemo</mainClass></configuration></plugin>
       <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-checkstyle-plugin</artifactId><version>3.6.0</version><dependencies><dependency><groupId>com.puppycrawl.tools</groupId><artifactId>checkstyle</artifactId><version>14.3.0</version></dependency></dependencies><configuration><configLocation>${project.basedir}/../../../checkstyle/checkstyle.xml</configLocation><includeTestSourceDirectory>true</includeTestSourceDirectory><failOnViolation>true</failOnViolation><violationSeverity>warning</violationSeverity></configuration><executions><execution><phase>validate</phase><goals><goal>check</goal></goals></execution></executions></plugin>

examples/echo/demo/src/main/java/com/kingsrook/examples/echo/demo/EchoDemo.java

@@ -36,6 +36,7 @@ import com.kingsrook.qbits.printing.PrintingService;
 import com.kingsrook.qbits.recordfiles.RecordFilesQBitConfig;
 import com.kingsrook.qbits.recordfiles.RecordFilesQBitProducer;
 import com.kingsrook.qbits.recordfiles.RecordFilesSchema;
+import com.kingsrook.qbits.recordfiles.download.DownloadConfiguration;
 import com.kingsrook.qbits.recordfiles.lifecycle.RecordFilesAttachmentLifecycle;
 import com.kingsrook.qqq.backend.core.context.QContext;
 import com.kingsrook.qqq.backend.core.exceptions.QException;
@@ -220,8 +221,16 @@ public class EchoDemo extends MobileScannersDemo implements AutoCloseable
       // Documents are the operator's published, Echo-compatible templates, discovered per run; the legacy
       // ECHO_TEMPLATE_* host pin no longer selects one.
       EchoHost.install(instance, new EchoHost.Deployment(BACKEND, BACKEND, BACKEND, dataSource, printing, renderer, maximumOutputBytes));
-      RecordFilesQBitConfig recordFiles = new RecordFilesQBitConfig().withBackendName(BACKEND).withParentTables(List.of(EchoQBitProducer.SCAN_TABLE))
+      MobileTestData.register(instance);
+      RecordFilesQBitConfig recordFiles = new RecordFilesQBitConfig().withBackendName(BACKEND)
+         .withParentTables(List.of(EchoQBitProducer.SCAN_TABLE, MobileTestData.ORDERS, MobileTestData.ITEMS, MobileTestData.EVENTS))
          .withQuarantineGeneratedFiles(settings.releaseGeneratedFiles() ? Boolean.FALSE : null)
+         // Narrow, host-only opt-in: only CAPTURE intake with the verified approved-device identity from
+         // MobileCaptureIdentityProvider (JPEG/PNG, bounded; see EchoPhotoCapture.uploadConfiguration) is AVAILABLE
+         // on registration. quarantineNewFiles stays true for uploads, imports and attachment-panel files.
+         // Requires the Record Files version that contains withQuarantineCapturedFiles.
+         .withQuarantineCapturedFiles(Boolean.FALSE)
+         .withDownloadConfiguration(new DownloadConfiguration("http://127.0.0.1:" + settings.port() + "/qqq/v1", 20 * 1024 * 1024, 2))
          .withUploadConfiguration(EchoPhotoCapture.uploadConfiguration());
       new RecordFilesQBitProducer().withQBitConfig(recordFiles).produce(instance);
       // Configuring uploads makes the producer register the versioned record-files extension; the mobile widget
@@ -268,6 +277,7 @@ public class EchoDemo extends MobileScannersDemo implements AutoCloseable
          collaborationTables(statement, instance);
          script(statement, UploadJournalTable.h2Script());
          script(statement, RecordFilesSchema.h2Script(config(instance, RecordFilesQBitConfig.class)));
+         MobileTestData.initialize(connection, instance);
       }
    }
 

examples/echo/demo/src/main/java/com/kingsrook/examples/echo/demo/EchoDemoAuthentication.java

@@ -22,7 +22,10 @@ import com.kingsrook.qqq.backend.core.model.session.QSession;
 /*******************************************************************************
  ** The existing demo password/session validation plus exactly the grants the
  ** owners' source requires. The validated account selects the role, never a
- ** request field. Printing and Record Files administration is granted to no one.
+ ** request field. Only the fixed admin account receives Printing administration,
+ ** template configure/publish and Record Files release (so approved scanner photos
+ ** can be released through the normal audited process); the scanner receives none
+ ** of them, and no one receives Record Files configure or review rights.
  *******************************************************************************/
 public class EchoDemoAuthentication extends DemoAuthenticationModule
 {
@@ -35,14 +38,15 @@ public class EchoDemoAuthentication extends DemoAuthenticationModule
     */
    static final List<String> SCANNER = List.of(EchoQBitProducer.PERMISSION, "printing_operator", "document-generation.view",
       "document-generation.generate", "document-generation.print", "record-files.view", "record-files.manage",
-      EchoQBitProducer.SCAN_TABLE + ".attach");
+      EchoQBitProducer.SCAN_TABLE + ".attach", MobileTestData.ORDERS + ".attach", MobileTestData.ITEMS + ".attach", MobileTestData.EVENTS + ".attach");
 
    /**
     ** Admin also gets Printing's own administrator permission, which its native
     ** device pairing/approval/setup processes require, and what is needed to
-    ** prepare and publish templates. The scanner never receives these.
+    ** prepare and publish templates, and Record Files release for approved
+    ** captured photos. The scanner never receives these.
     */
-   static final List<String> ADMIN_ADDITIONS = List.of("printing_admin", "document-generation.configure", "document-generation.publish");
+   static final List<String> ADMIN_ADDITIONS = List.of("printing_admin", "document-generation.configure", "document-generation.publish", "record-files.release");
 
    private static volatile String tenant;
 

examples/echo/demo/src/main/java/com/kingsrook/examples/echo/demo/MobileTestData.java

@@ -0,0 +1,251 @@
+/*
+ * Copyright (c) 2026 Kingsrook, LLC
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+package com.kingsrook.examples.echo.demo;
+
+
+import java.math.BigDecimal;
+import java.sql.Connection;
+import java.sql.PreparedStatement;
+import java.sql.SQLException;
+import java.sql.Statement;
+import java.time.LocalDate;
+import java.time.LocalDateTime;
+import java.util.ArrayList;
+import java.util.List;
+import com.kingsrook.examples.echo.EchoSourceReadPermissions;
+import com.kingsrook.qqq.backend.core.model.metadata.QInstance;
+import com.kingsrook.qqq.backend.core.model.metadata.code.QCodeReference;
+import com.kingsrook.qqq.backend.core.model.metadata.fields.QFieldMetaData;
+import com.kingsrook.qqq.backend.core.model.metadata.fields.QFieldType;
+import com.kingsrook.qqq.backend.core.model.metadata.joins.JoinOn;
+import com.kingsrook.qqq.backend.core.model.metadata.joins.JoinType;
+import com.kingsrook.qqq.backend.core.model.metadata.joins.QJoinMetaData;
+import com.kingsrook.qqq.backend.core.model.metadata.layout.QAppMetaData;
+import com.kingsrook.qqq.backend.core.model.metadata.layout.QAppSection;
+import com.kingsrook.qqq.backend.core.model.metadata.permissions.PermissionLevel;
+import com.kingsrook.qqq.backend.core.model.metadata.permissions.QPermissionRules;
+import com.kingsrook.qqq.backend.core.model.metadata.tables.Association;
+import com.kingsrook.qqq.backend.core.model.metadata.tables.QFieldSection;
+import com.kingsrook.qqq.backend.core.model.metadata.tables.QTableMetaData;
+import com.kingsrook.qqq.backend.core.model.metadata.tables.Tier;
+import com.kingsrook.qqq.backend.module.rdbms.model.metadata.RDBMSTableBackendDetails;
+
+
+/*******************************************************************************
+ ** Synthetic, read-only browsing fixtures for the local demo. Ordinary metadata
+ ** owns sections and relationships; no custom mobile endpoints are involved.
+ *******************************************************************************/
+final class MobileTestData
+{
+   static final String ORDERS = "testOrder";
+   static final String ITEMS = "testOrderItem";
+   static final String EVENTS = "testOrderEvent";
+   static final List<String> TABLES = List.of(ORDERS, ITEMS, EVENTS);
+   static final int ORDER_COUNT = 1000;
+
+
+
+   /***************************************************************************
+    ** Keep all fixtures in the demo, visible to the ordinary Echo demo reader.
+    ***************************************************************************/
+   static void register(QInstance instance)
+   {
+      QTableMetaData orders = table(ORDERS, "Test Orders");
+      section(orders, "overview", "Order overview", "id:INTEGER", "reference:STRING", "status:STRING", "priority:STRING", "orderDate:DATE", "requestedDate:DATE", "expedited:BOOLEAN");
+      section(orders, "customer", "Customer", "customerCode:STRING", "customerName:STRING", "contactName:STRING", "email:STRING", "phone:STRING", "purchaseOrder:STRING");
+      section(orders, "shipping", "Shipping", "addressLine1:STRING", "addressLine2:STRING", "city:STRING", "region:STRING", "postalCode:STRING", "country:STRING", "carrier:STRING", "trackingNumber:STRING");
+      section(orders, "amounts", "Amounts", "currency:STRING", "subtotal:DECIMAL", "tax:DECIMAL", "shippingCost:DECIMAL", "total:DECIMAL", "paid:BOOLEAN");
+      section(orders, "warehouse", "Warehouse", "warehouse:STRING", "bin:STRING", "itemCount:INTEGER", "weightKg:DECIMAL", "fragile:BOOLEAN", "lotCode:STRING");
+      section(orders, "notes", "Notes and audit", "instructions:STRING", "notes:STRING", "createdAt:DATE_TIME", "updatedAt:DATE_TIME", "externalReference:STRING", "optionalNote:STRING");
+      orders.withRecordLabelFormatAndFields("%s — %s", "reference", "customerName");
+      orders.withSearchFields(List.of("reference", "customerName"));
+      for(String name : List.of("subtotal", "tax", "shippingCost", "total"))
+      {
+         orders.getField(name).withDisplayFormat("$%,.2f");
+      }
+      orders.getField("weightKg").withDisplayFormat("%,.2f kg");
+
+      QTableMetaData items = table(ITEMS, "Order Items");
+      section(items, "item", "Item", "id:INTEGER", "reference:STRING", "sku:STRING", "quantity:INTEGER", "description:STRING", "orderId:INTEGER");
+      section(items, "pricing", "Pricing and handling", "unitPrice:DECIMAL", "lineTotal:DECIMAL", "bin:STRING", "lotCode:STRING", "fragile:BOOLEAN", "notes:STRING");
+      items.withRecordLabelFormatAndFields("%s · %s × %s", "reference", "quantity", "sku");
+      items.withSearchFields(List.of("reference", "sku", "description"));
+      items.getField("unitPrice").withDisplayFormat("$%,.2f");
+      items.getField("lineTotal").withDisplayFormat("$%,.2f");
+
+      QTableMetaData events = table(EVENTS, "Order History");
+      section(events, "event", "History entry", "id:INTEGER", "status:STRING", "createdAt:DATE_TIME", "notes:STRING", "reference:STRING", "orderId:INTEGER");
+      events.withRecordLabelFormatAndFields("%s · %s", "reference", "status");
+      events.withSearchFields(List.of("reference", "status", "notes"));
+      instance.addTable(orders);
+      instance.addTable(items);
+      instance.addTable(events);
+      associate(instance, orders, items, "Items");
+      associate(instance, orders, events, "History");
+      instance.addApp(new QAppMetaData().withName("mobileTestData").withLabel("Test Data").withPermissionRules(readRules())
+         .withSection(new QAppSection().withName("browse").withLabel("Synthetic test records").withTables(TABLES)));
+   }
+
+
+
+   /***************************************************************************
+    ** Native read permission enforcement also protects related-record queries.
+    ***************************************************************************/
+   private static QPermissionRules readRules()
+   {
+      return new QPermissionRules().withLevel(PermissionLevel.HAS_ACCESS_PERMISSION)
+         .withCustomPermissionChecker(new QCodeReference(EchoSourceReadPermissions.class));
+   }
+
+
+
+   /***************************************************************************
+    ** Physical names deliberately match metadata names for the demo's H2 schema.
+    ***************************************************************************/
+   private static QTableMetaData table(String name, String label)
+   {
+      return new QTableMetaData().withName(name).withLabel(label).withBackendName(EchoDemo.BACKEND)
+         .withBackendDetails(new RDBMSTableBackendDetails().withTableName(name)).withPrimaryKeyField("id").withPermissionRules(readRules());
+   }
+
+
+
+   /***************************************************************************
+    ** The ordinary metadata section controls order and grouping on every client.
+    ***************************************************************************/
+   private static void section(QTableMetaData table, String name, String label, String... definitions)
+   {
+      List<String> names = new ArrayList<>();
+      for(String definition : definitions)
+      {
+         String[] parts = definition.split(":");
+         names.add(parts[0]);
+         table.withField(new QFieldMetaData(parts[0], QFieldType.valueOf(parts[1])).withIsEditable(false));
+      }
+      table.withSection(new QFieldSection().withName(name).withLabel(label).withTier(Tier.T1).withFieldNames(names));
+   }
+
+
+
+   /***************************************************************************
+    ** Associations use declared joins, never client-inferred foreign-key names.
+    ***************************************************************************/
+   private static void associate(QInstance instance, QTableMetaData parent, QTableMetaData child, String label)
+   {
+      String join = parent.getName() + "_" + child.getName();
+      instance.addJoin(new QJoinMetaData().withName(join).withLeftTable(parent.getName()).withRightTable(child.getName())
+         .withType(JoinType.ONE_TO_MANY).withJoinOn(new JoinOn("id", "orderId")));
+      parent.withAssociation(new Association().withName(label).withAssociatedTableName(child.getName()).withJoinName(join));
+   }
+
+
+
+   /***************************************************************************
+    ** Add only missing fixture rows. Reapplying never resets photos or edits.
+    ** This metadata-derived schema is intentionally H2-only and demo-only.
+    ***************************************************************************/
+   static void initialize(Connection connection, QInstance instance) throws SQLException
+   {
+      for(String name : TABLES)
+      {
+         QTableMetaData table = instance.getTable(name);
+         List<QFieldMetaData> fields = new ArrayList<>(table.getFields().values());
+         List<String> columns = new ArrayList<>();
+         for(QFieldMetaData field : fields)
+         {
+            String type = switch(field.getType())
+            {
+               case INTEGER -> "INTEGER";
+               case BOOLEAN -> "BOOLEAN";
+               case DATE -> "DATE";
+               case DATE_TIME -> "TIMESTAMP";
+               case DECIMAL -> "DECIMAL(16,2)";
+               default -> "VARCHAR(4000)";
+            };
+            columns.add(field.getName() + " " + type + (field.getName().equals("id") ? " PRIMARY KEY" : ""));
+         }
+         try(Statement statement = connection.createStatement())
+         {
+            statement.execute("CREATE TABLE IF NOT EXISTS " + name + " (" + String.join(",", columns) + ")");
+            if(!name.equals(ORDERS))
+            {
+               statement.execute("CREATE INDEX IF NOT EXISTS idx_" + name + "_order ON " + name + " (orderId)");
+            }
+         }
+         String names = String.join(",", fields.stream().map(QFieldMetaData::getName).toList());
+         String placeholders = String.join(",", java.util.Collections.nCopies(fields.size(), "?"));
+         String sql = "INSERT INTO " + name + " (" + names + ") SELECT " + placeholders + " WHERE NOT EXISTS (SELECT 1 FROM " + name + " WHERE id = ?)";
+         int perOrder = name.equals(ORDERS) ? 1 : name.equals(ITEMS) ? 12 : 3;
+         boolean autoCommit = connection.getAutoCommit();
+         connection.setAutoCommit(false);
+         try(PreparedStatement insert = connection.prepareStatement(sql))
+         {
+            for(int id = 1; id <= ORDER_COUNT * perOrder; id++)
+            {
+               int order = (id - 1) / perOrder + 1;
+               for(int index = 0; index < fields.size(); index++)
+               {
+                  insert.setObject(index + 1, value(name, fields.get(index), id, order));
+               }
+               insert.setInt(fields.size() + 1, id);
+               insert.addBatch();
+               if(id % 250 == 0)
+               {
+                  insert.executeBatch();
+               }
+            }
+            insert.executeBatch();
+            connection.commit();
+         }
+         catch(SQLException failure)
+         {
+            connection.rollback();
+            throw failure;
+         }
+         finally
+         {
+            connection.setAutoCommit(autoCommit);
+         }
+      }
+   }
+
+
+
+   /***************************************************************************
+    ** Deterministic, obviously synthetic values exercise long, empty, Unicode,
+    ** leading-zero, numeric, boolean, date and date-time display paths.
+    ***************************************************************************/
+   private static Object value(String table, QFieldMetaData field, int id, int order)
+   {
+      return switch(field.getName())
+      {
+         case "id" -> id;
+         case "orderId" -> order;
+         case "reference" -> (table.equals(ORDERS) ? "TEST-" : table.equals(ITEMS) ? "ITEM-" : "EVENT-") + String.format(java.util.Locale.ROOT, "%06d", id);
+         case "customerName" -> "Synthetic Customer " + order + (order % 3 == 0 ? " — Café & Supply" : "");
+         case "customerCode", "sku", "lotCode", "externalReference", "postalCode" -> String.format(java.util.Locale.ROOT, "%08d", id);
+         case "email" -> "customer" + order + "@example.invalid";
+         case "phone" -> "Not a real telephone number";
+         case "status" -> List.of("New", "Picking", "Packed", "Shipped", "On hold").get(id % 5);
+         case "priority" -> id % 4 == 0 ? "High" : "Normal";
+         case "currency" -> "USD";
+         case "country" -> "US";
+         case "description" -> "Synthetic product " + id + " — reusable storage container with a deliberately long description for wrapping";
+         case "notes", "instructions" -> "Synthetic test data only.\nOrder " + order + ": inspect all sides and attach a photo.\nAccents: café, naïve; symbols: & / +.";
+         case "optionalNote", "addressLine2" -> id % 2 == 0 ? null : "Optional example " + id;
+         case "itemCount" -> 12;
+         default -> switch(field.getType())
+         {
+            case BOOLEAN -> id % 2 == 0;
+            case INTEGER -> id % 9 + 1;
+            case DECIMAL -> BigDecimal.valueOf(1000L + id, 2);
+            case DATE -> LocalDate.of(2026, 1, 1).plusDays(id % 300);
+            case DATE_TIME -> LocalDateTime.of(2026, 1, 1, 10, 30).plusHours(id);
+            default -> "Test " + field.getName() + " " + order;
+         };
+      };
+   }
+}

examples/echo/demo/src/main/java/com/kingsrook/examples/echo/demo/PrivateObjectFiles.java

@@ -30,12 +30,17 @@ import com.fasterxml.jackson.databind.ObjectMapper;
  ** file name, so no key can address another path, alias another object or climb
  ** out of the root. Objects are written to a temporary file in their own folder
  ** and linked into place, so a reader never sees a partial object and an existing
- ** object is never replaced.
+ ** object is never replaced. Publication is serialized within one JVM only; the
+ ** demo does not support several processes sharing one private root.
  *******************************************************************************/
 final class PrivateObjectFiles
 {
    private static final ObjectMapper JSON = new ObjectMapper();
    private static final int MAXIMUM_KEY = 2048;
+
+   // Guards final existence check, metadata publication and linking (and delete) across
+   // all instances in this JVM. The demo is a single process; this is not a cross-process lock.
+   private static final Object PUBLISH_LOCK = new Object();
    private final Path root;
 
 
@@ -68,7 +73,7 @@ final class PrivateObjectFiles
     ***************************************************************************/
    Path file(String bucket, String key)
    {
-      if(bucket == null || !bucket.matches("[A-Za-z0-9._-]{1,64}") || key == null || key.isEmpty() || key.length() > MAXIMUM_KEY)
+      if(bucket == null || !bucket.matches("[A-Za-z0-9._-]{1,64}") || bucket.equals(".") || bucket.equals("..") || key == null || key.isEmpty() || key.length() > MAXIMUM_KEY)
       {
          throw new IllegalArgumentException("Object bucket or key is outside policy");
       }
@@ -117,8 +122,7 @@ final class PrivateObjectFiles
             }
          }
          JSON.writeValue(sidecar.toFile(), metadata == null ? Map.of() : metadata);
-         Files.move(sidecar, metadataFile(target), StandardCopyOption.REPLACE_EXISTING, StandardCopyOption.ATOMIC_MOVE);
-         Files.createLink(target, temporary);
+         publish(target, temporary, sidecar);
       }
       finally
       {
@@ -129,6 +133,41 @@ final class PrivateObjectFiles
 
 
 
+   /***************************************************************************
+    ** Publish the metadata and then the object, as one step with respect to
+    ** other writers and deleters in this JVM. The lock is shared by every
+    ** instance, so two instances over the same root cannot interleave. It covers
+    ** only the final existence check and two cheap file operations, never the
+    ** copy of the content. A winner's metadata is therefore never replaced by a
+    ** loser's, and the metadata exists whenever the object does. This does not
+    ** coordinate separate processes.
+    ***************************************************************************/
+   private static void publish(Path target, Path temporary, Path sidecar) throws IOException
+   {
+      Path metadataFile = metadataFile(target);
+      synchronized(PUBLISH_LOCK)
+      {
+         if(Files.exists(target, java.nio.file.LinkOption.NOFOLLOW_LINKS))
+         {
+            throw new FileAlreadyExistsException("Object already exists");
+         }
+
+         // no object exists here, so any metadata is a stale leftover and may be replaced
+         Files.move(sidecar, metadataFile, StandardCopyOption.REPLACE_EXISTING, StandardCopyOption.ATOMIC_MOVE);
+         try
+         {
+            Files.createLink(target, temporary);
+         }
+         catch(IOException | RuntimeException failure)
+         {
+            Files.deleteIfExists(metadataFile);
+            throw failure;
+         }
+      }
+   }
+
+
+
    /***************************************************************************
     ** Read an object's identity; absent means empty. Links are refused.
     ***************************************************************************/
@@ -162,8 +201,11 @@ final class PrivateObjectFiles
    void delete(String bucket, String key) throws IOException
    {
       Path target = file(bucket, key);
-      Files.deleteIfExists(target);
-      Files.deleteIfExists(metadataFile(target));
+      synchronized(PUBLISH_LOCK)
+      {
+         Files.deleteIfExists(target);
+         Files.deleteIfExists(metadataFile(target));
+      }
    }
 
 

examples/echo/demo/src/test/java/com/kingsrook/examples/echo/demo/EchoDemoAcceptanceTest.java

@@ -16,14 +16,21 @@ import java.net.http.HttpResponse;
 import java.nio.charset.StandardCharsets;
 import java.nio.file.Files;
 import java.nio.file.Path;
+import java.nio.file.StandardCopyOption;
+import java.security.MessageDigest;
+import java.sql.Connection;
 import java.sql.DriverManager;
+import java.sql.Statement;
 import java.time.Duration;
 import java.util.ArrayList;
 import java.util.Base64;
+import java.util.Comparator;
 import java.util.HashSet;
+import java.util.HexFormat;
 import java.util.List;
 import java.util.Map;
 import java.util.Set;
+import java.util.TreeMap;
 import java.util.UUID;
 import java.util.concurrent.CopyOnWriteArrayList;
 import java.util.concurrent.atomic.AtomicInteger;
@@ -34,6 +41,7 @@ import com.kingsrook.examples.echo.EchoTemplatePublisher;
 import com.kingsrook.qbits.documentgeneration.DocumentDefinitionService;
 import com.kingsrook.qbits.documentgeneration.DocumentGenerationQBitConfig;
 import com.kingsrook.qbits.documentgeneration.GenerationPorts;
+import com.kingsrook.qbits.recordfiles.RecordFilesTables;
 import com.kingsrook.qqq.backend.core.context.QContext;
 import com.kingsrook.qqq.backend.core.exceptions.QException;
 import com.kingsrook.qqq.backend.core.model.metadata.QInstance;
@@ -71,11 +79,17 @@ class EchoDemoAcceptanceTest
    private static final int RENDERER_CAP = 262144;
    private static final String CODE_VALUE = "001234567890";
    private static final String QR_VALUE = "QR-VALUE-0099";
+   /** EchoPermissions.checkPermissionsThrowing: the refusal for any actor without a currently approved scanner. */
+   private static final String ECHO_DEVICE_REFUSAL = "Echo requires an approved scanner and current Echo access.";
    private static final Set<Integer> PROTECTED = Set.of(57832, 51631, 18081, 18086, 18443, 19443, 18447, 18448, 18547, 18549, 18593);
 
    @TempDir
    Path root;
 
+   /** A second, separate temporary directory: the only place the snapshot is written to or read from. */
+   @TempDir
+   Path snapshotDirectory;
+
    private final HttpClient client = HttpClient.newBuilder().connectTimeout(Duration.ofSeconds(5)).followRedirects(HttpClient.Redirect.NEVER).build();
    private String origin;
    private String deviceId;
@@ -823,6 +837,442 @@ class EchoDemoAcceptanceTest
 
 
 
+   /***************************************************************************
+    ** Everything a restore must give back exactly, read straight from the private
+    ** database and object directory rather than through the application.
+    ** retainedFiles are the Record Files owner's own rows (RecordFilesTables.FILE):
+    ** id, source table, source record, attachment, size.
+    ***************************************************************************/
+   private record Capture(List<List<String>> echoScans, List<List<String>> mobileScans, List<List<String>> retainedFiles, Map<String, String> objects)
+   {
+   }
+
+   /***************************************************************************
+    ** The status and error text of a refused request; see refusal().
+    ***************************************************************************/
+   private record Refusal(int status, String message)
+   {
+   }
+
+
+
+   /***************************************************************************
+    ** Bounded backup/restore qualification of the composed host, on private
+    ** temporary paths only. A synthetic approved device scans an exact
+    ** leading-zero value through real HTTP and the real Record Files service
+    ** retains the generated original (the owner's retained-file row names the scan
+    ** as its source table and record). With every server stopped and the H2 files
+    ** closed, the database and object directory are copied together. A second scan
+    ** and file, a revocation and an ended session are then made, and only the two
+    ** temporary directories are restored. The restored state must equal the
+    ** snapshot and the later changes must be gone. The reverted approval is
+    ** trusted until the existing Revoke and End Session processes re-audit it,
+    ** after which a run opened before the revocation, and a new sign-in, are
+    ** refused by the host's own authorization. The renderer is controlled and the
+    ** printer is a database fixture: no job is printed, and no normal demo
+    ** database, service or external provider is touched. Retained files are read
+    ** from the owner's table, not through its service, and this does not qualify
+    ** production storage.
+    ***************************************************************************/
+   @Test
+   void restoredSnapshotKeepsScanAndRetainedFileAndRevertedApprovalStateIsReaudited() throws Exception
+   {
+      String scannerPassword = UUID.randomUUID().toString();
+      String adminPassword = UUID.randomUUID().toString();
+      String firstZpl = "^XA^FO48,48^FDcode128|" + CODE_VALUE + "^FS^XZ";
+      String secondZpl = "^XA^FO48,48^FDqr|" + QR_VALUE + "^FS^XZ";
+      String printerRowId;
+      Integer template;
+      String staleCookie;
+      String sessionId;
+      String firstEventId;
+      Capture atSnapshot;
+
+      // 1. Enroll, approve and scan through the real host; the original is retained by the real service.
+      int firstPort = freePort();
+      EchoDemoSettings first = new EchoDemoSettings(root, firstPort, TENANT, TOKEN, true, null, null);
+      origin = "http://127.0.0.1:" + firstPort;
+      try(EchoDemo demo = new EchoDemo(first, new ControlledRenderer(RENDERER_CAP), RENDERER_CAP))
+      {
+         demo.initializeDatabase(scannerPassword, adminPassword);
+         printerRowId = enrollPrinter(demo, first);
+         demo.start(firstPort);
+         String admin = login("admin", adminPassword);
+         staleCookie = login("scanner", scannerPassword);
+         template = publishTemplate(demo, printerRowId, admin, "Echo recovery label", MEDIA, REVISION, 101600, 152400, 300);
+         enrollAndApproveDevice(staleCookie, admin);
+         HttpResponse<String> heartbeat = request("POST", "/qqq/v1/qbit/mobile-scanners/sessions/heartbeat", staleCookie, "{\"foreground\":true,\"screenAvailable\":false}", true);
+         assertEquals(200, heartbeat.statusCode(), "The approved device must open a session.");
+         sessionId = new JSONObject(heartbeat.body()).getString("sessionId");
+         JSONObject firstEvent = event("LABEL-TYPE-CODE128", CODE_VALUE);
+         firstEventId = firstEvent.getString("eventId");
+         assertEquals("QUEUED", scanInNewRun(staleCookie, printerRowId, template, firstEvent).getString("printStatus"));
+         atSnapshot = capture(first);
+      }
+      finally
+      {
+         stopDatabase(first);
+      }
+      assertEquals(1, atSnapshot.echoScans().size());
+      List<String> scan = atSnapshot.echoScans().getFirst();
+      assertEquals(firstEventId, scan.get(1));
+      assertEquals(CODE_VALUE, scan.get(3), "The exact leading-zero text must be stored.");
+      assertEquals("LABEL-TYPE-CODE128", scan.get(4));
+      assertEquals("code128", scan.get(5));
+      assertEquals(1, atSnapshot.mobileScans().size());
+      assertEquals(scan.get(2), atSnapshot.mobileScans().getFirst().get(0), "The Echo scan must name its mobile scan.");
+      assertEquals(firstEventId, atSnapshot.mobileScans().getFirst().get(1));
+      assertEquals(CODE_VALUE, atSnapshot.mobileScans().getFirst().get(2));
+      assertEquals("scanner", atSnapshot.mobileScans().getFirst().get(3), "Attribution is derived by the server.");
+      assertEquals(deviceId, atSnapshot.mobileScans().getFirst().get(4));
+      assertEquals(Set.of(firstZpl), retainedOriginals(), "Record Files retained exactly the generated original.");
+      // the owner's retained-file row: source table and record are this exact scan, and the size is that of the original
+      assertEquals(1, atSnapshot.retainedFiles().size(), "Exactly one retained-file row exists for the one scan.");
+      List<String> file = atSnapshot.retainedFiles().getFirst();
+      assertEquals(EchoQBitProducer.SCAN_TABLE, file.get(1), "The retained file's source table is the Echo scan table.");
+      assertEquals(scan.get(0), file.get(2), "The retained file's source record is this exact scan.");
+      assertNotNull(file.get(3), "The retained file references its standard attachment.");
+      assertEquals(String.valueOf(firstZpl.length()), file.get(4), "The retained size is that of the generated original.");
+
+      // 2. Snapshot the closed database and the object directory together, into the other temporary directory.
+      takeSnapshot();
+
+      // 3. Change state after the snapshot, then stop.
+      int secondPort = freePort();
+      EchoDemoSettings second = new EchoDemoSettings(root, secondPort, TENANT, TOKEN, true, null, null);
+      origin = "http://127.0.0.1:" + secondPort;
+      try(EchoDemo demo = new EchoDemo(second, new ControlledRenderer(RENDERER_CAP), RENDERER_CAP))
+      {
+         demo.start(secondPort);
+         String admin = login("admin", adminPassword);
+         scanInNewRun(staleCookie, printerRowId, template, event("QRCODE", QR_VALUE));
+         runSelected("mobileDeviceRevoke", "mobileDevice", deviceId, new JSONObject(), admin);
+         runSelected("mobileSessionEnd", "mobileSession", sessionId, new JSONObject().put("reason", "post-snapshot change"), admin);
+         awaitSessionEnded(second, sessionId, staleCookie);
+         assertEquals(List.of(List.of("REVOKED")), sql(second, "SELECT status FROM mobileDevice WHERE id = '" + deviceId + "'", 1));
+         assertEquals(2, sql(second, "SELECT id FROM echo_scan", 1).size());
+         assertEquals(2, sql(second, "SELECT id FROM record_files_file", 1).size());
+         assertEquals(Set.of(firstZpl, secondZpl), retainedOriginals());
+      }
+      finally
+      {
+         stopDatabase(second);
+      }
+
+      // 4. Restore only the two temporary directories, then read them with no application running.
+      restoreSnapshot();
+      int thirdPort = freePort();
+      EchoDemoSettings third = new EchoDemoSettings(root, thirdPort, TENANT, TOKEN, true, null, null);
+      try
+      {
+         assertEquals(atSnapshot, capture(third), "The restored scan rows, retained-file row and object bytes must equal the snapshot.");
+         assertEquals(List.of(List.of("APPROVED")), sql(third, "SELECT status FROM mobileDevice WHERE id = '" + deviceId + "'", 1),
+            "The restore reverts the later revocation, so the device is approved again.");
+         assertEquals(List.of(List.of("ACTIVE")), sql(third, "SELECT status FROM mobileSession WHERE id = '" + sessionId + "'", 1),
+            "The restore reverts the later session end.");
+         assertEquals(1, sql(third, "SELECT id FROM demoSession WHERE id = '" + staleCookie + "'", 1).size(), "The earlier sign-in session is restored too.");
+         assertEquals(1, sql(third, "SELECT id FROM printing_job", 1).size());
+         assertEquals(Set.of(firstZpl), retainedOriginals(), "No object from after the snapshot may remain.");
+      }
+      finally
+      {
+         stopDatabase(third);
+      }
+
+      // 5. Restart on a new ephemeral port: the restored scan is served, stale authority works until re-audit, and then is refused.
+      ControlledRenderer renderer = new ControlledRenderer(RENDERER_CAP);
+      origin = "http://127.0.0.1:" + thirdPort;
+      try(EchoDemo demo = new EchoDemo(third, renderer, RENDERER_CAP))
+      {
+         demo.start(thirdPort);
+         JSONArray scans = query(EchoQBitProducer.SCAN_TABLE, staleCookie);
+         assertEquals(1, scans.length());
+         assertEquals(CODE_VALUE, scans.getJSONObject(0).getJSONObject("values").getString("barcode"));
+         HttpResponse<String> current = request("GET", "/qqq/v1/qbit/mobile-scanners/devices/current", staleCookie, null, true);
+         assertEquals(200, current.statusCode());
+         assertEquals("APPROVED", new JSONObject(current.body()).getString("status"), "Reopening without a re-audit would trust the reverted approval.");
+
+         // a real run, opened while the restored approval is still trusted and parked at its scan step
+         String run = openRun(staleCookie, printerRowId, template);
+         JSONObject lateScan = event("QRCODE", "STALE-SUBMIT-0001");
+
+         String admin = login("admin", adminPassword);
+         runSelected("mobileDeviceRevoke", "mobileDevice", deviceId, new JSONObject(), admin);
+         assertEquals(List.of(List.of("REVOKED")), sql(third, "SELECT status FROM mobileDevice WHERE id = '" + deviceId + "'", 1));
+         // the sign-in session is still valid, so this refusal is the host's device authorization, not authentication
+         assertEquals(200, request("GET", "/qqq/v1/qbit/mobile-scanners/devices/current", staleCookie, null, true).statusCode());
+         assertAuthorizationRefused(refusal(form("/qqq/v1/processes/echoPrint/" + run + "/step/scan", staleCookie, lateScan, true), staleCookie));
+         assertAuthorizationRefused(refusal(form("/qqq/v1/processes/echoPrint/init", staleCookie, new JSONObject(), true), staleCookie));
+
+         runSelected("mobileSessionEnd", "mobileSession", sessionId, new JSONObject().put("reason", "restore re-audit"), admin);
+         awaitSessionEnded(third, sessionId, staleCookie);
+         assertEquals(401, request("GET", "/qqq/v1/metaData", staleCookie, null, true).statusCode(), "The ended session must no longer authenticate.");
+         assertEquals(401, form("/qqq/v1/processes/echoPrint/" + run + "/step/scan", staleCookie, lateScan, true).statusCode(),
+            "The same run cannot be continued with the ended session.");
+
+         String freshCookie = login("scanner", scannerPassword);
+         assertAuthorizationRefused(refusal(form("/qqq/v1/processes/echoPrint/init", freshCookie, new JSONObject(), true), freshCookie));
+         assertEquals(0, renderer.renders.size(), "Nothing may be generated after the restore.");
+         assertEquals(1, sql(third, "SELECT id FROM echo_scan", 1).size());
+         assertEquals(1, sql(third, "SELECT id FROM mobileScan", 1).size());
+         assertEquals(1, sql(third, "SELECT id FROM printing_job", 1).size());
+         assertEquals(atSnapshot.objects(), objectHashes(), "Refused submissions must not change retained files.");
+      }
+      finally
+      {
+         stopDatabase(third);
+      }
+   }
+
+
+
+   /***************************************************************************
+    ** A new Echo run, then one scan in it, as the approved scanner device.
+    ***************************************************************************/
+   private JSONObject scanInNewRun(String scanner, String printerRowId, Integer template, JSONObject event) throws Exception
+   {
+      String process = openRun(scanner, printerRowId, template);
+      return echo(form("/qqq/v1/processes/echoPrint/" + process + "/step/scan", scanner, event, true), scanner).getJSONObject("values");
+   }
+
+
+
+   /***************************************************************************
+    ** A new Echo run chosen through setup, ready for its scan step.
+    ***************************************************************************/
+   private String openRun(String scanner, String printerRowId, Integer template) throws Exception
+   {
+      String process = echo(form("/qqq/v1/processes/echoPrint/init", scanner, new JSONObject(), true), scanner).getString("processUUID");
+      assertEquals("scan", echo(form("/qqq/v1/processes/echoPrint/" + process + "/step/setup", scanner,
+         new JSONObject().put("printerId", printerRowId).put("mediaId", MEDIA).put("templateId", template), true), scanner).getString("nextStep"));
+      return process;
+   }
+
+
+
+   /***************************************************************************
+    ** Run an existing administrator process on one selected record, from its
+    ** Actions menu, exactly as the browser and native client do.
+    ***************************************************************************/
+   private void runSelected(String process, String table, String recordId, JSONObject input, String admin) throws Exception
+   {
+      JSONObject selection = new JSONObject().put("recordsParam", "recordIds").put("recordIds", recordId).put("tableName", table);
+      JSONObject launched = complete(form("/qqq/v1/processes/" + process + "/init", admin, selection, false), process, admin, false);
+      assertEquals("input", launched.getString("nextStep"));
+      complete(form("/qqq/v1/processes/" + process + "/" + launched.getString("processUUID") + "/step/input", admin, input, false), process, admin, false);
+   }
+
+
+
+   /***************************************************************************
+    ** The End Session process commits the tombstone, then removes the stored
+    ** authentication session asynchronously; wait for both, within a bound.
+    ***************************************************************************/
+   private static void awaitSessionEnded(EchoDemoSettings settings, String sessionId, String cookie) throws Exception
+   {
+      long deadline = System.nanoTime() + Duration.ofSeconds(15).toNanos();
+      List<List<String>> state;
+      List<List<String>> remaining;
+      boolean done;
+      do
+      {
+         state = sql(settings, "SELECT status, authCleanupStatus FROM mobileSession WHERE id = '" + sessionId + "'", 2);
+         remaining = sql(settings, "SELECT id FROM demoSession WHERE id = '" + cookie + "'", 1);
+         done = List.of(List.of("ENDED", "REQUESTED")).equals(state) && remaining.isEmpty();
+         if(!done)
+         {
+            Thread.sleep(50);
+         }
+      }
+      while(!done && System.nanoTime() < deadline);
+      assertEquals(List.of(List.of("ENDED", "REQUESTED")), state, "The session must be ended with cleanup requested.");
+      assertTrue(remaining.isEmpty(), "The stored authentication session must be removed.");
+   }
+
+
+
+   /***************************************************************************
+    ** Follow an Echo process request to its outcome: the immediate HTTP status,
+    ** or, when the step went asynchronous, the final status body. Returns the
+    ** HTTP status and the "error" text, with no assertion about either.
+    ***************************************************************************/
+   private Refusal refusal(HttpResponse<String> response, String cookie) throws Exception
+   {
+      long deadline = System.nanoTime() + Duration.ofSeconds(30).toNanos();
+      JSONObject body = new JSONObject(response.body());
+      while(response.statusCode() == 200 && ("JOB_STARTED".equals(body.optString("type")) || "RUNNING".equals(body.optString("type"))))
+      {
+         assertTrue(System.nanoTime() < deadline, "Native process timed out.");
+         Thread.sleep(25);
+         response = request("GET", "/qqq/v1/processes/" + EchoQBitProducer.PROCESS + "/" + body.getString("processUUID") + "/status/" + body.getString("jobUUID"), cookie, null, true);
+         body = new JSONObject(response.body());
+      }
+      return new Refusal(response.statusCode(), body.optString("error"));
+   }
+
+
+
+   /***************************************************************************
+    ** The exact refusal of a revoked device under a still-valid sign-in: the
+    ** Echo process permission checker's own message (EchoPermissions), as a 403
+    ** or as the process error, and never a success or any other failure.
+    ***************************************************************************/
+   private static void assertAuthorizationRefused(Refusal refusal)
+   {
+      assertTrue(refusal.status() == 403 || refusal.status() == 200, "Unexpected status " + refusal.status() + ": " + refusal.message());
+      assertEquals(ECHO_DEVICE_REFUSAL, refusal.message(), "The refusal must be Echo's own device authorization message.");
+   }
+
+
+
+   /***************************************************************************
+    ** Read the durable state straight from the closed-to-the-app database and
+    ** the object directory.
+    ***************************************************************************/
+   private Capture capture(EchoDemoSettings settings) throws Exception
+   {
+      List<List<String>> echoScans = sql(settings, "SELECT id, eventId, mobileScanId, barcode, symbology, rendererSymbology, printJobId, state FROM echo_scan ORDER BY id", 8);
+      List<List<String>> mobileScans = sql(settings, "SELECT id, eventId, barcode, userId, deviceId FROM mobileScan ORDER BY id", 5);
+      List<List<String>> retainedFiles = sql(settings, "SELECT id, table_name, record_id, attachment_id, size_bytes FROM " + RecordFilesTables.FILE + " ORDER BY id", 5);
+      return new Capture(echoScans, mobileScans, retainedFiles, objectHashes());
+   }
+
+
+
+   /***************************************************************************
+    ** The SHA-256 of every file under the object directory, by relative path,
+    ** including each object's metadata file.
+    ***************************************************************************/
+   private Map<String, String> objectHashes() throws Exception
+   {
+      Path objects = root.resolve("objects");
+      Map<String, String> hashes = new TreeMap<>();
+      try(Stream<Path> files = Files.walk(objects))
+      {
+         for(Path file : files.filter(Files::isRegularFile).toList())
+         {
+            hashes.put(objects.relativize(file).toString().replace('\\', '/'), HexFormat.of().formatHex(MessageDigest.getInstance("SHA-256").digest(Files.readAllBytes(file))));
+         }
+      }
+      return hashes;
+   }
+
+
+
+   /***************************************************************************
+    ** The content of every retained original (an object that is not metadata).
+    ***************************************************************************/
+   private Set<String> retainedOriginals() throws Exception
+   {
+      Set<String> retained = new HashSet<>();
+      try(Stream<Path> files = Files.walk(root.resolve("objects")))
+      {
+         for(Path file : files.filter(Files::isRegularFile).filter(path -> !path.getFileName().toString().endsWith(".json")).toList())
+         {
+            retained.add(Files.readString(file, StandardCharsets.US_ASCII));
+         }
+      }
+      return retained;
+   }
+
+
+
+   /***************************************************************************
+    ** Close the private file database so its files are complete and unlocked.
+    ** The server is already stopped when this runs.
+    ***************************************************************************/
+   private static void stopDatabase(EchoDemoSettings settings) throws Exception
+   {
+      QContext.clear();
+      try(Connection connection = DriverManager.getConnection(EchoDemo.jdbcUrl(settings), "sa", ""); Statement statement = connection.createStatement())
+      {
+         statement.execute("SHUTDOWN");
+      }
+      com.kingsrook.qqq.backend.module.rdbms.jdbc.ConnectionManager.resetConnectionProviders();
+   }
+
+
+
+   /***************************************************************************
+    ** Copy the closed database and object directory, together, to the snapshot
+    ** directory.
+    ***************************************************************************/
+   private void takeSnapshot() throws Exception
+   {
+      for(String name : List.of("db", "objects"))
+      {
+         copyTree(root.resolve(name), snapshotDirectory.resolve(name));
+      }
+      try(Stream<Path> files = Files.list(snapshotDirectory.resolve("db")))
+      {
+         List<String> names = files.map(path -> path.getFileName().toString()).toList();
+         assertTrue(names.stream().anyMatch(name -> name.endsWith(".mv.db")), "The snapshot must contain the database file: " + names);
+         assertFalse(names.stream().anyMatch(name -> name.endsWith(".lock.db")), "The database must be closed before the snapshot.");
+      }
+   }
+
+
+
+   /***************************************************************************
+    ** Replace only this test's database and object directories from the snapshot.
+    ***************************************************************************/
+   private void restoreSnapshot() throws Exception
+   {
+      Path liveRoot = root.toAbsolutePath().normalize();
+      Path snapshotRoot = snapshotDirectory.toAbsolutePath().normalize();
+      assertFalse(snapshotRoot.startsWith(liveRoot) || liveRoot.startsWith(snapshotRoot), "The two temporary directories must be separate.");
+      for(String name : List.of("db", "objects"))
+      {
+         Path live = liveRoot.resolve(name).normalize();
+         assertTrue(live.startsWith(liveRoot), "Only paths inside this test's temporary directory may be replaced.");
+         assertTrue(Files.isDirectory(snapshotRoot.resolve(name)));
+         deleteTree(live);
+         copyTree(snapshotRoot.resolve(name), live);
+      }
+   }
+
+
+
+   /***************************************************************************
+    ** Copy a directory tree, creating directories and preserving file times.
+    ***************************************************************************/
+   private static void copyTree(Path from, Path to) throws Exception
+   {
+      try(Stream<Path> paths = Files.walk(from))
+      {
+         for(Path source : paths.toList())
+         {
+            Path target = to.resolve(from.relativize(source).toString());
+            if(Files.isDirectory(source))
+            {
+               Files.createDirectories(target);
+            }
+            else
+            {
+               Files.copy(source, target, StandardCopyOption.COPY_ATTRIBUTES);
+            }
+         }
+      }
+   }
+
+
+
+   /***************************************************************************
+    ** Delete a directory tree, children first.
+    ***************************************************************************/
+   private static void deleteTree(Path tree) throws Exception
+   {
+      try(Stream<Path> paths = Files.walk(tree))
+      {
+         for(Path path : paths.sorted(Comparator.reverseOrder()).toList())
+         {
+            Files.delete(path);
+         }
+      }
+   }
+
+
+
    /***************************************************************************
     ** One scan event with a unique id and the exact scanned text.
     ***************************************************************************/

examples/echo/demo/src/test/java/com/kingsrook/examples/echo/demo/EchoDemoSettingsTest.java

@@ -110,8 +110,8 @@ class EchoDemoSettingsTest
    void permissionSetsAreLeastPrivilege()
    {
       assertEquals(List.of("echo.use", "printing_operator", "document-generation.view", "document-generation.generate", "document-generation.print",
-         "record-files.view", "record-files.manage", "echoScan.attach"), EchoDemoAuthentication.SCANNER);
-      assertEquals(List.of("printing_admin", "document-generation.configure", "document-generation.publish"), EchoDemoAuthentication.ADMIN_ADDITIONS);
-      assertFalse(EchoDemoAuthentication.SCANNER.stream().anyMatch(name -> name.endsWith(".configure") || name.endsWith(".publish") || name.endsWith("admin")));
+         "record-files.view", "record-files.manage", "echoScan.attach", "testOrder.attach", "testOrderItem.attach", "testOrderEvent.attach"), EchoDemoAuthentication.SCANNER);
+      assertEquals(List.of("printing_admin", "document-generation.configure", "document-generation.publish", "record-files.release"), EchoDemoAuthentication.ADMIN_ADDITIONS);
+      assertFalse(EchoDemoAuthentication.SCANNER.stream().anyMatch(name -> name.endsWith(".configure") || name.endsWith(".publish") || name.endsWith("admin") || name.endsWith(".release")));
    }
 }

examples/echo/demo/src/test/java/com/kingsrook/examples/echo/demo/EchoDemoStartupTest.java

@@ -6,6 +6,10 @@
 package com.kingsrook.examples.echo.demo;
 
 
+import javax.imageio.ImageIO;
+import java.awt.image.BufferedImage;
+import java.io.ByteArrayInputStream;
+import java.io.ByteArrayOutputStream;
 import java.net.ServerSocket;
 import java.net.URI;
 import java.net.http.HttpClient;
@@ -14,17 +18,25 @@ import java.net.http.HttpResponse;
 import java.nio.charset.StandardCharsets;
 import java.nio.file.Files;
 import java.nio.file.Path;
+import java.security.MessageDigest;
 import java.sql.DriverManager;
 import java.time.Duration;
 import java.util.Base64;
+import java.util.HexFormat;
+import java.util.Map;
 import java.util.Set;
 import java.util.UUID;
 import java.util.concurrent.atomic.AtomicInteger;
 import com.kingsrook.qbits.documentgeneration.GenerationPorts;
+import com.kingsrook.qbits.recordfiles.files.IntakeRequest;
+import com.kingsrook.qbits.recordfiles.files.RetainedFileService;
+import com.kingsrook.qbits.recordfiles.review.FileReviewService;
+import com.kingsrook.qqq.backend.core.context.QContext;
 import com.kingsrook.qqq.backend.core.exceptions.QException;
 import com.kingsrook.qqq.backend.core.model.metadata.QInstance;
 import com.kingsrook.qqq.backend.core.model.session.QSession;
 import com.kingsrook.qqq.backend.core.model.session.QUser;
+import com.kingsrook.qqq.backend.core.modules.authentication.implementations.TableBasedAuthenticationModule;
 import com.kingsrook.qqq.middleware.javalin.specs.extensions.MiddlewareSpecExtensionsMetaData;
 import org.junit.jupiter.api.AfterEach;
 import org.junit.jupiter.api.BeforeEach;
@@ -53,7 +65,8 @@ class EchoDemoStartupTest
    @TempDir
    Path root;
 
-   private final HttpClient client = HttpClient.newBuilder().connectTimeout(Duration.ofSeconds(5)).build();
+   private final HttpClient client = HttpClient.newBuilder().connectTimeout(Duration.ofSeconds(5))
+      .cookieHandler(new java.net.CookieManager(null, java.net.CookiePolicy.ACCEPT_ALL)).build();
 
 
 
@@ -151,6 +164,7 @@ class EchoDemoStartupTest
          demo.start(port);
 
          QInstance instance = demo.defineQInstance();
+         seedPreviewPhotos(instance, ADMIN_PASSWORD);
          assertNotNull(instance.getApp("echo"));
          assertNotNull(instance.getProcess("echoPrint"));
          assertNotNull(instance.getTable("echoScan"));
@@ -165,12 +179,31 @@ class EchoDemoStartupTest
          assertFalse(scanner.hasPermission("printing_admin") || scanner.hasPermission("document-generation.publish"));
          assertTrue(admin.hasPermission("printing_admin") && admin.hasPermission("document-generation.publish"));
          assertFalse(stranger.hasPermission("echo.use") || stranger.hasPermission("printing_operator"));
+         assertTrue(admin.hasPermission("record-files.release"));
+         assertFalse(scanner.hasPermission("record-files.release") || stranger.hasPermission("record-files.release"));
+         assertFalse(admin.hasPermission("record-files.configure") || admin.hasPermission("record-files.review"));
+         // Revalidation keeps the role derived from the validated user, never widening or dropping it.
+         assertTrue(EchoDemoAuthentication.grant(instance, admin).hasPermission("record-files.release"));
+         assertFalse(EchoDemoAuthentication.grant(instance, scanner).hasPermission("record-files.release"));
 
          HttpResponse<String> version = send(port, "/printing/v1/version", null, null);
          assertEquals(200, version.statusCode());
          assertTrue(version.body().contains("protocolVersion"));
          assertNotEquals(200, send(port, "/qqq/v1/metaData", null, null).statusCode());
          assertEquals(200, login(port, "scanner", SCANNER_PASSWORD).statusCode());
+         HttpResponse<String> metadata = send(port, "/qqq/v1/metaData/table/testOrder", null, null);
+         assertEquals(200, metadata.statusCode());
+         assertTrue(metadata.body().contains("Order overview") && metadata.body().contains("associatedTableName"));
+         HttpResponse<String> page = send(port, "/qqq/v1/table/testOrder/query", null,
+            "{\"filter\":{\"skip\":25,\"limit\":25,\"orderBys\":[{\"fieldName\":\"id\",\"isAscending\":true}]}}");
+         assertEquals(200, page.statusCode());
+         assertTrue(page.body().contains("TEST-000026"));
+         assertFalse(page.body().contains("TEST-000001"));
+         HttpResponse<String> children = send(port, "/qqq/v1/table/testOrderItem/query", null,
+            "{\"filter\":{\"limit\":10,\"criteria\":[{\"fieldName\":\"orderId\",\"operator\":\"EQUALS\",\"values\":[26]}]}}");
+         assertEquals(200, children.statusCode());
+         assertTrue(children.body().contains("ITEM-000301"));
+         assertFalse(children.body().contains("ITEM-000001"));
          assertNotEquals(200, login(port, "scanner", "not-the-password-1").statusCode());
 
          assertEquals(0, renderer.calls.get());
@@ -203,6 +236,64 @@ class EchoDemoStartupTest
 
 
 
+   /***************************************************************************
+    ** Disposable real-server fixture for native record browsing acceptance.
+    ** Requires a fresh temporary directory; never accepts a database to adopt.
+    ***************************************************************************/
+   public static void main(String[] args) throws Exception
+   {
+      if(!"rich-records-e2e".equals(System.getenv("ECHO_FIXTURE_TYPE")))
+      {
+         throw new IllegalArgumentException("An isolated record fixture is required.");
+      }
+      int port = Integer.parseInt(args[0]);
+      if(port < 1024 || PROTECTED.contains(port))
+      {
+         throw new IllegalArgumentException("Protected runtime port.");
+      }
+      System.setProperty("qqq.logger.logSessionId.disabled", "true");
+      Path directory = Files.createTempDirectory("qqq-rich-records-");
+      EchoDemoSettings settings = new EchoDemoSettings(directory, port, "rich-records-test", TOKEN, false, null, null);
+      EchoDemo demo = new EchoDemo(settings, new RefusingRenderer());
+      Runtime.getRuntime().addShutdownHook(new Thread(demo::close));
+      demo.initializeDatabase(System.getenv("ECHO_FIXTURE_SCANNER_PASSWORD"), System.getenv("ECHO_FIXTURE_ADMIN_PASSWORD"));
+      seedPreviewPhotos(demo.defineQInstance(), System.getenv("ECHO_FIXTURE_ADMIN_PASSWORD"));
+      demo.start(port);
+   }
+
+
+
+   /***************************************************************************
+    ** Synthetic approved images exist only in the disposable native fixture.
+    ** A second parent's image makes accidental unscoped gallery reads detectable.
+    ***************************************************************************/
+   private static void seedPreviewPhotos(QInstance instance, String password) throws Exception
+   {
+      QContext.setQInstance(instance);
+      String basic = Base64.getEncoder().encodeToString(("admin:" + password).getBytes(StandardCharsets.UTF_8));
+      QSession session = new EchoDemoAuthentication().createSession(instance, Map.of(TableBasedAuthenticationModule.BASIC_AUTH_KEY, basic))
+         .withPermission("record-files.release").withSecurityKeyValue("qqq.session.userId", "admin");
+      QContext.init(instance, session);
+      try(ByteArrayOutputStream output = new ByteArrayOutputStream())
+      {
+         ImageIO.write(new BufferedImage(16, 16, BufferedImage.TYPE_INT_RGB), "jpg", output);
+         byte[] bytes = output.toByteArray();
+         String hash = HexFormat.of().formatHex(MessageDigest.getInstance("SHA-256").digest(bytes));
+         for(int parent : new int[] {26, 27})
+         {
+            var file = new RetainedFileService().intake(new IntakeRequest("preview-" + parent, MobileTestData.ORDERS, parent,
+               "Preview example " + parent + ".jpg", hash).withContentType("image/jpeg"), new ByteArrayInputStream(bytes));
+            new FileReviewService().release(file.id(), "Synthetic native preview fixture");
+         }
+      }
+      finally
+      {
+         QContext.clear();
+      }
+   }
+
+
+
    /***************************************************************************
     ** One loopback request; a body makes it a JSON POST.
     ***************************************************************************/

examples/echo/demo/src/test/java/com/kingsrook/examples/echo/demo/EchoPhotoCaptureTest.java

@@ -169,8 +169,11 @@ class EchoPhotoCaptureTest
 
          RecordFilesQBitConfig config = (RecordFilesQBitConfig) instance.getQBits().values().stream().map(bit -> bit.getConfig())
             .filter(RecordFilesQBitConfig.class::isInstance).findFirst().orElseThrow();
-         assertEquals(List.of(EchoQBitProducer.SCAN_TABLE), config.getParentTables());
+         assertEquals(List.of(EchoQBitProducer.SCAN_TABLE, MobileTestData.ORDERS, MobileTestData.ITEMS, MobileTestData.EVENTS), config.getParentTables());
          assertEquals(Set.of("image/jpeg", "image/png"), config.getUploadConfiguration().limits().acceptedMediaTypes());
+         assertEquals(Boolean.FALSE, config.getQuarantineCapturedFiles(), "approved-device captures are admitted immediately");
+         assertEquals(Boolean.TRUE, config.getQuarantineNewFiles(), "every other origin keeps the quarantine default");
+         assertNull(config.getQuarantineGeneratedFiles(), "the generated-output policy is unchanged");
          assertTrue(config.getUploadConfiguration().createIdentityProvider() instanceof MobileCaptureIdentityProvider);
          assertTrue(config.getUploadConfiguration().createStorage() instanceof LocalStagingChunkStorage);
 

examples/echo/demo/src/test/java/com/kingsrook/examples/echo/demo/MobileTestDataTest.java

@@ -0,0 +1,63 @@
+/*
+ * Copyright (c) 2026 Kingsrook, LLC
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+package com.kingsrook.examples.echo.demo;
+
+
+import java.sql.DriverManager;
+import java.util.UUID;
+import com.kingsrook.qqq.backend.core.model.metadata.QInstance;
+import org.junit.jupiter.api.Test;
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+
+
+/*******************************************************************************
+ ** Fixture volume, relationships, variety and preserving reapplication on H2.
+ *******************************************************************************/
+class MobileTestDataTest
+{
+   /***************************************************************************
+    ** Every section uses real fields and every child belongs to one test order.
+    ** Existing fixture values survive repeated startup, just like attachments.
+    ***************************************************************************/
+   @Test
+   void seedsRichRelatedRecordsWithoutReplacingExistingRows() throws Exception
+   {
+      QInstance instance = new QInstance();
+      MobileTestData.register(instance);
+      var table = instance.getTable(MobileTestData.ORDERS);
+      assertEquals(39, table.getFields().size());
+      assertEquals(6, table.getSections().size());
+      assertEquals(2, table.getAssociations().size());
+      assertTrue(table.getSections().stream().flatMap(section -> section.getFieldNames().stream()).allMatch(table.getFields()::containsKey));
+      try(var connection = DriverManager.getConnection("jdbc:h2:mem:" + UUID.randomUUID() + ";DATABASE_TO_UPPER=FALSE"); var statement = connection.createStatement())
+      {
+         MobileTestData.initialize(connection, instance);
+         statement.executeUpdate("UPDATE testOrder SET notes = 'Retain this value' WHERE id = 1");
+         MobileTestData.initialize(connection, instance);
+         for(String name : MobileTestData.TABLES)
+         {
+            try(var rows = statement.executeQuery("SELECT COUNT(*) FROM " + name))
+            {
+               rows.next();
+               assertEquals(name.equals(MobileTestData.ORDERS) ? 1000 : name.equals(MobileTestData.ITEMS) ? 12000 : 3000, rows.getInt(1));
+            }
+         }
+         try(var rows = statement.executeQuery("SELECT notes, customerCode, optionalNote FROM testOrder WHERE id = 1"))
+         {
+            rows.next();
+            assertEquals("Retain this value", rows.getString(1));
+            assertEquals("00000001", rows.getString(2));
+            assertEquals("Optional example 1", rows.getString(3));
+         }
+         try(var rows = statement.executeQuery("SELECT COUNT(*) FROM testOrderItem i JOIN testOrder o ON i.orderId = o.id WHERE o.id = 26"))
+         {
+            rows.next();
+            assertEquals(12, rows.getInt(1));
+         }
+      }
+   }
+}

examples/echo/demo/src/test/java/com/kingsrook/examples/echo/demo/PrivateObjectFilesTest.java

@@ -8,16 +8,24 @@ package com.kingsrook.examples.echo.demo;
 
 import java.io.ByteArrayInputStream;
 import java.io.IOException;
+import java.io.InputStream;
 import java.nio.file.FileAlreadyExistsException;
 import java.nio.file.Files;
 import java.nio.file.Path;
 import java.util.Map;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.ExecutionException;
+import java.util.concurrent.ExecutorService;
+import java.util.concurrent.Executors;
+import java.util.concurrent.Future;
+import java.util.concurrent.TimeUnit;
 import java.util.stream.Stream;
 import org.junit.jupiter.api.Test;
 import org.junit.jupiter.api.io.TempDir;
 import static org.junit.jupiter.api.Assertions.assertArrayEquals;
 import static org.junit.jupiter.api.Assertions.assertEquals;
 import static org.junit.jupiter.api.Assertions.assertFalse;
+import static org.junit.jupiter.api.Assertions.assertInstanceOf;
 import static org.junit.jupiter.api.Assertions.assertNotEquals;
 import static org.junit.jupiter.api.Assertions.assertThrows;
 import static org.junit.jupiter.api.Assertions.assertTrue;
@@ -109,6 +117,147 @@ class PrivateObjectFilesTest
 
 
 
+   /***************************************************************************
+    ** Dot path segments are not buckets; ordinary names containing dots are.
+    ***************************************************************************/
+   @Test
+   void dotBucketsAreRefusedAndValidBucketsStillWork() throws IOException
+   {
+      PrivateObjectFiles files = new PrivateObjectFiles(root);
+      assertThrows(IllegalArgumentException.class, () -> files.file(".", "k"));
+      assertThrows(IllegalArgumentException.class, () -> files.file("..", "k"));
+      assertThrows(IllegalArgumentException.class, () -> files.create("..", "k", bytes("x"), 1024, Map.of()));
+
+      assertTrue(files.file("canonical", "k").normalize().startsWith(root.resolve("canonical")));
+      assertTrue(files.file("a.b-c_d", "k").normalize().startsWith(root.resolve("a.b-c_d")));
+      assertTrue(files.file("..x", "k").normalize().startsWith(root.resolve("..x")));
+      files.create("canonical", "k", bytes("ok"), 1024, Map.of("a", "b"));
+      assertEquals(Map.of("a", "b"), files.find("canonical", "k").orElseThrow().metadata());
+   }
+
+
+
+   /***************************************************************************
+    ** A stream that, on its first read, reports that its writer is inside the
+    ** write path and then waits until the test releases that writer.
+    ***************************************************************************/
+   private static InputStream gated(String value, CountDownLatch entered, CountDownLatch release)
+   {
+      ByteArrayInputStream delegate = bytes(value);
+      return new InputStream()
+      {
+         private boolean first = true;
+
+
+
+         @Override
+         public int read() throws IOException
+         {
+            gate();
+            return delegate.read();
+         }
+
+
+
+         @Override
+         public int read(byte[] buffer, int offset, int length) throws IOException
+         {
+            gate();
+            return delegate.read(buffer, offset, length);
+         }
+
+
+
+         private void gate() throws IOException
+         {
+            if(first)
+            {
+               first = false;
+               entered.countDown();
+               try
+               {
+                  if(!release.await(30, TimeUnit.SECONDS))
+                  {
+                     throw new IOException("Test writer was never released");
+                  }
+               }
+               catch(InterruptedException failure)
+               {
+                  Thread.currentThread().interrupt();
+                  throw new IOException(failure);
+               }
+            }
+         }
+      };
+   }
+
+
+
+   /***************************************************************************
+    ** Two adapters over one root write the same key with different bytes and
+    ** metadata. Both pass the initial existence check and block in their streams;
+    ** the first is released and completes, then the second is released and must
+    ** be refused at the final existence check without touching the first's
+    ** bytes or metadata (the old code replaced the metadata before failing).
+    ***************************************************************************/
+   @Test
+   void lateSecondWriterIsRefusedAndFirstWritersBytesAndMetadataRemain() throws Exception
+   {
+      PrivateObjectFiles first = new PrivateObjectFiles(root);
+      PrivateObjectFiles second = new PrivateObjectFiles(root);
+      CountDownLatch enteredOne = new CountDownLatch(1);
+      CountDownLatch enteredTwo = new CountDownLatch(1);
+      CountDownLatch releaseOne = new CountDownLatch(1);
+      CountDownLatch releaseTwo = new CountDownLatch(1);
+      ExecutorService executor = Executors.newFixedThreadPool(2);
+      try
+      {
+         Future<?> one = executor.submit(() ->
+         {
+            first.create("canonical", "same", gated("content-from-one", enteredOne, releaseOne), 1024, Map.of("writer", "one"));
+            return null;
+         });
+         Future<?> two = executor.submit(() ->
+         {
+            second.create("canonical", "same", gated("content-from-two-longer", enteredTwo, releaseTwo), 1024, Map.of("writer", "two"));
+            return null;
+         });
+
+         // both writers are past their initial existence check and blocked in their streams
+         assertTrue(enteredOne.await(30, TimeUnit.SECONDS), "first writer should enter the write path");
+         assertTrue(enteredTwo.await(30, TimeUnit.SECONDS), "second writer should enter the write path");
+
+         // first finishes completely while second stays blocked
+         releaseOne.countDown();
+         one.get(30, TimeUnit.SECONDS);
+         assertFalse(two.isDone(), "second writer must still be blocked in its stream");
+
+         // second now reaches publication with an object already in place and must refuse
+         releaseTwo.countDown();
+         ExecutionException failure = assertThrows(ExecutionException.class, () -> two.get(30, TimeUnit.SECONDS));
+         assertInstanceOf(FileAlreadyExistsException.class, failure.getCause());
+
+         var stored = first.find("canonical", "same").orElseThrow();
+         assertEquals("content-from-one", Files.readString(stored.file()));
+         assertEquals(Map.of("writer", "one"), stored.metadata());
+         assertEquals(stored.metadata(), second.find("canonical", "same").orElseThrow().metadata());
+      }
+      finally
+      {
+         releaseOne.countDown();
+         releaseTwo.countDown();
+         executor.shutdownNow();
+         assertTrue(executor.awaitTermination(30, TimeUnit.SECONDS));
+      }
+
+      try(Stream<Path> all = Files.walk(root))
+      {
+         assertFalse(all.anyMatch(path -> path.getFileName().toString().startsWith(".incoming-")));
+      }
+   }
+
+
+
    /***************************************************************************
     ** Delete removes the object and its metadata; absent is not an error.
     ***************************************************************************/

examples/echo/docs/SESSION-STATE.md

@@ -1,23 +1,5 @@
 # Echo session state
 
-November 1, 2026: optional example source is being implemented under this directory only. Echo registers ordinary setup and scanner-loop process metadata, uses current approved-device attribution and canonical persisted scan context, and delegates generation/retention/printing to existing QBits. Its state store admits one event, preserves uncertain identities and refuses silent reprint. Core protected process identity, exact media/template revision and owner read-only acceptance seams are under coordinated implementation; no physical printer or peer service has been touched.
+Echo status is tracked with the rest of the project in [session state](../../../docs/SESSION-STATE.md), so there is a single current record. For what Echo does and does not support, read the [Echo README](../README.md) and its [fidelity limits](../README.md#fidelity-and-limits).
 
-Initial private offline build stopped on an unavailable aggregate JUnit artifact; dependency declarations now use the already available split API/engine. Current compilation and focused H2/process tests remain pending. There is no runnable fully wired demo or production-release claim. See [TODO](TODO.md) for remaining acceptance.
-
-Verification now passes14 real QQQ USER process/mobile-approval/H2 tests, zero failures/errors/skips, and zero Checkstyle violations, against the qualified protected-process SDK4.1.0-pu.507b0d21e09d7eebb76782d14660483c45c77b11 and scanner facade JAR9A5728B7…. Tests cover setup once, two-type exact-value loop, canonical receipt, changed-type retry refusal, uncertain/crashed read-only receipt adoption without re-enqueue, deterministic in-flight concurrency, post-setup cancellation, same-user run substitution, media drift/too-small plan and enforced native source reads including forged reserved keys. Destination/layout/generation fixtures are synthetic; no real renderer, owner adapter, Android or physical-print acceptance is implied. Private evidence is under Ccache/qqq-echo-final-verify-e3929445f6a144e889ba12d90e4c7efb. The unqualified generation API dependency is compile-only provenance, not release adoption.
-
-Final packaging follow-up: module-directory wrapper verification passes15 tests (including canonical cross-run replay refusal), zero failures/errors/skips, zero Checkstyle violations and deprecation/unchecked warnings-as-errors. Apache license metadata is present in the POM; the JAR contains byte-identical existing repository LICENSE/NOTICE under META-INF/qqq-echo and unchanged db/echo-h2.sql. No duplicate license source files were introduced. Real adapters, hosted integration and physical printing remain pending.
-
-## Semantic scanner presentation companion
-
-Echo now supplies acknowledgmentLabel=Print queued and manualEntryEnabled=false through the registered scanner extension 1.4. The companion Android implementation passes 167 JVM cases, strict compilation and lint with zero errors/warnings. The server passes 69 consumer cases plus two contract-generation cases. Echo's 15 strict process/state tests also pass against the qualified 1.4 scanner artifact. This remains synthetic owner-port qualification; actual pinned rendering, media/profile propagation, native Echo UI and physical output still require owner handoffs and acceptance.
-
-2026-11-01: Added test-scope EchoHttpFixture + actual semantic HTTP smoke, reusing the qualified demo artifact, TABLE auth and mobile routes. No production row lock or service changed. UI fixture has random in-memory state and unmistakable simulated printing branding. Real HTTP retry exposed database precision changes in server receivedAt; removed that observation timestamp from print intent comparison while preserving the first persisted observation. Canonical scan identity, payload/type/source/capture/run bindings remain enforced. Final fixture verification pending; old qualified Echo15 proof is retained.
-
-Fixture verification: private qqq-echo-http-fixture-e66c4b1bc35a434a8e668fa7cff49dd8, strict16/0/0/0 +Checkstyle0 PASS. Snapshot includes compiled test/main classes, fixture-java.args and source provenance. HTTP test stops its listener cleanly; no device or physical print run. Native execution is the next independent gate.
-
-2026-11-01 13:15 local: Split only EchoScan reads from approved-device capture. EchoSourceReadPermissions admits current nonblank actor + echo.use for native Get/Query/Count/Aggregate and metadata discovery; native actor RecordSecurityLock remains unchanged and direct writes remain denied. Echo app/widget/process/capture and test-only run inspection retain the approved-device checker. Original-actor desktop read after run close succeeds without mobile.scan/device scope; revoked Echo grant, anonymous actor, different actor with spoofed reserved security key, direct update/delete and desktop capture/process attempts fail. EchoTest17/0fail/0error/0skip, Checkstyle0 and strict Java21 package PASS against core pu.507b0d21 + mobile1.4 FDDB118A; evidence source-read-split.log in the private Echo HTTP fixture cache. Frozen native fixture classes/args were not replaced.
-
-Critical path: qualify this split's HTTP companion, finish frozen native TC22 UI gate, then compose a production adapter only after reviewed owner media-capability/adoption + exact-pinned template/stock/media + read-only acceptance lookup handoffs. Printing must qualify current original-actor/source reauthorization before pending delivery/retry bytes release. Actual rendering/physical label fidelity and rescan are still unqualified; simulated fixture receipts do not satisfy them.
-
-Companion semantic HTTP smoke1/0/0/0 +Checkstyle0 PASS after the split (source-read-http.log). Combined bounded cohort18 tests passes; original frozen UI fixture bundle is unchanged.
+The earlier Echo-only log (November 1) is archived unchanged in [history](../../../docs/history/ECHO-SESSION-STATE-through-2026-11-04.md).

examples/echo/docs/TODO.md

@@ -1,44 +1,9 @@
 # Echo remaining work
 
-## Current checkpoint — November 2, copies live
+Open items only, as of 2026-11-04. Project-wide open work is in the [TODO](../../../docs/TODO.md); the earlier Echo ledger, with its completed items, is archived in [history](../../../docs/history/ECHO-TODO-through-2026-11-04.md).
 
-- [x] Printer, paper/label size and Document selection, real installed Printing client connection and 4x1 document publication are complete on the normal local server57832.
-- [x] Copies per scan is optional, defaults to 1 and accepts 1–100; pinned for the run and carried as one job's copy quantity. Null/blank/default, selected 3, mutation refusal, retry identity and additive migration tests pass.
-- [x] Root gates pass: 68 Echo and 35 composed demo tests; 377 unique tests including the Generation/Printing/scanner/files dependencies across verified module runs.
-- [x] Real TC22 semantic acceptance passes ten stages/116 requests using simulated scans and printing. The normal connected TC22 is left on setup showing Copies per scan = 1; normal server advertises mobile1.5.
-- [ ] Physical quantity, trigger/print/rescan and AIM/EAN/UPC fidelity checks remain unqualified. The operator is remote.
-- [ ] Canonical Generation copies adoption/publication and coherent public CI remain pending; qualified local source/handoff lives in C:/Users/james/.cache/qqq-generation-copies-20261102 and qqq-generation-copies-handoff.md.
-
-The older ledger below is historical; its unrun-test, setup and mobile1.4 notes are superseded by this checkpoint.
-
-- [ ] Root gate for the required Document choice (printer, paper or label size, then Document at run start; see DOCUMENT-CHOICE-HANDOFF.md): module and demo verify, then on-device check that the generic form shows the dependent Document field.
-
-Verified by root (2026-11-02): module `verify` 33 tests, Checkstyle 0, against the complete private cohort `0.1.0-echo.gen64c9pu507`. Runnable demo `verify` 22 tests, Checkstyle 0, including the composed acceptance below, with the real new Echo read checker and the renderer owner's TL1 factory (52 owner tests pass, no copied transport). A local demo run was observed live on an ephemeral loopback port (scanner and admin native login and metadata 200). No printer or template on it, and no physical printing.
-
-## Done
-
-- [x] Process, state, mobile-approval and H2 tests against the protected-process-identity core API; concurrency, crash recovery, cancellation and run-substitution regressions.
-- [x] Test-only isolated semantic HTTP fixture (simulated printing) and split read-only `echoScan` permission with actor-lock, revoked, anonymous and write negatives; the read rule also accepts Collaboration's and Record Files' plain capability probe for sessions with `echo.use`.
-- [x] Owner adapters from actual public APIs: authorized printer/media from Printing, exact pinned template/revision/stock/media generation, read-only accepted-print lookup, `QUEUED` only for a durable available receipt.
-- [x] Media choices filtered by the selected printer through the semantic dependency value.
-- [x] Host composition `EchoHost.install` using `PrintingDispatch.forOwnerMediaEnforcement(source)`.
-- [x] Publisher scene reviewed against the worker source and owner fixture shape; EAN13/EAN8/UPCA/UPCE0 refused before admission; six types admitted.
-- [x] Runnable demo module and the owner's trusted-local renderer factory integration.
-- [x] **Clean composed acceptance** (demo `EchoDemoAcceptanceTest`): authenticated approved scanner, real `echoPrint`, real Generation, Record Files retention and Printing job acceptance; two scans give two retained originals and two accepted jobs on one printer, a retry gives the same job, and leaving closes the run. Controlled synthetic renderer and simulated Printing queue; not physical.
-
-## Open
-
-- [ ] Actual native Printing client (Windows agent) connection to the composed server and the current stock/media handoff.
-- [ ] Publish the ZPL template through the real renderer, then preview and independently decode Code 128 and a leading-zero QR (`001234567890`) at 4 x 6 in / 300 dpi.
-- [ ] Real-server native TC22 run: setup once, scan twice, rotate/recreate, leave; one stable print identity after transport loss.
-- [ ] Physical print and TC22 rescan with exact value, symbology, quiet zones and stock dimensions; native Printing acceptance. A queue acknowledgment is not paper.
-- [x] Source: AIM persistence (`echo_scan.aimIdentifier`), EAN13/EAN8/UPCA/UPCE0 validation, and a scanner-fidelity document through the renderer's scanner mode; candidate Android AIM output profile (`AimOutputProfile`, driver config/readback/restore). Not yet run (root builds) and not physically qualified.
-- [x] Source: Copies per scan (setup field, server-pinned `echo_run.copies`, scan-stage forgery refusal, widget text). Library tests added, not run.
-- [x] Source: copies reach Generation's request and the accepted-lookup binding (needs the Generation copies cohort from `C:/Users/james/.cache/qqq-generation-copies-handoff.md`, unbuilt). Optional field with 1..100 core limits and real HTTP tests for default 1, chosen 3 and mutation rejection; not run.
-- [ ] Root gate with the Generation copies cohort, the `20261102-print-copies-h2.sql` migration in the demo's `GENERATION_MIGRATIONS`, a Printing owner that honors `options.copies`, and a physical count check on the printer.
-- [ ] TC22 pulls proving what `getData()` and `getRawData()` contain under `codeIdType=AIM`, then a physical EAN/UPC scan, print and rescan on the scanner-fidelity document. Normal server 1.5 adoption (the live server is 1.4 and drops AIM and raw bytes).
-- [ ] GS1, ECI, structured, binary and non-ASCII payloads stay refused: the existing public renderer has no scanner-mode profile for them (see `C:/Users/james/.cache/qqq-finish-barcode-handoff.md`).
-- [ ] Original-actor source reauthorization policy confirmed for delayed byte release (Printing retained source authority).
-- [ ] Deployment: Windows agent exposing `printer-media-v1`, ZPL printer, tenant, operator permissions without `printing_admin` (the scanner never receives it).
-- [ ] Public immutable SDK publication, Gitea CI and distribution, then signing, last. The private cohort is unpublished; PR 7 is on Gitea and earlier GitHub references are historical.
-- [ ] Release and production readiness: not done and not claimed.
+- [ ] Public, coherent Generation, Printing and Record Files bridge, Record Files and Scripting artifacts from their owner (including Generation copies support), then pin them in both Echo POMs in a reviewed change. No public version is known yet; do not guess coordinates.
+- [ ] Decide whether to support or keep refusing GS1, ECI, structured and binary payloads. They are refused because the public renderer has no scanner-mode profile for them ([limits](../README.md#fidelity-and-limits)).
+- [ ] Optional per-case evidence for physical label count, AIM and EAN/UPC fidelity on a future run. The November 4 operator report (all manual tests pass) is accepted and not to be requested again.
+- [ ] Confirm the Printing owner's original-actor source reauthorization policy for delayed byte release.
+- [ ] Signed-build HTTPS device qualification and distribution, last, by the user's decision (the signed APK and channel exist). Echo is an example and is not claimed production-ready.

examples/echo/pom.xml

@@ -16,14 +16,15 @@
    <properties>
       <maven.compiler.release>21</maven.compiler.release>
       <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-      <qqq.version>4.1.0-RC.21</qqq.version>
+      <qqq.version>4.1.0-RC.26</qqq.version>
       <mobile.version>0.1.0-SNAPSHOT</mobile.version>
       <!-- Echo's copies per scan needs a Generation build with the print-copies change (appended copies on
            DocumentGenerationService.Request and GenerationPorts.PrintRequest, supportsCopies on the printing bridge,
-           migration 20261102-print-copies-h2.sql). Until that is published at this coordinate, override
-           generation.version and printing.version with a coherent build that has it; no private build is named here. -->
-      <generation.version>0.1.0-SNAPSHOT</generation.version>
-      <printing.version>0.4.0-SNAPSHOT</printing.version>
+           migration 20261102-print-copies-h2.sql). Printing 1.0.0 is released and qualified; only the Generation
+           cohort still needs a coherent published input. Until that is published at this coordinate, override
+           generation.version with a coherent build that has it; no private build is named here. -->
+      <generation.version>1.1.0-RC.1</generation.version>
+      <printing.version>1.2.0-RC.1</printing.version>
    </properties>
    <dependencyManagement><dependencies>
       <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-bom-pom</artifactId><version>${qqq.version}</version><type>pom</type><scope>import</scope></dependency>
@@ -36,14 +37,15 @@
       <dependency><groupId>com.kingsrook.qbits</groupId><artifactId>qbit-document-generation-record-files</artifactId><version>${generation.version}</version></dependency>
       <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-backend-module-rdbms</artifactId></dependency>
       <dependency><groupId>com.h2database</groupId><artifactId>h2</artifactId><version>2.2.224</version><scope>test</scope></dependency>
+      <dependency><groupId>org.postgresql</groupId><artifactId>postgresql</artifactId><version>42.7.8</version><scope>test</scope></dependency>
       <dependency><groupId>org.junit.jupiter</groupId><artifactId>junit-jupiter-api</artifactId><version>6.0.2</version><scope>test</scope></dependency>
       <dependency><groupId>org.junit.jupiter</groupId><artifactId>junit-jupiter-engine</artifactId><version>6.0.2</version><scope>test</scope></dependency>
-      <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-frontend-next</artifactId><version>1.0.0-RC.35</version><scope>test</scope></dependency>
+      <dependency><groupId>com.kingsrook.qqq</groupId><artifactId>qqq-frontend-next</artifactId><version>1.0.0-RC.38</version><scope>test</scope></dependency>
       <dependency><groupId>com.kingsrook.qbits</groupId><artifactId>qbit-mobile-scanners-demo</artifactId><version>${mobile.version}</version><scope>test</scope></dependency>
    </dependencies>
    <build><resources><resource><directory>src/main/resources</directory><filtering>false</filtering></resource><resource><directory>${project.basedir}/../..</directory><filtering>false</filtering><includes><include>LICENSE</include><include>NOTICE</include></includes><targetPath>META-INF/qqq-echo</targetPath></resource></resources><plugins>
       <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-compiler-plugin</artifactId><version>3.13.0</version><configuration><showWarnings>true</showWarnings><failOnWarning>true</failOnWarning><proc>none</proc><compilerArgs><arg>-Xlint:deprecation</arg><arg>-Xlint:unchecked</arg><arg>-Werror</arg></compilerArgs></configuration></plugin>
-      <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId><version>3.5.2</version></plugin>
+      <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId><version>3.5.6</version></plugin>
       <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-checkstyle-plugin</artifactId><version>3.6.0</version><dependencies><dependency><groupId>com.puppycrawl.tools</groupId><artifactId>checkstyle</artifactId><version>14.3.0</version></dependency></dependencies><configuration><configLocation>${project.basedir}/../../checkstyle/checkstyle.xml</configLocation><includeTestSourceDirectory>true</includeTestSourceDirectory><failOnViolation>true</failOnViolation><violationSeverity>warning</violationSeverity></configuration><executions><execution><phase>validate</phase><goals><goal>check</goal></goals></execution></executions></plugin>
    </plugins></build>
 </project>

examples/echo/src/main/java/com/kingsrook/examples/echo/EchoGs1.java

@@ -0,0 +1,115 @@
+/*
+ * Copyright (c) 2026 Kingsrook, LLC
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+package com.kingsrook.examples.echo;
+
+
+import java.util.Map;
+import com.kingsrook.qqq.backend.core.exceptions.QException;
+
+
+/*******************************************************************************
+ ** Bounded GS1-128 element-string profile. Original scan bytes remain unchanged.
+ ** Fixed-length identifiers need no separator; variable fields end only at GS
+ ** or end of input. Never guess an AI boundary from digits inside a value.
+ ** Source: GS1 General Specifications, element strings and predefined lengths.
+ *******************************************************************************/
+final class EchoGs1
+{
+   private static final char SEPARATOR = 29;
+   private static final Map<String, Integer> FIXED = Map.ofEntries(
+      Map.entry("00", 18), Map.entry("01", 14), Map.entry("02", 14),
+      Map.entry("11", 6), Map.entry("12", 6), Map.entry("13", 6),
+      Map.entry("15", 6), Map.entry("16", 6), Map.entry("17", 6), Map.entry("20", 2));
+   private static final Map<String, Integer> VARIABLE = Map.of("10", 20, "21", 20, "30", 8, "37", 8);
+
+
+
+   /***************************************************************************
+    ** Utility class.
+    ***************************************************************************/
+   private EchoGs1()
+   {
+   }
+
+
+
+   /***************************************************************************
+    ** Convert the supported AIs to canonical encoder input and printed HRI.
+    ** The renderer independently validates canonical GS1 before producing bytes.
+    ***************************************************************************/
+   static Value parse(String value) throws QException
+   {
+      if(value == null || value.isEmpty() || value.length() > 48
+         || value.chars().anyMatch(c -> (c < 32 && c != SEPARATOR) || c > 126 || c == '[' || c == ']' || c == '\\'))
+      {
+         throw refusal();
+      }
+      StringBuilder canonical = new StringBuilder();
+      StringBuilder readable = new StringBuilder();
+      int offset = 0;
+      while(offset < value.length())
+      {
+         if(offset + 2 > value.length())
+         {
+            throw refusal();
+         }
+         String ai = value.substring(offset, offset + 2);
+         Integer fixed = FIXED.get(ai);
+         Integer maximum = VARIABLE.get(ai);
+         if(fixed == null && maximum == null)
+         {
+            throw new QException("This GS1 application identifier is not in the qualified Echo profile. No print was requested.");
+         }
+         offset += 2;
+         int end = fixed == null ? value.indexOf(SEPARATOR, offset) : offset + fixed;
+         if(end < 0)
+         {
+            end = value.length();
+         }
+         if(end > value.length() || end == offset || (maximum != null && end - offset > maximum))
+         {
+            throw refusal();
+         }
+         String data = value.substring(offset, end);
+         boolean numeric = fixed != null || "30".equals(ai) || "37".equals(ai);
+         if(data.indexOf(SEPARATOR) >= 0 || (numeric && !data.chars().allMatch(c -> c >= '0' && c <= '9')))
+         {
+            throw refusal();
+         }
+         canonical.append('[').append(ai).append(']').append(data);
+         readable.append('(').append(ai).append(')').append(data);
+         offset = end;
+         if(offset < value.length() && value.charAt(offset) == SEPARATOR)
+         {
+            // Refuse redundant/trailing separators instead of silently changing the scan. //
+            if(fixed != null || ++offset == value.length())
+            {
+               throw refusal();
+            }
+         }
+      }
+      return new Value(canonical.toString(), readable.toString());
+   }
+
+
+
+   /***************************************************************************
+    ** A safe refusal carries no barcode contents.
+    ***************************************************************************/
+   private static QException refusal()
+   {
+      return new QException("The GS1-128 payload is outside the qualified profile or has invalid field boundaries. No print was requested.");
+   }
+
+
+
+   /***************************************************************************
+    ** Derived output, never a replacement for the original persisted barcode.
+    ***************************************************************************/
+   record Value(String canonical, String readable)
+   {
+   }
+}

examples/echo/src/main/java/com/kingsrook/examples/echo/EchoPermissions.java

@@ -10,10 +10,14 @@ import com.kingsrook.qqq.backend.core.actions.permissions.CustomPermissionChecke
 import com.kingsrook.qqq.backend.core.context.QContext;
 import com.kingsrook.qqq.backend.core.exceptions.QPermissionDeniedException;
 import com.kingsrook.qqq.backend.core.model.actions.AbstractActionInput;
+import com.kingsrook.qqq.backend.core.model.actions.metadata.MetaDataInput;
+import com.kingsrook.qqq.backend.core.model.actions.metadata.ProcessMetaDataInput;
 import com.kingsrook.qqq.backend.core.model.actions.tables.delete.DeleteInput;
 import com.kingsrook.qqq.backend.core.model.actions.tables.insert.InsertInput;
 import com.kingsrook.qqq.backend.core.model.actions.tables.update.UpdateInput;
+import com.kingsrook.qqq.backend.core.model.metadata.layout.QAppMetaData;
 import com.kingsrook.qqq.backend.core.model.metadata.permissions.MetaDataWithPermissionRules;
+import com.kingsrook.qqq.backend.core.model.metadata.processes.QProcessMetaData;
 
 
 /*******************************************************************************
@@ -35,7 +39,13 @@ public final class EchoPermissions implements CustomPermissionChecker
          {
             throw new QPermissionDeniedException("Echo access is required; direct state writes are not allowed.");
          }
-         EchoConfig.current().identities.current();
+         // Browsing the application performs no scan or print operation.
+         // Process execution, widget and record access still require approved device authority.
+         boolean processDiscovery = metadata instanceof QProcessMetaData && (action instanceof MetaDataInput || action instanceof ProcessMetaDataInput);
+         if(!(metadata instanceof QAppMetaData) && !processDiscovery)
+         {
+            EchoConfig.current().identities.current();
+         }
       }
       catch(Exception failure)
       {
@@ -43,3 +53,4 @@ public final class EchoPermissions implements CustomPermissionChecker
       }
    }
 }
+

examples/echo/src/main/java/com/kingsrook/examples/echo/EchoPrintingDestinations.java

@@ -118,7 +118,7 @@ public final class EchoPrintingDestinations implements EchoDestinations
       String refusal = refusal(current.mode(), scan);
       if(refusal != null)
       {
-         throw new QException(refusal);
+         throw new EchoScanRejected(refusal);
       }
       return current.plan();
    }
@@ -201,7 +201,7 @@ public final class EchoPrintingDestinations implements EchoDestinations
     ***************************************************************************/
    enum SceneMode
    {
-      PLAIN, SCANNER
+      PLAIN, SCANNER, GS1
    }
 
 
@@ -222,6 +222,13 @@ public final class EchoPrintingDestinations implements EchoDestinations
          for(Object item : scene.getJSONArray("elements"))
          {
             JSONObject element = (JSONObject) item;
+            if("barcode".equals(element.optString("type")) && "gs1-128".equals(element.optString("symbology"))
+               && "/record/rendererValue".equals(element.optString("valuePath"))
+               && !element.has("scannerSymbologyPath") && !element.has("aimIdentifierPath") && !element.has("symbologyPath")
+               && element.has("fit") && hasGs1Text(scene, element))
+            {
+               return SceneMode.GS1;
+            }
             if(!"barcode".equals(element.optString("type")) || !"/record/rendererSymbology".equals(element.optString("symbologyPath"))
                || !"/record/barcode".equals(element.optString("valuePath")) || element.optJSONArray("allowedSymbologies") == null)
             {
@@ -259,19 +266,43 @@ public final class EchoPrintingDestinations implements EchoDestinations
 
 
 
+   /***************************************************************************
+    ** GS1 documents must include the derived human-readable value below the bars.
+    ***************************************************************************/
+   private static boolean hasGs1Text(JSONObject scene, JSONObject barcode)
+   {
+      for(Object item : scene.getJSONArray("elements"))
+      {
+         JSONObject text = (JSONObject) item;
+         if(("text".equals(text.optString("type")) || "rasterText".equals(text.optString("type")))
+            && "/record/humanReadable".equals(text.optString("valuePath"))
+            && text.optInt("y", -1) > barcode.optInt("y", -1))
+         {
+            return true;
+         }
+      }
+      return false;
+   }
+
+
+
    /***************************************************************************
     ** Plain scenes reproduce text only and refuse EAN/UPC outright; the
     ** scanner-fidelity scene needs this scan's AIM identifier. Null means usable.
     ***************************************************************************/
    static String refusal(SceneMode mode, EchoService.Scan scan)
    {
+      if((mode == SceneMode.GS1) != "gs1-128".equals(scan.rendererSymbology()))
+      {
+         return "GS1-128 scans require the GS1-128 document; that document accepts only GS1-128. No print was requested. Scan a barcode matching the selected document.";
+      }
       if(mode == SceneMode.PLAIN && EchoTemplates.SCANNER_SYMBOLOGIES.contains(scan.rendererSymbology()))
       {
-         return "EAN and UPC need the scanner-fidelity document. Leave Echo and choose it; no print was requested.";
+         return "EAN and UPC need the scanner-fidelity document. No print was requested. Scan a barcode matching the selected document.";
       }
       if(mode == SceneMode.SCANNER && scan.aimIdentifier() == null)
       {
-         return "The scanner-fidelity document needs the scanner's AIM identifier and this scan has none. Leave Echo and choose the plain document; no print was requested.";
+         return "The scanner-fidelity document needs the scanner's AIM identifier and this scan has none. No print was requested. Scan a barcode with its AIM identifier.";
       }
       return null;
    }
@@ -319,8 +350,7 @@ public final class EchoPrintingDestinations implements EchoDestinations
          for(Object item : new JSONArray(mediaProfilesJson == null ? "[]" : mediaProfilesJson))
          {
             PrintingMediaProfile profile = PrintingMediaProfile.parse((JSONObject) item);
-            choices.add(new MediaChoice(profile.id(), profile.name() + " (" + String.format(Locale.ROOT, "%.1f x %.1f mm, %d dpi",
-               profile.widthMicrons() / 1000.0, profile.heightMicrons() / 1000.0, profile.dpiX()) + ")"));
+            choices.add(new MediaChoice(profile.id(), mediaLabel(profile)));
          }
       }
       catch(RuntimeException failure)
@@ -332,6 +362,26 @@ public final class EchoPrintingDestinations implements EchoDestinations
 
 
 
+   /***************************************************************************
+    ** Prefer exact quarter-inch stock sizes; other stock retains metric units.
+    ** Keep meaningful printer names without repeating a dimensions-only name.
+    ***************************************************************************/
+   private static String mediaLabel(PrintingMediaProfile profile)
+   {
+      boolean inches = profile.widthMicrons() % 6350 == 0 && profile.heightMicrons() % 6350 == 0;
+      int divisor = inches ? 25400 : 1000;
+      String width = java.math.BigDecimal.valueOf(profile.widthMicrons()).divide(java.math.BigDecimal.valueOf(divisor)).stripTrailingZeros().toPlainString();
+      String height = java.math.BigDecimal.valueOf(profile.heightMicrons()).divide(java.math.BigDecimal.valueOf(divisor)).stripTrailingZeros().toPlainString();
+      String resolution = profile.dpiX() == profile.dpiY() ? String.valueOf(profile.dpiX()) : profile.dpiX() + " × " + profile.dpiY();
+      String name = profile.name().strip();
+      String remainder = name.toLowerCase(Locale.ROOT).replaceAll("\\b(inches|inch|in|mm|label|paper|dpi)\\b", "")
+         .replaceAll("[\\s0-9.,x×()·-]+", "");
+      boolean generic = remainder.isBlank() || List.of("custom", "default", "media", "userdefined", "windowsqueuedefault").contains(remainder);
+      return (generic ? "" : name + " · ") + width + " × " + height + (inches ? " in label · " : " mm label · ") + resolution + " dpi";
+   }
+
+
+
    /***************************************************************************
     ** Select one reported media profile by identity; never guess dimensions.
     ***************************************************************************/