docs: remove trailing whitespace in bootstrap analysis reports

Author: Sam-Bolling

docs/research/All_Bootstraps_Full_Scope_Gap_Analysis_2026-03-12.md

@@ -1,8 +1,8 @@
 # All Bootstraps Full-Scope Gap Analysis
 
-**Date:** 2026-03-12  
-**Author:** Codex (GPT-5)  
-**Status:** Full-scope semantics-first gap analysis  
+**Date:** 2026-03-12
+**Author:** Codex (GPT-5)
+**Status:** Full-scope semantics-first gap analysis
 **Scope:** current `OSHConnect-Python` public-data publisher fleet, legacy `csapi-explorer` bootstrap corpus, helper-layer and artifact-state analysis, and official-source review.
 
 ---
@@ -270,64 +270,64 @@ The right move for most of the legacy scenario corpus is not migration into the
 
 ### 8.1 Tier 1: universal high-priority gaps
 
-1. Restore TLS verification across active runtimes.  
+1. Restore TLS verification across active runtimes.
    Type: `runtime-follow-on`
 
-2. Codify the bootstrap families as first-class shared patterns.  
+2. Codify the bootstrap families as first-class shared patterns.
    Type: `bootstrap-only`
 
-3. Publish and enforce an artifact-state taxonomy for packs, total packs, historical source bases, and research notes.  
+3. Publish and enforce an artifact-state taxonomy for packs, total packs, historical source bases, and research notes.
    Type: `archive/clarify`
 
-4. Standardize provenance manifests and semantic-contract sidecars for every active publisher.  
+4. Standardize provenance manifests and semantic-contract sidecars for every active publisher.
    Type: `metadata-only`
 
-5. Add automated round-trip conformance probes for SensorML and result-schema retrieval.  
+5. Add automated round-trip conformance probes for SensorML and result-schema retrieval.
    Type: `runtime-follow-on`
 
-6. Close the ISS canonical-home gap.  
+6. Close the ISS canonical-home gap.
    Type: `migration`
 
 ### 8.2 Tier 2: publisher-family gaps
 
-1. Extract the station-per-system family builder.  
+1. Extract the station-per-system family builder.
    Type: `bootstrap-only`
 
-2. Define a canonical Pattern C feed-adapter contract.  
+2. Define a canonical Pattern C feed-adapter contract.
    Type: `metadata-only`
 
-3. Define a canonical Pattern A dependency contract for companion datastreams.  
+3. Define a canonical Pattern A dependency contract for companion datastreams.
    Type: `bootstrap-only`
 
-4. Separate scenario-only bootstraps from public-data publisher workflows.  
+4. Separate scenario-only bootstraps from public-data publisher workflows.
    Type: `archive/clarify`
 
 ### 8.3 Tier 3: per-bootstrap target-state work
 
-1. NWS and NDBC: integrate the mature parts of their enrichment work into a verified, canonical runtime-plus-bootstrap state.  
+1. NWS and NDBC: integrate the mature parts of their enrichment work into a verified, canonical runtime-plus-bootstrap state.
    Type: `runtime-follow-on`
 
-2. CO-OPS and Aviation WX: bring them to pack parity with the better-supported publishers.  
+2. CO-OPS and Aviation WX: bring them to pack parity with the better-supported publishers.
    Type: `metadata-only`
 
-3. OpenSky: keep the current model but harden runtime behavior and quality semantics.  
+3. OpenSky: keep the current model but harden runtime behavior and quality semantics.
    Type: `runtime-follow-on`
 
-4. USGS water: reconcile the missing total-pack directory and elevate the statistic-specific semantic contract into a canonical package.  
+4. USGS water: reconcile the missing total-pack directory and elevate the statistic-specific semantic contract into a canonical package.
    Type: `total-pack`
 
-5. USGS NIMS and USGS EQ: extend the already-strong packages into clearer next-stage runtime and semantic guidance.  
+5. USGS NIMS and USGS EQ: extend the already-strong packages into clearer next-stage runtime and semantic guidance.
    Type: `runtime-follow-on`
 
 ### 8.4 Tier 4: legacy migration or archival cleanup
 
-1. Migrate legacy ISS bootstrap into the current publisher repo.  
+1. Migrate legacy ISS bootstrap into the current publisher repo.
    Type: `migration`
 
-2. Archive or clearly label UAS, localizer, v2.5, v3.1, v4, and phase2 as scenario-specific or historical.  
+2. Archive or clearly label UAS, localizer, v2.5, v3.1, v4, and phase2 as scenario-specific or historical.
    Type: `archive/clarify`
 
-3. Preserve reusable ideas from the legacy scenario family without preserving insecure transport and credential patterns.  
+3. Preserve reusable ideas from the legacy scenario family without preserving insecure transport and credential patterns.
    Type: `archive/clarify`
 
 ---

docs/research/All_Bootstraps_Full_Scope_Gap_Analysis_Appendix_A_Inventory_and_Rubric_2026-03-12.md

