@overscore/cli 0.13.10 → 0.13.11

package/dist/index.js

@@ -572,10 +572,32 @@ async function deploy() {
     // Pull latest platform rules so the local project stays up to date
     await syncPlatformRules(process.cwd(), baseUrl, apiKey);
 }
+/**
+ * Print the project's warehouse-connection status. A live connection (e.g.
+ * BigQuery) can exist with ZERO registered queries — so this is surfaced
+ * independently of the query list. Without it, an empty query list reads as
+ * "no warehouse here" even when one is wired and queryable via `query run`.
+ */
+function printConnection(connection) {
+    if (!connection)
+        return;
+    if (connection.connected) {
+        const label = connection.type === "bigquery" ? "BigQuery" : connection.type ?? "warehouse";
+        const where = connection.gcp_project_id ? ` — GCP project: ${connection.gcp_project_id}` : "";
+        console.log(`  Data connection: ${label} connected${where}`);
+        console.log(`    A live warehouse is wired up. Explore it with: npx @overscore/cli query run "<sql>"`);
+        console.log(`    Then register the metrics you want: npx @overscore/cli query add <name> "<sql>"\n`);
+    }
+    else {
+        console.log(`  Data connection: none (uploaded datasets only — no warehouse connected)\n`);
+    }
+}
 async function queryList() {
     const { dashboardSlug } = await loadEnv();
     const data = (await apiRequest("GET", `/api/dashboards/${dashboardSlug}/queries`, undefined, "query-list"));
     console.log(`\n  Dashboard: ${data.dashboard}\n`);
+    // Warehouse connection status (independent of registered queries)
+    printConnection(data.connection);
     // Registered queries
     if (data.queries.length === 0) {
         console.log("  No queries registered yet.\n");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@overscore/cli",
-  "version": "0.13.10",
+  "version": "0.13.11",
   "description": "CLI for deploying Overscore dashboards and publishing analyses",
   "bin": {
     "overscore": "dist/index.js"

package/templates/analysis/.claude/CLAUDE.md

@@ -24,6 +24,13 @@ Every meaningful exploration step in the log is a new entry: the question being
 
 ## How to run BigQuery queries
 
+This project has a **live BigQuery connection** — the credentials live in the Hub and `query run` executes against your real warehouse. You don't need to "find" or "set up" a connection: if `query run` returns rows, the warehouse is wired and working. If you're unsure what's in it, discover the schema directly rather than assuming there's no data:
+
+```bash
+# list datasets/tables you can reach
+npx @overscore/cli query run "SELECT table_schema, table_name FROM \`<gcp_project>\`.region-us.INFORMATION_SCHEMA.TABLES LIMIT 200"
+```
+
 Use the Overscore CLI to run SQL against the project's BigQuery connection:
 
 ```bash

package/templates/analysis/.claude/skills/start-analysis/SKILL.md

@@ -33,7 +33,7 @@ Ask these one or two at a time conversationally — don't dump all 7 at once lik
 
 ## After the interview
 
-1. **Read `.claude/knowledge/INDEX.md`** and any relevant knowledge files to understand what previous sessions have already documented about this project's data. Cross-reference what the user said against what's already known.
+1. **Read `.claude/knowledge/INDEX.md`** and any relevant knowledge files to understand what previous sessions have already documented about this project's data. Cross-reference what the user said against what's already known. An empty knowledge base does NOT mean there's no data — this project has a **live BigQuery connection**. If neither the user nor the knowledge base names the tables, your first approved query can be an `INFORMATION_SCHEMA.TABLES` discovery pass (see CLAUDE.md); never conclude "there's no warehouse/no data" without actually querying it.
 
 2. **Write `this-analysis.md` immediately** — before proposing a query plan. Fill in every section:
    - **Question** — the clarified question, not the original title