tools/validation/UPSTREAM.md

# Upstream sync

`tools/validation/` is a **verbatim fork** of the `validation/` tree from:

- **Repo:** `omniverse/kit-extensions/simready-explorer`
- **Host:** `gitlab-master.nvidia.com`
- **Branch:** `dev/dloginowski/validation-reporting`
- **URL:** https://gitlab-master.nvidia.com/omniverse/kit-extensions/simready-explorer/-/tree/dev/dloginowski/validation-reporting

It is **not** a git submodule. Upstream changes do not flow here automatically.

## Current pin

```
upstream_sha: 4bd42394685156d97f3e3bf371117f53e8dd8ab1
synced_at:    2026-05-22
synced_by:    dloginowski
```

> Bump these three fields whenever you re-run `_sync.sh`.

## Check for drift

```bash
git ls-remote https://gitlab-master.nvidia.com/omniverse/kit-extensions/simready-explorer.git \
  refs/heads/dev/dloginowski/validation-reporting
```

Compare the printed SHA to `upstream_sha` above. If they differ, upstream has
new commits we don't have.

## Pull a new version

```bash
bash tools/validation/_sync.sh
```

The script:

1. Shallow-clones the upstream branch to a temp dir.
2. Reports the new SHA and how many commits ahead of `upstream_sha` it is.
3. Rsyncs upstream `validation/*` over `tools/validation/*`, preserving
   `UPSTREAM.md` and `_sync.sh` themselves.
4. Prints a diff stat so you can see what changed.

After running, review the diff, **manually update the pin block above**, then
commit:

```bash
git add tools/validation/
git commit -m "Sync tools/validation/ from upstream <short-sha>"
```

## When upstream lands in `simready-explorer` proper

The upstream README (`tools/validation/README.md`) calls this directory
"demo / review staging" and outlines the intended integration into
`simready-explorer`'s existing library + skills patterns. Once that lands:

1. Delete `tools/validation/`.
2. Replace the runner-side driver `tools/hf_watch/validate.py` with calls
   into `simready-explorer`'s public CLI (likely `repo.bat validate` or
   the `simready.validate` library entry points).
3. Drop this file.

Until then, treat this fork as a snapshot.