fix(copy): align FAQ and docs tier names with pricing page

[bishopBethel]

The bounty FAQ and docs still referenced the retired Pro/Max/Enterprise tiers after pricing was rebranded to Free/Personal/Team, so an investor reading the site saw two different product lineups.

• bounty FAQ: private-repo bounties are on Personal and Team
• docs: private repos, Linear integration, advanced-controls pill, and the two model-routing passages all now name Personal/Team

Copy only; "Gemini 2.5 Pro" is a model name and is left alone.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
devasign-website	Ready	Preview	Aug 31, 2026 12:07pm

[devasign-app]

AI Review: Changes Requested

All seven acceptance criteria are re-derived as met: the bounty FAQ (BountyAutomationPage.tsx:279) and the five DocsPage passages (274, 362, 613, 957, 971) now name Personal/Team, "Gemini 2.5 Pro" at line 964 is untouched, and every edit is JSX text content with identical element structure, attributes and imports, so nothing functional changed. No correctness, security or regression defects exist in the changed lines. One blocker survives the audit and it is infrastructural rather than code: the authoritative PR state reports merge state CONFLICTING (DIRTY), so the branch cannot merge until it is rebased and the six tier-name sites re-verified; one nit remains asking for a site-wide sweep for other retired tier names.

Acceptance Criteria

Met

• ✅ The bounty FAQ no longer states that private-repository bounties require the retired Pro/Max/Enterprise tiers, and instead states they are available on Personal and Team. — The FAQ answer body at BountyAutomationPage.tsx:279 (confirmed at the PR head in Chunk 4) contains no occurrence of Pro, Max, or Enterprise and explicitly names Personal and Team; the surrounding <details>/<summary> for "Can I bounty private-repo issues?" is unchanged, so the replaced text is the one rendered for that question. Checked the rest of the FAQ list (lines 253-284) for other tier mentions: only the plan-agnostic "every DevAsign plan — Free included" at line 275 remains, which is not a retired name.

  src/pages/BountyAutomationPage.tsx:279

  279 | <div className="da-faq-body"><p>Yes — on Personal and Team, which both include private repositories. The Free plan supports bounties on public repos only, matching the Free plan's open-source scope.</p></div>

• ✅ The docs passage about private repositories names Personal/Team rather than the retired Pro/Max/Enterprise tier names. — The Installation paragraph at DocsPage.tsx:274 (PR-head chunk) now reads "private repositories require Personal or Team" inside the same <strong> emphasis, with the sentence structure and the /pricing link preserved. Scanned the rest of the installation section (lines 271-291) for any other Pro/Max/Enterprise wording and found none.

  src/pages/DocsPage.tsx:274

  274 | Sign up on <a href="https://app.devasign.com/authenticate/account" target="_blank" rel="noopener noreferrer" className="docs-link">DevAsign</a> with GitHub and install the app on a repository. Public repositories are reviewed on every plan; <strong>private repositories require Personal or Team</strong>.

• ✅ The docs passage about Linear integration names Personal/Team rather than the retired Pro/Max/Enterprise tier names. — The Linear "Connecting" paragraph at DocsPage.tsx:362 ends with "The Linear integration is a <strong>Personal / Team</strong> feature"; the rest of the Linear section (lines 355-405, PR head) contains no other tier reference, so no stale Pro/Max text survives in that section.

  src/pages/DocsPage.tsx:362

  362 | The Linear integration is a <strong>Personal / Team</strong> feature.

• ✅ The docs advanced-controls pill names Personal/Team rather than the retired Pro/Max/Enterprise tier names. — The advanced-controls subheading at DocsPage.tsx:613 carries the pill text "Personal / Team"; the className "docs-pill write" is unchanged, so only the label text differs and the pill still styles identically. The neighbouring plan sentence at line 583 ("Stage toggles are available on every plan") names no retired tier.

  src/pages/DocsPage.tsx:613

  613 | <h3 className="docs-subheading">Advanced controls <span className="docs-pill write">Personal / Team</span></h3>

• ✅ Both docs passages about model routing name Personal/Team rather than the retired Pro/Max/Enterprise tier names. — Both model-routing passages are updated: the Claude Opus table row at DocsPage.tsx:957 ("The reasoning passes on Personal and Team") and the routing paragraph at line 971 ("<strong>Personal</strong> and <strong>Team</strong> run the frontier reasoning model"). Re-read the whole models section (lines 941-972, PR head) for a third tier mention: the Haiku row at 961 names only "the Free plan", so no retired name remains.

  src/pages/DocsPage.tsx:971

  971 | The review model follows the repo owner's plan: <strong>Free</strong> reviews run end-to-end on Claude Haiku, while <strong>Personal</strong> and <strong>Team</strong> run the frontier reasoning model.