@@ -2,7 +2,7 @@
 
 ## Appendix A. Inventory and Rubric
 
-**Date:** 2026-03-12  
+**Date:** 2026-03-12
 **Scope:** current `OSHConnect-Python` bootstrap fleet, legacy `csapi-explorer` bootstrap corpus, and the adjacent artifacts required to judge bootstrap completeness and semantic maturity.
 
 ---

docs/research/All_Bootstraps_Full_Scope_Gap_Analysis_Appendix_B_Current_Fleet_Dossiers_2026-03-12.md

@@ -2,15 +2,15 @@
 
 ## Appendix B. Current Fleet Dossiers
 
-**Date:** 2026-03-12  
+**Date:** 2026-03-12
 **Scope:** current `OSHConnect-Python` public-data fleet, including the current ISS runtime slot as a missing-bootstrap case.
 
 ---
 
 ## B.1 NWS
 
-**Primary path:** `publishers/nws/bootstrap_nws.py`  
-**Pattern family:** Station-per-system  
+**Primary path:** `publishers/nws/bootstrap_nws.py`
+**Pattern family:** Station-per-system
 **Current topology summary:** one procedure, ten station systems, one weather datastream per station, and a root/group/station deployment tree driven by `publishers/nws/stations.json`.
 
 **Current strengths**
@@ -75,8 +75,8 @@ NWS should become the canonical station-family reference once its mature pack co
 
 ## B.2 NDBC
 
-**Primary path:** `publishers/ndbc/bootstrap_ndbc.py`  
-**Pattern family:** Station-per-system with imagery companion datastream support  
+**Primary path:** `publishers/ndbc/bootstrap_ndbc.py`
+**Pattern family:** Station-per-system with imagery companion datastream support
 **Current topology summary:** one core buoy-observation procedure, one optional BuoyCAM procedure, five buoy systems, one buoy datastream per buoy, optional imagery datastreams, and a root/group/buoy deployment tree driven by `publishers/ndbc/stations.json`.
 
 **Current strengths**
@@ -141,8 +141,8 @@ NDBC should become the canonical "multi-stream station publisher" reference once
 
 ## B.3 CO-OPS
 
-**Primary path:** `publishers/coops/bootstrap_coops.py`  
-**Pattern family:** Station-per-system  
+**Primary path:** `publishers/coops/bootstrap_coops.py`
+**Pattern family:** Station-per-system
 **Current topology summary:** one water-level procedure, five station systems, one coastal-observation datastream per station, and a root/group/station deployment tree driven by `publishers/coops/stations.json`.
 
 **Current strengths**
@@ -207,8 +207,8 @@ CO-OPS should evolve into a stronger coastal-observation reference with clearer
 
 ## B.4 Aviation WX
 
-**Primary path:** `publishers/aviation_wx/bootstrap_aviation_wx.py`  
-**Pattern family:** Station-per-system  
+**Primary path:** `publishers/aviation_wx/bootstrap_aviation_wx.py`
+**Pattern family:** Station-per-system
 **Current topology summary:** one METAR decoding procedure, five airport systems, one METAR datastream per airport, and a root/group/station deployment tree driven by `publishers/aviation_wx/stations.json`.
 
 **Current strengths**
@@ -273,8 +273,8 @@ Aviation WX should be brought up to the metadata-pack baseline so it is no longe
 
 ## B.5 OpenSky
 
-**Primary path:** `publishers/opensky/bootstrap_opensky.py`  
-**Pattern family:** Pattern C feed adapter  
+**Primary path:** `publishers/opensky/bootstrap_opensky.py`
+**Pattern family:** Pattern C feed adapter
 **Current topology summary:** one ADS-B decoding procedure, one feed-adapter system, one state-vector datastream, and a small root/feed deployment tree driven by `publishers/opensky/config.json`.
 
 **Current strengths**
@@ -339,8 +339,8 @@ OpenSky should serve as the canonical Pattern C reference once runtime hardening
 
 ## B.6 ISS Current Slot
 
-**Primary path:** `publishers/iss/`  
-**Pattern family:** Intended Pattern C / dual-product publisher, but currently a missing canonical bootstrap  
+**Primary path:** `publishers/iss/`
+**Pattern family:** Intended Pattern C / dual-product publisher, but currently a missing canonical bootstrap
 **Current topology summary:** `publishers/iss/iss_publisher.py` and `publishers/iss/Dockerfile` exist, but there is no current bootstrap file and the fleet README still points to `python -m publishers.iss.bootstrap_iss`.
 
 **Current strengths**
@@ -405,8 +405,8 @@ ISS should exist as a first-class current bootstrap in `publishers/iss/`, preser
 
 ## B.7 USGS Water
 
