@viibestack/ui 0.6.2 → 0.6.3

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@viibestack/ui",
-  "version": "0.6.2",
-  "description": "Dependency-free React UI kit -- icons, core components (Button, Card, Input, Modal, etc.), a real per-app data client (listRows/upsertRow/deleteRow/reportError), and a real per-app end-user auth client (signUp/logIn/logOut/getCurrentUser) backed by ViibeStack's own platform-managed data store.",
+  "version": "0.6.3",
+  "description": "Dependency-free React UI kit -- icons, core components (Button, Card, Input, Modal, etc.), a real per-app data client (listRows/upsertRow/deleteRow/captureClientError), and a real per-app end-user auth client (signUp/logIn/logOut/getCurrentUser/reportError) backed by ViibeStack's own platform-managed data store.",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./src/index.ts",

package/src/data.ts

@@ -107,7 +107,18 @@ export async function deleteRow(table: string, id: string): Promise<void> {
   }
 }
 
-export async function reportError(message: string, stack?: string): Promise<void> {
+// Renamed from reportError in 0.6.3 -- it collided with auth.ts's own
+// reportError(message, details?, reporterEmail?) (the DOCUMENTED public
+// helper for integrationRequirements() item 3b, referenced by name in
+// mcp-agent.ts's generation prompt and ai-edit.ts's edit prompt). Both
+// symbols surviving index.ts's `export * from "./data"; export * from
+// "./auth";` produced a TypeScript "already exported a member" build
+// error for every consumer on 0.6.2 (see agent report a7b39641). This one
+// was never itself part of the documented public API -- item 3a's own
+// instructions always described a raw fetch to .../errors, not a
+// packages/ui helper call -- so renaming it doesn't break any documented
+// usage pattern.
+export async function captureClientError(message: string, stack?: string): Promise<void> {
   const appId = await resolveAppId();
   if (!appId) return;
   try {