Skip to content

chore(docs): remove pre-Fern assets - #6654

Merged
miyoungc merged 1 commit into
mainfrom
codex/cleanup-pre-fern-assets
Jul 10, 2026
Merged

chore(docs): remove pre-Fern assets#6654
miyoungc merged 1 commit into
mainfrom
codex/cleanup-pre-fern-assets

Conversation

@miyoungc

@miyoungc miyoungc commented Jul 10, 2026

Copy link
Copy Markdown
Collaborator

Summary

Remove the retired Sphinx documentation assets and dependency environment left behind after the Fern migration.
Keep contributor setup aligned with the current Fern toolchain by validating Python directly without creating an unused uv environment.

Changes

  • Remove the legacy Sphinx JSON/search extensions and layout template under docs/_ext/ and docs/_templates/.
  • Remove the Sphinx-only pyproject.toml and uv.lock, plus their Biome and hook wiring.
  • Update contributor setup, tests, and guidance to require Python 3.11+ directly while preserving the Fern-era platform docs generator.
  • Remove remaining Sphinx/MyST migration wording and compatibility handling from Fern documentation checks.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Quality Gates

  • Tests added or updated for changed behavior
  • Existing tests cover changed behavior — justification:
  • Tests not applicable — justification:
  • Docs updated for user-facing behavior changes
  • Docs not applicable — justification:
  • Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
  • Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification:
  • Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Verification

  • PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run check:diff passed when hooks were skipped or unavailable
  • Targeted behavior tests pass for the current change set, or tests are marked not applicable above — test/dev-setup-doctor.test.ts (38 passed), focused test/pr-workflow-contract.test.ts assertion (passed), and check-docs.sh --only-cli (passed)
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — deferred to draft PR CI
  • Quality Gates section completed with required justifications or waivers
  • No secrets, API keys, or credentials committed
  • npm run docs builds without warnings (doc changes only) — passed with 0 errors and one Fern upgrade warning
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Miyoung Choi miyoungc@nvidia.com

Summary by CodeRabbit

  • Removed Features

    • Removed enhanced documentation search, including advanced filtering, highlighting, and AI-assisted search integration.
    • Removed automatic JSON documentation output generation and related search-index data exports.
    • Removed the legacy analytics script integration from documentation pages.
  • Documentation

    • Updated contributor setup instructions to use locally installed Python 3.11 or newer.
    • Refreshed documentation guidance for Fern MDX pages and official tool documentation links.
  • Developer Experience

    • Simplified repository setup by removing the requirement for uv.

Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
@miyoungc miyoungc added the area: docs Documentation, examples, guides, or docs build label Jul 10, 2026
@miyoungc miyoungc self-assigned this Jul 10, 2026
@copy-pr-bot

copy-pr-bot Bot commented Jul 10, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The PR removes legacy JSON-output and enhanced-search documentation tooling, updates Fern and contributor guidance, removes the uv-managed Python setup path, and adjusts linting and documentation contract checks for the new documentation layout.

Changes

Documentation and setup cleanup

