Merge pull request #9 from blueflare-energy/org-transfer-refs

Org transfer: update repo references to blueflare-energy

README.md

@@ -1,6 +1,6 @@
 # warden-sdk
 
-[![ci](https://github.com/bfe-noah/warden-sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/bfe-noah/warden-sdk/actions/workflows/ci.yml)
+[![ci](https://github.com/blueflare-energy/warden-sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/blueflare-energy/warden-sdk/actions/workflows/ci.yml)
 ![Lines of code](.github/badges/loc.svg)
 ![Tests](.github/badges/tests.svg)
 ![Coverage](.github/badges/coverage.svg)

docs/decisions/0003-standalone-repo.md

@@ -10,7 +10,8 @@ no CI, tests, or versioning of their own. The SDK requirement (future-features-2
 §SDK) calls for "its own repo, held to firmware standards."
 
 ## Decision
-A **private** `bfe-noah/warden-sdk` GitHub repo, standalone from day one with its own
+A **private** `warden-sdk` GitHub repo (now `blueflare-energy/warden-sdk` and public
+per ADR-0007), standalone from day one with its own
 CI/versioning. Work lands on a `bringup` branch; the first commit to `main` is gated
 on a passing review run, green CI, and the maintainer's fresh explicit go-ahead.
 

docs/decisions/0004-ci-runner.md

@@ -12,7 +12,7 @@ registration cannot be shared across repos by label alone.
 
 ## Decision
 Register a **third repo-scoped runner instance** on `bfe-mpc-0640`, label
-`warden-sdk` (own systemd unit `actions.runner.bfe-noah-warden-sdk.*`, own
+`warden-sdk` (its own repo-scoped runner systemd unit, own
 `CPUQuota=400%`/`MemoryMax=6G` drop-in). Only the heavy `kernel-build` job uses
 `runs-on: [self-hosted, warden-sdk]`; all host-testable jobs (tests, coverage, MC/DC,
 benchmarks, badges, patches-apply) run on GitHub-hosted runners.