v1.11.0 — daily worklog: check_in / check_out + standup

Adds a daily worklog for standups: check_in stamps the start of the day and returns the last working day's summary plus loose threads; check_out harvests the day's evidence from disk (git commits across every repo, uncommitted WIP, memory writes, initiative progress) and stores a standup summary composed strictly from that evidence (two-pass tool protocol, works in any MCP client). npx -y @kaaustubh/project-memory-mcp standup [YYYY-MM-DD] prints it with no agent. Days live in ROOT/.worklog/YYYY-MM-DD.json, local-time stamps, multiple segments per day, forgotten checkouts auto-reconstructed, pruned after WORKLOG_KEEP_DAYS (default 10).

v1.10.0

install now also registers Kimi Code CLI (~/.kimi-code/mcp.json, or $KIMI_CODE_HOME — not to be confused with the separate "Kimi CLI" product, which uses ~/.kimi/mcp.json), Gemini CLI (~/.gemini/settings.json), and Windsurf (~/.codeium/windsurf/mcp_config.json) — all three match the existing mcpServers/no-type schema registerMcp already handled for Cursor, so each was a one-line addition.

OpenAI Codex CLI (~/.codex/config.toml) needed real work: it's the first non-JSON client, configured via TOML [mcp_servers.<name>] tables. Added registerMcpToml, a text-based find-the-table/replace-or-append merge rather than a TOML parser dependency, keeping the zero-hard-dependency posture.

Caught and fixed a real bug in it before shipping: the first version matched a table's body as "everything up to the next literal [," which truncates mid-table because args = [...] arrays use [ too — fixed to match "up to the next line that starts with [" instead, verified idempotent across repeated install runs against a pre-seeded config.toml with an unrelated table.

v1.9.0

Feature: Initiatives. Four new tools — start_initiative, get_initiative, list_initiatives, update_initiative — track a named, multi-session effort (a codename, a plan, an evolving todo list) so it's resumable by name from ANY future session, not just the one that started it.

Motivated by a real failure mode reported using another agent's session-local "codename" convention: no persistent registry mapping name → session, todos scoped to one session's private store, and discovery requiring an exact-string match across raw transcripts.

Fixed here by storing one markdown file per initiative (<project>/initiatives/<slug>.md — mutable, so todo checkboxes toggle in place) plus a synced pointer under a new ## Active Initiatives heading in the project's auto-loaded AGENTS.md, so a brand-new session sees what's in flight with zero tool calls.

Codename matching is case/spacing-insensitive (slugify splits camelCase boundaries first, so "HashGate" and "hash gate" resolve to the same initiative). list_initiatives searches across all projects when none is given, so "what was I working on?" doesn't require remembering which repo it was in either.

v1.8.3

• Infra: Added a real CI workflow (Node 18/20/22 matrix) backed by a new stdio smoke test, plus a CodeQL workflow. Both were previously entirely absent, which is why Glama's quality page showed "CI status not available" and "No code scanning findings" — those meant "never measured," not a clean bill of health.
• Fix: Regenerated package-lock.json (it predated @xenova/transformers's optional-dep subtree ever being resolved, which broke npm ci on a clean runner) and ran npm audit fix to clear the @modelcontextprotocol/sdk-transitive advisories.
• Known issue: @xenova/transformers (optional, powers semantic recall) still carries a critical + 4 high severity CVE chain via old onnxruntime-web/protobufjs/sharp; the only fix is a breaking downgrade to 1.4.2, tracked as a follow-up rather than forced in blind.

v1.8.2

• Docs/meta: Added glama.json (declares maintainers) to fix Glama's "No glama.json" profile-completion check. Paired with cutting an actual GitHub Release for this version — previously we only pushed git tags, which Glama's "Has a release" check doesn't see (it reads the Releases API, not tags).