K2GO-422 fix(forgejo): scope the seed completion gate to the module flow

Third-pass review: seedPendingRun released the completion gate on
mq.didFail("forgejo") in the post-install flow too, where the module queue is a
stale/unrelated verdict. Scope it to moduleShown so a post-install seed run
waits on its own state. Behavior-preserving for the module-install and
post-install flows; closes the fragile coupling.

Author: luisguzman-adfa

controller/app/src/main/java/org/appdevforall/k2go/redesign/SetupProgressActivity.java

@@ -770,8 +770,11 @@ private void render() {
         // K2GO-422: also wait in a post-install seed run (the "Install repos" button, no module this
         // run). The stranded case (a banked seed leaking into an unrelated Get More flow) has neither
         // moduleShown nor the launch extra, so it still does not block -- no hang reintroduced.
-        boolean seedPendingRun = forgejoSeedActive() && !batchServerSlow && !mq.didFail("forgejo")
-                && (moduleShown || postInstallSeed);
+        boolean seedPendingRun = forgejoSeedActive() && !batchServerSlow
+                && (moduleShown || postInstallSeed)
+                // The forgejo runrole failing releases the gate ONLY in a module-install flow; a
+                // post-install seed run (postInstallSeed) must not read a stale/unrelated queue verdict.
+                && !(moduleShown && mq.didFail("forgejo"));
         if (noRest && prootShown) {
             // proot-only: complete when the queue is terminal — plus, for a module batch, once the server
             // is back (up) or the restart has failed (a dead home that wakes up seconds later is exactly