fix(ci): dispatch to .git-private-farm, not the nonexistent dot-git-private-farm - #720
Merged
Merged
Conversation
…rivate-farm inbox-steward-intake.yml POSTed to /repos/hyperpolymath/dot-git-private-farm/dispatches, which 404s — the repo is named .git-private-farm. Hidden by the same two mechanisms as the companion defect in gitbot-fleet: the call is wrapped in `>/dev/null 2>&1` with an `::warning::` fallback, and the surrounding echo already printed the correct ".git-private-farm", so the run log never showed the real target. Second hop of the closed loop (gitbot-fleet/inbox-steward -> hypatia/inbox-steward-intake -> farm/inbox-steward-propagate). See gitbot-fleet#490. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 25, 2026
hyperpolymath
added a commit
that referenced
this pull request
Aug 25, 2026
…721) ## The problem `Merge Orchestrate (scheduled)` is **active** and has been ticking hourly at `:17`. It reads `MERGE_ORCH_STORE`, which defaults to the in-repo `data/verisim`. `data/verisim/` contains: ``` annealing-states dispatch health neural-states outcomes patterns recipes scan-history ``` **No `observations/`.** And `lib/merge_orchestration/loop.ex:30` documents that as exactly what the loop reads: ``` * `observations/*.json` — per-PR observations (from `observe.sh`) ``` So every tick has sensed nothing, decided nothing, and uploaded an empty `merge-decisions.jsonl` that expired after 7 days. ## The fix this workflow already specified Its own header comment named it: > *"Point MERGE_ORCH_STORE at a populated store (e.g. a checked-out verisim-data) via a repo variable; the default `data/verisim` is the in-repo store."* This does that as the **default** rather than requiring a repo variable be set by hand. Checks out `hyperpolymath/verisimdb-data` (public) at `./store` and defaults `MERGE_ORCH_STORE` to it. The `vars.MERGE_ORCH_STORE` override still wins. That repo is the right target and is demonstrably live — last push `2026-08-25T06:37Z` with commit `scan: estate rescan (run 32810961229)`, and 20+ modules in this repo already read from it (`verisim_connector.ex`, `fleet_dispatcher.ex`, `dispatch_manifest.ex`, `pattern_registry.ex`, `outcome_tracker.ex`, …). ## Safety - **The brain stays token-free.** This is a read-only checkout of a public repo; no PAT, no write. The architecture's whole point — that a compromised scanner cannot write to 400 repos — is preserved. - **Nothing merges.** This only lets the cycle *see* real observations and write a manifest artifact. `actuate.sh` remains unwired per the owner ruling of 2026-08-25. - **No behaviour change without the companion PR.** The producer that fills `observations/` is hyperpolymath/.git-private-farm#127. Until that lands, this checkout finds an empty `observations/` and the cycle behaves exactly as it does today. ## Lockfile No `actions.lock` change required. The added step reuses `actions/checkout@v7.0.1`, already registered for this workflow at `.github/workflows/actions.lock:52`. Verified rather than assumed — an unregistered entry would kill the workflow at 0s with `startup_failure`. ## Companion - hyperpolymath/.git-private-farm#127 — wires `observe.sh`, the producer - #720 — unrelated, fixes the `dot-git-private-farm` dispatch 404 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 <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
1 participant
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.
The bug
.github/workflows/inbox-steward-intake.yml:338POSTs to:hyperpolymath/dot-git-private-farmdoes not exist (gh repo view→ 404). The repo ishyperpolymath/.git-private-farm.Why it stayed invisible
Identical to the companion defect in
gitbot-fleet(see hyperpolymath/gitbot-fleet#490):>/dev/null 2>&1with an::warning::Failed to dispatch to .git-private-farmfallback — a 404 never fails the run.echo "Dispatching to .git-private-farm: ...". So the run log tells you it dispatched to.git-private-farmwhile the API path says otherwise.Impact
Second hop of the loop documented in
.git-private-farm/.github/workflows/inbox-steward-propagate.yml:Both the first and second hops target the nonexistent repo, so the ruleset-update propagation path has never reached the farm.
Changes
Verified:
grep -rn dot-git-private-farmreturns zero hits after the change.Companion PR: hyperpolymath/gitbot-fleet#490
🤖 Generated with Claude Code