docs: point markdown backlogs at Gitea issues (status lives in Gitea)

Adds the family backlog standard to the root index (open work = Gitea issues, shared label set, BTDB excluded) and converts components/*/GAPS, hosted-lib CLAUDE.md notes, code-reviews, infra/glauth and plan docs to banner + issue pointers (scadaproj #5-#19, ScadaBridge#79).
2026-11-06 15:34:30 -05:00
parent 967da5b43b
commit fd180e576f
24 changed files with 123 additions and 29 deletions
@@ -147,7 +147,7 @@ Single page (`/`), `ThemeShell` chassis with its own product name/accent so it r
 ## 9. Acceptance (v1 definition of done)

 - The §4 ScadaBridge site-node health PR is merged and site rows render with full check detail + Active/Standby (no special-cased rows anywhere).
- Registry pointed at the live docker-dev rigs (OtOpcUa 6-node + ScadaBridge local cluster) renders every instance correctly, including: each Active/Standby pair (central **and** site pairs) showing exactly one Active; **each cluster group showing its current leader, and the leader chip moving when the leader node is stopped**; killing a node flips its card to Unreachable within ~2 cadences and back on restart; a Degraded check (e.g. stop a dependency) shows Warn with the failing entry visible; management links open the right app UIs; the page is reachable with no login.
+- Registry pointed at the live docker-dev rigs (OtOpcUa 6-node + ScadaBridge local cluster) renders every instance correctly, including: each Active/Standby pair (central **and** site pairs) showing exactly one Active; **each cluster group showing its current leader, and the leader chip moving when the leader node is stopped**; killing a node flips its card to Unreachable within ~2 cadences and back on restart; a Degraded check (e.g. stop a dependency) shows Warn with the failing entry visible; management links open the right app UIs; the page is reachable with no login. (OtOpcUa one-Active + leader-chip checks still to re-run → #14)
 - **Cache/staleness proven live:** first page load renders instantly from cache (no poll on request); with auto-refresh paused (or the poller stopped) past `StaleAfterSeconds`, every card flips to Stale, and resumes cleanly.
 - Boot fails with a clear `ConfigPreflight` message on a malformed registry.
 - `dotnet test` green: options validator, status derivation (incl. flap damping, staleness marking, leader extraction + disagreement flag, JSON parsing golden tests against captured real payloads from all four apps — with and without `data`), snapshot store, and a bUnit render test of `InstanceCard`.
@@ -1,6 +1,11 @@
 # VD03 NAM AD LDAP cutover — plan (NOT executed)

-**Written 2026-08-13. Status: PLAN ONLY.** Swap every auth-bearing service on
+> **Status lives in Gitea.** Open items from this file are tracked as issues on
+> [gitea.dohertylan.com/dohertj2/scadaproj](https://gitea.dohertylan.com/dohertj2/scadaproj/issues)
+> (label `migrated`, 2026-11-06). This file is a historical/design record — do not track status
+> here; file new work as an issue.
+
+**Written 2026-08-13. Status: PLAN ONLY.** Execution (VD03, then QA) → #6; consider the Auth `0.4.1` bump first → #5. Swap every auth-bearing service on
 `wonder-app-vd03` from its current login posture (mostly login-disabled) to the real
 Zimmer NAM Active Directory, with the service-account password held as a
 `${secret:}` reference in each app's encrypted Secrets store — never in config.
@@ -21,7 +26,7 @@ and the wonder deploy records (memory: `wonder-upgrade-program`).
 | Overview | ❌ exempt | — | No login **by design** (holds no credentials; references no Auth package) |

 Out of scope: windev's OtOpcUa/mxgw instances, the QA pair (VQ03/VQ04 — do it as a
-follow-on once VD03 has soaked; QA is where the 2-node/failover behaviour actually gets
+follow-on once VD03 has soaked, → #6; QA is where the 2-node/failover behaviour actually gets
 exercised), and OtOpcUa's OPC UA data plane (API-key auth since Gitea #520).

 > ⚠️ **ignitionoee (router): LDAP setup ON HOLD** — explicit decision 2026-08-13. Its role