james.maesandCodex
476210ae22
Preserve table search, filters and paging; add grouped details, related-record tabs, formatted values and parent-scoped saved photo previews. Retain upload guards across rotation and support GS1 AIM metadata. Validate with 232 unit tests, clean lint, isolated native semantic acceptance and actual TC22 visual checks. Co-Authored-By: Codex (GPT-6) <noreply@openai.com>
6.6 KiB
Historical checkpoint before the November 5 record UX update. Current state is in session state.
November 5 rich-record preview
The same TC22 app now has grouped fields and direct related-record navigation through standard semantic metadata/query APIs. The maintained Echo demo supplies Test Data: 1,000 orders (39 fields, six sections), 12,000 items and 3,000 history entries. Android unit tests, lint and debug/E2E builds passed. Isolated MC9400 native acceptance passed paging, grouping, filtered child navigation, camera/gallery attachments to order 26, rotation and remote logout cleanup; all requests matched the semantic API. Installed TC22 APK SHA-256: 65FB631F0CFF9B68A0F3FC01D37D656FD69D690F1BA63F8A34FB314A2B03B97F, matching signer and installed bytes verified. Existing app data, enrollment and server address were retained. These source changes remain local/uncommitted; no new release was published. This supersedes the earlier preview/server-selection status below.
November 5 TC22 preview update
At the user's request, the existing TC22 app was updated in place to the local records/photo debug build, with matching signer verified before installation and installed APK SHA-256 79E6CD0559419E059EC253DD0364C13BDDB3C27F566F0DA9A478FBB70D99A038 verified afterward. No uninstall, data clear, separate QA app or server change occurred. Server selection and hands-on record/photo acceptance are pending. The older acceptance evidence below applies to the prior development build.
Current status
As of 2026-11-05. Scope: the scanner host and the local Echo workflow only. This is the authoritative current view; earlier rolling notes are historical and kept in docs/history. Nothing here claims a stable or fully qualified 1.0; a signed preview is published. Checklist: TODO. Ledger: FINISH-1.0.
Local feature verification
Uncommitted GS1 and record-photo work adds permitted-table browsing, record details, and camera/gallery attachments using existing semantic APIs. Android unit tests, lint and debug/E2E builds passed. Disposable MC9400 tests passed synthetic GS1 capture with exact HRI and saved-record browsing, plus record-linked camera/gallery upload, rotation, navigation blocking and remote-logout cleanup. These tests used isolated apps/databases and simulated barcode input/printing. The companion composed server cohort passed 188 tests and Checkstyle; the existing photo-process regression and eight runner guard tests also passed. The ordinary scanner app is unchanged; physical GS1 print/rescan and deployment remain outstanding.
Source
- Protected
maincontains all application work (PR 8 and PR 10 merged). Application source is unchanged by the documentation and signing work after that merge. - The Gitea workflow
.gitea/workflows/qrun-android-release.yamlexists onmain; it calls the shared platform Android workflow and is not a scanner-APK release pipeline (see RELEASING). - Documentation is published separately (signing guide and this reconciliation). Shared CI/CD redesign is outside this repository's local use and does not gate the demo.
Local demo: accepted
- Local server on the workstation (port 57832): public QQQ 4.1.0-RC.21 plus released Printing 1.0 and qualified document, files and scripting owner inputs. UI API 1.10, mobile-scanners 1.5, printing 2.3, mobile-record-files 1.0.
- TC22 runs the development-signed debug APK (version 0.1.0, versionCode 1, SHA-256
38A11155BF6A9C089A1EE6D9E44401E8FF39497B7150B51A85F1F916148BE60D), reaching the server through device port 8080 forwarded to the workstation. - The operator reported the outstanding manual TC22 acceptance group ALL PASS on 2026-11-04, including label count/fidelity, camera and GPS, and screen viewing. This is operator-reported acceptance, not instrumented or per-case evidence; no per-case artifacts are recorded and the checks are not requested again.
- Desktop-browser Authentik acceptance passed with strict TLS (nonce rejection, login, company logout, fresh second operator).
MC9400 (second device)
- A production-signed 1.0.0 (versionCode 2) APK was installed on a fresh MC9400 (Android 13, EMDK present) and launched; installed bytes matched the signed APK hash. No fatal crash at startup.
- At the user's request the MC9400 now runs the same development APK as the TC22 in demo mode, with device port 8080 forwarded to the workstation server over paired wireless ADB. It signed in and was approved through the ordinary mobile device approval process (status APPROVED).
- Remaining check: a physical MC9400 trigger scan confirmed in the backend. Not yet verified; no scan claim is made.
Signed release
- Direct signed-APK / MDM distribution was chosen. A QRun-owned key exists (alias
qqq-mobile-release, certificate SHA-256BDDB2D2F45A5925C643A83ABAF616C1EAB2387DC5CDA7B645A6F4C0D5B17A9FF) with a verified backup. Key, passwords and vault details are not in this repository. - Signed
QQQ-Mobile-1.0.0.apk(versionCode 2, SHA-256EE5AC896B8985AF6F11B2E883955925D6571A2913D74A4AACCDB564B79394D51) exists locally, built frommainapplication source: lint 0 errors/0 warnings, v2/v3 signature with the exact certificate, alignment and non-debuggable verified. - It is published as a signed preview: Gitea prerelease scanner-v1.0.0 (ID 1361, signed tag on protected
main3eef6431ca39b6450cf764424d921a02b2afb9ab; app source matches0ae2101f, the tag adds documentation only). Hosted assets are the APK (14933499 bytes) andSHA256SUMS(88 bytes), both downloaded back and matching the hash above. The local installation kit ZIP was not published. Forge sign-in is required. This is not a stable release. No automatic signing CI is configured, and SDK CI publication is a separate path. - Production qualification (still pending) needs an HTTPS server and a full device pass of the signed build (RELEASING, INSTALLATION). The local demo does not need HTTPS; release builds reject HTTP.
Open (not claimed)
- Release qualification of the signed APK end to end (HTTPS server, enrollment, scan, navigation, update).
- Actual on-device Authentik callback: unverified; no separate evidence, remains production qualification.
- Dependency publication: the Generation, Record Files and Scripting owner inputs behind the local server are qualified inputs, not a fully public, reproducible or released cohort.
- Company profile / MDM rollout: nothing applied or verified on a device (DEVICE-PROVISIONING).