Re-enable finishingbot/seambot/rhodibot via gitbot-fleet tiered runner (not phantom standalone clone)

[hyperpolymath]

Summary

The finishingbot / seambot / rhodibot workflows are disabled
(if: false + TODO, merged in #36) because they clone a repo that
does not exist. They should be re-enabled by integrating against the
gitbot-fleet monorepo + its tiered runner — not by a clone-URL swap.

Root cause (verified)

Each workflow does:

git clone https://github.com/hyperpolymath/finishing-bot.git /tmp/finishing-bot
cd /tmp/finishing-bot && cargo build --release

hyperpolymath/finishing-bot (and seambot, rhodibot) do not
exist — never under hyperpolymath or metadatastician; estate
search empty. The clone fails at Set up job (could not read Username … exit 128), so these were permanent false-red on every push,
unrelated to source.

Real location

The bots live in hyperpolymath/gitbot-fleet (public Rust
monorepo, pushed 2026-05-16):

• crates: bots/finishingbot/, bots/seambot/, bots/rhodibot/
  (each with a fuzz/ target)
• BOT-OPERATIONS.md documents a four-tier dependency model
  (rhodibot → glambot → seambot → finishbot, cross-deps;
  session state in ~/.gitbot-fleet/sessions/). The bots are not
  independently clone-and-run; they execute via the fleet's tiered
  runner (Justfile).

What "done" looks like

Re-enable the three checks by integrating ubicity CI against
gitbot-fleet properly:

1. Clone https://github.com/hyperpolymath/gitbot-fleet.git (public —
   no secret needed) at a pinned ref.
2. Build the workspace and invoke the relevant bot(s) through the
   fleet's tier runner / Justfile, honouring the dependency order,
   rather than cargo build in a standalone dir.
3. Map results back to the existing "Upload results / Fail on findings"
   steps.
4. Remove the if: false guards (added in ci: disable phantom-bot workflows until bot repos exist #36) once green.

Interim state

#36 disabled the jobs (job-level if: false + TODO pointing here).
No behaviour change to ubicity; CI no longer falsely red.

Refs #36. Related: hyperpolymath/gitbot-fleet.

[hyperpolymath]

All three sub-issues (#39 seambot, #40 finishingbot, #41 rhodibot) landed via PR #47 (squash 1e4fa2c). The bots are integrated against gitbot-fleet @ pinned ref 2e0ea3ca (incl. gitbot-fleet#150's rhodibot check CLI); the two structural CI bugs (cache-before-clone; exit-code capture aborting under bash -e) are fixed. Closing the parent — re-enablement complete.