docs: Reafactor the README.md

.agents/skills/review-doc-style/SKILL.md

@@ -30,6 +30,16 @@ and NVIDIA NeMo Fabric repo conventions.
 - Run `just docs` to regenerate and validate the API reference after changing a
   source or generator.
 
+## Documentation Links
+
+- For links between files under `docs/`, use paths relative to the source file
+  and include the target file's `.mdx` extension. These links work in both Fern
+  builds and repository browsers.
+- Do not use Fern site-root paths such as
+  `[NeMo Fabric overview](/nemo/fabric/about-nemo-fabric/overview)`.
+- Use the repository-relative equivalent, such as
+  `[NeMo Fabric overview](../about-nemo-fabric/overview.mdx)`.
+
 ## Review Priorities
 
 - Prioritize factual accuracy over copy polish
@@ -65,6 +75,8 @@ Treat these as blocking issues:
 - User-facing naming is inconsistent with current repo terminology
 - MDX top-of-file SPDX comments use HTML comment delimiters instead of
   `{/* ... */}`
+- Links between files under `docs/` use Fern site-root paths instead of
+  repository-relative `.mdx` paths
 - NVIDIA is not capitalized correctly
 - Code, commands, paths, or filenames are not formatted as inline code where needed
 
@@ -87,7 +99,8 @@ Flag these when they materially improve clarity or consistency:
 - **Entry points**: Top-level docs changed wherever users would naturally look first.
 - **Headings**: Technical docs use title case consistently.
 - **Voice**: Prefer active voice, present tense, short sentences, and plain English.
-- **Links**: Use descriptive anchor text, not bare URLs or weak labels.
+- **Links**: Use descriptive anchor text, not bare URLs or weak labels. For links
+  within `docs/`, use repository-relative paths with the `.mdx` extension.
 - **Formatting**: Commands, code elements, expressions, file names, and paths are monospace.
 - **MDX headers**: Top-of-file MDX SPDX comments use `{/*` and `*/}` delimiters.
 - **Procedures**: Steps are easy to scan, imperative, and split into smaller tasks when long.

.coderabbit.yaml

@@ -74,6 +74,7 @@ reviews:
     - path: "{docs/**,README.md,AGENTS.md}"
       instructions: |
         Review documentation for technical accuracy against the current API, command correctness, and consistency with generated schemas.
+        For links between files under docs/, require paths relative to the source file with the target file's .mdx extension so they work in both Fern builds and repository browsers. Flag Fern site-root links such as [NeMo Fabric overview](/nemo/fabric/about-nemo-fabric/overview); use the repository-relative equivalent, such as [NeMo Fabric overview](../about-nemo-fabric/overview.mdx).
     - path: "{*.md,**/*.md,**/*.mdx,**/*.ipynb}"
       instructions: |
         Enforce the product name in user-facing prose: use "NVIDIA NeMo Fabric" on first use and "NeMo Fabric" thereafter. Flag standalone capitalized "Fabric" when it refers to the product. Do not flag the lowercase `fabric` CLI command, package/import/crate names, code identifiers, API symbols, configuration keys, file paths, or unrelated generic uses of the word.

.gitignore

@@ -18,6 +18,7 @@ build/
 /docs/node_modules/
 
 examples/*/artifacts/
+examples/harbor/*/runs/
 tests/fixtures/*/artifacts/
 integrations/harbor/demo/runs/
 integrations/harbor/demo/task/environment/vendor/

AGENTS.md

@@ -36,7 +36,10 @@ Key conventions for the two tiers:
   and example URLs rather than a docs-site domain, so they keep working when
   exported.
 - **Supported consumer surface:** the consumer tier currently ships one skill,
-  `nemo-fabric-integrate`, for typed Python SDK integration.
+  `skills/integrations/consumer/nemo-fabric-integrate`, for typed Python SDK
+  integration. Future public harness adapter-authoring skills belong under
+  `skills/integrations/harness/`; repository-internal adapter maintenance stays
+  in `.agents/skills/`.
 
 ## Documentation And Contribution Workflow
 

CONTRIBUTING.md

@@ -13,25 +13,6 @@ the development workflow, coding standards, and pull request process.
 This section collects the setup steps needed before building, testing, or
 contributing changes.
 
-### Package Installation
-
-NeMo Fabric is not currently available on PyPI. To consume the Python packages,
-build wheels from a source checkout:
-
-```bash
-just wheels
-uv pip install --find-links dist nemo-fabric
-```
-
-Adapters are distributed as optional extras. For example, install the Hermes Agent adapter with:
-
-```bash
-uv pip install --find-links dist "nemo-fabric[hermes]"
-```
-
-Refer to the [installation guide](docs/getting-started/install.mdx) for the
-complete list of adapters and installation options.
-
 ### Source Development
 
 Install these tools before you start:
@@ -54,8 +35,36 @@ uv sync --all-groups --all-extras
 just no_uv=true build-all
 ```
 
-Verify the checkout by running the test suites described in
-[Testing Requirements](#testing-requirements).
+In the above, replace `3.13` with the Python version you want to use for development.
+
+Verify the checkout by running the test suites described in [Testing](#testing).
+
+### Package Installation
+
+To build Python packages (wheels) locally from a source checkout:
+
+```bash
+just wheels
+```
+
+The resulting wheel files are placed in the `dist/` directory. Install the
+packages into a virtual environment with:
+
+```bash
+uv pip install --find-links ./dist "nemo-fabric[runtime]"
+```
+
+Adapters are distributed as optional extras. For example, install the Hermes
+Agent adapter with:
+
+```bash
+uv pip install --find-links ./dist "nemo-fabric[hermes]"
+```
+
+Refer to the [installation guide](docs/getting-started/install.mdx) for the
+complete list of adapters and installation options.
+
+
 
 ## Release Tagging
 
@@ -95,7 +104,7 @@ Use the naming conventions appropriate to each language: Rust and Python use
 `snake_case` for functions and variables, Rust types use `PascalCase`, and
 Python classes use `PascalCase`.
 
-## Testing Requirements
+## Testing
 
 **Run tests for every language surface affected by your changes.** If a change
 touches the Rust core or public schemas, run both the Rust and Python suites