edit-timeline : The server all others will measure themselves by. A governance server for AI coding agents.

edit-timeline is an MCP server that sits between your AI coding agent and your code. The agent plans and reasons; edit-timeline does the writing, and refuses to let a change land until it can prove it. Every edit is recorded with why it was made, so you can ask any file how it got to be the way it is. It's built for projects where you need security and accuracy from your AI agent: every change proven, reviewed, and recorded, on your own machine. Your code and its history stay local; a plain local git repo is all it needs. What 0.11.2 changes Improved efficiencies. The checks that catch real problems stay on; the ones that cost time without catching much now report instead of blocking: The mutation check (it breaks your code on purpose to see if your tests notice) now writes its results into the commit instead of holding the change up. Changes that only touch test files re-run just those tests. Heavy background jobs take turns with the full test run instead of competing with it. Safer releases. A release now refuses unless every packaged file matches what was actually committed, so unreviewed edits sitting on disk can never ship. More honest records. Commits name any test that had to be skipped during a check, each full test run records how busy the machine was, and timings are accurate. We also fixed a bug that had quietly disabled two test shortcuts. Examples of changes edit-timeline ran this release A bug fix. A test was written first and shown to fail. The fix was applied at exact byte positions (no model retyping the file), the test passed, a second model reviewed the change, and the full test suite ran before the commit was allowed. A test-only change. A test that dumped an entire 780 KB file into the log whenever it failed was tightened. edit-timeline recognized that only a test changed and re-ran just that test. A new safety rule. Releases now refuse if any packaged file differs from the committed version. While building it, edit-timeline measured that 31 files differ only in line endings, so those warn instead of blocking every release. A change that was pulled. Running two checks side by side was attempted. The reviewer found five real problems across four rounds, so the change was reverted instead of patched further, and is being redesigned. A caught mistake. A new test only worked inside the real project folder, so it was silently skipped elsewhere and caused a false alarm. edit-timeline's records surfaced it, and the test was fixed. Install Claude Code: run these two commands, approve the MCP server when asked, then restart your session. /plugin marketplace add SMC1177/edit-timeline /plugin install edit-timeline@edit-timeline Claude Desktop: download edit-timeline-mcp-0.11.2.mcpb from github.com/SMC1177/edit-timeline/releases/latest and open it. You can check it against the .sha256 file. Other MCP clients: see the install section at edit-timeline.smacktax.com .