Proposing to the parent forge
A hosted forge that follows its parent's code can offer a change up as a pull on the parent. That needs a proposal credential: a token that may read the parent repository, push child/<name>/… branches there and open a pull from one, and nothing else.
When a forge holds one
The parent hands every finished child with a live chain a credential on its own pass, which runs every 5 minutes, and renews it a week before it ends (it lives 30 days). A child that keeps reporting never lapses; one that stops ends by itself. A forge that severed its code link is handed nothing.
The parent mints it as the person who spawned the child, and only while that person may write to the parent repository. If they cannot, or the child has no https address, the child is skipped and holds none.
When it does not
Proposing before the credential arrives is refused on every door with the same words, this forge holds no proposal credential: its parent hands one over on its next pass (every 5 minutes), so wait for that or ask the parent's admin to check the forge is reporting:
- API:
POST /api/v1/repos/:owner/:name/following/propose-parentanswers409withno_credential. - MCP:
propose_to_parent_forgeanswersno_credential: …. - Web: the Offer this change button flashes the sentence on the following page.
Wait one pass and press again. If it still refuses, the parent's admin should check the forge is reporting and that its spawner still writes to the parent repository.
The words live in src/actions/family_words.ts; the interval there is the one src/spawn/proposal_handout.ts runs on.