ci: disable phantom-bot workflows until bot repos exist#36
Merged
Conversation
finishingbot/seambot/rhodibot each `git clone https://github.com/hyperpolymath/<bot>.git`, but none of those repos exist (verified: not under hyperpolymath or metadatastician; estate search empty; auth confirmed working). So these checks can never pass and were permanent red on every push, unrelated to source. Gate each job behind `if: false` with a TODO (not deleted — the scaffolding is intentional; "Part of gitbot-fleet"). Re-enable by removing `if: false` once the bot repos are created/restored. Pre-existing estate-infra drift; no behaviour change to ubicity. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced May 16, 2026
hyperpolymath
added a commit
that referenced
this pull request
May 16, 2026
#37) (#42) ## Summary Re-enables the three bot checks disabled in #36. They were permanent false-red because they cloned **phantom repos** (`hyperpolymath/finishing-bot`, `/seambot`, `/rhodibot`) that never existed. The bots actually live in **`hyperpolymath/gitbot-fleet`** under `bots/`. Each workflow now: clones `gitbot-fleet` at a **pinned commit** (partial clone + checkout SHA), builds the specific bot crate, runs the **correct binary**, then the `if: false` guard is removed. | Bot | Root cause fixed | Invocation | |---|---|---| | finishingbot | phantom clone **+ wrong binary name** (`finishingbot` → crate binary is `finishing-bot`) | `finishing-bot --path "$GITHUB_WORKSPACE" audit` | | seambot | phantom clone | `seambot check` (keeps the `spec/seams/seam-register.json` guard) | | rhodibot | phantom clone **+ rhodibot had no CLI** (was webhook-server-only) | `rhodibot check --owner --repo`, built-in read-only `GITHUB_TOKEN` (public repo, no PAT) | ## Dependency rhodibot needs the new `rhodibot check` subcommand added in **hyperpolymath/gitbot-fleet#150**. The pinned ref is currently that PR's branch HEAD (`2e0ea3ca67821a91e650f51bf48a6cfd1c7aae1c`); it will be **bumped to the post-merge `main` SHA** once #150 lands. Do not merge this before that bump. ## Tracking `Refs #37`. Native sub-issues: #39 (seambot), #40 (finishingbot — binary-name bug), #41 (rhodibot — blocked on gitbot-fleet#150). Per estate workflow, #37 closes only on explicit joint agreement. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ci: disable phantom-bot workflows until the bot repos exist
finishingbot/seambot/rhodibot each
git clone https://github.com/hyperpolymath/<bot>.git, but none of those reposexist (verified: not under hyperpolymath or metadatastician; estate
search empty; auth confirmed working). So these checks can never pass
and were permanent red on every push, unrelated to source.
Gate each job behind
if: falsewith a TODO (not deleted — thescaffolding is intentional; "Part of gitbot-fleet"). Re-enable by
removing
if: falseonce the bot repos are created/restored.Pre-existing estate-infra drift; no behaviour change to ubicity.
Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com