docs: relabel wonder-app-vd03 as DEV, not production, across plans, records, reviews and API specs

vd03 is the DEV box (vd = DEV, vq03/vq04 = QA). Historical docs called it prod/production.
Only vd03-referential uses are changed; generic 'production' wording (production HOCON,
production code paths, ASPNETCORE_ENVIRONMENT=Production, real-world production guidance)
is unchanged. One verbatim git commit message quoted in PLAN-07 is left as recorded.
This commit is contained in:
Joseph Doherty
2026-11-10 15:11:45 -05:00
parent ee320cd544
commit 48517b49fb
35 changed files with 110 additions and 110 deletions
+2 -2
View File
@@ -158,7 +158,7 @@ Queried live against `scadabridge-mssql` on 2026-08-11:
Not only has the library never been used — most scripts don't declare a typed parameter shape at
all, which is the precondition for ever wanting a reusable one.
*(Production `wonder-app-vd03` was deliberately not queried; see §7.)*
*(DEV `wonder-app-vd03` was deliberately not queried; see §7.)*
### 6.2 Origin: speculative, not requirement-driven
@@ -203,7 +203,7 @@ months, take option 1 rather than leaving permanent unexercised surface in the c
- The CLI has no schema-library commands either (`src/ZB.MOM.WW.ScadaBridge.CLI/` has no
`SharedSchema` reference), so there is no scriptable authoring path as a workaround. This is why
§3's trap is currently unreachable: hand-editing the database is the only way to create a ref.
- The §6.1 counts are from the two **local docker** environments only. Production
- The §6.1 counts are from the two **local docker** environments only. DEV
(`wonder-app-vd03`) was not queried — that is an operator action, not one to take unasked. If
that box carries inbound methods with `$ref` definitions, §3 is live there and the §6.4
recommendation changes.