Skip to content

Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS

docs: say the reference-repo PATCH gate keys on a named repoUrl or branch, not a changed one

Adam Eivy144aa585571f
diff --git a/docs/API.md b/docs/API.md
index 9ea5c4a347..ce95f9b7ce 100644
--- a/docs/API.md
+++ b/docs/API.md
@@ -736,7 +736,7 @@ Every mounted API prefix (see `server/index.js` for the authoritative list). Dom
| `/api/capabilities` | Feature capability flags |
| `/api/agent-context` | Opt-in, loopback-only MCP context plus separately granted semantic PortOS actions |
| `/api/workspace-contexts` | Workspace context management |
-| `/api/apps/:appId/reference-repos` | Per-app reference repos (create, a PATCH that changes `repoUrl`/`branch`, and `check` are host control: the path names a host directory the scheduled reference-watch runs git in) |
+| `/api/apps/:appId/reference-repos` | Per-app reference repos (create, a PATCH that names `repoUrl` or `branch`, and `check` are host control: the path names a host directory the scheduled reference-watch runs git in) |
| `/api/managed-visitor-admin` | Owner-only provisioning and revocation of scoped managed-app visitor credentials; [contract](features/managed-visitors.md) |
| `/api/managed-visitors/v1` | Loopback managed visitor admission, observation, bounded actions and confirmed cleanup; requires a separate scoped app credential even when the instance password is off; [contract](features/managed-visitors.md) |
| `/api/network-exposure` | Network exposure checks |
diff --git a/server/lib/hostControlRoutes.js b/server/lib/hostControlRoutes.js
index cadece9922..e0cc8d0564 100644
--- a/server/lib/hostControlRoutes.js
+++ b/server/lib/hostControlRoutes.js
@@ -108,7 +108,7 @@
* file PortOS then reads, writes or runs against is the same choice as a
* stored host-file setting, made once. A remote password-free caller
* could otherwise point PortOS at any path the host user owns. Gated:
- * reference-repo create (and a PATCH that changes `repoUrl`/`branch`,
+ * reference-repo create (and a PATCH that names `repoUrl` or `branch`,
* which the scheduled reference-watch runs git in and hands to an
* analysis agent), share-bucket create (PortOS writes records into and
* imports manifests from the folder), the sprite source-tree import and