Harden agentic workflows: fix libtorch pin bump, tighten scopes, correct shepherd/closer logic

- libtorch-bump: bump BOTH unconditional <LibTorchPackageVersion> lines in
  Directory.Build.props (top-level and the libtorch- PropertyGroup) and fix the
  grep verification counts; previously only one was updated, leaving the package
  build on the old version.
- libtorch-bump: restrict create-pull-request allowed-files to the two props
  files actually edited (was build/**, pkg/**, *_cuda.txt).
- libtorch-bump: make intent consistent - only patch-level bumps get a PR; any
  major OR minor change files a tracking issue (minor libtorch releases change
  the native ABI).
- pr-shepherd: description no longer claims it applies labels (it is comment-only);
  fetch statusCheckRollup before claiming merge-ready; stop listing bogus conflict
  paths (the API does not expose them).
- out-of-scope-closer: close idempotency no longer strands issues left open by a
  partial prior run; fetch full issue detail for the active-discussion check;
  handle regex: entries locally since GitHub search cannot evaluate them.
- issue-triage: only demand a stack trace for crash/exception bugs.
- Recompiled lock files (gh aw compile); setup action is now SHA-pinned.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: kotlarmilos

.github/aw/actions-lock.json

@@ -4,6 +4,11 @@
       "repo": "actions/github-script",
       "version": "v9.0.0",
       "sha": "3a2844b7e9c422d3c10d287c895573f7108da1b3"
+    },
+    "github/gh-aw-actions/setup@v0.71.5": {
+      "repo": "github/gh-aw-actions/setup",
+      "version": "v0.71.5",
+      "sha": "b8068426813005612b960b5ab0b8bd2c27142323"
     }
   }
 }

.github/workflows/code-review.agent.lock.yml

@@ -86,7 +86,7 @@ Classify issue #${{ github.event.issue.number }} into exactly one of TorchSharp'
    - Title or body mentions `TorchSharp.Examples`, `models/`, pretrained, model zoo -> `zoo`.
    - Title or body mentions `libtorch`, version bump, NuGet, dependency -> `dependencies`.
 4. Decide whether to comment. Comment ONLY if:
-   - `bug` and (no code block in body OR no stack trace OR no version info), OR
+   - `bug` and (no minimal repro / code block in body OR no version info OR (the issue describes a crash or exception AND no stack trace is included)). Do not demand a stack trace for non-crash bugs such as numerical regressions or incorrect output.
    - `enhancement` / `Missing Feature` and the body has no concrete proposal (no method signature, no PyTorch link, no concrete use case).
 5. Apply labels; post the comment if step 4 says to.