Merge pull request #4 from NVIDIA-NeMo/chore/release-cleanup

chore: release cleanup — scrub internal refs, fix versions, add gover…

Author: rdasilveiracabral

.cursor/rules/viewer-react.mdc

@@ -0,0 +1,24 @@
+---
+name: Bug report
+about: Report a problem to help us improve
+title: "[Bug] "
+labels: bug
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To reproduce**
+Minimal steps or code to reproduce the behavior.
+
+**Expected behavior**
+What you expected to happen.
+
+**Environment**
+- OS:
+- Python version:
+- NOOA version (`nooa --version` or `python -c "import nooa; print(nooa.__version__)"`):
+- Model / provider:
+
+**Additional context**
+Logs, traces, or anything else relevant.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,18 @@
+---
+name: Feature request
+about: Suggest an idea or enhancement
+title: "[Feature] "
+labels: enhancement
+---
+
+**What problem are you trying to solve?**
+A clear description of the use case or limitation.
+
+**Proposed solution**
+What you'd like to happen.
+
+**Alternatives considered**
+Other approaches you've thought about.
+
+**Additional context**
+Anything else that helps explain the request.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,14 @@
+## What does this PR do?
+
+<!-- A clear, concise description of the change. -->
+
+## Related issues
+
+<!-- e.g. Closes #123 -->
+
+## Checklist
+
+- [ ] Code follows the project style (`uv run ruff check .` and `uv run ruff format --check .` pass)
+- [ ] Tests added/updated and passing (`uv run pytest`)
+- [ ] Docs updated if behavior or public APIs changed
+- [ ] New source files carry an SPDX license header

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is loosely
+based on [Keep a Changelog](https://keepachangelog.com/), and the project aims
+to follow semantic versioning.
+
+## [Unreleased]
+
+- Initial public release of NVIDIA Object-Oriented Agents (NOOA).

CHANGELOG.md

@@ -55,7 +55,7 @@ Install directly from GitHub with [uv](https://docs.astral.sh/uv/getting-started
 uv init my-agent-project
 cd my-agent-project
 
-uv add "nemo-labs-oo-agents @ git+https://github.com/NVIDIA-NeMo/labs-OO-Agents.git@main"
+uv add "nooa @ git+https://github.com/NVIDIA-NeMo/labs-OO-Agents.git@main"
 ```
 
 <details>
@@ -67,10 +67,10 @@ All of these live in the same repo and are addressed with `#subdirectory=…`.
 
 ```bash
 # CLI + TUI (beta): the `nooa` command, agent REPL, trace viewer, TUI
-uv add "nemo-labs-oo-agents-cli @ git+https://github.com/NVIDIA-NeMo/labs-OO-Agents.git@main#subdirectory=packages/nooa-cli"
+uv add "nooa-cli @ git+https://github.com/NVIDIA-NeMo/labs-OO-Agents.git@main#subdirectory=packages/nooa-cli"
 
 # Long-term memory subsystem (MemoryManager)
-uv add "nemo-labs-oo-agents-memory @ git+https://github.com/NVIDIA-NeMo/labs-OO-Agents.git@main#subdirectory=packages/nooa-memory"
+uv add "nooa-memory @ git+https://github.com/NVIDIA-NeMo/labs-OO-Agents.git@main#subdirectory=packages/nooa-memory"
 
 # Evaluation pipeline for agent testing
 uv add "eval_pipeline @ git+https://github.com/NVIDIA-NeMo/labs-OO-Agents.git@main#subdirectory=util/eval_pipeline"

CLAUDE.md

@@ -1,6 +1,6 @@
 # Releasing nemo-oo-agents
 
-Three workspace packages — `nemo-oo-agents`, `nemo-labs-oo-agents-cli`, and
+Three workspace packages — `nemo-oo-agents`, `nooa-cli`, and
 `nemo-oo-agents-benchmarks` — release together from the same git commit.
 Version is derived from `git describe` at build time by
 [`uv-dynamic-versioning`](https://github.com/ninoseki/uv-dynamic-versioning).
@@ -81,7 +81,7 @@ The wheel ships as `0.3.0-rc1` (PEP 440 normalizes to `0.3.0rc1`).
 
 ## Cross-package dependencies
 
-`nemo-labs-oo-agents-cli` and `nemo-oo-agents-benchmarks` declare their
+`nooa-cli` and `nemo-oo-agents-benchmarks` declare their
 dependency on core as a static lower-bound floor in their pyproject.toml:
 
 ```toml

README.md

@@ -0,0 +1,25 @@
+## Security
+
+NVIDIA is dedicated to the security and trust of our software products and services, including all source code repositories managed through our organization.
+
+If you need to report a security issue, please use the appropriate contact points outlined below. **Please do not report security vulnerabilities through GitHub.** If a potential security issue is inadvertently reported via a public issue or pull request, NVIDIA maintainers may limit public discussion and redirect the reporter to the appropriate private disclosure channels.
+
+## Reporting Potential Security Vulnerability in an NVIDIA Product
+
+To report a potential security vulnerability in any NVIDIA product:
+
+- Web: [Security Vulnerability Submission Form](https://www.nvidia.com/object/submit-security-vulnerability.html)
+- E-Mail: psirt@nvidia.com
+  - We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key)
+  - Please include the following information:
+    - Product/Driver name and version/branch that contains the vulnerability
+  - Type of vulnerability (code execution, denial of service, buffer overflow, etc.)
+    - Instructions to reproduce the vulnerability
+    - Proof-of-concept or exploit code
+    - Potential impact of the vulnerability, including how an attacker could exploit the vulnerability
+
+While NVIDIA currently does not have a bug bounty program, we do offer acknowledgement when an externally reported security issue is addressed under our coordinated vulnerability disclosure policy. Please visit our [Product Security Incident Response Team (PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) policies page for more information.
+
+## NVIDIA Product Security
+
+For all security-related concerns, please visit NVIDIA's Product Security portal at https://www.nvidia.com/en-us/security