chore: final sweep — fix remaining stale repo/hostname references

Comprehensive grep across both repos for any case variant of the
pre-rename names (OpenSentry-Command / opensentry-cloud-node /
OpenSentry-CloudNode / opensentry-cloudnode) surfaced four CC files
still pointing at the old CloudNode repo via the PascalCase typo
"OpenSentry-CloudNode" (which was never the actual repo name —
GitHub's case-insensitive resolution had been masking it):

  - README.md — 5 occurrences across the header badges, the install
    banner, and the troubleshooting CloudNode-releases link.
  - CONTRIBUTING.md — repository table row (display text + URL) +
    the `cd OpenSentry-CloudNode` snippet + the "See the CloudNode
    README" link.
  - docs/LAUNCH_HANDOFF.md — operator-launch reference to the
    CloudNode README path.
  - .github/ISSUE_TEMPLATE/config.yml — the Documentation contact-
    link URL was the wrong hostname entirely (`opensentry.fly.dev`
    instead of `opensentry-command.fly.dev`).  Probably a stragger
    from a pre-fly-app-rename era.  Fixed to the canonical
    production docs URL.

All of these would have redirected (GitHub case-insensitive matches
+ permanent-redirects on repo renames) but anyone landing via these
links would see "OpenSentry-CloudNode" in their address bar after
the redirect chain — and that's exactly the trail of stale-brand
crumbs the user asked me to wipe.

Final state: every `github.com/SourceBox-LLC/<repo>` URL in source
points at one of the four current canonical names — Sentinel-Command,
Sentinel-CameraNode, SourceBox-Sentinel, or an issues/discussions/
security path under those.  The only remaining `OpenSentry-Command`
/ `opensentry-cloud-node` strings live in the AGENTS.md brand-history
note (grep-discoverability, plain text not a URL) plus the deliberate
load-bearing identifier comments in Cargo.toml / database.rs /
release.yml.

612 backend tests pass; frontend build clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Sbussiso

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
   - name: Documentation
-    url: https://opensentry.fly.dev/docs.html
+    url: https://opensentry-command.fly.dev/docs
     about: Check the documentation for setup guides and troubleshooting
   - name: Discussions
     url: https://github.com/SourceBox-LLC/Sentinel-Command/discussions

CONTRIBUTING.md

@@ -40,7 +40,7 @@ Sentinel has two main components:
 | Component | Language | Repository |
 |-----------|----------|------------|
 | **Command Center** | Python (FastAPI) + React | [Sentinel-Command](https://github.com/SourceBox-LLC/Sentinel-Command) |
-| **CloudNode** | Rust | [OpenSentry-CloudNode](https://github.com/SourceBox-LLC/OpenSentry-CloudNode) |
+| **CloudNode** | Rust | [Sentinel-CameraNode](https://github.com/SourceBox-LLC/Sentinel-CameraNode) |
 
 ### Command Center
 
@@ -61,12 +61,12 @@ npm run dev                   # http://localhost:5173
 ### CloudNode
 
 ```bash
-cd OpenSentry-CloudNode
+cd Sentinel-CameraNode
 cargo build --release
 ./target/release/sourcebox-sentry-cloudnode setup
 ```
 
-See the [CloudNode README](https://github.com/SourceBox-LLC/OpenSentry-CloudNode) for full setup instructions.
+See the [CloudNode README](https://github.com/SourceBox-LLC/Sentinel-CameraNode) for full setup instructions.
 
 ## License
 

README.md

@@ -9,7 +9,7 @@
     ·
     <a href="#api-reference">API Reference</a>
     &middot;
-    <a href="https://github.com/SourceBox-LLC/OpenSentry-CloudNode">CloudNode</a>
+    <a href="https://github.com/SourceBox-LLC/Sentinel-CameraNode">CloudNode</a>
   </p>
 </p>
 
@@ -21,7 +21,7 @@
 
 ---
 
-Sentinel Command Center is the cloud hub for the Sentinel ecosystem (Sentinel by SourceBox). It receives live HLS video streams from [CloudNode](https://github.com/SourceBox-LLC/OpenSentry-CloudNode) devices on your local network, caches segments in memory, and proxies them to any browser. Authentication and multi-tenant isolation are handled by Clerk.
+Sentinel Command Center is the cloud hub for the Sentinel ecosystem (Sentinel by SourceBox). It receives live HLS video streams from [CloudNode](https://github.com/SourceBox-LLC/Sentinel-CameraNode) devices on your local network, caches segments in memory, and proxies them to any browser. Authentication and multi-tenant isolation are handled by Clerk.
 
 **What it does:**
 - Receives live HLS video from CloudNode devices and proxies it to the browser via a same-origin in-memory cache — no object store, no presigned URLs
@@ -38,7 +38,7 @@ Sentinel Command Center is the cloud hub for the Sentinel ecosystem (Sentinel by
 
 > **Looking for the product?** Sign up at the [live app](https://opensentry-command.fly.dev) — we host Sentinel by SourceBox as a SaaS, you don't run any servers. The repo is public for trust + transparency: every claim on `/security` and `/docs` points at the file that implements it.
 >
-> The Quick Start below is for **engineers who want to clone the repo and run it locally** — for code review, contributing fixes, or auditing what we run. It is **not** the install path for end users; users sign up at the link above. The CloudNode camera daemon (the piece that genuinely runs on customer hardware) is in a [separate repo](https://github.com/SourceBox-LLC/OpenSentry-CloudNode) — its own README walks through installation.
+> The Quick Start below is for **engineers who want to clone the repo and run it locally** — for code review, contributing fixes, or auditing what we run. It is **not** the install path for end users; users sign up at the link above. The CloudNode camera daemon (the piece that genuinely runs on customer hardware) is in a [separate repo](https://github.com/SourceBox-LLC/Sentinel-CameraNode) — its own README walks through installation.
 
 ---
 
@@ -74,7 +74,7 @@ App available at `http://localhost:5173`
 
 ### 3. Connect a CloudNode
 
-Create a camera node from the Settings page, then run [CloudNode](https://github.com/SourceBox-LLC/OpenSentry-CloudNode) with those credentials. Cameras auto-register when the CloudNode first connects.
+Create a camera node from the Settings page, then run [CloudNode](https://github.com/SourceBox-LLC/Sentinel-CameraNode) with those credentials. Cameras auto-register when the CloudNode first connects.
 
 ### 4. Connect an MCP client (optional)
 
@@ -549,7 +549,7 @@ This project is **not currently accepting external code contributions**. Bug rep
 <p align="center">
   <a href="https://opensentry-command.fly.dev">Sentinel Command Center</a>
   &middot;
-  <a href="https://github.com/SourceBox-LLC/OpenSentry-CloudNode">CloudNode</a>
+  <a href="https://github.com/SourceBox-LLC/Sentinel-CameraNode">CloudNode</a>
   &middot;
   Made by <a href="https://github.com/SourceBox-LLC">SourceBox LLC</a>
 </p>

docs/LAUNCH_HANDOFF.md

@@ -279,7 +279,7 @@ under a realistic camera load.
    - Egress bandwidth to Command Center.
    - Whether motion detection completes within the segment window.
 3. Document the result somewhere — at minimum in
-   `OpenSentry-CloudNode/README.md` under a "Performance reference"
+   `Sentinel-CameraNode/README.md` under a "Performance reference"
    section. If a Pi 4 only handles 2 cameras at 1080p, that's
    useful for users to know upfront. If it handles 8, even better.