docs: update Skyhook wording to NodeWright in operator topic docs

[lockwobr]

What

Continues the Skyhook→NodeWright rename into the operator topic docs, updating the product/concept noun in prose. Five files, pure word swaps (68/68):

• docs/uninstall.md
• docs/runtime_required.md
• docs/resource_management.md
• docs/operator-status-definitions.md
• docs/kubernetes-support.md

How it stays safe

Unlike the test READMEs, these docs are dense with live commands where skyhook is a frozen literal — the -n skyhook namespace, kubectl get/delete/patch skyhook, the skyhook.nvidia.com/* group / annotations / finalizer, SKYHOOK_* env vars, and YAML examples. Every one of those lives inside a backtick code span or a fenced code block.

So the swap runs only in prose — it skips fenced code blocks and inline-code spans entirely. That mechanically preserves every command, namespace, annotation key, finalizer, env var, YAML example, and Go identifier (CleanupSCRMetadata, processSkyhooksPerNode). Verified post-swap: zero -n nodewright, zero nodewright.nvidia.com, zero NODEWRIGHT_, no broken doc links, no shifted-heading anchors referenced elsewhere.

SCR → CR

SCR ("Skyhook Custom Resource") no longer expands sensibly, so these docs now use plain CR. The CleanupSCRMetadata Go function name is left intact (word-boundary replace). Note SCR is still used elsewhere in the repo (code comments, other docs) — a broader SCR→CR sweep is a separate follow-up.

Deliberately out of scope

• docs/nodewright-migration.md — intentionally discusses both names.
• docs/cli.md, docs/metrics/README.md — have version-matrix / metric-name nuance; deferred to focused follow-ups.
• Frozen surfaces everywhere (namespace, agent image/package, CRD group + kind, chart/config CRD+RBAC, metric names, examples).

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated five documentation files to replace affected Skyhook terminology with NodeWright. Kubernetes support, operator status, resource management, runtime-required behavior, uninstall workflows, troubleshooting, deletion edge cases, and known issues were revised. No exported or public entity declarations changed.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels: doc

Suggested reviewers: rice-riley, ayuskauskas

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: renaming Skyhook wording to NodeWright across operator topic docs.
Description check	✅ Passed	The description is directly related to the changeset and accurately explains the prose-only rename and scoped files.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/docs-nodewright-prose

---

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

[coderabbitai]

Actionable comments posted: 3

🤖 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 `@docs/resource_management.md`:
- Around line 1-3: Update the introductory description of resource management to
state that NodeWright consumes an existing namespace LimitRange for defaults and
does not install or guarantee one. Keep the documented behavior in the later
LimitRange section consistent, including that namespaces without one produce
BestEffort pods.

In `@docs/runtime_required.md`:
- Around line 52-55: Update the prose in the taint-removal section to
consistently use the terms “NodeWright” and “NodeWrights,” replacing “skyhook,”
“nodewrights,” and “nodewright” where they are descriptive nouns. Preserve the
`skyhook.nvidia.com` namespace unchanged.

In `@docs/uninstall.md`:
- Around line 86-89: Update the NodeWright CR deletion documentation to clarify
that finalizer cleanup removes only this NodeWright’s
nodewright.nvidia.com/cordon_<nodewright-name> annotation. State that nodes are
uncordoned only when no other cordon_* owner annotations remain, preserving
cordons owned by other NodeWrights.

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

Plan: Enterprise

Run ID: 6126d91f-082a-40a8-89c7-8e9a18104b77

📥 Commits

Reviewing files that changed from the base of the PR and between afa1b84 and e99a9a3.

📒 Files selected for processing (5)

• docs/kubernetes-support.md
• docs/operator-status-definitions.md
• docs/resource_management.md
• docs/runtime_required.md
• docs/uninstall.md