• ✅ The occurrence of "Gemini 2.5 Pro" is left unchanged, since "Pro" there is part of a model name and not a tier name. — The Gemini table row at DocsPage.tsx:964 appears only as an unchanged context line in the models hunk and is identical in the PR-head chunk, so the substitution did not blanket-replace the substring "Pro" in the model name.

  src/pages/DocsPage.tsx:964

  964 | <td><strong>Gemini 2.5 Pro</strong></td>

• ✅ The change is copy-only: no functional behavior, component logic, routing, or pricing data changes accompany the text edits, and the affected FAQ and docs pages still render as before. — Every changed line is JSX text content inside existing elements: no imports, props, className values, hrefs, handlers, hooks, or exported data were touched (compare lines 274, 362, 613, 957, 971 and BountyAutomationPage.tsx:279 against their pre-images — only the prose differs, element structure and attributes are byte-identical). The only gate the repo enforces on these files is vite build (package.json scripts, build.yml), which the PR state reports green 2/2; there are no tests in this repo to collect, so no failing-on-revert test is expected for a copy change.

  src/pages/DocsPage.tsx:613

  613 | <h3 className="docs-subheading">Advanced controls <span className="docs-pill write">Personal / Team</span></h3>

Suggestions

Blockers

• Branch conflicts with the base branch and cannot be merged
  The authoritative PR state reports merge state CONFLICTING (DIRTY): GitHub cannot perform this merge as it stands. This PR rewrites exactly the lines a concurrent rebrand would also touch (DocsPage.tsx:274, 362, 613, 957, 971 and BountyAutomationPage.tsx:279), so the resolution must be checked rather than auto-taken: a careless resolution can reintroduce Pro/Max/Enterprise wording or silently drop one of the six edits. Rebase onto the base branch, resolve, then re-read all six sites and confirm "Gemini 2.5 Pro" at DocsPage.tsx:964 is still intact.

Nitpicks

• Sweep the rest of the site for remaining retired tier names
  The provided context covers only the two edited files, so it cannot confirm whether other pages or shared components still print Pro/Max/Enterprise. Since the PR's stated goal is a consistent lineup for a site visitor, grep the whole src tree for the retired names (excluding the "Gemini 2.5 Pro" model string) before merging.

Additional Findings

Warnings

• Merge conflict with base branch
  GitHub reports this PR as DIRTY: it has merge conflicts with main and cannot be merged as-is. Resolve the conflicts (rebase onto or merge main) before acting on this review's verdict.

📋 Copy Review for AI Agent

Copy the prompt below and paste it into your AI coding assistant to apply all findings.

Apply the following code review findings to the codebase. For each item, make the described change at the specified file and line. Use the fix instruction when provided, otherwise implement the fix based on the issue description.

1. [BLOCKER] (general)
   Issue: Branch conflicts with the base branch and cannot be merged — The authoritative PR state reports merge state CONFLICTING (DIRTY): GitHub cannot perform this merge as it stands. This PR rewrites exactly the lines a concurrent rebrand would also touch (DocsPage.tsx:274, 362, 613, 957, 971 and BountyAutomationPage.tsx:279), so the resolution must be checked rather than auto-taken: a careless resolution can reintroduce Pro/Max/Enterprise wording or silently drop one of the six edits. Rebase onto the base branch, resolve, then re-read all six sites and confirm "Gemini 2.5 Pro" at DocsPage.tsx:964 is still intact.
   Fix: Rebase this branch onto the base branch, resolve the conflicts, and confirm all six tier-name sites read Personal/Team while "Gemini 2.5 Pro" stays unchanged.

2. [WARN] (general)
   Issue: Merge conflict with base branch — GitHub reports this PR as DIRTY: it has merge conflicts with `main` and cannot be merged as-is. Resolve the conflicts (rebase onto or merge `main`) before acting on this review's verdict.
   Fix: Rebase this branch onto main (or merge it in) and resolve all merge conflicts, keeping the intent of both sides.

3. [NIT] (general)
   Issue: Sweep the rest of the site for remaining retired tier names — The provided context covers only the two edited files, so it cannot confirm whether other pages or shared components still print Pro/Max/Enterprise. Since the PR's stated goal is a consistent lineup for a site visitor, grep the whole src tree for the retired names (excluding the "Gemini 2.5 Pro" model string) before merging.
   Fix: Grep src/ for the strings "Pro", "Max", and "Enterprise" used as plan tiers and update any remaining occurrences to Personal/Team, leaving "Gemini 2.5 Pro" alone.

