Files
learnharness/tests/activity-feed.test.ts
T
amosblomqvist f8ba5b1628 Activity feed: one dock-shaped GET /api/activity (cross-chat processes)
The dock is visible in every view, so it needs every running process —
sub-agent jobs across ALL chats (not just the open one) plus the global
extraction runs — in one poll. /api/jobs stays chat-scoped and untouched:
it is the transcript machinery's poll and carries turnInFlight for the
re-attach seam (chat-transport), the seam we spent three live rounds
stabilizing; making it polymorphic would fork its response shape by mode
and put regression risk on exactly the wrong path. The dock is a different
consumer with a different shape (cross-chat, running-only, cost-bearing),
served by a thin route over server/observability.ts:

- activityFeed(): running jobs from every chat (title-joined, oldest-first
  on last activity) + extraction runs + busyChats (chats with a teacher
  turn in flight — the biggest spender; data made available, rendering is
  a dock decision).
- GET /api/activity — the dock's single poll everywhere.
- Cost math stays client-side (core/prices.ts folds); raw usage rides the
  records and the transport stays thin.

Decided with the user over the polymorphic-/api/jobs and
separate-all-jobs-endpoint alternatives.
2026-09-11 02:54:31 +03:00

55 lines
2.6 KiB
TypeScript

/**
* Activity-feed tests — the dock's composition (server/observability.ts).
*
* Real stores with fixture chats/jobs, cleaned up in a top-level test.
* Verifies the cross-chat gathering, running-only filtering, title joins,
* stable oldest-first ordering, and busy-chat reporting.
*/
import assert from "node:assert/strict";
import test from "node:test";
import * as fs from "node:fs";
import * as path from "node:path";
import { chatStore } from "../src/store/chats.ts";
import { jobStore } from "../src/store/jobs.ts";
import { PATHS } from "../config.ts";
import { activityFeed } from "../src/server/observability.ts";
test("activityFeed: running jobs across ALL chats, running-only, title-joined, oldest first", () => {
const chatA = chatStore.createChat("feed chat A");
const chatB = chatStore.createChat("feed chat B");
try {
const jobA = jobStore.createJob({ kind: "research", chatId: chatA.id, toolCallId: "tc_a" });
const jobB = jobStore.createJob({ kind: "demo", chatId: chatB.id, toolCallId: "tc_b" });
const jobDone = jobStore.createJob({ kind: "research", chatId: chatA.id, toolCallId: "tc_done" });
jobStore.updateJob(jobDone.id, { status: "done" });
const jobB2 = jobStore.createJob({ kind: "research", chatId: chatB.id, toolCallId: "tc_b2" });
// make jobB2 the MOST recently active → should still sort AFTER jobA/jobB (oldest-first).
// Explicit later timestamp: the real bump can land in the same ms as creation.
jobStore.updateJob(jobB2.id, { activity: "second step", updatedAt: new Date(Date.now() + 10).toISOString() });
const feed = activityFeed();
const feedJobs = feed.jobs.filter((j) => [jobA.id, jobB.id, jobB2.id].includes(j.id));
assert.equal(feedJobs.length, 3); // done job filtered out
for (const j of feedJobs) {
assert.ok(j.title.length > 0, "title joined onto every job");
assert.equal(typeof j.chatId, "string");
}
// title join is the chat's title
assert.equal(feedJobs.find((j) => j.id === jobA.id)?.title, "feed chat A");
// oldest-first on updatedAt: jobA/jobB created before jobB2's bump
const order = feedJobs.map((j) => j.id);
assert.equal(order.indexOf(jobB2.id), order.length - 1);
// extraction runs are absent when the pipeline is idle (registry empty)
assert.deepEqual(feed.extractions, []);
// busyChats reports turn-liveness (none in flight here)
assert.deepEqual(feed.busyChats, []);
} finally {
fs.unlinkSync(`${PATHS.chats}/${chatA.id}.json`);
fs.unlinkSync(`${PATHS.chats}/${chatB.id}.json`);
const jobsDir = path.join(PATHS.data, "jobs");
for (const f of fs.readdirSync(jobsDir)) fs.unlinkSync(path.join(jobsDir, f));
}
});