Skip to content

docs: refresh roadmap for September planning - #6897

Open
ascerra wants to merge 8 commits into
mainfrom
docs/september-roadmap
Open

docs: refresh roadmap for September planning#6897
ascerra wants to merge 8 commits into
mainfrom
docs/september-roadmap

Conversation

@ascerra

@ascerra ascerra commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Replace the August Now/Next/Later table with a September theme-led roadmap (Auto-merge, review quality and cost, GitLab, Jira, community, platform, partners, user support).
  • Keep Now/Next/Later as date-free confidence horizons; issue links use titles and track both fullsend and agents (including agents#1132).
  • Split published editions into dated pages under docs/archived-roadmaps/ plus an index. docs/archived-roadmap.md is a meta-refresh + canonical redirect to archived-roadmaps/ (same pattern as docs/index.md).

Deprecated per-org (ADR 0044)

This PR mentions leftover cleanup from deprecated per-org installation mode (ADR 0044), tracked as fullsend#2887. That is remaining teardown, not new org-mode architecture.

Protected path

.pre-commit-config.yaml / Makefile lychee --exclude-path is narrowed to docs/archived-roadmaps/2026-07.md only (the fragment-heavy historical page). README and other dated archives stay link-checked. Needs human approval for the protected-path change.

Test plan

Made with Cursor

Publish a theme-led Now/Next/Later snapshot from the September session
and keep the August edition in docs/archived-roadmaps/ so monthly
archives do not accumulate in one file.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Refresh September roadmap and add monthly archives

📝 Documentation ⚙️ Configuration changes 🕐 20-40 Minutes

Grey Divider

AI Description

• Reframes September planning around themes and date-free confidence horizons.
• Archives the August snapshot in a discoverable monthly roadmap collection.
• Adds archive navigation while excluding historical links from offline validation.
Diagram

graph TD
  R["Live Roadmap"] -->|archives prior snapshot| A["August Archive"] -->|listed by| I["Archive Index"] -->|shown in| S["Docs Sidebar"]
  L["Legacy Archive"] -->|listed by| I
  S -->|links to| R
  C["Link Checker"] -->|skips| A
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Continue the combined archive file
  • ➕ Avoids introducing a new archive directory and generated sidebar group.
  • ➕ Keeps all historical roadmap content in one document.
  • ➖ The archive grows indefinitely and becomes difficult to navigate.
  • ➖ Monthly snapshots cannot have stable, independently discoverable pages.
  • ➖ Reviewing future rotations requires editing an increasingly large file.
2. Recover snapshots from Git history
  • ➕ Avoids storing duplicated historical roadmap content in the documentation tree.
  • ➕ Preserves the live roadmap as the only maintained page.
  • ➖ Historical editions are not discoverable from the published documentation.
  • ➖ Readers must understand Git and locate the correct revision.
  • ➖ Past planning links become less accessible to non-contributors.

Recommendation: Keep the PR's one-file-per-month archive strategy. It preserves published snapshots as stable documentation, prevents the legacy aggregate from growing indefinitely, and integrates cleanly with the existing VitePress file discovery helper; the combined archive should remain only for older editions until a separate migration is worthwhile.

Files changed (7) +305 / -75

Documentation (4) +288 / -67
archived-roadmap.mdRetain July and earlier roadmaps in the legacy archive +3/-1

Retain July and earlier roadmaps in the legacy archive

• Clarifies that this aggregate file now covers July 2026 and earlier editions. Adds an August entry pointing to the new monthly snapshot archive.

docs/archived-roadmap.md

2026-08.mdPreserve the published August 2026 roadmap +117/-0

Preserve the published August 2026 roadmap

• Adds the complete August roadmap as a standalone historical snapshot, including its original Now/Next/Later tables and July completion recap. Archive notices distinguish it from current planning.

docs/archived-roadmaps/2026-08.md

README.mdCreate the monthly roadmap archive index +17/-0

Create the monthly roadmap archive index

• Introduces an archive landing page that links the August snapshot and the legacy collection for July 2026 and earlier.

docs/archived-roadmaps/README.md

roadmap.mdPublish the theme-led September 2026 roadmap +151/-66

Publish the theme-led September 2026 roadmap

• Replaces the August deliverable tables with a September snapshot organized around Auto-merge, review quality and cost, GitLab, Jira, community, platform, and partners. Retains date-free Now/Next/Later confidence horizons, adds titled issue links across both repositories, and summarizes shipped August work with a link to its archive.

docs/roadmap.md

Other (3) +17 / -8
.pre-commit-config.yamlExclude monthly roadmap archives from pre-commit link checks +1/-1

Exclude monthly roadmap archives from pre-commit link checks

• Extends the Lychee pre-commit command to skip the new archived-roadmaps directory, where stale historical links are expected.

.pre-commit-config.yaml

MakefileExclude monthly archives from manual link linting +1/-1

Exclude monthly archives from manual link linting

• Keeps the Makefile link-lint target aligned with pre-commit by excluding the new historical roadmap directory.

Makefile

config.tsAdd grouped navigation for archived roadmaps +15/-6

Add grouped navigation for archived roadmaps

• Replaces the single archive link with a collapsed group containing the archive index, dynamically discovered monthly snapshots, and the legacy archive. It also classifies monthly archive pages with contributing content for search and normalizes nearby formatting.

docs/.vitepress/config.ts

@qodo-code-review

qodo-code-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

Grey Divider


Remediation recommended

1. Per-org roadmap lacks ADR reference ✓ Resolved 📘 Rule violation § Compliance
Description
The roadmap adds and modifies deprecated per-org installation-mode content, including the remaining
per-org removal work, but the PR description does not explicitly identify this as touching
deprecated per-org functionality or reference ADR 0044. This violates the requirement to call out
any per-org-mode changes in the PR description.
Code

docs/roadmap.md[R109-116]

+Host-side APIs for sandboxed subagents, finish public mint, complete the
+per-org removal leftovers, let teams choose artifact storage, and shift
+tests toward behaviour coverage in the agents repo.
+
+- [fullsend#879 — Host-side API servers for sandboxed agents](https://github.com/fullsend-ai/fullsend/issues/879)
+- [fullsend#881 — fullsend run: implement host-side API server lifecycle](https://github.com/fullsend-ai/fullsend/issues/881)
+- [fullsend#5116 — Deploy PROD public CF mint at mint.fullsend.sh](https://github.com/fullsend-ai/fullsend/issues/5116)
+- [fullsend#2887 — Remove install_mode input from per-repo shim template](https://github.com/fullsend-ai/fullsend/issues/2887)
Relevance

●●● Strong

Recent history accepts explicit ADR 0044 references and deprecation callouts for per-org
installation changes.

PR-#5462
PR-#2743

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The changed roadmap describes completing per-org removal leftovers and links to an issue for
removing the per-org install mode. The PR description discusses the roadmap themes but does not
mention per-org installation mode or ADR 0044.

Rule 2795055: Flag and avoid changes to deprecated per-org installation mode content (ADR 0044)
docs/roadmap.md[109-116]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The PR updates roadmap content concerning deprecated per-org installation mode without explicitly calling out that functionality or referencing ADR 0044.

## Issue Context
The compliance requirement applies whenever per-org installation mode is touched, including documentation changes and removals.

## Fix Focus Areas
- docs/roadmap.md[109-116]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Misclassified archived roadmap search results ✓ Resolved 🐞 Bug ≡ Correctness
Description
Adding /docs/archived-roadmaps/ to the Contributing search scope causes archived roadmap pages
to appear under the Contributing filter, even though they are historical planning documents. This
makes scoped documentation search return misleading results and hides the archive’s intended
categorization.
Code

docs/.vitepress/config.ts[442]

+          { label: "Contributing", prefixes: ["/docs/contributing/", "/docs/archived-roadmaps/"] },
Relevance

●●● Strong

Accepted history favors correcting misleading documentation taxonomy and search behavior; archived
roadmaps are explicitly separate.

PR-#6683
PR-#4020

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The local search configuration defines a Contributing scope for /docs/contributing/, but the PR
adds /docs/archived-roadmaps/ to the same scope. The sidebar separately presents archived roadmaps
as their own Archived roadmaps group, confirming they are a distinct document category rather than
contributor guidance.

docs/.vitepress/config.ts[364-373]
docs/.vitepress/config.ts[429-443]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Archived roadmap pages are assigned to the `Contributing` local-search scope, so users filtering for contributing documentation receive historical roadmap results.

## Issue Context
The changed scope currently combines `/docs/contributing/` and `/docs/archived-roadmaps/`. Keep contributing documentation and archived planning documents as separate search categories, or place archived roadmaps in the general `Others` scope.

## Fix Focus Areas
- docs/.vitepress/config.ts[441-443]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Context sources
✅ Compliance rules (platform): 65 rules
Review mode: 🚀 Fast: The changes are localized to roadmap documentation, VitePress navigation, and markdown-link lint exclusions, with no runtime or high-risk behavioral impact.

Grey Divider

Tip of the day
💡 Did you know, you can commit Qodo's fix in one click with committable suggestions (GitHub & GitLab)

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment thread docs/roadmap.md Outdated
Comment thread docs/.vitepress/config.ts Outdated
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

🤖 Review · ⚠️ Cancelled · Started 2:23 AM UTC · Ended 2:36 AM UTC

Commit: 34086ff · View workflow run →

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

Site preview

Preview: https://09fe0eea-site.fullsend-ai.workers.dev

Commit: 334bd22f93ac062abd6589f3be5d244016417f23

@codecov

codecov Bot commented Sep 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Gate auto-merge opt-in on revert/defect visibility, point maintainer
process at the canonical GitHub file, and avoid nested H1/H2 inside the
August archive snapshot.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 2:38 AM UTC · Completed 2:54 AM UTC

Commit: cd5ec9b · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $5.46

@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

Risk Assessment: moderate (2/5)

Details

Tier 1 signals are unchanged from the prior assessment (large BLAST radius, CI_WORKFLOW_CHANGED, one protected path all reflecting benign documentation reorganization with zero security-sensitive or dependency changes); Tier 2 confirms low-risk documentation file history with no regression or contention signals; no linked issue; anchoring preserves prior score of 2.

Previous run

Risk Assessment: moderate (2/5)

Details

Docs-focused roadmap refresh with bulk archive moves inflating line count and BLAST radius, but all high-scoring signals (large BLAST, CI_WORKFLOW_CHANGED, protected path) reflect benign documentation reorganization with no functional code changes; prior score of 2 is preserved as Tier 1 signals are unchanged.

Previous run (2)

Risk Assessment: moderate (2/5)

Details

Docs-focused roadmap refresh with trivial 1-line touches to Makefile and pre-commit config; elevated slightly by CI workflow flag and protected path hit, but all non-doc changes are minimal config adjustments with no functional impact.

Previous run (3)

Risk Assessment: moderate (2/5)

Details

Docs-focused roadmap refresh with trivial 1-line touches to Makefile and pre-commit config; elevated slightly by CI workflow flag and protected path hit, but all non-doc changes are minimal config adjustments with no functional impact.

Previous run (4)

Risk Assessment: moderate (2/5)

Details

Docs-focused roadmap refresh with trivial 1-line touches to Makefile and pre-commit config; elevated slightly by CI workflow flag and protected path hit, but all non-doc changes are minimal config adjustments with no functional impact.

Previous run (5)

Risk Assessment: moderate (2/5)

Details

Docs-focused roadmap refresh with trivial 1-line touches to Makefile and pre-commit config; elevated slightly by CI workflow flag and protected path hit, but all non-doc changes are minimal config adjustments with no functional impact.

@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

Review

Findings

High

  • [protected-path] .pre-commit-config.yaml — PR modifies a protected governance/infrastructure file. The change narrows the lychee --exclude-path from docs/archived-roadmap.md to docs/archived-roadmaps/2026-07.md to target only the file with broken fragment references. The PR body explains the rationale but no linked issue provides authorization for modifying this protected path. Human sign-off is required for protected-path changes.

Low

  • [API shape patterns] docs/.vitepress/seo.ts:121 — Three SEO functions reference the archived-roadmap page using different string forms: archived-roadmap.md in isIndexablePage and pageRobotsHead, but archived-roadmap and archived-roadmap.html in isSitemapUrl. The different forms match their respective input formats (page paths vs sitemap URLs), but extracting a shared stem constant would reduce coordination cost for future renames.
    Remediation: Optional — extract a stem constant and derive each form programmatically.

  • [missing-authorization] docs/roadmap.md — No directly linked issue authorizes the September roadmap refresh. The established monthly cadence (four prior editions) and the purely documentation nature of the change substantially mitigate the traceability gap.
    Remediation: Open or link a planning issue (e.g., "docs: September 2026 roadmap refresh").


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run

Review

Findings

High

  • [protected-path] .pre-commit-config.yaml — PR modifies a protected governance/infrastructure file. The change updates lychee --exclude-path from docs/archived-roadmap.md to docs/archived-roadmaps to match the new archive directory structure. The PR body explains the rationale but has no linked issue providing authorization. Human sign-off is required for protected-path changes.

Low

  • [missing-authorization] docs/roadmap.md — The PR has no directly linked issue authorizing the roadmap refresh. Periodic planning refreshes follow an established monthly cadence (four prior editions exist), which substantially mitigates the traceability concern. The PR is entirely documentation with no production code affected.
    Remediation: Open or link a planning issue (e.g., "docs: September 2026 roadmap refresh") as the driving authorization for the refresh.

  • [scope-coherence] docs/.vitepress/config.ts:314 — Two formatting-only changes unrelated to the roadmap refresh: collapsing the Reference items array to a single line and reformatting the OpenAI Workload Identity entry to multi-line. These appear to be auto-formatter output.

  • [architectural-coherence] docs/archived-roadmap.md — The old monolithic archived-roadmap.md now serves as a redirect page pointing to the new per-month directory. Clean migration pattern: existing bookmarks still work. The sidebar change uses getMarkdownFiles with .reverse(), aligning with the established auto-discovery pattern.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (2)

Review

Findings

High

  • [protected-path] .pre-commit-config.yaml:165 — PR modifies a protected governance/infrastructure file. The change updates lychee --exclude-path from docs/archived-roadmap.md to docs/archived-roadmaps to match the new archive directory structure. The PR body acknowledges this requires human approval, but no linked issue provides authorization. Human sign-off is required for protected-path changes.

Low

  • [scope-coherence] docs/.vitepress/config.ts:314 — Two formatting-only changes unrelated to the roadmap refresh: collapsing the Reference items array to a single line and reformatting the OpenAI Workload Identity entry to multi-line. These appear to be auto-formatter output.

  • [architectural-coherence] docs/archived-roadmap.md — The old monolithic archived-roadmap.md now serves as a redirect page pointing to the new per-month directory. Clean migration pattern: existing bookmarks still work. The sidebar change uses getMarkdownFiles with .reverse(), aligning with the established auto-discovery pattern.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (3)

Review

Findings

High

  • [protected-path] .pre-commit-config.yaml — This PR modifies .pre-commit-config.yaml, which is a protected governance/infrastructure file. The PR has no linked issue providing authorization for modifying protected paths. The change updates the lychee link checker's --exclude-path from docs/archived-roadmap.md (single file) to docs/archived-roadmaps (directory) to match the new archive structure. Human approval is required for protected-path changes.

Low

  • [scope-coherence] docs/.vitepress/config.ts:314 — The diff includes two formatting-only changes unrelated to the roadmap refresh: collapsing the Reference items array to a single line and reformatting the OpenAI Workload Identity entry to multi-line. These appear to be auto-formatter output.

  • [architectural-coherence] docs/archived-roadmap.md — The old monolithic archived-roadmap.md now serves as a redirect page pointing to the new per-month directory. Clean migration pattern: existing bookmarks still work. The sidebar change uses getMarkdownFiles with .reverse(), aligning with the established auto-discovery pattern.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (4)

Review

Findings

High

  • [protected-path] .pre-commit-config.yaml — This PR modifies .pre-commit-config.yaml, which is a protected governance/infrastructure file. The PR has no linked issue providing authorization for modifying protected paths. The change updates the lychee link checker's --exclude-path from docs/archived-roadmap.md (single file) to docs/archived-roadmaps (directory) to match the new archive structure. Human approval is required for protected-path changes.

Low

  • [scope-coherence] docs/.vitepress/config.ts:314 — The diff includes two formatting-only changes unrelated to the roadmap refresh: collapsing the Reference items array to a single line and reformatting the OpenAI Workload Identity entry to multi-line. These appear to be auto-formatter output.

  • [architectural-coherence] docs/archived-roadmap.md — The old monolithic archived-roadmap.md now serves as a redirect page pointing to the new per-month directory. Clean migration pattern: existing bookmarks still work. The sidebar change uses getMarkdownFiles, aligning with the established auto-discovery pattern used by ADRs and other sections.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (5)

Review

Findings

High

  • [protected-path] .pre-commit-config.yaml — This PR modifies .pre-commit-config.yaml, which is a protected governance/infrastructure file. The PR has no linked issue providing authorization for modifying protected paths. The change adds --exclude-path docs/archived-roadmaps to the lychee link checker configuration. Human approval is required for protected-path changes.

Low

  • [architectural-coherence] docs/.vitepress/config.ts:365 — The PR introduces a per-month archiving pattern (docs/archived-roadmaps/) alongside the existing monolithic archive (docs/archived-roadmap.md). Both files cross-reference each other and the sidebar labels the old file "July 2026 and earlier," making the boundary clear in practice. Future contributors should follow the per-month pattern for new editions.

  • [scope-coherence] docs/.vitepress/config.ts:314 — The diff includes two formatting-only changes (collapsing the Reference items array to a single line and reformatting the OpenAI Workload Identity entry to multi-line) unrelated to the roadmap refresh. These appear to be auto-formatter output.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

fullsend-ai-review[bot]

This comment was marked as outdated.

August was only on /archived-roadmaps while the sidebar still opened the
old combined file, so August never appeared. Put July, June, and
Foundation next to August as dated files under archived-roadmaps/.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 10:56 AM UTC · Completed 11:11 AM UTC

Commit: 2046baf · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $4.84

fullsend-ai-review[bot]

This comment was marked as outdated.

ascerra and others added 2 commits September 2, 2026 07:14
Bring the September roadmap branch onto current main.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Call out ADR 0044 for leftover per-org cleanup, and drop
unrelated prettier-only VitePress config churn.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 11:19 AM UTC · Completed 11:36 AM UTC

Commit: 2a7985c · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $7.13

fullsend-ai-review[bot]

This comment was marked as outdated.

@waynesun09 waynesun09 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One documentation-accuracy finding inline on docs/roadmap.md.

Comment thread docs/roadmap.md Outdated
Give standing user-support work its own last-place theme, and label
August Jira leftovers as issues vs ADR PRs per review.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 8:22 PM UTC · Completed 8:36 PM UTC

Commit: 22cab23 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $4.57

fullsend-ai-review[bot]

This comment was marked as outdated.

@waynesun09 waynesun09 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review sweep — inline findings below, plus one finding on an unchanged line the diff doesn't cover:

docs/.vitepress/config.ts (line 442, outside diff hunks)

[MEDIUM] archived-roadmaps folder is entirely absent from VitePress search scopes (overcorrection from an earlier review round)

Verified via git history on this PR: commit 34086ff (the PR's first commit) added "/docs/archived-roadmaps/" to the Contributing scope's prefixes array, which drew a qodo-code-review[bot] comment (id 3910157431, orig_line 442) calling that a misclassification (archived pages showing up under the live "Contributing" filter). A later commit, cd5ecbbb, responded by removing "/docs/archived-roadmaps/" from the Contributing prefixes entirely rather than moving it to its own scope. On the current head (22cab23), search.options.scopes lists Guides, Design Docs, Experiments, Contributing (["/docs/contributing/"] only), and a catch-all Others — /docs/archived-roadmaps/ appears in no scope's prefix list. The archived pages are still placed under "Contributing" in the sidebar navigation (config.ts ~line 368-370), so with the Contributing search pill active, the archived roadmap pages are now unreachable there and only surface under the generic "Others" scope — inconsistent with their sidebar placement. This is a different, currently-live defect from the one the earlier bot comment flagged (which described the opposite state and was already addressed by the intervening commit), so no existing comment covers it. Note: line 442 (the unchanged scopes array) falls outside this PR's diff hunks, so this finding is included in the review body rather than as an inline comment.

Suggestion: Add "/docs/archived-roadmaps/" to an appropriate scopes entry — either a new dedicated scope (e.g. "Archived Roadmaps") or back into Contributing's prefixes if that classification is intended — so local search matches the sidebar placement, without reintroducing the earlier misclassification-under-Contributing complaint if a dedicated scope is used instead.

Comment thread docs/roadmap.md Outdated
Comment thread docs/archived-roadmap.md Outdated
Comment thread .pre-commit-config.yaml Outdated
Add the open scheduled/nightly agent docs PR from planning feedback
to the standing User support theme.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 8, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 4:46 PM UTC · Completed 5:00 PM UTC

Commit: 3385bc2 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $4.67

fullsend-ai-review[bot]

This comment was marked as outdated.

Resolve conflicts and address open review findings: drop the wrong
#6464 link, redirect archived-roadmap with canonical SEO, and narrow
the lychee exclude to the fragment-heavy July archive page.

Assisted-by: Cursor Grok 4.6
Signed-off-by: Adam Scerra <ascerra@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 9, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 12:15 AM UTC · Completed 12:33 AM UTC

Commit: 334bd22 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $6.26

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

Comment thread docs/.vitepress/seo.ts
@@ -117,7 +120,12 @@ export function pageRobotsHead(page: string): HeadConfig[] {
*/
export function isSitemapUrl(url: string): boolean {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] API shape patterns

Three SEO functions reference the archived-roadmap page using different string forms: archived-roadmap.md in isIndexablePage and pageRobotsHead, but archived-roadmap and archived-roadmap.html in isSitemapUrl. The different forms match their respective input formats (page paths vs sitemap URLs), but extracting a shared stem constant would reduce coordination cost for future renames.

Suggested fix: Optional: extract a stem constant and derive each form programmatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk/moderate PR risk: moderate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants