npm: publish 0.4.0 and expose ObjectRef in the type surface

npm/package.json carries its own version, independent of the workspace
Cargo.toml, so a release bump does not reach it. Bumped by hand to 0.4.0 —
worth wiring to the workspace version before the next release, since the
failure mode is silently republishing under the previous number.

types.d.ts gains ObjectRef and Finding.object, re-exported from both the node
and web entrypoints, so the published typings match what the WASM now returns:
a plan finding names its table, a token finding does not.

Author: dbopt

npm/node.d.ts

@@ -13,6 +13,7 @@ export type {
   Engine,
   Location,
   Finding,
+  ObjectRef,
   Recommendation,
   AnalysisReport,
   AnalyzeOptions,

npm/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dbopt-core",
-  "version": "0.3.9",
+  "version": "0.4.0",
   "description": "Find and fix slow SQL before it reaches production. A local-first database performance analyzer compiled from Rust to WebAssembly \u2014 runs in Node and the browser and sends nothing anywhere. SQL Server rules today; engine-agnostic by design.",
   "license": "Apache-2.0",
   "homepage": "https://dbopt.org",

npm/types.d.ts

@@ -25,6 +25,25 @@ export interface Location {
   col: number;
 }
 
+/**
+ * The database object a finding is about.
+ *
+ * Present only when the rule genuinely knows the object — a plan's `<Object>`
+ * or a DMV row. Absent for token rules, which match *text*: a rule that saw
+ * `SELECT *` has no table identity, and one is never inferred from the message.
+ *
+ * `row_count` / `reserved_kb` appear only when they were measured (from
+ * `sys.dm_db_partition_stats`). Absent means unknown — never read it as zero.
+ */
+export interface ObjectRef {
+  schema: string;
+  table: string;
+  /** Set when the finding is about one index rather than the whole table. */
+  index?: string;
+  row_count?: number;
+  reserved_kb?: number;
+}
+
 export interface Finding {
   /** Stable rule id, e.g. `"sarg.function_on_column"`. Safe to match on. */
   rule: string;
@@ -35,6 +54,8 @@ export interface Finding {
   location: Location | null;
   /** The concrete fix, usually copy-paste ready T-SQL. */
   recommendation: string | null;
+  /** The object this finding concerns, when the rule knows it. */
+  object?: ObjectRef;
 }
 
 export interface Recommendation {

npm/web.d.ts

@@ -11,6 +11,7 @@ export type {
   Engine,
   Location,
   Finding,
+  ObjectRef,
   Recommendation,
   AnalysisReport,
   AnalyzeOptions,