max-agent-ui 0.0.21 → 0.0.23

package/README.md

@@ -66,28 +66,27 @@ projected into the chat header:
 </max-assistant>
 ```
 
-For authenticated host applications, provide shared configuration once. The
-current token and API version are sent as headers, while role, permissions,
-route, and timezone are sent as request context:
+For authenticated host applications, provide shared configuration once. The
+current token and API version are sent as the standard `x-auth-token` and
+`x-version` headers. Display identity is sent separately in the request body,
+and the agent retrieves current permissions directly from the calling product
+API:
 
 ```ts
 providers: [
   {
     provide: MAX_ASSISTANT_CONFIG,
-    useFactory: (session: SessionService, router: Router) => ({
+    useFactory: (session: SessionService) => ({
       app: 'cortex',
-      user: () => ({
-        token: session.authToken(),
+      user: () => ({
+        name: session.name(),
+        username: session.username(),
+        email: session.email(),
+        token: session.authToken(),
         version: session.apiVersion()
-      }),
-      context: () => ({
-        role: session.role(),
-        permissions: session.agentPermissions(),
-        route: router.url,
-        timezone: Intl.DateTimeFormat().resolvedOptions().timeZone
-      })
-    }),
-    deps: [SessionService, Router]
+      })
+    }),
+    deps: [SessionService]
   }
 ]
 ```
@@ -114,22 +113,22 @@ assistant.sendStructuredAction(
 The agent still validates the capability and permissions in Supabase, performs
 live preflight reads, and returns the normal Approve/Reject proposal.
 
-For another product, supply product-specific authentication headers through
-`requestHeaders`. Cortex's existing `user.token` and `user.version` shortcuts
-remain supported:
-
-```ts
-requestHeaders: () => ({
-  'x-nemesys-auth-token': session.nemesysToken()
-})
-```
+For Cortex and Nemesys, provide `user.token` and `user.version`; the library
+uses the same standard API headers for both products. Use `requestHeaders` only
+for additional custom headers:
+
+```ts
+requestHeaders: () => ({
+  'x-correlation-id': session.correlationId()
+})
+```
 
 Host apps should provide Angular `HttpClient` for real API calls and include their PrimeNG theme and PrimeIcons styles.
 
 For local integration, install the generated tarball and peer UI dependencies in the consuming app:
 
 ```bash
-npm install C:/Users/Dev100/Documents/Maxtime/Projects/maxtime-ui-library/dist/max-agent-ui/max-agent-ui-0.0.30.tgz primeng primeicons @angular/cdk
+npm install C:/Users/Dev100/Documents/Maxtime/Projects/maxtime-ui-library/dist/max-agent-ui/max-agent-ui-0.0.33.tgz primeng primeicons @angular/cdk
 ```
 
 ### Publishing the Library
@@ -146,7 +145,7 @@ Publish the generated tarball after logging in to npm:
 
 ```bash
 npm login
-npm publish max-agent-ui-0.0.30.tgz
+npm publish max-agent-ui-0.0.33.tgz
 ```
 
 ## Running unit tests