@patimweb/pi-teams 1.3.0 → 1.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@patimweb/pi-teams",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "Microsoft Teams integration for pi coding agent — acts fully as the signed-in user across multiple accounts and tenants: chats, channels, meetings, presence, with configurable guardrails",
   "keywords": [
     "pi-package",

package/src/extension/index.ts

@@ -143,12 +143,23 @@ export default function (pi: ExtensionAPI) {
 	/** The watcher running in this session, when listen mode is on. */
 	let watchLoop: WatchLoop | undefined;
 
+	/**
+	 * The settings the running watcher was started from.
+	 *
+	 * Used to tell a real config change from a tool that merely *read* the
+	 * settings. Restarting resets the watcher's baseline, which discards every
+	 * chat it has already looked at and swallows whatever arrived just before —
+	 * so a `teams_watch status` must not be treated like an edit.
+	 */
+	let watchSignature: string | undefined;
+
 	/** The last polling error the user was told about, so it is said once. */
 	let reportedWatchError: string | undefined;
 
 	const stopWatch = () => {
 		watchLoop?.stop();
 		watchLoop = undefined;
+		watchSignature = undefined;
 		setActiveWatchLoop(undefined);
 	};
 
@@ -159,9 +170,15 @@ export default function (pi: ExtensionAPI) {
 	 * change cannot leave two pollers running.
 	 */
 	const startWatch = (ctx: any) => {
+		const conn = refresh();
+
+		// Already watching this exact configuration: leave the loop alone, so its
+		// baseline and its cooldowns survive a look at the status.
+		const signature = conn?.watch.enabled ? JSON.stringify(conn.watch) : undefined;
+		if (watchSignature !== undefined && signature === watchSignature && watchLoop) return;
+
 		stopWatch();
 
-		const conn = refresh();
 		if (!conn?.watch.enabled) return;
 
 		reportedWatchError = undefined;
@@ -182,6 +199,7 @@ export default function (pi: ExtensionAPI) {
 		});
 
 		watchLoop = loop;
+		watchSignature = signature;
 		setActiveWatchLoop(loop);
 	};
 

package/src/graph/mappers.ts

@@ -134,6 +134,25 @@ export function teamCandidates(team: TeamSummary): (string | undefined)[] {
 // Chats
 // ---------------------------------------------------------------------------
 
+/**
+ * When did this chat last *move*?
+ *
+ * Deliberately the time of the last **message** rather than Graph's
+ * `lastUpdatedDateTime`. That field tracks chat metadata and is badly stale for
+ * 1:1 and ad-hoc group chats: measured against a live tenant, a chat whose
+ * newest message arrived minutes ago still reported a `lastUpdatedDateTime`
+ * from more than a year earlier.
+ *
+ * Everything that dates a chat depends on this — the chat list order, the
+ * inbox window, and the freshness cut-off that decides whether listen mode
+ * looks at a chat at all — so a stale value here silently disabled listen mode
+ * for exactly the chats people write in. `lastUpdatedDateTime` stays as the
+ * fallback for chats Graph returns without a preview.
+ */
+function chatActivity(raw: Raw): string | undefined {
+	return raw.lastMessagePreview?.createdDateTime ?? raw.lastUpdatedDateTime ?? undefined;
+}
+
 /**
  * Build a chat summary.
  *
@@ -162,7 +181,7 @@ export function mapChat(raw: Raw, meId?: string): ChatSummary {
 		topic: raw.topic ?? undefined,
 		label: raw.topic || derived || raw.id || "(chat)",
 		members,
-		lastUpdated: raw.lastUpdatedDateTime ?? raw.lastMessagePreview?.createdDateTime ?? undefined,
+		lastUpdated: chatActivity(raw),
 		lastMessagePreview: preview,
 		lastMessageFrom: mapPerson(raw.lastMessagePreview?.from)?.displayName,
 		webUrl: raw.webUrl ?? undefined,