npm - @agent-native/core - Versions diffs - 0.137.0 → 0.137.2 - Mend

@agent-native/core 0.137.0 → 0.137.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (47) hide show

package/dist/collab/struct-routes.d.ts CHANGED Viewed

@@ -13,8 +13,8 @@
  * Body: { json: any, fieldName?: string, type?: "map"|"array", requestSource?: string }
  */
 export declare const postCollabJson: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    error: string;
     ok?: undefined;
+    error: string;
 } | {
     error?: undefined;
     ok: boolean;

package/dist/deploy/build.js CHANGED Viewed

@@ -1449,7 +1449,8 @@ export function generateCloudflarePagesStaticShellFromManifest(manifest, basePat
     const encodedInitialState = rootRoute.hasLoader
         ? DEFAULT_ROOT_LOADER_REACT_ROUTER_TURBO_STREAM
         : EMPTY_REACT_ROUTER_TURBO_STREAM;
-    return `<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"/><link rel="manifest" href="/manifest.json"/><link rel="icon" type="image/svg+xml" href="/favicon.svg"/>${modulePreloads}${stylesheets}</head><body><div style="display:flex;flex-direction:column;align-items:center;justify-content:center;gap:16px;height:100vh;width:100%"><svg role="status" aria-label="Loading" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" style="animation:an-spin 1s linear infinite;opacity:0.7"><path d="M21 12a9 9 0 1 1-6.219-8.56"></path></svg><p class="an-stall-hint">Still loading. If this does not finish, reload the page — the browser console may show what failed.</p><style>@keyframes an-spin { to { transform: rotate(360deg) } } @keyframes an-stall-in { to { opacity: 0.6 } } .an-stall-hint { opacity: 0; margin: 0; max-width: 32rem; padding: 0 1.5rem; text-align: center; font-size: 0.875rem; line-height: 1.5; font-family: ui-sans-serif, system-ui, sans-serif; animation: an-stall-in 0.4s ease-out 10s forwards } @media (prefers-reduced-motion: reduce) { .an-stall-hint { animation-duration: 0s } } @media (prefers-color-scheme: dark) { html { background: #09090b; color: #fafafa } }</style></div><script>window.__reactRouterContext = ${JSON.stringify(context)};window.__reactRouterContext.stream = new ReadableStream({start(controller){window.__reactRouterContext.streamController = controller;}}).pipeThrough(new TextEncoderStream());</script><script type="module" async="">${routeModuleScript}</script><!--$--><script>window.__reactRouterContext.streamController.enqueue(${JSON.stringify(encodedInitialState)});</script><!--$--><script>window.__reactRouterContext.streamController.close();</script><!--/$--><!--/$--></body></html>`;
+    // guard:allow-raw-color - static shell loads before app theme tokens exist
+    return `<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"/><link rel="manifest" href="/manifest.json"/><link rel="icon" type="image/svg+xml" href="/favicon.svg"/>${modulePreloads}${stylesheets}</head><body><div style="display:flex;align-items:center;justify-content:center;height:100vh;width:100%"><svg role="status" aria-label="Loading" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" style="animation:an-spin 1s linear infinite;opacity:0.7"><path d="M21 12a9 9 0 1 1-6.219-8.56"></path></svg><style>@keyframes an-spin { to { transform: rotate(360deg) } } @media (prefers-color-scheme: dark) { html { background: #09090b; color: #fafafa } }</style></div><script>window.__reactRouterContext = ${JSON.stringify(context)};window.__reactRouterContext.stream = new ReadableStream({start(controller){window.__reactRouterContext.streamController = controller;}}).pipeThrough(new TextEncoderStream());</script><script type="module" async="">${routeModuleScript}</script><!--$--><script>window.__reactRouterContext.streamController.enqueue(${JSON.stringify(encodedInitialState)});</script><!--$--><script>window.__reactRouterContext.streamController.close();</script><!--/$--><!--/$--></body></html>`;
 }
 function writeCloudflarePagesStaticShell({ serverDir, distDir, tmpDir, }) {
     const serverEntry = path.join(serverDir, "index.js");

package/dist/notifications/routes.d.ts CHANGED Viewed

@@ -13,13 +13,13 @@
 export declare function createNotificationsHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<"" | import("./types.js").Notification[] | {
     count: number;
     updated?: undefined;
-    ok?: undefined;
     error?: undefined;
+    ok?: undefined;
 } | {
     count?: undefined;
     updated: number;
-    ok?: undefined;
     error?: undefined;
+    ok?: undefined;
 } | {
     count?: undefined;
     updated?: undefined;

package/dist/progress/routes.d.ts CHANGED Viewed

@@ -15,7 +15,7 @@ export declare function createProgressHandler(): import("h3").EventHandlerWithFe
     error: string;
     ok?: undefined;
 } | {
-    ok: boolean;
     error?: undefined;
+    ok: boolean;
 }>>;
 //# sourceMappingURL=routes.d.ts.map

package/dist/server/realtime-token.d.ts CHANGED Viewed

@@ -26,9 +26,9 @@ export declare function createRealtimeTokenHandler(): import("h3").EventHandlerW
     expiresAt?: undefined;
     ttlSeconds?: undefined;
 } | {
+    error?: undefined;
     token: string;
     expiresAt: string;
     ttlSeconds: number;
-    error?: undefined;
 }>>;
 //# sourceMappingURL=realtime-token.d.ts.map

package/dist/templates/workspace-core/.agents/skills/address-feedback/SKILL.md CHANGED Viewed

@@ -1,9 +1,9 @@
 ---
 name: address-feedback
 description: >-
-  Triage feedback docs or pasted feedback into bugs to fix, UX suggestions to
-  propose, unclear questions, and skipped noise; verify bugs, check Sentry when
-  relevant, and keep UI changes minimal.
+  Triage feedback from docs, issues, Slack threads, or pasted notes into
+  verified bugs, UX proposals, unclear questions, and skipped noise. Use when a
+  user asks you to address product feedback or investigate a reported workflow.
 scope: dev
 metadata:
   internal: true
@@ -20,6 +20,7 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
 - If no link or feedback text is provided, ask for it.
 - Read the repo `AGENTS.md` before touching code.
 - Use the relevant connector/plugin/skill for the source when available, instead of scraping authenticated pages.
+- Before starting work, search available task history and local Git/PR metadata for the exact feedback link or issue identifiers. Reuse existing work instead of creating a duplicate fix.
 ## Steps
@@ -35,16 +36,28 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    | Public URL | Web browsing |
    | Pasted text | Read directly |
-   Use web browsing only for public URLs. Auth-gated docs usually need their matching connector.
+   Use web browsing only for public URLs. Auth-gated docs usually need their matching connector. For threads, read the parent and all replies; note when there are no replies, and inspect linked files or newer follow-ups when the source refers to them.
-2. Categorize every actionable item.
+2. Decompose and categorize every actionable item.
+   Build a compact checklist before changing code. For each item, record the
+   symptom, expected behavior, evidence, and owning surface: UI, action/tool,
+   data model, provider/runtime, or product policy.
    - **Bug**: Broken behavior, crash, wrong data, dead link, package/API mismatch, or captured exception. Verify and fix when you agree.
    - **UX suggestion**: Design, discoverability, workflow, or feature feedback. Propose the cleanest version first unless the user explicitly asked you to implement UX changes.
    - **Question or unclear**: Missing detail, contradictory feedback, or behavior you cannot inspect. Ask or flag it.
    - **Out of scope**: Outside this repo, already shipped, intentionally unsupported, or too low-signal. Note briefly and skip.
-3. Check Sentry when the feedback smells like an error.
+3. For data, permissions, or resource-lifecycle feedback, verify the whole capability boundary before calling it UX.
+   - Check the supported create/read/update/delete lifecycle, including whether the backend/action exists when a UI control is missing.
+   - Inspect both the UI and the shared action/tool surface so agent and UI behavior stay in parity.
+   - Verify scope semantics such as owner/private, organization, shared, and public access. Test owner and non-owner paths with safe fixtures or read-only checks; never use another user's production data to test access.
+   - Treat possible cross-user or cross-organization exposure as a security/correctness bug and verify it before proposing polish.
+   - Keep undefined product policy separate from implementation bugs. If supported source types or scope semantics are not defined, flag the contract question instead of inventing behavior.
+4. Check Sentry when the feedback smells like an error.
    - Use the Sentry skill/plugin if available, or the repo's Sentry scripts if documented.
    - Search by route, stack symbol, error text, and symptom keywords.
@@ -52,7 +65,7 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    - Cite issue IDs or links when you find a match.
    - If nothing matches, say that plainly.
-4. Fix only the clear bugs you agree with.
+5. Fix only the clear bugs you agree with.
    - Verify before fixing: reproduce locally, read the relevant code, inspect logs, or confirm with a stack trace.
    - Keep each fix narrow and mapped to a feedback item.
@@ -60,7 +73,7 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    - Do not switch branches, stash, reset, force-push, or open a PR unless the user asks.
    - Add or update focused tests when the bug risk warrants it.
-5. Treat UX feedback with restraint.
+6. Treat UX feedback with restraint.
    Do not solve UX problems by adding more visible controls, helper text, banners, top-level nav, or always-open panels by default. Prefer cleaner interaction models:
@@ -72,11 +85,14 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    When proposing a UX change, write it as: what to change, why it helps, and the tradeoff. Keep each proposal short.
-6. Verify changed behavior.
+7. Verify changed behavior.
    - Run the smallest relevant test or typecheck command.
    - For UI fixes, inspect the actual screen with a browser tool you already
      have. Do not write a browser-automation script to check a small fix.
+   - For resource visibility or lifecycle changes, verify both the screen and
+     shared action/tool behavior, including owner versus non-owner access when
+     relevant.
    - If you cannot run a useful verification, say why.
 ## Report Format

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.137.0",
+  "version": "0.137.2",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -401,7 +401,7 @@
     "yjs": "^13.6.31",
     "zod": "^4.3.6",
     "@agent-native/recap-cli": "0.5.3",
-    "@agent-native/toolkit": "^0.12.2"
+    "@agent-native/toolkit": "^0.13.0"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",

package/src/templates/workspace-core/.agents/skills/address-feedback/SKILL.md CHANGED Viewed

@@ -1,9 +1,9 @@
 ---
 name: address-feedback
 description: >-
-  Triage feedback docs or pasted feedback into bugs to fix, UX suggestions to
-  propose, unclear questions, and skipped noise; verify bugs, check Sentry when
-  relevant, and keep UI changes minimal.
+  Triage feedback from docs, issues, Slack threads, or pasted notes into
+  verified bugs, UX proposals, unclear questions, and skipped noise. Use when a
+  user asks you to address product feedback or investigate a reported workflow.
 scope: dev
 metadata:
   internal: true
@@ -20,6 +20,7 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
 - If no link or feedback text is provided, ask for it.
 - Read the repo `AGENTS.md` before touching code.
 - Use the relevant connector/plugin/skill for the source when available, instead of scraping authenticated pages.
+- Before starting work, search available task history and local Git/PR metadata for the exact feedback link or issue identifiers. Reuse existing work instead of creating a duplicate fix.
 ## Steps
@@ -35,16 +36,28 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    | Public URL | Web browsing |
    | Pasted text | Read directly |
-   Use web browsing only for public URLs. Auth-gated docs usually need their matching connector.
+   Use web browsing only for public URLs. Auth-gated docs usually need their matching connector. For threads, read the parent and all replies; note when there are no replies, and inspect linked files or newer follow-ups when the source refers to them.
-2. Categorize every actionable item.
+2. Decompose and categorize every actionable item.
+   Build a compact checklist before changing code. For each item, record the
+   symptom, expected behavior, evidence, and owning surface: UI, action/tool,
+   data model, provider/runtime, or product policy.
    - **Bug**: Broken behavior, crash, wrong data, dead link, package/API mismatch, or captured exception. Verify and fix when you agree.
    - **UX suggestion**: Design, discoverability, workflow, or feature feedback. Propose the cleanest version first unless the user explicitly asked you to implement UX changes.
    - **Question or unclear**: Missing detail, contradictory feedback, or behavior you cannot inspect. Ask or flag it.
    - **Out of scope**: Outside this repo, already shipped, intentionally unsupported, or too low-signal. Note briefly and skip.
-3. Check Sentry when the feedback smells like an error.
+3. For data, permissions, or resource-lifecycle feedback, verify the whole capability boundary before calling it UX.
+   - Check the supported create/read/update/delete lifecycle, including whether the backend/action exists when a UI control is missing.
+   - Inspect both the UI and the shared action/tool surface so agent and UI behavior stay in parity.
+   - Verify scope semantics such as owner/private, organization, shared, and public access. Test owner and non-owner paths with safe fixtures or read-only checks; never use another user's production data to test access.
+   - Treat possible cross-user or cross-organization exposure as a security/correctness bug and verify it before proposing polish.
+   - Keep undefined product policy separate from implementation bugs. If supported source types or scope semantics are not defined, flag the contract question instead of inventing behavior.
+4. Check Sentry when the feedback smells like an error.
    - Use the Sentry skill/plugin if available, or the repo's Sentry scripts if documented.
    - Search by route, stack symbol, error text, and symptom keywords.
@@ -52,7 +65,7 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    - Cite issue IDs or links when you find a match.
    - If nothing matches, say that plainly.
-4. Fix only the clear bugs you agree with.
+5. Fix only the clear bugs you agree with.
    - Verify before fixing: reproduce locally, read the relevant code, inspect logs, or confirm with a stack trace.
    - Keep each fix narrow and mapped to a feedback item.
@@ -60,7 +73,7 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    - Do not switch branches, stash, reset, force-push, or open a PR unless the user asks.
    - Add or update focused tests when the bug risk warrants it.
-5. Treat UX feedback with restraint.
+6. Treat UX feedback with restraint.
    Do not solve UX problems by adding more visible controls, helper text, banners, top-level nav, or always-open panels by default. Prefer cleaner interaction models:
@@ -72,11 +85,14 @@ The default posture is judgment plus action: fix clear, verified bugs you agree
    When proposing a UX change, write it as: what to change, why it helps, and the tradeoff. Keep each proposal short.
-6. Verify changed behavior.
+7. Verify changed behavior.
    - Run the smallest relevant test or typecheck command.
    - For UI fixes, inspect the actual screen with a browser tool you already
      have. Do not write a browser-automation script to check a small fix.
+   - For resource visibility or lifecycle changes, verify both the screen and
+     shared action/tool behavior, including owner versus non-owner access when
+     relevant.
    - If you cannot run a useful verification, say why.
 ## Report Format