Layer / File(s) Summary
Local Python setup validation
scripts/dev-setup.sh, test/dev-setup-doctor.test.ts
Setup and doctor flows now locate Python 3.11+ from PATH, no longer require uv sync, and test unsupported local Python versions.
Documentation pipeline and guidance cleanup
docs/_ext/json_output/*, docs/_ext/search_assets/*, docs/_templates/layout.html, pyproject.toml, CONTRIBUTING.md, docs/CONTRIBUTING.md, AGENTS.md, fern/docs.yml
Legacy JSON output, enhanced search assets, Adobe DTM hooks, and project dependency configuration are removed; contributor guidance describes Fern MDX and updated setup/link policies.
Lint and documentation contract updates
.pre-commit-config.yaml, biome.json, test/e2e/e2e-cloud-experimental/check-docs.sh, test/pr-workflow-contract.test.ts
Lint scopes exclude legacy extension JavaScript, and documentation contract checks use the updated component path and heading format.

Estimated code review effort: 4 (Complex) | ~45 minutes

Possibly related PRs

  • NVIDIA/NemoClaw#771: Both changes update linting or type-checking treatment for docs/_ext JavaScript files.

Suggested labels: chore

Suggested reviewers: ericksoa, brandonpelfrey

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: removing legacy pre-Fern documentation assets.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/cleanup-pre-fern-assets

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown
Contributor

@github-code-quality

github-code-quality Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage remains at 96%, unchanged from the main branch.

TypeScript / code-coverage/cli

The overall coverage in the codex/cleanup-pre-fe... branch remains at 77%, unchanged from the main branch.

Show a code coverage summary of the most impacted files.
File main 90d5cdf codex/cleanup-pre-fe... b732773 +/-
src/lib/actions...light-guards.ts 88% 71% -17%
src/lib/actions...ge-preflight.ts 89% 74% -15%
src/lib/actions...confirmation.ts 81% 69% -12%
src/lib/actions...saging-stage.ts 100% 88% -12%
src/lib/actions...try-rollback.ts 85% 74% -11%
src/lib/onboard...e-patch-flow.ts 71% 61% -10%
src/lib/actions...de-preflight.ts 60% 51% -9%
src/lib/actions...estore-phase.ts 93% 87% -6%
src/lib/onboard...ovider-reuse.ts 100% 94% -6%
src/lib/agent/defs.ts 82% 85% +3%

Updated July 10, 2026 20:02 UTC
Code Coverage is in Public Preview. Learn more and provide us with your feedback.

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

E2E Advisor Recommendation

Required E2E: cloud-onboard
Optional E2E: docs-validation

Dispatch hint: cloud-onboard

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • cloud-onboard (high): Required by the deterministic risk plan for the platform-install family. The setup/install path changed in scripts/dev-setup.sh, so run hosted cloud onboarding as the validation floor for a clean supported host reaching a usable agent path.

Optional E2E

  • docs-validation (medium): Useful adjacent confidence because docs build/search assets and the E2E docs check script changed. This validates the live docs-validation E2E boundary but is not merge-blocking for the installer/platform risk floor.

New E2E recommendations

  • contributor-setup (medium): The required cloud-onboard job validates hosted runtime onboarding, but it does not appear to directly exercise ./scripts/dev-setup.sh on a clean contributor workstation image, including the no-uv Python dependency behavior and doctor/readiness output. A dedicated live or branch-validation contributor setup smoke would close that gap for future changes to dev setup.
    • Suggested test: Add a clean-host contributor setup E2E that runs ./scripts/dev-setup.sh, npm run dev:doctor, and optional --expose-cli assertions without creating a runtime sandbox.

Dispatch hint

  • Workflow: .github/workflows/e2e.yaml
  • jobs input: cloud-onboard

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

E2E Target Recommendation

Required E2E targets: cloud-onboard
Optional E2E targets: None

Dispatch required E2E targets:

  • gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=cloud-onboard

Workflow run

Full E2E target advisor summary

E2E Target Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E targets

  • cloud-onboard: Installer and platform changes must work on a clean supported host with the pinned runtime dependencies.
    • Dispatch: gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=cloud-onboard

Optional E2E targets

  • None.

Relevant changed files

  • scripts/dev-setup.sh
  • test/e2e/e2e-cloud-experimental/check-docs.sh

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor (Nemotron Ultra) — Informational

Merge posture: Informational / low confidence
Primary next action: Resolve or justify PRA-1: PR review advisor unavailable.
Open items: 0 required · 1 warning · 0 suggestions · 1 test follow-up
Top item: PR review advisor unavailable

Action checklist

  • PRA-1 Resolve or justify: PR review advisor unavailable
  • PRA-T1 Add or justify test follow-up: Runtime validation

Findings index

ID Severity Category Location Required action
PRA-1 Resolve/justify correctness Re-run the PR Review Advisor or perform a manual review.
Review findings by urgency: 0 required fixes, 1 item to resolve/justify, 0 in-scope improvements

⚠️ Resolve or justify before merge

Investigate these in the current review; either fix them, explain why they are not applicable, or document the accepted risk.

PRA-1 Resolve/justify — PR review advisor unavailable

  • Location: not file-specific
  • Category: correctness
  • Problem: The automated advisor could not complete: PR review advisor SDK execution failed: session: scope-risk-map-analysis omitted required analysis; turn: scope-risk-map-analysis: scope-risk-map-analysis omitted required analysis
  • Impact: Automated review evidence is incomplete, so human review must cover the changed code manually.
  • Recommended action: Re-run the PR Review Advisor or perform a manual review.
  • Expected follow-up: Resolve in this PR or explain why the risk is acceptable.
  • Verification: Inspect the workflow logs and raw advisor artifact for the execution failure.
  • Missing regression test: No regression test recommendation is available because the advisor did not complete.
  • Done when: The risk is fixed or explicitly justified in the PR. Verification: Inspect the workflow logs and raw advisor artifact for the execution failure.
  • Evidence: PR review advisor SDK execution failed: session: scope-risk-map-analysis omitted required analysis; turn: scope-risk-map-analysis: scope-risk-map-analysis omitted required analysis

💡 In-scope improvements

These are lower-risk, not throwaway. Prefer fixing them in this PR when they are local to changed code; defer only with rationale or a linked follow-up.

  • None.
Test follow-ups to resolve or justify

If these cover changed behavior, prefer adding them in this PR; otherwise state why existing coverage is enough or link the follow-up.

  • PRA-T1 Runtime validation — Run the `cloud-onboard` E2E job for Installer and platform changes must work on a clean supported host with the pinned runtime dependencies. Matched files: `scripts/dev-setup.sh`.. Deterministic regression risks require live validation: platform-install.

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — Changes requested

Merge posture: Do not merge yet
Primary next action: Resolve or justify PRA-1: Add coverage for falling back to a versioned Python when python3 is too old.
Open items: 0 required · 1 warning · 0 suggestions · 6 test follow-ups
Since last review: 0 prior items resolved · 1 still applies · 0 new items found

Action checklist

  • PRA-1 Resolve or justify: Add coverage for falling back to a versioned Python when python3 is too old in scripts/dev-setup.sh:277
  • PRA-T1 Add or justify test follow-up: Runtime validation
  • PRA-T2 Add or justify test follow-up: Runtime validation
  • PRA-T3 Add or justify test follow-up: Runtime validation
  • PRA-T4 Add or justify test follow-up: Add coverage for falling back to a versioned Python when python3 is too old
  • PRA-T5 Add or justify test follow-up: Acceptance clause
  • PRA-T6 Add or justify test follow-up: scripts/dev-setup.sh Python interpreter discovery

Findings index

ID Severity Category Location Required action
PRA-1 Resolve/justify tests scripts/dev-setup.sh:277 Add a `test/dev-setup-doctor.test.ts` case that fakes `python3` as `Python 3.10.0` and `python3.12` or `python3.11` as supported, then asserts doctor/setup succeeds, reports or uses the versioned interpreter, proceeds to dependency installation, and does not run `uv sync`.
Review findings by urgency: 0 required fixes, 1 item to resolve/justify, 0 in-scope improvements

⚠️ Resolve or justify before merge

Investigate these in the current review; either fix them, explain why they are not applicable, or document the accepted risk.

PRA-1 Resolve/justify — Add coverage for falling back to a versioned Python when python3 is too old

  • Location: scripts/dev-setup.sh:277
  • Category: tests
  • Problem: The new Python discovery path tries `python3` first and then versioned interpreters, but checked-in tests only cover the default supported `python3` case and the all-candidates-unsupported case. A host with stale `python3` and supported `python3.12`/`python3.11` could regress without a test catching it.
  • Impact: A clean supported host where `python3` is older than 3.11 but a versioned Python 3.11+ binary is installed could fail setup or doctor after future edits to candidate ordering/version parsing, undermining the platform-install invariant without checked-in regression coverage.
  • Recommended action: Add a `test/dev-setup-doctor.test.ts` case that fakes `python3` as `Python 3.10.0` and `python3.12` or `python3.11` as supported, then asserts doctor/setup succeeds, reports or uses the versioned interpreter, proceeds to dependency installation, and does not run `uv sync`.
  • Expected follow-up: Resolve in this PR or explain why the risk is acceptable.
  • Verification: Read `scripts/dev-setup.sh:274-292` and grep `test/dev-setup-doctor.test.ts` for `Python 3.10.0`/`python3.12`; current tests cover all candidates unsupported and the default supported `python3`, but not stale `python3` plus supported versioned fallback.
  • Missing regression test: Add a mocked setup/doctor regression in `test/dev-setup-doctor.test.ts` with fake `python3` returning `Python 3.10.0` and fake `python3.12` or `python3.11` returning `Python 3.12.1`, then assert success and dependency-install progression without `uv sync`.
  • Done when: The risk is fixed or explicitly justified in the PR. Verification: Read `scripts/dev-setup.sh:274-292` and grep `test/dev-setup-doctor.test.ts` for `Python 3.10.0`/`python3.12`; current tests cover all candidates unsupported and the default supported `python3`, but not stale `python3` plus supported versioned fallback.
  • Evidence: scripts/dev-setup.sh:277 loops over `python3 python3.14 python3.13 python3.12 python3.11`. test/dev-setup-doctor.test.ts:139 sets the default fixture `python3` to `Python 3.12.1`. test/dev-setup-doctor.test.ts:316-325 covers all Python candidates below 3.11 for doctor mode. test/dev-setup-doctor.test.ts:615-624 covers all Python candidates below 3.11 for setup mode.

💡 In-scope improvements

These are lower-risk, not throwaway. Prefer fixing them in this PR when they are local to changed code; defer only with rationale or a linked follow-up.

  • None.
Test follow-ups to resolve or justify

If these cover changed behavior, prefer adding them in this PR; otherwise state why existing coverage is enough or link the follow-up.

  • PRA-T1 Runtime validation — Run the `cloud-onboard` E2E job for Installer and platform changes must work on a clean supported host with the pinned runtime dependencies. Matched files: `scripts/dev-setup.sh`.. Deterministic regression risks require live validation: platform-install. The deterministic risk plan flags `platform-install` because `scripts/dev-setup.sh` changed. Unit/mocked tests cover many fail-closed setup paths, but the versioned-Python fallback success branch lacks checked-in coverage, and `cloud-onboard` remains the runtime validation floor.
  • PRA-T2 Runtime validation — Add a `test/dev-setup-doctor.test.ts` case with fake `python3` returning `Python 3.10.0` and fake `python3.12` or `python3.11` returning `Python 3.12.1`, then assert doctor/setup succeeds and dependency installation proceeds without `uv sync`.. Deterministic regression risks require live validation: platform-install. The deterministic risk plan flags `platform-install` because `scripts/dev-setup.sh` changed. Unit/mocked tests cover many fail-closed setup paths, but the versioned-Python fallback success branch lacks checked-in coverage, and `cloud-onboard` remains the runtime validation floor.
  • PRA-T3 Runtime validation — Use the required `cloud-onboard` validation floor for the `platform-install` risk family; this review did not observe or claim its execution.. Deterministic regression risks require live validation: platform-install. The deterministic risk plan flags `platform-install` because `scripts/dev-setup.sh` changed. Unit/mocked tests cover many fail-closed setup paths, but the versioned-Python fallback success branch lacks checked-in coverage, and `cloud-onboard` remains the runtime validation floor.
  • PRA-T4 Add coverage for falling back to a versioned Python when python3 is too old — Add a `test/dev-setup-doctor.test.ts` case that fakes `python3` as `Python 3.10.0` and `python3.12` or `python3.11` as supported, then asserts doctor/setup succeeds, reports or uses the versioned interpreter, proceeds to dependency installation, and does not run `uv sync`.
  • PRA-T5 Acceptance clause — Update contributor setup, tests, and guidance to require Python 3.11+ directly while preserving the Fern-era platform docs generator. — add test evidence or identify existing coverage. `scripts/dev-setup.sh` now checks for Python 3.11+ directly and no longer runs `uv sync`; `CONTRIBUTING.md` lists Python 3.11+; `scripts/generate-platform-docs.py` remains present. The unproven versioned-Python fallback success branch is tracked by finding F-001.
  • PRA-T6 scripts/dev-setup.sh Python interpreter discovery — Missing checked-in test for stale `python3` plus supported versioned interpreter success; covered by F-001.. `scripts/dev-setup.sh:274-292` implements `find_local_python`; tests cover default `python3` success and all-candidates failure but not versioned fallback success.
Since last review details

Current findings, using the urgency labels above:

PRA-1 Resolve/justify — Add coverage for falling back to a versioned Python when python3 is too old

  • Location: scripts/dev-setup.sh:277
  • Category: tests
  • Problem: The new Python discovery path tries `python3` first and then versioned interpreters, but checked-in tests only cover the default supported `python3` case and the all-candidates-unsupported case. A host with stale `python3` and supported `python3.12`/`python3.11` could regress without a test catching it.
  • Impact: A clean supported host where `python3` is older than 3.11 but a versioned Python 3.11+ binary is installed could fail setup or doctor after future edits to candidate ordering/version parsing, undermining the platform-install invariant without checked-in regression coverage.
  • Recommended action: Add a `test/dev-setup-doctor.test.ts` case that fakes `python3` as `Python 3.10.0` and `python3.12` or `python3.11` as supported, then asserts doctor/setup succeeds, reports or uses the versioned interpreter, proceeds to dependency installation, and does not run `uv sync`.
  • Expected follow-up: Resolve in this PR or explain why the risk is acceptable.
  • Verification: Read `scripts/dev-setup.sh:274-292` and grep `test/dev-setup-doctor.test.ts` for `Python 3.10.0`/`python3.12`; current tests cover all candidates unsupported and the default supported `python3`, but not stale `python3` plus supported versioned fallback.
  • Missing regression test: Add a mocked setup/doctor regression in `test/dev-setup-doctor.test.ts` with fake `python3` returning `Python 3.10.0` and fake `python3.12` or `python3.11` returning `Python 3.12.1`, then assert success and dependency-install progression without `uv sync`.
  • Done when: The risk is fixed or explicitly justified in the PR. Verification: Read `scripts/dev-setup.sh:274-292` and grep `test/dev-setup-doctor.test.ts` for `Python 3.10.0`/`python3.12`; current tests cover all candidates unsupported and the default supported `python3`, but not stale `python3` plus supported versioned fallback.
  • Evidence: scripts/dev-setup.sh:277 loops over `python3 python3.14 python3.13 python3.12 python3.11`. test/dev-setup-doctor.test.ts:139 sets the default fixture `python3` to `Python 3.12.1`. test/dev-setup-doctor.test.ts:316-325 covers all Python candidates below 3.11 for doctor mode. test/dev-setup-doctor.test.ts:615-624 covers all Python candidates below 3.11 for setup mode.

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

@miyoungc
miyoungc marked this pull request as ready for review July 10, 2026 20:43

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
scripts/dev-setup.sh (1)

277-294: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Discover all supported Python 3.x binaries.

find_local_python only probes python3 and python3.11 through python3.14. If a machine exposes only a newer versioned executable on PATH, setup and doctor incorrectly report that Python 3.11+ is unavailable. Enumerate python3.* candidates dynamically and add a regression fixture for a newer versioned interpreter.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@scripts/dev-setup.sh` around lines 277 - 294, Update find_local_python to
dynamically discover all python3.* executables available on PATH, while
retaining the unversioned python3 candidate and validating each discovered
interpreter with the existing version checks. Ensure candidates are deduplicated
and safely handled, then add a regression fixture covering a newer versioned
interpreter that is at least Python 3.11.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@AGENTS.md`:
- Line 156: Update the external-link guidance in AGENTS.md to match the broader
exception already permitted in CONTRIBUTING.md, including official dependency
documentation and industry standards; alternatively, explicitly state that
Node.js and Python are examples rather than an exhaustive allowlist. Keep both
documents consistent.

---

Outside diff comments:
In `@scripts/dev-setup.sh`:
- Around line 277-294: Update find_local_python to dynamically discover all
python3.* executables available on PATH, while retaining the unversioned python3
candidate and validating each discovered interpreter with the existing version
checks. Ensure candidates are deduplicated and safely handled, then add a
regression fixture covering a newer versioned interpreter that is at least
Python 3.11.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f205760c-09bb-4216-aab0-f77b4b0b9017

📥 Commits

Reviewing files that changed from the base of the PR and between d643898 and b732773.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (41)
  • .pre-commit-config.yaml
  • AGENTS.md
  • CONTRIBUTING.md
  • biome.json
  • docs/CONTRIBUTING.md
  • docs/_ext/json_output/__init__.py
  • docs/_ext/json_output/config.py
  • docs/_ext/json_output/content/__init__.py
  • docs/_ext/json_output/content/extractor.py
  • docs/_ext/json_output/content/metadata.py
  • docs/_ext/json_output/content/structured.py
  • docs/_ext/json_output/content/text.py
  • docs/_ext/json_output/core/__init__.py
  • docs/_ext/json_output/core/builder.py
  • docs/_ext/json_output/core/document_discovery.py
  • docs/_ext/json_output/core/global_metadata.py
  • docs/_ext/json_output/core/hierarchy_builder.py
  • docs/_ext/json_output/core/json_formatter.py
  • docs/_ext/json_output/core/json_writer.py
  • docs/_ext/json_output/processing/__init__.py
  • docs/_ext/json_output/processing/cache.py
  • docs/_ext/json_output/processing/processor.py
  • docs/_ext/json_output/utils.py
  • docs/_ext/search_assets/__init__.py
  • docs/_ext/search_assets/enhanced-search.css
  • docs/_ext/search_assets/main.js
  • docs/_ext/search_assets/modules/DocumentLoader.js
  • docs/_ext/search_assets/modules/EventHandler.js
  • docs/_ext/search_assets/modules/ResultRenderer.js
  • docs/_ext/search_assets/modules/SearchEngine.js
  • docs/_ext/search_assets/modules/SearchInterface.js
  • docs/_ext/search_assets/modules/SearchPageManager.js
  • docs/_ext/search_assets/modules/Utils.js
  • docs/_ext/search_assets/templates/search.html
  • docs/_templates/layout.html
  • fern/docs.yml
  • pyproject.toml
  • scripts/dev-setup.sh
  • test/dev-setup-doctor.test.ts
  • test/e2e/e2e-cloud-experimental/check-docs.sh
  • test/pr-workflow-contract.test.ts
💤 Files with no reviewable changes (31)
  • pyproject.toml
  • docs/_ext/search_assets/templates/search.html
  • docs/_ext/json_output/init.py
  • docs/_ext/search_assets/modules/SearchPageManager.js
  • docs/_templates/layout.html
  • docs/_ext/json_output/core/init.py
  • docs/_ext/search_assets/modules/DocumentLoader.js
  • docs/_ext/json_output/config.py
  • docs/_ext/json_output/core/builder.py
  • docs/_ext/json_output/content/init.py
  • docs/_ext/json_output/core/json_writer.py
  • docs/_ext/json_output/core/hierarchy_builder.py
  • docs/_ext/search_assets/modules/ResultRenderer.js
  • docs/_ext/json_output/content/metadata.py
  • docs/_ext/json_output/content/structured.py
  • docs/_ext/search_assets/main.js
  • docs/_ext/json_output/core/document_discovery.py
  • docs/_ext/json_output/content/text.py
  • docs/_ext/json_output/utils.py
  • docs/_ext/search_assets/modules/Utils.js
  • docs/_ext/search_assets/modules/SearchEngine.js
  • docs/_ext/json_output/processing/init.py
  • docs/_ext/search_assets/modules/SearchInterface.js
  • docs/_ext/search_assets/modules/EventHandler.js
  • docs/_ext/json_output/processing/cache.py
  • docs/_ext/json_output/core/global_metadata.py
  • docs/_ext/search_assets/enhanced-search.css
  • docs/_ext/json_output/core/json_formatter.py
  • docs/_ext/search_assets/init.py
  • docs/_ext/json_output/content/extractor.py
  • docs/_ext/json_output/processing/processor.py

Comment thread AGENTS.md
### No External Project Links

Do not add links to third-party code repositories, community collections, or unofficial resources. Links to official tool documentation (Node.js, Python, uv) are acceptable.
Do not add links to third-party code repositories, community collections, or unofficial resources. Links to official tool documentation (Node.js and Python) are acceptable.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Clarify the external-link exception.

CONTRIBUTING.md Line 351 also permits official documentation for dependencies and industry standards, so this narrower Node.js/Python wording may give agents and contributors contradictory guidance. Use the same allowlist in both files, or make the examples explicitly non-exhaustive.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@AGENTS.md` at line 156, Update the external-link guidance in AGENTS.md to
match the broader exception already permitted in CONTRIBUTING.md, including
official dependency documentation and industry standards; alternatively,
explicitly state that Node.js and Python are examples rather than an exhaustive
allowlist. Keep both documents consistent.

Source: Coding guidelines

@miyoungc
miyoungc merged commit 58d8559 into main Jul 10, 2026
58 of 59 checks passed
@miyoungc
miyoungc deleted the codex/cleanup-pre-fern-assets branch July 10, 2026 20:51
Hadar301 pushed a commit to Hadar301/NemoClaw-OpenShift that referenced this pull request Jul 12, 2026
<!-- markdownlint-disable MD041 -->
## Summary
Remove the retired Sphinx documentation assets and dependency
environment left behind after the Fern migration.
Keep contributor setup aligned with the current Fern toolchain by
validating Python directly without creating an unused `uv` environment.

## Changes
- Remove the legacy Sphinx JSON/search extensions and layout template
under `docs/_ext/` and `docs/_templates/`.
- Remove the Sphinx-only `pyproject.toml` and `uv.lock`, plus their
Biome and hook wiring.
- Update contributor setup, tests, and guidance to require Python 3.11+
directly while preserving the Fern-era platform docs generator.
- Remove remaining Sphinx/MyST migration wording and compatibility
handling from Fern documentation checks.

## Type of Change

- [ ] Code change (feature, bug fix, or refactor)
- [x] Code change with doc updates
- [ ] Doc only (prose changes, no code sample modifications)
- [ ] Doc only (includes code sample changes)

## Quality Gates
<!-- Check exactly one tests line and one docs line. Check other lines
when applicable. Add every requested justification or approval
reference. -->
- [x] Tests added or updated for changed behavior
- [ ] Existing tests cover changed behavior — justification:
- [ ] Tests not applicable — justification:
- [x] Docs updated for user-facing behavior changes
- [ ] Docs not applicable — justification:
- [ ] Sensitive paths changed (security, policy, credentials, preflight,
onboarding, inference, runner, sandbox, or messaging)
- [ ] Sensitive-path review completed or maintainer-approved waiver
recorded — reviewer/approval link/justification:
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## Verification
<!-- Check each applicable item only when supported by the requested
evidence. Run targeted tests once per relevant change set and rerun
after later edits or hook autofixes that can affect the tested behavior.
Do not rerun hook-covered checks. -->
- [x] PR description includes the DCO sign-off declaration and every
commit appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run check:diff` passed when hooks were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — `test/dev-setup-doctor.test.ts` (38
passed), focused `test/pr-workflow-contract.test.ts` assertion (passed),
and `check-docs.sh --only-cli` (passed)
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — deferred to draft PR CI
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only) — passed
with 0 errors and one Fern upgrade warning
- [x] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)

---
<!-- DCO sign-off is required in this PR description, and every commit
must appear as Verified in GitHub. Run: git config user.name && git
config user.email -->
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Removed Features**
- Removed enhanced documentation search, including advanced filtering,
highlighting, and AI-assisted search integration.
- Removed automatic JSON documentation output generation and related
search-index data exports.
- Removed the legacy analytics script integration from documentation
pages.

- **Documentation**
- Updated contributor setup instructions to use locally installed Python
3.11 or newer.
- Refreshed documentation guidance for Fern MDX pages and official tool
documentation links.

- **Developer Experience**
  - Simplified repository setup by removing the requirement for `uv`.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation, examples, guides, or docs build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants