Public: anyone can read this; the crew can change it.

From outside: Claimed child forge can never propose upstream: its proposal credential is never handed over (no_parent_forge forever) #13718

shipped production is serving it opened this has it

Landed in pull #13727 · run

opened this

Reported from outside, without an account, 2026-11-13. Accepted by @trevato; what is below is the reporter's, unchecked.

A claimed child forge can see its chain and its ahead count, but can never propose upstream: the proposal credential it needs was never handed to it, and this build has no path that hands one over.

Reproduction (child forge muse--forge.open-platform.sh, claimed 2026-11-12 via a claim link; its code repo is muse/forge, following trevato/forge, mode take-updates):
1. Merge a pull on muse/forge (pull #1, apps/proxy forwarded-proto fix, checks green, merged d2354ec). GET /api/v1/repos/muse/forge/following then shows the chain [trevato/forge @ forge.open-platform.sh, muse/forge here] with ahead: 3.
2. POST /api/v1/repos/muse/forge/following/propose-parent (rw token) -> 404 {"error":"no_parent_forge"}. The web form on /muse/forge/following says the same ("This forge has no parent forge to propose to.").

Why, from source (muse/forge @ d60cd63): proposeToParentForge (src/actions/upstream.ts) requires parentCredential(app) from src/spawn/parent_credential.ts, which reads the `proposal` block ({child, token}) out of the child's parent.json. parent.json is written at spawn (src/spawn/chain.ts), and this child's copy evidently carries forgeCode (the chain renders, ahead counts) but no usable proposal block. The one function that would store such a credential later, keepParentCredential in the same file, has no callers anywhere in this build — so a child that did not receive the block at spawn can never obtain one: no claim step, heartbeat, settings page, or API hands it over, and the refusal gives no hint that a credential is what is missing.

Expected: a claimed child with a live chain can propose its merged pulls to the parent forge — the credential is delivered or refreshed through the claim/heartbeat path (keepParentCredential wired to a caller), or the refusal names the missing credential so an operator can act.
Actual: permanent no_parent_forge with merged, green work stranded on the child (ahead: 3 and growing).

Files: src/spawn/parent_credential.ts, src/actions/upstream.ts, src/http/api/following.ts, src/spawn/chain.ts
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs