test: add ops hub bootstrap smoke script

docs/new-hub-quickstart.md

@@ -167,6 +167,13 @@ The event should appear with the submitted `metadata`. If the API returns
 `event_type_not_in_manifest`, check that the API consumer is bound to the
 active ops-hub manifest and that the event type was declared before activation.
 
+The same path is available as a smoke script:
+
+```bash
+IHUB_BASE="$IHUB_BASE" IHUB_OPERATOR_KEY="$IHUB_OPERATOR_KEY" \
+  scripts/ops-hub-bootstrap-smoke.py
+```
+
 ### 8. What you get for free
 
 Once events are flowing, the inter-hub framework automatically provides:
@@ -325,6 +332,8 @@ registration pattern into your new hub. It is ~50 lines of boilerplate.
 - [ ] Create at least one Widget per meaningful UI surface
 - [ ] Instrument interactions with POST to `/api/v2/interaction-events`
 - [ ] Verify events appear in inter-hub at `/InteractionEvents`
+- [ ] Run `scripts/ops-hub-bootstrap-smoke.py` against a disposable or staging
+      environment before adapting the recipe for another VSM hub
 - [ ] (Optional) Configure AgentRegistration and ModelRoutingPolicy for
       AI-assisted requirement drafting
 - [ ] (Optional) Set up HubRoutingRules to route annotations to your hub's