Skip to content

Epic: APR wiring — connect repo creation to a route, scaffold it, and retire the stale transfer path #10085

Description

@JSONbored

Problem

src/orb/apr-repo-creation.ts creates a repo under the customer's own GitHub account
using their own live OAuth token (POST /user/repos), per the design correction recorded
in its header (2026-07-21, decision #7590). It works and nothing calls it.

Meanwhile src/orb/apr-repo-transfer.ts (377 lines) implements transfer-to-customer and
its header still describes the superseded design: "An APR repo is created under a
loopover-controlled GitHub org (#7637) and can later be transferred… to the customer's own
account."
Two incompatible models are live in the tree.

Sub-issues

  • wire creation to the idea-submission route
  • scaffold the created repo so the loop can run on it
  • resolve the transfer path against the corrected design
  • operator runbook for a live customer project

Acceptance

A submitted idea produces a scaffolded repo under the customer's own account, the tree
carries one repo-ownership model rather than two, and there is a written procedure for
running a real project on it.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions