docs(contributing): adopt technical English profile - #7263
Merged
Conversation
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
cv
added
area: docs
Contributor
|
🌿 Preview your docs: https://nvidia-preview-pr-7263.docs.buildwithfern.com/nemoclaw |
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (5)
🚧 Files skipped from review as they are similar to previous changes (3)
📝 WalkthroughWalkthroughThis PR revises NemoClaw workflow policies, maintainer and contributor skill instructions, PR comparator contracts, E2E gate terminology, Technical English guidance, supporting documentation, tests, and pinned prompt-asset references. ChangesWorkflow and policy guidance
PR comparison and E2E coordination
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Contributor
Contributor
PR Review Advisor — InformationalAdvisor assessment: Informational / high confidence Model lanes
Nemotron output stays in workflow artifacts and does not change the assessment above. E2E guidanceAdvisory only. E2E / PR Gate selects and runs jobs independently. Recommended E2E: 2 optional E2E recommendations
This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 14
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tools/e2e/pr-e2e-required.mts (1)
139-150: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winMake the validation error cover all rejected identity fields.
The predicate also rejects a wrong PR number or a non-open PR, but the message mentions only the head/base SHA pair. A closed PR can therefore be reported as a SHA mismatch.
Proposed fix
- throw new Error("PR no longer matches the PR SHA and base SHA observed by this job"); + throw new Error( + "PR is not the expected open PR with the observed head SHA and base SHA", + );🤖 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 `@tools/e2e/pr-e2e-required.mts` around lines 139 - 150, Update the error message in validatePullRequest so it accurately covers every rejected identity condition: PR number, open state, head SHA, and base SHA. Keep the existing validation predicate and success behavior unchanged.
🤖 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/skills/nemoclaw-contributor-create-pr/SKILL.md:
- Around line 254-258: Update the draft PR creation guidance to require
completion of Step 4 and reuse the completed trusted body file, including the
Signed-off-by declaration and commit-verification results, instead of allowing
an inline --body value. Keep draft creation behind the same compliance gates as
the standard gh pr create flow.
In
@.agents/skills/nemoclaw-maintainer-cross-issue-sweep/checks/relationship-judgment.md:
- Around line 16-22: Update the judgment prompt in relationship judgment logic
to render the declared first five candidate-issue comments through a
{candidate_comments} section. Ensure the prompt actually includes the candidate
comments for model evaluation, while preserving the existing model-input
contract and post-classification reverse-link behavior.
In @.agents/skills/nemoclaw-maintainer-day/MERGE-GATE.md:
- Around line 177-181: Update the manual fallback flow at
.agents/skills/nemoclaw-maintainer-day/MERGE-GATE.md lines 177-181 to perform a
final fail-closed recheck of PR open status, PR SHA, base SHA, and coordination
identity before recording success. Apply the same terminal recheck to the
authorized control-plane flow at
.agents/skills/nemoclaw-maintainer-day/MERGE-GATE.md lines 217-230 before any
result reaches terminal success; preserve the existing result-recording
requirements.
In @.agents/skills/nemoclaw-maintainer-day/SALVAGE-PR.md:
- Around line 77-90: Update the “Fork PRs” push guidance to branch on
headRepository: for PRs whose head repository is NVIDIA/NemoClaw, allow pushing
to the corresponding origin branch; for fork PRs, retain the maintainerCanModify
check and push to the fork’s head repository and headRefName. Remove the blanket
prohibition on origin and clearly preserve the no-push behavior when fork
modification is unavailable.
In @.agents/skills/nemoclaw-maintainer-day/SEQUENCE-WORK.md:
- Around line 34-37: Update the general ranking near “Use repo priorities” in
.agents/skills/nemoclaw-maintainer-day/SEQUENCE-WORK.md:34-37 to explicitly
state that identified security concerns override the default backlog-first
ordering. Leave the authoritative security-priority rule in
.agents/skills/nemoclaw-maintainer-day/SECURITY-SWEEP.md:60-64 unchanged.
In @.agents/skills/nemoclaw-maintainer-day/STATE-SCHEMA.md:
- Around line 61-62: Update the history retention guidance in STATE-SCHEMA.md to
say “Keep at most 50 entries,” matching the 50-entry limit enforced by state.ts
and preserving the instruction to remove oldest entries first.
In
@.agents/skills/nemoclaw-maintainer-policies/references/triage-instructions.md:
- Around line 152-153: Clarify the label mutation policy around labels_to_add
and labels_to_remove: without workflow authorization, outputs must be dry-run
only and perform no label writes; when authorized, agent-owned mutations may add
or remove only agt:* labels. Keep label creation and deletion subject to the
same authorization gate.
In
@.agents/skills/nemoclaw-maintainer-pr-comparator/checks/tier-1-correctness.md:
- Around line 87-93: Update the contents entry for check 1.6 to use the renamed
heading “Mock boundaries” instead of “Mocking purity,” keeping it synchronized
with the corresponding section heading.
In @.agents/skills/nemoclaw-maintainer-pr-comparator/SKILL.md:
- Around line 102-105: The comparator contract and renderer validation are
inconsistent: happy mode must require a winner, degraded mode must
deterministically select no winner, and salvage output must be rendered per PR.
Update .agents/skills/nemoclaw-maintainer-pr-comparator/SKILL.md lines 102-105
and .agents/skills/nemoclaw-maintainer-pr-comparator/tiebreakers.md lines 40-51
to define and enforce distance-to-ready ordering, require winner
eligibility/output rules in render-verdict.py, and render the required per-PR
salvage steps; keep closest_to_ready restricted to open, contributor-compliant
PRs.
In @.agents/skills/nemoclaw-maintainer-security-code-review/SKILL.md:
- Line 172: Update the security review stopping rule in the draft-review
guidance: do not stop solely when a draft lacks application code. Continue
inspecting all changed security surfaces, including Dockerfiles, workflows,
network policies, blueprints, dependencies, and security configuration; stop
only when no changed or reviewable security surface exists.
- Around line 3-4: Update the skill’s input handling and workflow so it either
accepts only pull-request URLs or resolves ordinary issue URLs to their
associated pull request before Step 2. Ensure the subsequent gh pr checkout and
gh pr view calls receive a verified pull-request number, and reject unsupported
issues without proceeding.
In @.agents/skills/nemoclaw-maintainer-triage/SKILL.md:
- Around line 70-73: Update Step 4, “Apply Only the Accepted Write Set,” to
re-read and refresh the item state immediately before every write. Detect
changes to the base state, including Issue Type, Project, or labels, and stop
the ordered writes to re-present the proposal for acceptance when any change is
found; continue resolving live IDs only after the refreshed proposal is
accepted.
In `@docs/CONTRIBUTING.md`:
- Line 257: Update the Technical English profile link in the contributing
documentation to use the Fern-published route resolved through docs/index.yml
and redirects, replacing the source-relative
../CONTRIBUTING.md#nemoclaw-technical-english target. Keep the existing link
text and anchor destination semantics.
In `@test/pr-e2e-gate-fork-skip.test.ts`:
- Around line 460-462: Update the expectedError value in the “fails closed when
PR/base SHA history contains $label” test case to exactly match the message
thrown by startPrGate: “Multiple PR gate checks already exist for this PR/base
SHA pair”.
---
Outside diff comments:
In `@tools/e2e/pr-e2e-required.mts`:
- Around line 139-150: Update the error message in validatePullRequest so it
accurately covers every rejected identity condition: PR number, open state, head
SHA, and base SHA. Keep the existing validation predicate and success behavior
unchanged.
🪄 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: 01466a9d-2bd4-485f-89f9-53037f1db3dc
📒 Files selected for processing (73)
.agents/skills/_shared/git-github-hard-stop.md.agents/skills/_shared/pr-follow-up.md.agents/skills/nemoclaw-contributor-create-pr/SKILL.md.agents/skills/nemoclaw-contributor-update-docs/SKILL.md.agents/skills/nemoclaw-maintainer-cross-issue-sweep/SKILL.md.agents/skills/nemoclaw-maintainer-cross-issue-sweep/checks/fingerprint-extraction.md.agents/skills/nemoclaw-maintainer-cross-issue-sweep/checks/relationship-judgment.md.agents/skills/nemoclaw-maintainer-cross-issue-sweep/relationship-rules.md.agents/skills/nemoclaw-maintainer-cross-issue-sweep/repo-policy.md.agents/skills/nemoclaw-maintainer-cross-issue-sweep/templates/report.md.agents/skills/nemoclaw-maintainer-day/HOTSPOTS.md.agents/skills/nemoclaw-maintainer-day/MERGE-GATE.md.agents/skills/nemoclaw-maintainer-day/PR-REVIEW-PRIORITIES.md.agents/skills/nemoclaw-maintainer-day/RISKY-AREAS.md.agents/skills/nemoclaw-maintainer-day/SALVAGE-PR.md.agents/skills/nemoclaw-maintainer-day/SECURITY-SWEEP.md.agents/skills/nemoclaw-maintainer-day/SEQUENCE-WORK.md.agents/skills/nemoclaw-maintainer-day/SKILL.md.agents/skills/nemoclaw-maintainer-day/STATE-SCHEMA.md.agents/skills/nemoclaw-maintainer-day/TEST-GAPS.md.agents/skills/nemoclaw-maintainer-find-review-pr/SKILL.md.agents/skills/nemoclaw-maintainer-policies/SKILL.md.agents/skills/nemoclaw-maintainer-policies/references/label-taxonomy.md.agents/skills/nemoclaw-maintainer-policies/references/project-workflow.md.agents/skills/nemoclaw-maintainer-policies/references/release-train.md.agents/skills/nemoclaw-maintainer-policies/references/triage-instructions.md.agents/skills/nemoclaw-maintainer-policies/references/workflow-policy.md.agents/skills/nemoclaw-maintainer-pr-comparator/SKILL.md.agents/skills/nemoclaw-maintainer-pr-comparator/checks/tier-0-gates.md.agents/skills/nemoclaw-maintainer-pr-comparator/checks/tier-1-correctness.md.agents/skills/nemoclaw-maintainer-pr-comparator/checks/tier-2-quality.md.agents/skills/nemoclaw-maintainer-pr-comparator/repo-policy.md.agents/skills/nemoclaw-maintainer-pr-comparator/scripts/collect-gates.sh.agents/skills/nemoclaw-maintainer-pr-comparator/scripts/render-verdict.py.agents/skills/nemoclaw-maintainer-pr-comparator/templates/verdict.md.agents/skills/nemoclaw-maintainer-pr-comparator/tiebreakers.md.agents/skills/nemoclaw-maintainer-release-notes/SKILL.md.agents/skills/nemoclaw-maintainer-security-code-review/SKILL.md.agents/skills/nemoclaw-maintainer-triage/SKILL.md.agents/skills/nemoclaw-skills-guide/SKILL.md.github/PULL_REQUEST_TEMPLATE.md.github/actions/ci-wechat-runtime-audit/audit.sh.github/workflows/e2e.yaml.github/workflows/pr-e2e-gate.yamlAGENTS.mdCONTRIBUTING.mdci/full-e2e-cold-path-calibration.jsondocs/CONTRIBUTING.mddocs/get-started/quickstart.mdxdocs/resources/prompt-assets/dgx-station.mddocs/resources/starter-prompt.mddocs/security/openclaw-2026.6.10-dependency-review.mddocs/security/openshell-0.0.85-migration-review.mdtest/create-require-ratchet.test.tstest/e2e/README.mdtest/e2e/docs/README.mdtest/e2e/live/issue-6194-tui-expect.tstest/onboard-performance-config-schema.test.tstest/pr-comparator-render-verdict.test.tstest/pr-e2e-gate-fork-skip.test.tstest/pr-e2e-gate-lifecycle.test.tstest/pr-e2e-gate-retry-history.test.tstest/pr-e2e-gate-shards.test.tstest/pr-e2e-gate-workflow.test.tstest/pr-e2e-gate.test.tstest/pr-e2e-required.test.tstest/skills-frontmatter.test.tstest/skills/check-gates-compliance.test.tstest/skills/check-gates-evidence.test.tstest/starter-prompt-docs.test.tstools/e2e/pr-e2e-gate.mtstools/e2e/pr-e2e-required.mtstools/pr-review-advisor/README.md
| ## Style Guide | ||
|
|
||
| Write like you are explaining something to a colleague. Be direct, specific, and concise. | ||
| Apply the [NemoClaw Technical English profile](../CONTRIBUTING.md#nemoclaw-technical-english) to changed prose. |
Contributor
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use the published route for the Technical English profile.
../CONTRIBUTING.md#nemoclaw-technical-english is a source-relative .md link. Resolve this target through docs/index.yml and redirects, then use the Fern route instead of relying on repository layout.
As per path instructions, docs/** links must use Fern published routes rather than source-file-relative paths.
🤖 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 `@docs/CONTRIBUTING.md` at line 257, Update the Technical English profile link
in the contributing documentation to use the Fern-published route resolved
through docs/index.yml and redirects, replacing the source-relative
../CONTRIBUTING.md#nemoclaw-technical-english target. Keep the existing link
text and anchor destination semantics.
Source: Path instructions
Comment on lines
+460
to
+462
| expectedError: "Multiple active PR gate checks exist for one PR/base SHA pair", | ||
| }, | ||
| ])("fails closed when exact-diff history contains $label", async ({ checks, expectedError }) => { | ||
| ])("fails closed when PR/base SHA history contains $label", async ({ checks, expectedError }) => { |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Match the duplicate-check expectation to the controller error.
The test now expects Multiple active PR gate checks exist for one PR/base SHA pair, but startPrGate throws Multiple PR gate checks already exist for this PR/base SHA pair. This expectation will fail unless another wrapper rewrites the error.
Proposed correction
- expectedError: "Multiple active PR gate checks exist for one PR/base SHA pair",
+ expectedError: "Multiple PR gate checks already exist for this PR/base SHA pair",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| expectedError: "Multiple active PR gate checks exist for one PR/base SHA pair", | |
| }, | |
| ])("fails closed when exact-diff history contains $label", async ({ checks, expectedError }) => { | |
| ])("fails closed when PR/base SHA history contains $label", async ({ checks, expectedError }) => { | |
| expectedError: "Multiple PR gate checks already exist for this PR/base SHA pair", | |
| }, | |
| ])("fails closed when PR/base SHA history contains $label", async ({ checks, expectedError }) => { |
🤖 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 `@test/pr-e2e-gate-fork-skip.test.ts` around lines 460 - 462, Update the
expectedError value in the “fails closed when PR/base SHA history contains
$label” test case to exactly match the message thrown by startPrGate: “Multiple
PR gate checks already exist for this PR/base SHA pair”.
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@test/pr-review-advisor.test.ts`:
- Line 433: Add a negative assertion in the relevant prompt test near the
existing SSRF guidance assertion, verifying that the exact superseded
sandbox-escape instruction is absent from prompt. Keep the current positive
assertion and ensure the test proves the old guidance was removed.
🪄 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: 37cdeb76-15d9-4e92-a290-d3de51618324
📒 Files selected for processing (6)
.agents/skills/nemoclaw-maintainer-day/MERGE-GATE.md.agents/skills/nemoclaw-maintainer-day/PR-REVIEW-PRIORITIES.md.agents/skills/nemoclaw-maintainer-day/SKILL.md.agents/skills/nemoclaw-maintainer-pr-comparator/SKILL.mdtest/maintainer-skills-policy.test.tstest/pr-review-advisor.test.ts
🚧 Files skipped from review as they are similar to previous changes (3)
- .agents/skills/nemoclaw-maintainer-day/SKILL.md
- .agents/skills/nemoclaw-maintainer-day/MERGE-GATE.md
- .agents/skills/nemoclaw-maintainer-pr-comparator/SKILL.md
| expect(skill).toContain("Category 1: Secrets and Credentials"); | ||
| expect(prompt).toContain("Trusted security review skill from main checkout"); | ||
| expect(prompt).toContain("For NemoClaw PRs, check sandbox escape vectors"); | ||
| expect(prompt).toContain("For NemoClaw PRs, check SSRF bypasses"); |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Prove that the superseded guidance is removed.
This assertion only proves that the SSRF wording exists; it would still pass if the old sandbox-escape instruction remained in the prompt. Add a negative assertion for the exact superseded text.
As per path instructions, migration tests must prove the superseded path is unreachable or removed.
Suggested test update
expect(prompt).toContain("For NemoClaw PRs, check SSRF bypasses");
+expect(prompt).not.toContain("For NemoClaw PRs, check sandbox escape vectors");📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| expect(prompt).toContain("For NemoClaw PRs, check SSRF bypasses"); | |
| expect(prompt).toContain("For NemoClaw PRs, check SSRF bypasses"); | |
| expect(prompt).not.toContain("For NemoClaw PRs, check sandbox escape vectors"); |
🤖 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 `@test/pr-review-advisor.test.ts` at line 433, Add a negative assertion in the
relevant prompt test near the existing SSRF guidance assertion, verifying that
the exact superseded sandbox-escape instruction is absent from prompt. Keep the
current positive assertion and ensure the test proves the old guidance was
removed.
Source: Path instructions
22 tasks
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Collaborator
|
LGTM. Good to merge after resolving the conflicts. |
miyoungc
approved these changes
Jul 20, 2026
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
22 tasks
jyaunches
added a commit
that referenced
this pull request
Jul 20, 2026
<!-- markdownlint-disable MD041 --> ## Summary Add the canonical `## v0.0.90` entry to `docs/changelog/2026-07-20.mdx` before the release tag is planned. The update also corrects the documented custom-image migration window so the compatibility fallback that first ships in v0.0.90 remains available until v0.0.91. ## Changes - Add the v0.0.90 summary and detailed release bullets for managed-image routing, provider-reset recovery, WhatsApp health reporting, and DGX Station guidance. - Keep the newest release first in the shared dated changelog and use root-absolute links to the canonical OpenClaw routes. - Correct `docs/reference/commands.mdx` to state that the legacy image route selector remains supported through v0.0.90 and is removed in v0.0.91. - Release source summary: - [#7264](#7264) -> `docs/resources/prompt-assets/dgx-station.md`, `docs/changelog/2026-07-20.mdx`: Record the versioned Station installer path, Nemotron 3 Ultra 550B default, and explicit DeepSeek override. - [#7261](#7261) -> `docs/get-started/dgx-station-preparation.mdx`, `docs/manage-sandboxes/recover-rebuild-sandboxes.mdx`, `docs/changelog/2026-07-20.mdx`: Include the OpenIB, legacy recovery, and Additional Setup documentation follow-ups. - [#7232](#7232) -> `docs/changelog/2026-07-20.mdx`: Document provider-reset recovery for wrapped OpenShell attachment diagnostics. - [#7189](#7189) -> `docs/reference/commands.mdx`, `docs/changelog/2026-07-20.mdx`: Document the managed-image route-selector rename and correct its one-release migration window. - [#7015](#7015) -> `docs/changelog/2026-07-20.mdx`: Document corrected OpenClaw WhatsApp health reporting. - No additional user-facing page update is needed for [#7193](#7193), [#7110](#7110), [#6783](#6783), or [#7263](#7263) because they change contributor governance, internal CI or release automation, or editorial style without changing supported user behavior. - [#7242](#7242) and [#7225](#7225) are already ancestors of and documented in v0.0.89, so this entry does not duplicate them despite their stale v0.0.90 labels. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [x] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates - [ ] Tests added or updated for changed behavior - [x] Existing tests cover changed behavior — justification: `test/changelog-docs.test.ts` validates the dated changelog heading, SPDX form, version order, and published links. - [ ] 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: ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: Not applicable; this PR does not change `scripts/prepare-dgx-station-host.sh` or runtime behavior. - Station profile/scenario: Not applicable. - Result: Not applicable. - Supporting evidence: Not applicable. ## Verification - [x] PR description includes a `Signed-off-by:` line 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 — `npx vitest run test/changelog-docs.test.ts` (6 passed). - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — command/result: Not run; this is a focused documentation-only change. - [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 two unrelated baseline warnings for unauthenticated redirect checks and the existing light-mode contrast ratio. - [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) --- Signed-off-by: Julie Yaunches <jyaunches@nvidia.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Added release notes for v0.0.90 covering inference routing, credential reset behavior, WhatsApp status detection, and DGX Station coding-agent guidance. - Updated custom Dockerfile guidance to document continued support for the legacy provider argument through v0.0.90. - Clarified that legacy declarations must be renamed to `NEMOCLAW_INFERENCE_PROVIDER_ID` before v0.0.91. - Added and refreshed related documentation links. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
22 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a NemoClaw technical-English profile based on ASD-STE100 Issue 9 without claiming full compliance. It simplifies 40 PR-related skill files, standardizes PR SHA terms in E2E messages and documentation, and starts a 30-day non-blocking changed-text pilot. It also repins platform prompt assets after the DGX Station guidance rewrite.
Changes
ci_green_shaand update its tests.PR SHA,base SHA, or the referenced SHA across E2E messages, tests, workflows, and review documents.Type of Change
Quality Gates
DGX Station Hardware Evidence
scripts/prepare-dgx-station-host.shis unchanged.Verification
Signed-off-by:line and every commit appears asVerifiedin GitHubpre-commit,commit-msg, andpre-pushhooks passed, ornpm run check:diffpassed when hooks were skipped or unavailablenpm run docsbuilds without warnings (doc changes only) — Build passed. Fern reported two unrelated warnings: the unauthenticated redirect check and the existing light-mode contrast ratio.Signed-off-by: Carlos Villela cvillela@nvidia.com
Summary by CodeRabbit