diff --git a/plugin-designs/cities-internet/connectivity-list.meta.json b/plugin-designs/cities-internet/connectivity-list.meta.json
new file mode 100644
index 000000000..404b780ed
--- /dev/null
+++ b/plugin-designs/cities-internet/connectivity-list.meta.json
@@ -0,0 +1,5 @@
+{
+  "stage": "experimental",
+  "label": "Cities with Internet — connectivity list",
+  "note": "The Studio and gallery read this label from here (internal/plugin-gallery/discover.mjs: `meta.label || profile`); with no meta file at all they fell back to the humanised profile id. The wording tracks the pane's own heading, t('connectivity.list.title') = \"Cities with Internet\", plus the view name — the same shape as the sibling connectivity-map.meta.json, so the three profiles read as one family in the picker. stage is declared EXPLICITLY rather than left to the default: the default is already experimental (internal/profile-meta.mjs), so this changes nothing today, but a meta that states its stage cannot be silently promoted if that default ever moves, and bundleStage() turns the whole bundle production as soon as ONE profile claims it."
+}
diff --git a/plugin-designs/cities-internet/data-tables.meta.json b/plugin-designs/cities-internet/data-tables.meta.json
new file mode 100644
index 000000000..3a55f9241
--- /dev/null
+++ b/plugin-designs/cities-internet/data-tables.meta.json
@@ -0,0 +1,5 @@
+{
+  "stage": "experimental",
+  "label": "Cities with Internet — data tables",
+  "note": "Label read by internal/plugin-gallery/discover.mjs (`meta.label || profile`); without a meta file this profile showed as the humanised id 'data tables'. The pane's own heading is t('connectivity.tables.title') = \"Cities Data\"; the label leads with the bundle's product name so the picker groups it with connectivity-map and connectivity-list rather than sorting it away under a different first word. stage declared explicitly for the reason given in connectivity-list.meta.json."
+}