-**Primary path:** `publishers/usgs_water/bootstrap_usgs_water.py`  
-**Pattern family:** Station-per-system with paired parameter streams  
+**Primary path:** `publishers/usgs_water/bootstrap_usgs_water.py`
+**Pattern family:** Station-per-system with paired parameter streams
 **Current topology summary:** one water-observation procedure, eight station systems, two datastreams per station (`usgsDischarge` and `usgsGageHeight`), and a root/group/station deployment tree driven by a comparatively rich `publishers/usgs_water/stations.json`.
 
 **Current strengths**
@@ -471,8 +471,8 @@ USGS water should become the strongest station-family public-data reference afte
 
 ## B.8 USGS NIMS
 
-**Primary path:** `publishers/usgs_nims/bootstrap_usgs_nims.py`  
-**Pattern family:** Pattern A companion datastream  
+**Primary path:** `publishers/usgs_nims/bootstrap_usgs_nims.py`
+**Pattern family:** Pattern A companion datastream
 **Current topology summary:** one imagery procedure, no new systems, one imagery datastream attached to each existing USGS water station system selected in `publishers/usgs_nims/cameras.json`, and a NIMS-specific root/group/station deployment tree.
 
 **Current strengths**
@@ -537,8 +537,8 @@ USGS NIMS should remain the reference Pattern A implementation, with the next st
 
 ## B.9 USGS Earthquake
 
-**Primary path:** `publishers/usgs_eq/bootstrap_usgs_eq.py`  
-**Pattern family:** Pattern C feed adapter  
+**Primary path:** `publishers/usgs_eq/bootstrap_usgs_eq.py`
+**Pattern family:** Pattern C feed adapter
 **Current topology summary:** one feed-normalizer procedure, one feed system, one earthquake-event datastream, and a root/feed deployment tree driven by `publishers/usgs_eq/config.json`.
 
 **Current strengths**

docs/research/All_Bootstraps_Full_Scope_Gap_Analysis_Appendix_C_Legacy_Fleet_Dossiers_2026-03-12.md

@@ -2,14 +2,14 @@
 
 ## Appendix C. Legacy Fleet Dossiers
 
-**Date:** 2026-03-12  
+**Date:** 2026-03-12
 **Scope:** legacy bootstraps in `csapi-explorer/scripts` that still matter architecturally, historically, or as migration references.
 
 ---
 
 ## C.1 `bootstrap_iss.py`
 
-**Path:** `scripts/bootstrap_iss.py`  
+**Path:** `scripts/bootstrap_iss.py`
 **Current role classification:** Active precedent and migration candidate
 
 **What still matters architecturally**
@@ -52,7 +52,7 @@ Migrate this script into `publishers/iss/bootstrap_iss.py`, preserve its dual-pr
 
 ## C.2 `bootstrap_uas.py`
 
-**Path:** `scripts/bootstrap_uas.py`  
+**Path:** `scripts/bootstrap_uas.py`
 **Current role classification:** Historical artifact with reusable enrichment ideas
 
 **What still matters architecturally**
@@ -95,7 +95,7 @@ Archive it as a scenario-specific enrichment reference and extract only the reus
 
 ## C.3 `bootstrap_localizer.py`
 
-**Path:** `scripts/bootstrap_localizer.py`  
+**Path:** `scripts/bootstrap_localizer.py`
 **Current role classification:** Scenario-only bootstrap
 
 **What still matters architecturally**
@@ -138,7 +138,7 @@ Keep it only as a scenario-only reference for small focused bootstraps and do no
 
 ## C.4 `bootstrap_v25.py`
 
-**Path:** `scripts/bootstrap_v25.py`  
+**Path:** `scripts/bootstrap_v25.py`
 **Current role classification:** Historical migration bridge
 
 **What still matters architecturally**
@@ -181,7 +181,7 @@ Retain it only as a historical migration bridge and mine it for reusable import
 
 ## C.5 `bootstrap_v3.1.py`
 
-**Path:** `scripts/bootstrap_v3.1.py`  
+**Path:** `scripts/bootstrap_v3.1.py`
 **Current role classification:** Historical artifact
 
 **What still matters architecturally**
@@ -224,7 +224,7 @@ Archive it as a historical scenario-hierarchy milestone and do not treat it as a
 
 ## C.6 `bootstrap_v4.py`
 
-**Path:** `scripts/bootstrap_v4.py`  
+**Path:** `scripts/bootstrap_v4.py`
 **Current role classification:** Scenario-only authoritative bootstrap
 
 **What still matters architecturally**

docs/research/All_Bootstraps_Full_Scope_Gap_Analysis_Appendix_D_Source_Corpus_and_Roadmap_2026-03-12.md

@@ -2,7 +2,7 @@
 
 ## Appendix D. Source Corpus and Roadmap
 
-**Date:** 2026-03-12  
+**Date:** 2026-03-12
 **Method note:** external claims in the master report and dossiers are grounded in primary or official sources only. Repo-local artifacts were treated as the source of truth for current implementation state; official public documentation was treated as the source of truth for upstream semantics and service behavior.
 
 ---