The status snapshot (.agenthub/status/latest.md) was only refreshed on an explicit `status --update`, so it drifted stale and misled agents that follow golden rule #2 ("read status/latest.md") — e.g. an implementer seeing an old task list and picking the wrong task. - src/server/statusRefresh.ts: subscribe to the event bus and regenerate the snapshot on every task/handoff/decision/memory change (REST and filesystem-watch paths), debounced 300 ms. Presence ('agent') events are skipped; the snapshot lives outside the watched dirs so it can't feed back into the watcher. - wired into startServer lifecycle (start + stop on close). - test: status/latest.md reflects a new task shortly after POST /tasks. 117/117 green. Bump 0.3.0 -> 0.3.1. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
53 lines
983 B
JSON
53 lines
983 B
JSON
{
|
|
"name": "agenthub",
|
|
"version": "0.3.1",
|
|
"description": "Local coordination layer for AI coding agents",
|
|
"type": "module",
|
|
"main": "./dist/index.js",
|
|
"types": "./dist/index.d.ts",
|
|
"files": [
|
|
"dist",
|
|
"bin"
|
|
],
|
|
"bin": {
|
|
"agenthub": "./bin/agenthub.js"
|
|
},
|
|
"scripts": {
|
|
"build": "tsc",
|
|
"dev": "tsc --watch",
|
|
"test": "vitest run",
|
|
"test:watch": "vitest"
|
|
},
|
|
"engines": {
|
|
"node": ">=20"
|
|
},
|
|
"dependencies": {
|
|
"@inquirer/prompts": "^7.0.0",
|
|
"better-sqlite3": "^12.0.0",
|
|
"commander": "^13.0.0",
|
|
"fastify": "^5.0.0",
|
|
"yaml": "^2.6.0",
|
|
"zod": "^3.23.0"
|
|
},
|
|
"devDependencies": {
|
|
"@types/better-sqlite3": "^7.6.12",
|
|
"@types/node": "^22.0.0",
|
|
"typescript": "^5.7.0",
|
|
"vitest": "^3.0.0"
|
|
},
|
|
"keywords": [
|
|
"ai",
|
|
"agents",
|
|
"claude",
|
|
"codex",
|
|
"kimi",
|
|
"collaboration"
|
|
],
|
|
"license": "MIT",
|
|
"pnpm": {
|
|
"onlyBuiltDependencies": [
|
|
"better-sqlite3"
|
|
]
|
|
}
|
|
}
|