Repository navigation
Tags
Tags
docs: add an agent field report for the DeepSeek Harness MCP registra… …tion (xerj-org#2444) One new file under user-feedback/16-agent-field-reports/, nothing else: what registering `xerj mcp` v1.0.0-rc.99 in DeepSeek Harness 44.7.0 on Windows was like, what the retrieval looked like, and the one thing I would want a reader to know before wiring it in - the server's `instructions` tell the agent to file a report on its own, which I disabled with XERJ_DISABLE_FEEDBACK=true. No code, docs or other reports touched. Written by an AI coding agent (DeepSeek-V4.1-Flash, DeepSeek Harness 44.7.0), run by PensiveFei. Co-authored-by: PensiveFei <pensivefei@users.noreply.github.com>
docs: add an agent field report for the DeepSeek Harness MCP registra… …tion (xerj-org#2444) One new file under user-feedback/16-agent-field-reports/, nothing else: what registering `xerj mcp` v1.0.0-rc.99 in DeepSeek Harness 44.7.0 on Windows was like, what the retrieval looked like, and the one thing I would want a reader to know before wiring it in - the server's `instructions` tell the agent to file a report on its own, which I disabled with XERJ_DISABLE_FEEDBACK=true. No code, docs or other reports touched. Written by an AI coding agent (DeepSeek-V4.1-Flash, DeepSeek Harness 44.7.0), run by PensiveFei. Co-authored-by: PensiveFei <pensivefei@users.noreply.github.com>
docs: add an agent field report for the DeepSeek Harness MCP registra… …tion (xerj-org#2444) One new file under user-feedback/16-agent-field-reports/, nothing else: what registering `xerj mcp` v1.0.0-rc.99 in DeepSeek Harness 44.7.0 on Windows was like, what the retrieval looked like, and the one thing I would want a reader to know before wiring it in - the server's `instructions` tell the agent to file a report on its own, which I disabled with XERJ_DISABLE_FEEDBACK=true. No code, docs or other reports touched. Written by an AI coding agent (DeepSeek-V4.1-Flash, DeepSeek Harness 44.7.0), run by PensiveFei. Co-authored-by: PensiveFei <pensivefei@users.noreply.github.com>
docs: add an agent field report for the DeepSeek Harness MCP registra… …tion (xerj-org#2444) One new file under user-feedback/16-agent-field-reports/, nothing else: what registering `xerj mcp` v1.0.0-rc.99 in DeepSeek Harness 44.7.0 on Windows was like, what the retrieval looked like, and the one thing I would want a reader to know before wiring it in - the server's `instructions` tell the agent to file a report on its own, which I disabled with XERJ_DISABLE_FEEDBACK=true. No code, docs or other reports touched. Written by an AI coding agent (DeepSeek-V4.1-Flash, DeepSeek Harness 44.7.0), run by PensiveFei. Co-authored-by: PensiveFei <pensivefei@users.noreply.github.com>
docs: mark Kimi CLI MCP row tested. teach 'xerj' in the Kimi configur… …ation path. (xerj-org#2386) Xerj Merger made the fix: marks the Kimi CLI MCP row as tested in the README (Kimi Code CLI 2.3.1 against rc.99 loaded ~/.kimi-code/mcp.json and listed xerj_search) and adds the Kimi config path to the MCP registration hints printed by xerj init.
docs: mark Kimi CLI MCP row tested. teach 'xerj' in the Kimi configur… …ation path. (xerj-org#2386) Xerj Merger made the fix: marks the Kimi CLI MCP row as tested in the README (Kimi Code CLI 2.3.1 against rc.99 loaded ~/.kimi-code/mcp.json and listed xerj_search) and adds the Kimi config path to the MCP registration hints printed by xerj init.
docs: mark Kimi CLI MCP row tested. teach 'xerj' in the Kimi configur… …ation path. (xerj-org#2386) Xerj Merger made the fix: marks the Kimi CLI MCP row as tested in the README (Kimi Code CLI 2.3.1 against rc.99 loaded ~/.kimi-code/mcp.json and listed xerj_search) and adds the Kimi config path to the MCP registration hints printed by xerj init.
docs: mark Kimi CLI MCP row tested. teach 'xerj' in the Kimi configur… …ation path. (xerj-org#2386) Xerj Merger made the fix: marks the Kimi CLI MCP row as tested in the README (Kimi Code CLI 2.3.1 against rc.99 loaded ~/.kimi-code/mcp.json and listed xerj_search) and adds the Kimi config path to the MCP registration hints printed by xerj init.
fix(common): make SpawnedThread Send on musl so rc.99 release builds … …compile (backport of xerj-org#2376)
feat(cluster): replay the on-disk Raft log when a node restarts (xerj… …-org#2313) Part of xerj-org#1170. The server built its Raft node with an in-memory log, so a restart or a member that joined late had no shard plan even though FileRaftLog already existed. Followers also acknowledged AppendEntries before writing them, and a truncated tail came back on reopen because the append-only file was scanned in full. Cluster mode now opens {data_dir}/_raft, persists appended entries, the commit index, the term, and the vote, and hides a replaced tail behind hard.meta. Startup replays the committed prefix after the engine applier and the shard handler are installed, so the shard plan and the in-sync set are back before HTTP is served. A member whose log is empty copies the leader's log and applies the same metadata. Documents are not in this log and are not copied. There is no InstallSnapshot. hard.meta is replaced, and the directory synced, before the in-memory term, vote, or log end move. A failed write stays off disk, so a later save cannot publish an election this process aborted. Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: xerj-org <xerj-org@users.noreply.github.com>
PreviousNext