archy/Release & Testing/Non-IndeeHub-Execution.md

Curated documentation snapshot as of 2026-10-24 08:08 UTC. Lane-owner factual review pending unless explicitly stated; not release approval, execution admission, or confirmation that implementation is published.

Non-IndeeHub execution

Current bindings and latest outcomes

The current inspected app source is 9194e2d4a26ae7879188547cc768399c89f28cfd on local branch work/uat-cloud-isolation-20261021. The app owner reports this current source unpublished by that lane, with no canonical proposal/ref publication receipt. This does not describe all historical source. Earlier source results apply to their exact revisions, not automatically to this entire candidate.

• D09 disposable transport and rollback: eb2958377 passed one actual browser → production HTTP/WebSocket → private tmux test including input/reconnect/history and metadata-write failure rollback. Only the new session is removed; old record/session/sentinel preservation is asserted. Desktop/mobile screenshots were inspected. Runtime raw/outer verdicts passed and owned cleanup was established. The earlier compiler succeeded but its unrelated-inventory guard failed; that failure remains.
• D09 installed boundary remains open: the explicit-workspace fixture does not prove default-workspace creation under the packaged service sandbox. Source inspection identified a writable-path risk, not a demonstrated installed defect. Actual package binding, installed login/creation/tooling/keys/process/reboot, physical input and independent acceptance remain.
• B03 actual pagination remains unqualified: the fixed scenario is real Nextcloud traversal of 251 items across a 250-item page boundary (not 251 pages), later-page exact bytes and old/fresh/old revision with refresh. First runtime failed module resolution before UI. Second ran the original UI flow but timed out while seeding before pagination.
• Earlier diagnostic r2: Apache syntax/modules/exact include passed; the real fixture validator rejected a third read-only configuration mount. Probe/Node phases were UNRUN; operation exit 2 and outer exit 90. Owned cleanup passed. This is not a pagination pass or a diagnosed latency cause.
• Latest owner-reported diagnostic r3: real configuration/tmpfs/protocol gates passed. The run emitted 11 client records: three PUT pre-header timeouts and all five later GETs with exact 40-byte bodies and ETags, before helper/capture failure. The helper was killed and correlation is incomplete. Operation exit 1/outer exit 90; child and processes were absent but the owned provider container still existed after bounded removal was killed. Inventory differed and cleanup release was NOT established at this snapshot. Supplemental exact-owned cleanup was requested, not yet confirmed. No retry or pagination credit.

Post-cutoff cleanup addendum

The app owner subsequently confirmed one exact-owned supplemental removal exited 0 and both owned container/process/scope sets were absent; the coordinator released that owned exclusion. Supplemental outer verdict 1 remains FAILED because an unrelated inventory replacement was already present before removal; its actor is unknown and no foreign cleanup was performed. This supersedes only the pending-cleanup statement above. Original operation 1/outer 90, incomplete correlation and lack of pagination/cause/whole-UAT qualification remain unchanged.

Retained narrower progress

Owner records describe real disposable Nextcloud/Immich browser/RPC and account/permission/album sub-exits; authenticated download and cancellation work; terminal renderer/reconnect/history corrections; signed hardware-discovery source/browser checks; generated starter-app and package checks; Podsteadr/MediaMTX/Blossom synthetic media, publication and preservation checks; and a Qortal fresh-start candidate correction. These do not close whole B03/D09/D11/D10 requirements or any entire app. Exact historical source/result bindings require owner reconciliation before reuse.

Still required

All 35 platform IDs and eight apps remain represented in the matrix. Major open boundaries include installed connector/native identity/lifecycle, File Browser preservation defects, managed app migration/ownership, Qortal accepted provenance/packaging, Podsteadr provisioning/review, actual relay/network/device behavior, nonempty backup/rollback, exact release artifacts and integrated UAT. Historical mocked/synthetic checks do not replace actual account, device or managed-installation acceptance.

No implementation push, deployment or whole-lane completion is established by this documentation.