From 93ec73144e92b6e20bffc55ae00a2ddd0601afef Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Fri, 17 Jul 2026 01:01:57 -0700
Subject: [PATCH] docs(ams): document AMS's verified standalone,
 ORB/gittensor-optional capability

Adds an explicit invariant plus a verified-behavior callout to the AMS
deployment guide (and its DEPLOYMENT.md source): AMS works against
any GitHub repository, requiring neither ORB, gittensor registration,
nor a target repo's .loopover.yml.

Verified end to end (init, doctor, discover) against real public
repositories with no .loopover.yml and no gittensor registration,
using only a plain GITHUB_TOKEN.

Closes #6205
---
 apps/loopover-ui/content/docs/ams-deployment.mdx | 12 ++++++++++++
 packages/loopover-miner/DEPLOYMENT.md            |  1 +
 2 files changed, 13 insertions(+)

diff --git a/apps/loopover-ui/content/docs/ams-deployment.mdx b/apps/loopover-ui/content/docs/ams-deployment.mdx
index 6f02675bb6..7347bb922c 100644
--- a/apps/loopover-ui/content/docs/ams-deployment.mdx
+++ b/apps/loopover-ui/content/docs/ams-deployment.mdx
@@ -237,6 +237,18 @@ sends SIGTERM, which the loop handles cleanly at its next kill-switch check.
 - Discovery/ranking primitives that touch GitHub only run when explicitly invoked and only perform
   documented GETs unless a future command says otherwise.
 - Operators own secret injection; images and packages ship without embedded tokens.
+- AMS works against **any** GitHub repository — it does not require ORB installed, gittensor
+  registration, or a `.loopover.yml` file on the target repo to function.
+
+<Callout variant="note" title="Verified against a real, non-gittensor repo">
+  `loopover-miner init`, `doctor`, and `discover <owner/repo>` were run end to end against real
+  public GitHub repositories with no `.loopover.yml` and no gittensor registration, using only a
+  plain `GITHUB_TOKEN` — every step worked as documented, including correctly returning zero
+  candidates on a repo with no open issues and ranking real issues on repos that had them. The
+  `loopover-mcp login` device-flow session path (a separate mechanism from AMS's own credential
+  resolution) currently has a known reliability issue independent of AMS itself — see the linked
+  issue tracker for status before relying on it for unattended AMS setups.
+</Callout>
 
 For operational scenarios (ledger corruption, two miners on one state dir, post-upgrade schema
 migration) see the [AMS operations runbook](/docs/ams-operations-runbook), and for measured
diff --git a/packages/loopover-miner/DEPLOYMENT.md b/packages/loopover-miner/DEPLOYMENT.md
index 8ef06b5622..f7a4709b4d 100644
--- a/packages/loopover-miner/DEPLOYMENT.md
+++ b/packages/loopover-miner/DEPLOYMENT.md
@@ -180,6 +180,7 @@ Want the dashboard too? [`systemd/loopover-miner-ui.service.example`](../../syst
 - `loopover-miner status` and `loopover-miner doctor` make **no network calls**.
 - Discovery/ranking primitives that touch GitHub only run when explicitly invoked and only perform documented GETs unless a future command says otherwise.
 - Operators own secret injection; images and packages ship without embedded tokens.
+- AMS works against **any** GitHub repository — it does not require ORB installed, gittensor registration, or a `.loopover.yml` file on the target repo to function. Verified end to end (`init`, `doctor`, `discover <owner/repo>`) against real public repositories with no `.loopover.yml` and no gittensor registration, using only a plain `GITHUB_TOKEN`.
 
 See [`docs/operations-runbook.md`](docs/operations-runbook.md) for operational scenarios: ledger corruption, two miners on one state dir, and post-upgrade schema migration ([#4875](https://github.com/JSONbored/gittensory/issues/4875)).