chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-06-15:
  - ADHOC-2026-06-15-T01: wait → progress

workplans/ADHOC-2026-06-15.md

@@ -45,3 +45,28 @@ Blocked before live completion:
 - Local `nix develop ... scripts/compile-check` is blocked by local devenv
   setup, and the local `nix build .#docker` remained in dependency compilation
   after more than 20 minutes. The build was stopped cleanly.
+
+Deploy trigger attempt on 2026-06-15:
+
+- Confirmed current `main` contains the COUNT decode fix and is at commit
+  `f8fde35`.
+- Confirmed the deploy workflow is the normal path and is pinned to
+  `runs-on: [self-hosted, haskelseed]`.
+- Confirmed image tag `gitea.coulomb.social/coulomb/inter-hub:f8fde35`
+  returns `manifest unknown`.
+- Gitea Actions API inspection/dispatch was attempted using the locally
+  configured `tea` token, but the public HTTPS API returned `401 Unauthorized`
+  for Actions endpoints; the raw configured HTTP endpoint was not reachable
+  from this session.
+- Pushed empty commit `68c66b9` (`chore: trigger inter-hub deploy`) because
+  the previous contract/docs commit was ignored by the deploy workflow's
+  `paths-ignore` rules.
+- Polled the registry for
+  `gitea.coulomb.social/coulomb/inter-hub:68c66b9` for about five minutes
+  after push; it continued to return `manifest unknown`.
+
+Current wait reason: the source fix is pushed, but image publication/deploy now
+requires authenticated Gitea Actions workflow dispatch or inspection of the
+self-hosted `haskelseed` runner path. The normal workflow needs haskelseed as
+build runner; an equivalent operator-controlled build host with Nix, registry
+push credentials, and Railiance deploy credentials could substitute.