docs(contributing): add npm link step to developer setup

[dknos]

Summary

• Adds missing npm link step to the developer setup section in CONTRIBUTING.md
• Required for the nemoclaw CLI to work locally during development

Test plan

• Follow the updated setup instructions from scratch
• Verify nemoclaw command is available after setup

Fixes #1429
Fixes #989

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added a "Local Development Testing" section to the contribution guidelines with step-by-step instructions to build the project, locally link the CLI for testing, verify the linked CLI version, and unlink the local CLI after testing. Documentation-only change to help contributors test CLI changes without modifying code.

Signed-off-by: dknos rneebo@gmail.com

Signed-off-by: dknos rneebo@gmail.com

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Added a "Local Development Testing" subsection to CONTRIBUTING.md instructing developers to run npm link from the repo root (including an explicit cd .. if inside nemoclaw/), verify with nemoclaw --version, and use npm unlink -g nemoclaw to undo. Documentation-only change.

Changes

Cohort / File(s)	Summary
Documentation CONTRIBUTING.md	Added "Local Development Testing" section with post-build CLI workflow: cd .. if inside nemoclaw/, run npm link, verify via nemoclaw --version, and teardown using npm unlink -g nemoclaw.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I hopped into docs with a wink and a blink,
Linked the CLI so local tests won't sink,
npm link — a hop to make commands come true,
nemoclaw --version — a quick peep through,
npm unlink — tidy trail, carrot-cheery adieu 🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title accurately reflects the main change: adding npm link documentation to the developer setup in CONTRIBUTING.md.
Linked Issues check	✅ Passed	The PR fulfills all coding requirements from issues #1429 and #989: adds the missing npm link step, includes verification command, provides unlink instructions, and clarifies working directory context.
Out of Scope Changes check	✅ Passed	All changes are directly related to the linked issues. Only CONTRIBUTING.md was modified with a new Local Development Testing section, which is exactly what the issues required.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 56-61: The docs risk instructing users to run npm link from the
wrong directory (e.g., still in ./nemoclaw) which can link the plugin instead of
the root CLI; update the CONTRIBUTING.md step before the npm link command to
make the working directory explicit by telling users to return to the repo root
(or run the appropriate cd) so npm link targets the CLI package, then run npm
link and verify with the nemoclaw --version check.

🪄 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: Pro

Run ID: 3b8f0111-0648-4d9b-a5b7-76d01e93c77c

📥 Commits

Reviewing files that changed from the base of the PR and between c99e3e8 and f38642e.

📒 Files selected for processing (1)

• CONTRIBUTING.md

[dknos]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[dknos]

Addressed: the working directory before npm link is now explicit. After the plugin build step leaves the user in nemoclaw/, a cd .. returns them to the repo root before running npm link, ensuring the CLI package (not the plugin) is linked. See commits 785f2b4 and 95d00e2.

[dknos]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[prekshivyas]

Thanks for this contribution @dknos — clean, well-scoped fix that addresses #1429 exactly. Appreciate you following up on the CodeRabbit working-directory feedback too.

One blocker before we can merge:

DCO sign-off missing. The dco-check CI is failing because the PR description needs a Signed-off-by: line. Please add the following to the bottom of your PR description:

Signed-off-by: Your Name <your-email@example.com>

Once that's in place, this is good to go.