📊 Review metadata

• Processing time: 136s
• Completed: 2026-08-31T12:05:08.061Z

🤖 This review was generated by AI. While we strive for accuracy, please use your judgment when applying suggestions.

Superseded by follow-up review 2.

[devasign-app]

AI Follow-up Review 2: Changes Requested

Since the last review

Addressed (1)

• ✅ Branch conflicts with the base branch and cannot be merged — resolved: PR state now reports MERGEABLE (UNSTABLE) after the base merge, though the resolution itself introduced the DocsPage content regression filed in this review.

Still open (1)

• Sweep the rest of the site for remaining retired tier names

New (1)

• The conflict resolution reverts DocsPage past the tier renames and drops base-branch content: lin…

Criteria: 1 newly unmet

Since the last review the branch was merged with base (resolving prior S1: the PR now reports MERGEABLE) and the docs page was rewritten upstream, but the conflict resolution was botched: the PR's remaining DocsPage diff now reverts large parts of the base-branch rewrite instead of only renaming tiers. The six tier-name sites still read Personal/Team, so criteria 1-6 hold, but criterion 7 (copy-only, page renders as before) is unmet and one blocker-severity regression is filed: the diff deletes the base branch's Credits section, the allowance paragraph and the Free plan row from the review-model table, re-adds a duplicate Advanced-controls list with a mislabeled Per-stage-prompts heading, and reinstates stale copy that contradicts neighbouring base text. One nit (prior S2, site-wide sweep for retired tier names) remains open; PR state also shows CI only 1 of 3 passed with 2 checks still running, so the build gate is not yet green.

Acceptance Criteria

Regressed (previously satisfied)

• ⚠️ The change is copy-only: no functional behavior, component logic, routing, or pricing data changes accompany the text edits, and the affected FAQ and docs pages still render as before. — The current diff is no longer copy-only in the intended sense: beyond the tier strings it deletes base-branch content (the allowance paragraph, the whole "Credits" subsection and its "When the allowance runs out" callout at 1118-1119, and the Free plan row of the Plan/Review model table at 1085-1086) and re-adds removed blocks (the duplicate Advanced-controls list at 660-666 plus a "Per-stage prompts" heading at 667 that now labels a paragraph about saving edits). The docs page therefore does not render as before the merge: the Free plan vanishes from the review-model table, "Claude Opus" occupies the Plan column, and billing/credits documentation is gone.

  src/pages/DocsPage.tsx:1118

  1118 | <p className="docs-paragraph">
  1119 |                             The review model follows the repo owner's plan: <strong>Free</strong> reviews run end-to-end on Claude Haiku, while <strong>Personal</strong> and <strong>Team</strong> run the frontier reasoning model. System prompts are sent with <strong>prompt caching</strong> enabled, so the reused instruction blocks don't re-bill on every pass.
  1120 |                         </p>

  Fix: Re-resolve the merge so the PR changes only the tier-name strings, restoring the base branch's Credits section, allowance paragraph, Free plan model row, and the rewritten workflow/configuration section.

Met

• ✅ The bounty FAQ no longer states that private-repository bounties require the retired Pro/Max/Enterprise tiers, and instead states they are available on Personal and Team. — The new commits touch only DocsPage.tsx and package-lock.json, so the FAQ answer last shown at BountyAutomationPage.tsx:279 is unchanged and still reads Personal and Team with no Pro/Max/Enterprise wording; nothing in the current diff regresses it.

  src/pages/BountyAutomationPage.tsx:279

  279 | <div className="da-faq-body"><p>Yes — on Personal and Team, which both include private repositories. The Free plan supports bounties on public repos only, matching the Free plan's open-source scope.</p></div>

• ✅ The docs passage about private repositories names Personal/Team rather than the retired Pro/Max/Enterprise tier names. — At the PR head the Installation paragraph still reads "private repositories require Personal or Team"; the only edit this PR makes to that line is the metering sentence, which leaves the tier clause intact. Re-read the whole installation section (276-296) for a surviving retired tier name and found none.

  src/pages/DocsPage.tsx:279

  279 | Sign up on <a href="https://app.devasign.com/authenticate/account" target="_blank" rel="noopener noreferrer" className="docs-link">DevAsign</a> with GitHub and install the app on a repository. Public repositories are reviewed on every plan; <strong>private repositories require Personal or Team</strong>.

