bonzi/hermes-mobile
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record delivery verification limits

Browse Source
This commit is contained in:
Hermes Agent
2026-07-25 00:28:15 +00:00
parent 049e93ae3d
commit 6bf375ee78
4 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BLOCKERS.md
+2
View File
@@ -14,6 +14,8 @@ A later Task 5 rerun on 2026-07-24 was blocked before project execution: the gui
A follow-up P0 audit identified that a failed/offline first-run Bearer profile could be mistaken for a historical current-key profile and bypass setup after restart. On 2026-07-25, the gate was corrected to require recorded legacy provenance for migration and a focused Bearer restart regression was added. The offline focused `SetupWizardReducerTest` and `:app:assembleDebug` command then passed (43 tasks, 9 executed). This is source-level verification only; no fresh clean-install, device, authentication, release, or end-to-end evidence is claimed.
Task 5 delivery verification on 2026-07-25 retried the documented writable-cache offline `:app:testDebugUnitTest :app:assembleDebug` command. Gradle was blocked before project execution because its daemon could not open the sandbox-prohibited TCP socket (`java.net.SocketException: Operation not permitted`), so this run adds no fresh test or assembly result. The existing ignored debug APK was inspected without using the untracked `releases/` artifact: it was last modified `2026-07-25 00:16:06 UTC`, is 17,710,960 bytes, reports package `cloud.molberg.hermesmobile`, version `0.1.0-beta.1` (`10001`), and has SHA-256 `190efe9dd61bcfbe589d91d9676f57264107f90c7a3481de233b2e028ff138db`. The existing focused XML report records 30 `SetupWizardReducerTest` tests with 0 failures/errors/skips. `git diff --check` passed. No device installation, real credentials, release, or gateway end-to-end verification was performed.
The first-run Setup Wizard is also source-complete and unit/build verified, including None/Bearer/password choices and direct password-session cookie handling. No real None/Bearer/password credential flow has been exercised against a live gateway, so R2 must include the chosen authentication mode and observed connection result without recording credentials.
ADB is installed, but the R1 evidence above confirms that its daemon sockets are prohibited and that no emulator executable, AVD, `/dev/kvm`, USB device bus, or running target is available. Package metadata and the SHA-256 of the existing ignored source-current APK were inspected, but no fresh assembly, clean uninstall/install, launch, or direct-gateway device connection was verified here. No APK was published or uploaded, and no final release criterion is claimed.