@newheap/platform-ai-chat 0.13.0 → 0.15.0

package/README.md

@@ -125,6 +125,11 @@ conversation opens, and live only in this tab's memory. They clear on account ch
 loss of access, deletion or leaving a conversation. Standalone composers preserve their
 default behavior; opt into the extra send button with `[queueWhileBusy]="true"` and
 connect it to `NhAssistantStore.submit` using `canSubmit`.
+A failed turn leaves the conversation open, as on the server: the error bar keeps the
+translated failure and the next message starts a new turn in the same conversation or agent
+thread. While nothing is queued, that message is sent directly even with the error bar shown.
+A reopened conversation whose last turn failed says that the last answer could not be
+completed. Only an archived conversation is closed for new messages.
 Explicit send returns focus to the
 editor. Automatic focus restoration happens only when a disappearing composer control
 owned focus, never after the user chose another control, and is skipped for coarse
@@ -283,6 +288,33 @@ custom layouts. Opened in the panel, the thread offers its proposals to the same
 **Decided by** shows the name from the subject's member snapshot (`decidedByDisplayName`)
 and falls back to the actor id.
 
+Subjects show the name of their type (`subjectTypeName`, such as "Project") and link to where
+the application shows them (`subjectLink`, from the server's `AddSubjectType(...).OpenAt(...)`).
+A link within the application navigates through the router; an `https` link leaves it. Replace
+the server's link per subject type when the host's routes differ:
+
+```ts
+provideNhAssistant({
+  apiBaseUrl: environment.api.baseUrl + '/assistant',
+  getAccessToken: () => inject(AuthService).token(),
+  // Router commands or a URL; null shows no link, undefined keeps the server's link.
+  subjectLinks: { project: subject => ['/projects', subject.id] }
+});
+```
+
+`NhAssistantAgentRunApiService.searchSubjects(type, query, limit?)` finds the subjects of a type
+that the caller may read by name; the run catalog's `subjectTypes` say which types can be searched.
+
+The administration's agent editor asks what an agent created there works on: all objects or chosen
+kinds of objects by name, the whole application, per division when the run catalog reports
+`divisions`, and the run and view policy from the catalog's `agentPolicies`. Agent cards show what
+every agent works on; an agent in code shows its code setting.
+
+The trigger form and the guided setup let a schedule of an agent that works on the whole application
+run for the whole application instead of a set of objects (sent as `subjectSet: null`; once per
+division for an agent that works per division); the trigger list names it, and subject links name the
+whole application (`nh-system`, `isSystem` in the run catalog) once.
+
 With live updates the inbox, the thread view and its tabs reload by themselves when the hub
 reports `AgentWorkChanged` for work they show, debounced, and after every reconnect. The
 update names the thread, its subject (`subjectType`, `subjectId`) and whether a run, a