• ✅ The docs passage about Linear integration names Personal/Team rather than the retired Pro/Max/Enterprise tier names. — The Linear "Connecting" paragraph at the PR head still ends with the Personal / Team feature clause; this PR's only edit to that line swaps "just" for "simply". No other tier reference exists in the Linear section (369-431).

  src/pages/DocsPage.tsx:377

  377 | There are <strong>no tokens or API keys to paste</strong>, re-connecting simply refreshes the authorization, and one Linear workspace connects per account. The Linear integration is a <strong>Personal / Team</strong> feature.

• ✅ The docs advanced-controls pill names Personal/Team rather than the retired Pro/Max/Enterprise tier names. — The advanced-controls pill exists at the PR head and reads "Personal / Team" with the unchanged docs-pill write class, so the naming requirement holds. Note the block itself was re-added by this PR on top of the base branch's replacement "What you can configure" table (622-658), which is reported separately as a regression.

  src/pages/DocsPage.tsx:660

  660 | <h3 className="docs-subheading">Advanced controls <span className="docs-pill write">Personal / Team</span></h3>

• ✅ Both docs passages about model routing name Personal/Team rather than the retired Pro/Max/Enterprise tier names. — Both model-routing passages at the PR head name the new tiers: the table row at 1086 ("The reasoning passes on Personal and Team") and the closing paragraph at 1119 ("<strong>Personal</strong> and <strong>Team</strong> run the frontier reasoning model"). No Pro/Max/Enterprise string remains in the models section (1069-1121); the separate defects in that section are content reversion, not tier naming.

  src/pages/DocsPage.tsx:1119

  1119 | The review model follows the repo owner's plan: <strong>Free</strong> reviews run end-to-end on Claude Haiku, while <strong>Personal</strong> and <strong>Team</strong> run the frontier reasoning model. System prompts are sent with <strong>prompt caching</strong> enabled, so the reused instruction blocks don't re-bill on every pass.

• ✅ The occurrence of "Gemini 2.5 Pro" is left unchanged, since "Pro" there is part of a model name and not a tier name. — No hunk in the current DocsPage diff touches any "Gemini 2.5 Pro" text, so this PR performs no substring replacement on the model name. The string is absent from the PR head only because the base branch's own rewrite replaced the models table and the video-understanding paragraph (visible as base-side content in the merge, not in this PR's diff against base).

Suggestions

Nitpicks

• Sweep the rest of the site for remaining retired tier names
  The provided context still covers only DocsPage.tsx and BountyAutomationPage.tsx, so it cannot confirm whether other pages or shared components still print Pro/Max/Enterprise. Since the PR's goal is one consistent lineup for a visitor, grep the whole src tree for the retired names before merging.

📋 Copy Review for AI Agent

Copy the prompt below and paste it into your AI coding assistant to apply all findings.

Apply the following code review findings to the codebase. For each item, make the described change at the specified file and line. Use the fix instruction when provided, otherwise implement the fix based on the issue description.

1. [REGRESSED CRITERION] src/pages/DocsPage.tsx:1118
   Issue: The change is copy-only: no functional behavior, component logic, routing, or pricing data changes accompany the text edits, and the affected FAQ and docs pages still render as before. — The current diff is no longer copy-only in the intended sense: beyond the tier strings it deletes base-branch content (the allowance paragraph, the whole "Credits" subsection and its "When the allowance runs out" callout at 1118-1119, and the Free plan row of the Plan/Review model table at 1085-1086) and re-adds removed blocks (the duplicate Advanced-controls list at 660-666 plus a "Per-stage prompts" heading at 667 that now labels a paragraph about saving edits). The docs page therefore does not render as before the merge: the Free plan vanishes from the review-model table, "Claude Opus" occupies the Plan column, and billing/credits documentation is gone.
   Fix: Make the change that satisfies this criterion: The change is copy-only: no functional behavior, component logic, routing, or pricing data changes accompany the text edits, and the affected FAQ and docs pages still render as before.

2. [NIT] (general)
   Issue: Sweep the rest of the site for remaining retired tier names — The provided context still covers only DocsPage.tsx and BountyAutomationPage.tsx, so it cannot confirm whether other pages or shared components still print Pro/Max/Enterprise. Since the PR's goal is one consistent lineup for a visitor, grep the whole src tree for the retired names before merging.
   Fix: Grep src/ for "Pro", "Max", and "Enterprise" used as plan tiers and rename any remaining occurrences to Personal/Team.

📊 Review metadata

• Processing time: 186s
• Completed: 2026-08-31T12:10:15.609Z

🤖 This review was generated by AI. While we strive for accuracy, please use your judgment when applying suggestions.