Document Global Spot Oracle probe

Author: Sam-Bolling

docs/research/new-publisher-source-planning/Met_Office_Global_Spot_Forecast_Publisher_Status_2026-05-26.md

@@ -77,13 +77,23 @@ With five locations at one request per location per hour, the default operationa
 Local validation completed without printing or changing credentials:
 
 - Python compile passed for the new bootstrap, publisher, and parser test files.
-- Bootstrap dry run successfully constructed the procedure, 3 virtual systems, 18 datastreams, and deployment hierarchy.
+- Bootstrap dry run successfully constructed the procedure, 5 virtual systems, 30 datastreams, and deployment hierarchy.
 - Focused parser tests passed: `2 passed`.
 - Repository was pushed cleanly to `origin/main` at `3aaa637`.
 
+Oracle validation completed without printing or changing credentials:
+
+- Production Explorer loaded 846 features after the Exeter and Portsmouth Land Observations deployment, up from the earlier 810-feature view.
+- The Portsmouth / Thorney Island Met Office label rendered on the production map.
+- A sanitized Global Spot probe using the currently installed Land Observations key reached `/sitespecific/v0/point/hourly`, but Met Office returned HTTP 403 `Resource forbidden` for that forecast resource.
+- The fallback path `/sitespecific/v0/global/hourly` returned HTTP 404, which supports keeping `/point/hourly` as the current default while treating forecast-product subscription access as the blocker.
+- Oracle bootstrap dry run for Global Spot succeeded with 5 virtual forecast systems, 30 forecast datastreams, and 7 deployment resources; no forecast resources were written because live forecast API access is not yet available.
+
 ## Live Validation Boundary
 
-The local `publishers/.env` in this workspace has OSH credentials but does not currently include a Global Spot / Site-Specific Forecast key. The publisher therefore has not yet been live-probed against `/sitespecific/v0` from this machine.
+The local `publishers/.env` in this workspace has OSH credentials but does not currently include a Global Spot / Site-Specific Forecast key. The Oracle host also currently has only the Met Office Land Observations key installed. A sanitized Oracle probe confirmed that key is not authorized for the Site-Specific Forecast resource: `/sitespecific/v0/point/hourly` returns HTTP 403 `Resource forbidden`.
+
+Do not install a persistent Global Spot service or publish forecast observations until a Site-Specific Forecast / Global Spot key is installed host-locally.
 
 The runtime is deliberately configurable for the final subscribed endpoint check:
 
@@ -101,8 +111,8 @@ MET_OFFICE_DATAHUB_API_KEY_HEADER=apikey
 ## Next Steps
 
 1. Place the existing Site-Specific Forecast / Global Spot key in a host-local secret file or environment variable without rotating or printing it.
-2. Run `python -m publishers.met_office_global_spot.met_office_global_spot_publisher --probe --locations london-heathrow-area` to confirm the exact endpoint path and response shape.
-3. If the endpoint path differs from the conservative `/point/hourly` default, set `MET_OFFICE_GLOBAL_SPOT_HOURLY_PATH` rather than changing credentials.
+2. Run `python -m publishers.met_office_global_spot.met_office_global_spot_publisher --probe --locations london-heathrow-area` to confirm the response shape now that `/point/hourly` is the likely endpoint path.
+3. If the endpoint path differs from `/point/hourly`, set `MET_OFFICE_GLOBAL_SPOT_HOURLY_PATH` rather than changing credentials.
 4. Run `python -m publishers.met_office_global_spot.bootstrap_met_office_global_spot --force-sml` on the target OSH server.
 5. Run `python -m publishers.met_office_global_spot.met_office_global_spot_publisher --dry-run --once` and then one live `--once` cycle.
 6. Verify Explorer behavior: forecast points must be labeled as forecast, and existing rich source cards such as BuoyCAM and water monitoring media must remain unchanged.