Inferpal 1.7.10

Nineteen fixes. The first closes a way around your rules on Windows: a file they protect could be written under another spelling of its name.

Your files and your rules

• Windows: another spelling of a file is that file, for your rules too. To Windows, .env::$DATA and memory.md. are .env and memory.md themselves: written that way, a file a deny rule protects — or one of the files the agent reads back as its instructions — was written without the rule or the forced approval applying. Paths are now read as the file they write, and a hidden stream of a file (Cart.cs:hidden) is refused.
• Linux: two files whose names differ only by case are no longer taken for one. The impact analysis could leave a real dependant out, /check filed one file's findings under the other's name, Fix with AI mixed their errors, and opening a solution in a folder whose name differed only by case did not move Inferpal to it.
• Linux: renaming a file to change only its case keeps it in the semantic index. Widget.cs renamed widget.cs disappeared from the codebase search until the next full indexing.
• The agent's build check builds your solution, not a side project's. With a .slnx at the root and an older .sln in a sub-folder, the build check — and /tdd's test run — used the sub-folder's and reported its result as yours.

Stopping and waiting

• VS Code: Stop works from the moment the button shows. Pressed while /explain or /review was still sizing the code, an @file was being read or a template expanded, the question went anyway. The turn now ends there, with nothing sent.
• LM Studio: stopping an answer no longer hides the model's real context from the next questions. A model loaded with less context than your setting then had its next questions refused instead of compacted to fit.
• Stopping a /task propose keeps what it proposed. Its changes are counted in the notice and listed by /task <id>; and /task apply on a task still running says it has not finished.
• Unloading a model no longer breaks an answer in your other editor. With Visual Studio and VS Code (or Zed) open, Unload in the settings pulled the model from under the other one's answer. It now waits for any answer on the machine to end.

Visual Studio

• "Edit with AI" shows the change before applying it, when you asked for that — as Fix, Refactor and Add docs already did.
• After a crash, the new window no longer inherits the old one's state. A crashed Visual Studio leaves small state files behind, and the next one could take its debugger position, its "answering" marker, a pending preview or its open solution for its own.

VS Code

• The files the model is told are open are your tabs — not every document VS Code had loaded, and no longer missing an open file too large to mirror.
• The @ picker no longer offers Inferpal's backup copies or your Python environment, and the files it lists first are your open tabs.

Zed and other ACP clients

• An /arena vote goes to the duel that thread showed, not to a duel started in another thread.
• A reloaded thread keeps the part of a failed answer you had read, marked as a notice, as in Visual Studio and VS Code.

Everywhere

• Saved conversations are listed newest first in the session pickers, /sessions and /history.
• Dates written to files are the same on every machine — on a Windows set to the Thai calendar, notes were dated 2569; what Inferpal shows you keeps your settings.
• /snippets copy and /snippets delete say when your snippet library cannot be read, instead of "no snippet #3".
• A repository's Continue MCP server connects with its headers and key, and a server declaring the older SSE transport says so when it fails.
• An MCP server declared with WebSocket says why it does not run, and /import leaves it out with the reason instead of adding a server that could only fail.