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
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.
Problem
src/orb/apr-repo-creation.tscreates a repo under the customer's own GitHub accountusing their own live OAuth token (
POST /user/repos), per the design correction recordedin 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 andits 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
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.