Repository navigation
docs+web: MCP docs & new diagrams, stale-claim fixes, hide public auth CTAs - #6
Conversation
- architecture.md gains an MCP Server section (route gating, RFC 9728 discovery, auth chain, tenantScope, 9-tool scope table) plus endpoint and data-flow rows; command dispatch now documents the test command; licensing section corrected to AGPL-3.0 (was Sustainable Use License) - marketing docs page adds Contract/Context/Commands/Gauge/MCP diagrams and a new MCP Server section; new in-app /docs/mcp page; public/docs.md gains an MCP section - FAQ auto-review default corrected to on; praise severity row aligned with Review Laws (summary-only); README embeddings defaults now match code fallbacks; CONTEXT.md gains tenantScope + granted-scopes entries
Service is qbraid-only for now; the site is a brochure. Removes the navbar Sign in/Get started cluster (signed-in users still get the Dashboard button) and repoints every install/get-started CTA to the GitHub repo. The /sign-in and /sign-up routes still work — they are just no longer linked.
There was a problem hiding this comment.
All reported issues were addressed across 16 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
…e CTAs Cubic review on #6 — the public tree has no MCP backend, so every doc advertising /mcp sent readers to a route that does not exist. Removed the MCP architecture section, CONTEXT glossary, self-hosting block, marketing docs section, /docs/mcp page, and MCPDiagram; MCP stays a roadmap item. Also: FAQ auto-review corrected (hosted defaults OFF per decideAutoRun, self-hosted ON — prior edit claimed the opposite); repointed CTAs no longer advertise a 3-repo/50-review free tier or $19 Pro next to self-host links; GitHub CTAs emit marketing.github_clicked instead of install_clicked; ContextDiagram arrows rotate on stacked mobile layout.
There was a problem hiding this comment.
2 issues found across 14 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="web/src/components/marketing/sections/install-cta.tsx">
<violation number="1" location="web/src/components/marketing/sections/install-cta.tsx:249">
P2: The CTA claims there are no usage caps, but Argus still enforces a 30/hour per-install rate limit and a 2-per-10-minute per-PR refresh cap. Clarify that there are no paid-tier quotas instead of claiming usage is uncapped.</violation>
</file>
<file name="web/src/app/docs/faq/page.tsx">
<violation number="1" location="web/src/app/docs/faq/page.tsx:20">
P2: The hosted default is now documented inconsistently: `/docs` and the settings UI still say auto-review is on by default, while this FAQ says it is off. Update the remaining user-facing docs and toggle copy to the hosted-off/self-hosted-on policy.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| {"\u2192"} | ||
| </span> | ||
| Free tier · 50 reviews/mo | ||
| No usage caps |
There was a problem hiding this comment.
P2: The CTA claims there are no usage caps, but Argus still enforces a 30/hour per-install rate limit and a 2-per-10-minute per-PR refresh cap. Clarify that there are no paid-tier quotas instead of claiming usage is uncapped.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At web/src/components/marketing/sections/install-cta.tsx, line 249:
<comment>The CTA claims there are no usage caps, but Argus still enforces a 30/hour per-install rate limit and a 2-per-10-minute per-PR refresh cap. Clarify that there are no paid-tier quotas instead of claiming usage is uncapped.</comment>
<file context>
@@ -246,14 +246,14 @@ export function InstallCta() {
{"\u2192"}
</span>
- Free tier · 50 reviews/mo
+ No usage caps
</span>
<span aria-hidden className="hidden h-[10px] w-px bg-iron/70 sm:inline-block" />
</file context>
| No usage caps | |
| No paid-tier usage caps |
| review on demand. The default is off because large PRs (50+ files) can | ||
| cost several dollars per review on paid providers, and we want | ||
| reviewers to see the estimate first. | ||
| On the hosted service, auto-review is off until you enable it — a fresh |
There was a problem hiding this comment.
P2: The hosted default is now documented inconsistently: /docs and the settings UI still say auto-review is on by default, while this FAQ says it is off. Update the remaining user-facing docs and toggle copy to the hosted-off/self-hosted-on policy.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At web/src/app/docs/faq/page.tsx, line 20:
<comment>The hosted default is now documented inconsistently: `/docs` and the settings UI still say auto-review is on by default, while this FAQ says it is off. Update the remaining user-facing docs and toggle copy to the hosted-off/self-hosted-on policy.</comment>
<file context>
@@ -17,14 +17,16 @@ export default function FAQPage() {
- Auto-review is on by default — every opened, pushed, or reopened PR
- reviews itself. If Argus stayed silent, likely causes: auto-review was
- turned off for the repo or org (Argus posts a one-shot{" "}
+ On the hosted service, auto-review is off until you enable it — a fresh
+ repo gets a one-shot{" "}
<strong className="text-slate-200">Trigger Argus review</strong>{" "}
</file context>
…c matrix Landing page critique findings, all resolved: - Contrast: --muted-foreground 0.714 -> 0.78 (body copy was 3.15:1); --color-amber now resolves to the glow value under .dark (text-amber was 1.44:1 on void); bg-amber buttons switched to text-void. ARGUS wordmark dropped to /15 so it reads as an intentional echo, not a rendering bug. - Self-host story unified: chips, Argus row ($0 AGPL), estimator line, compare index — no more free-tier/Pro claims next to GitHub CTAs. - Price column math: competitor prices now computed at a 20-dev team/mo. - Fake liveness removed: LIVE -> DONE readout, "Streaming" -> "example run", "All systems operational" status gone, dead mock <button>s and the no-op expand control are now inert spans. - Demo lore unified on PR #412 / Jan 24; timeline rows are chronological. - Comparison matrix is a real <table> with scope'd headers; self-asserted "Last audited" date removed, sources link kept.
There was a problem hiding this comment.
1 issue found across 13 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="web/src/app/globals.css">
<violation number="1" location="web/src/app/globals.css:172">
P3: This makes dark-mode `bg-amber` identical to `hover:bg-amber-glow`, so the CTAs lose their visible hover feedback. Keep the base amber token distinct from the glow token, or the hover state becomes a no-op.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| --background: oklch(0.147 0.004 49.3); | ||
|
|
||
| /* Dark-theme amber is text-safe: --primary (deep amber) stays for fills. */ | ||
| --color-amber: oklch(0.77 0.15 75); |
There was a problem hiding this comment.
P3: This makes dark-mode bg-amber identical to hover:bg-amber-glow, so the CTAs lose their visible hover feedback. Keep the base amber token distinct from the glow token, or the hover state becomes a no-op.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At web/src/app/globals.css, line 172:
<comment>This makes dark-mode `bg-amber` identical to `hover:bg-amber-glow`, so the CTAs lose their visible hover feedback. Keep the base amber token distinct from the glow token, or the hover state becomes a no-op.</comment>
<file context>
@@ -168,6 +168,9 @@ body {
--background: oklch(0.147 0.004 49.3);
+ /* Dark-theme amber is text-safe: --primary (deep amber) stays for fills. */
+ --color-amber: oklch(0.77 0.15 75);
+
--foreground: oklch(0.986 0.002 67.8);
</file context>
Summary
architecture.mdgains a full MCP Server section (route gating, RFC 9728 discovery, auth chain,tenantScope, 9-tool scope table) + endpoint/data-flow rows.CONTEXT.mdgains MCP glossary entries.self-hosting.mdgains the MCP env-var block./docs; new in-app/docs/mcppage + sidebar link;public/docs.mdMCP section.public/docs.mdpraise row → summary-only per Review Laws./sign-in,/sign-uproutes still work — just unlinked. Service is qbraid-only for now.Test plan
pnpm lint— same 12 pre-existing warnings, none in touched filespnpm typecheck— clean/docsand/docs/mcprender 200 locallySummary by cubic
Removes live MCP setup claims because the public tree has no MCP backend; MCP now remains a roadmap item. It also updates product copy and public entry points to reflect the current AGPL self-hosted service.
/sign-inand/sign-upremain available but unlinked.$0 · AGPL, 20-dev team/mo math) and strips fake liveness indicators.<table>with scoped headers.Written for commit 1e7d0df. Summary will update on new commits.