docs: correct outdated/inaccurate sections across 4 doc pages

[SequeI]

Summary

• tool-sandbox.mdx: fix Tool Sandbox mental model — the outer session's exec grant is built from every trusted PATH directory (allow-listing every executable found there), not just the initial program and shims. Verified against crates/nono-cli/src/tool-sandbox/platform/linux.rs and reproduced on a real Landlock host.
• overview.mdx: update "Resource Exhaustion" — memory and process-count are now enforced on Linux via cgroup v2 (memory.max, pids.max); CPU/disk and macOS remain unenforced. Verified against resource_cgroup.rs and reproduced with --memory/--max-processes triggering real OOM kills and fork EAGAIN.
• profiles-groups.mdx: fix "Hooks" section — profile-level hooks.<target> installation was removed in v0.44.0 and now only prints a note; actual wiring lives in pack package.json wiring directives. Clarify this is distinct from Session Hooks.
• profiles-groups.mdx: fix heading nesting — promote "AF_UNIX Socket Grants" and "Working Directory" from h3 to h2 so they're no longer nested under "Session Hooks".

Closes #1630
Closes #1664
Closes #1645
Closes #1644

Verification

All four claims were manually verified, not just read from source:

• Ran a Landlock-enabled Linux VM (Lima) with a live Tool Sandbox profile: an undeclared PATH binary executed fine; an identical binary placed outside PATH was denied — confirming the corrected mental model in Docs: tool sandbox is not explained correcly #1630.
• On the same VM, nono run --memory 32M triggered a real cgroup v2 OOM kill of the whole process tree, and nono run --max-processes 5 triggered kernel fork EAGAIN without killing anything — confirming docs: "Resource Exhaustion" section in architecture overview is outdated — memory/process limits now exist #1664's corrected text.
• Confirmed macOS explicitly rejects --memory/--max-processes ("resource limits are only enforced on Linux (cgroup v2)").
• Read profile_runtime.rs::install_profile_hooks to confirm profile-level hooks installation was removed in v0.44.0 (CHANGELOG confirms), which is a stronger correction than Docs: How do hooks work? #1645 originally asked for.

Test plan

• Docs-only change — no code touched
• Manually verified all four corrected claims against actual code/runtime behavior (see above)
• CI docs build (if any) passes

[github-actions]

PR Review Summary

Size

Metric	Value
Lines added	+21
Lines removed	-23
Total changed	44
Classification	Small (< 50 lines)

Affected crates

No crate source directories are directly affected.

Blast radius — Contained

This PR touches: unknown file types

---

_{Updated automatically on each push to this PR.}

[nogent-nolabs-ai]

nogent code review

No issues found; the documentation updates are correct and precisely match the implementation.

Findings: none flagged in scope.

_{Automated code + security review. CI already covers clippy, rustfmt, tests, cargo-audit and commit-lint.}