@iloveagents/foundry-agent 0.1.5 → 0.2.2

package/CHANGELOG.md

@@ -1,5 +1,107 @@
 # @iloveagents/foundry-agent
 
+## 0.2.2
+
+### Patch Changes
+
+- 8184a8c: shell: URL is authoritative for the runtime threadId — fixes
+  resume-creates-new-conversation race
+
+  `ChatConversationAwareRuntime` previously computed
+  `effectiveThreadId = sticky ?? urlMatch ?? freshIdRef.current`.
+  When the user navigated from one chat to another via a Recents
+  click, the synchronous render that followed the URL change had:
+  - `urlMatch = B` (read from the now-updated `useLocation`)
+  - `sticky = A` (the active-chat-store hadn't been updated by
+    `useTrackActiveChatFromUrl`'s `useEffect` yet — effects run
+    AFTER the commit phase)
+
+  `sticky ?? urlMatch` picked `A` (the previous chat). The AG-UI
+  adapter was constructed with `threadId = A`. The first message the
+  user sent went to `/api/agent` with `thread_id = A`, the middleware
+  created a new row keyed by `A`... wait actually no, here's what
+  happens — the runtime mints a fresh runner UUID when given a
+  mismatched threadId; that fresh UUID became a new conversation row,
+  appearing as "Untitled chat" at the top of the sidebar while the
+  URL still said `/chat/B`. Two active-looking dots: one for `B`
+  (NavLink URL match), one for the new row (statusDot from the
+  updated active-chat-store after the lazy ensure ran).
+
+  Swap the priority: `urlMatch ?? sticky ?? freshIdRef.current`. The
+  URL is authoritative whenever it's set (i.e. on `/chat/<id>`
+  routes), eliminating the stale-sticky race entirely. `sticky` is
+  still consulted as the second-priority fallback for non-chat
+  routes (`/spaces`, `/tasks`) so the popout chat stays "live" while
+  the user browses workspaces — that's the original purpose of
+  `useStickyConversationId` and it's preserved.
+
+## 0.2.1
+
+### Patch Changes
+
+- No source changes. The 0.2.0 publish for `@iloveagents/foundry-agent` and
+  `@iloveagents/foundry-web-primitives` failed because npm had `0.2.0`
+  reserved for those two packages from an older publish-then-unpublish
+  cycle (the version was reserved before the recent v1 incident — see
+  git tag history). `@iloveagents/foundry-web-shell@0.2.0` and
+  `@iloveagents/foundry-web-ui@0.2.0` published cleanly. Bumping the
+  whole fixed group to 0.2.1 so all four publish together at a version
+  number that's free across all four packages.
+
+## 0.2.0
+
+### Minor Changes
+
+- shell: ChatConversationConfig API + sticky-runtime threadId
+
+  Lets a downstream module (e.g. `@ltwlf/spaces-web-ui`) attach a
+  `ChatConversationConfig` to its `ChatModule`. The shell then:
+  - Pre-mints a fresh thread UUID via `useRef` so the AG-UI runtime's
+    `threadId` is defined from first render — no `undefined → defined`
+    remount mid-conversation when the user sends the first message.
+  - Calls `config.useStickyConversationId()` (when declared) and
+    feeds the resulting id into the runtime so the chat stays "live"
+    while the user browses non-chat routes (Workspaces, Jobs, etc.).
+  - Per-config keyed child components (`StickyAwareRuntime` vs
+    `UrlOnlyRuntime`) so optional hooks satisfy Rules-of-Hooks across
+    multi-module config swaps.
+
+  UI: collapsible nav groups in `sidebar.tsx` with persisted state via
+  `useSyncExternalStore` + localStorage, plus stable group ordering via
+  new `priority` field in `nav-config.ts`.
+
+  `ag-ui-runtime-provider.tsx` accepts an external `threadId` and
+  `historyAdapterFactory` so the consuming app can wire its own
+  persistence (e.g. `ThreadHistoryAdapter` → REST `/api/conversations`).
+
+### Patch Changes
+
+- Fix `citationStore.clear()` so the registered handler survives per-conversation resets.
+
+  The previous implementation wiped both `results` AND `handler`. `useNewConversation` calls `clear()` on every "New Thread" click. Combined with the `registerOnce`-style handler registration in feature modules (e.g. SPACES' `registerSpacesCitationHandler`), the result was that all `[n]` citation markers in chat became inert non-clickable spans for the rest of the session after the first new-thread click. `clear()` now resets `results` only — the handler is module-level state and must persist.
+
+- Move sibling `@iloveagents/foundry-*` declarations from `peerDependencies`
+  to `dependencies` in `foundry-web-shell` and `foundry-web-ui`. These four
+  packages always ship together as a coordinated fixed group from the same
+  monorepo — they were never independently-versioned peers, so declaring
+  them as peerDeps caused changesets' `shouldBumpMajor` cascade to promote
+  the entire group to a major version on every minor changeset (a single
+  minor on any of the four would exit the sibling's `^0.x.y` peerDep range
+  → all dependents promoted to major → fixed group synced all four to
+  major → 0.1.5 unexpectedly jumped to 1.0.0). Moving to `dependencies`
+  eliminates the cascade entirely; `dependencies` never trigger
+  `shouldBumpMajor`. Consumers that already install each foundry-\* package
+  directly are unaffected — pnpm hoists by name, so a single instance
+  resolves across the dep graph regardless of declaration site.
+
+### NOTE: 1.0.0 / 1.0.1 were accidental
+
+These version numbers were published briefly on 2026-05-27 due to the
+peerDep cascade bug described above, then unpublished. The version
+numbers themselves are now permanently reserved on npm and CANNOT be
+re-published. This 0.2.0 release captures all the work that was in
+the accidental 1.0.x releases. Do not depend on 1.0.x.
+
 ## 0.1.5
 
 ## 0.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iloveagents/foundry-agent",
-  "version": "0.1.5",
+  "version": "0.2.2",
   "license": "SEE LICENSE IN LICENSE",
   "type": "module",
   "types": "./src/index.ts",

package/src/__tests__/citation-store.test.ts

@@ -33,14 +33,20 @@ describe("citationStore", () => {
   });
 
   describe("clear", () => {
-    it("resets results and handler", () => {
+    it("resets results but preserves the registered handler", () => {
+      // The handler is registered once at app boot by a feature module
+      // (e.g. SPACES). It MUST survive "New Thread" / per-conversation
+      // resets — otherwise every [n] marker in chat becomes inert after
+      // the first new-thread click, since the registration guard
+      // suppresses re-binding for the rest of the session.
+      const handler: CitationHandler = { openCitation: () => {} };
       citationStore.getState().setResults([mockResult]);
-      citationStore.getState().setHandler({ openCitation: () => {} });
+      citationStore.getState().setHandler(handler);
 
       citationStore.getState().clear();
 
       expect(citationStore.getState().results).toEqual([]);
-      expect(citationStore.getState().handler).toBeNull();
+      expect(citationStore.getState().handler).toBe(handler);
     });
   });
 });

package/src/store/citation-store.ts

@@ -26,7 +26,14 @@ interface CitationState {
   setResults: (results: CitationResult[]) => void;
   /** Register a handler for citation click actions */
   setHandler: (handler: CitationHandler) => void;
-  /** Clear all citations (e.g. on new conversation) */
+  /**
+   * Reset per-conversation state. Clears ``results`` only — the handler
+   * is module-level state registered once at app boot by feature modules
+   * (e.g. ``registerSpacesCitationHandler``) and must persist across
+   * conversations. Wiping it on "New Thread" produced inert ``[n]``
+   * markers for the rest of the session, since the registration guard
+   * (``registerOnce`` in spaces ``use-spaces-init``) suppresses re-binding.
+   */
   clear: () => void;
 }
 
@@ -41,5 +48,5 @@ export const citationStore = createStore<CitationState>((set) => ({
   handler: null,
   setResults: (results) => set({ results }),
   setHandler: (handler) => set({ handler }),
-  clear: () => set({ results: [], handler: null }),
+  clear: () => set({ results: [] }),
 }));