i18n::trf filled {name} placeholders with one replace per argument, so a value that looked like
a later placeholder was filled in turn. It now fills them in one pass over the translated
template: inserted values stay literal, and unknown names and stray braces are kept as written.
The saved-builder replacement notice uses it instead of its own split.
Picking game A, then B, then A again while the first look at A was still running could show the older result, because the screen matched an answer to the folder's path. Each look and each archive listing is now matched to the job that started it, so a repeated pick ignores the older answer, and a job that fails settles only its own request: one a newer pick replaced is logged and says nothing. A folder whose name isn't valid text used to be sent under a changed name and left the screen loading forever; picking one now says its name can't be read and asks for another folder. A failed save of a picture or asset also says so.
Review follow-up: folder_picked now refuses a folder whose name isn't text before dispatching either tool, with a message, and sends the exact UTF-8 path. Game files keeps one map of in-flight jobs with their kind and whether the screen still waits for them, instead of a looks list and a listing id. A worker failure is always logged; a current folder scan or listing clears only its own spinner and says so, a failed triage holds neither, and a superseded job says nothing. Export save errors say so without stopping the archive listing, even when the archive path matches a reopened listing.
The same-folder regression now starts both looks through folder_picked and feeds results through CraftApp dispatch; new regressions cover the non-text refusal, a failed triage keeping the scan running, a superseded failure staying quiet, and an export error not clearing loading.
Picking game A, B and A again while the first A look ran could still apply the older A result, because the screen compared the shown folder's path. Worse, a folder whose name has bytes that aren't text was sent as a lossy display string, so every completion failed the same path check and the screen loaded forever. act now returns its job id; GameFiles records the folder looks and the archive listing still expected, and tool_done applies only those. A repeated pick ignores the older answer, and a non-text folder's current answer finishes with its error.
Regressions: a stale same-folder look is ignored and the newer one fills the list; a non-text folder's current error clears looking and is shown. The three existing wrong-folder/archive guards still pass.
A folder walk says which folders it couldn't list and why, but five tools that walk a folder (two for Apple bundles, the app source import and comparison, the managed source check and the JavaScript source restore) read only "cut short". A folder that couldn't be opened was reported as a limit, with neither its name nor the reason, and some results still said they were complete.
- Each of those tools now names the folders and their reasons, and marks its result partial when a walk was cut or a folder couldn't be listed.
- When nothing is found and a folder couldn't be listed, the error says so ("no .cs files under …; 1 folder(s) couldn't be listed…") with what to do, since what was looked for may be in it.
- Two inputs with the same folder name are told apart in the notes ("dist (input 2)").
Codex now shows the model it uses ("Codex default" until one is chosen) with Change…, like Claude Code (#2109). The choices are its default (no model is passed, so its own settings decide) and the models `codex debug models` lists, in its order, leaving out the ones it hides; over SSH the remote Codex is asked. `ai model Codex` lists and sets them the same way. Until now the model could only be set by adding `cli_model` to config.toml by hand.
Follow-up to #2124. The pseudo-C could still show an argument's load in the call line after an instruction that overwrote the bytes it read, for writes the decompiler measured wrongly: 64-bit ARM pair and exclusive stores (both registers count, and non-temporal pairs are stores too), x86 bit writes through a register index, `movdir64b`, and a store that overwrites part of a Windows stack argument. Those are measured now. A register is treated as the stack frame only while the function really keeps its stack there, so a stack pointer loaded from elsewhere is no longer assumed clear of global data. 64-bit ARM loads also show the size they read (`*(uint8_t*)…`), and a pair store shows as two typed writes.
Measured on two real programs before and after (every function, default limits): an x86-64 `grep` folds 3,021 register arguments where it folded 3,023, the two lost being loads from a global with a store through a data pointer in between; an AArch64 `ls` folds 1,813 either way.
Follow-up to #2113. A window loading `file://localhost/ui/index.html` was looked up as `localhost/ui/index.html`, which could match the wrong page; `localhost` and an empty host both mean this computer now. And a page reference ending in a `.` or `..` part (`./boot.js/.`) names a folder, so it is no longer matched to the file before it.
Follow-up to #2116. A result with thousands of lists at its top level was still gone through in full, though its first 64 already decide what is listed. The top level is read first and the work stops at the 64th list; nested lists are only looked for when there is room left. What is listed doesn't change.
Follow-up to #2119, which stopped a load being shown after a store that may have changed the memory it read, but still let it through in several cases: on 64-bit ARM, where the size of an access wasn't known and a 16-byte pair store looked clear of a load 8 bytes on; when a stack address had an index, or the two addresses used different segments; after an instruction the decompiler doesn't model, such as a byte store on 32-bit ARM or an x86 string operation; and for a value loaded from a fixed address. A Win64 argument passed on the stack is also no longer shown with the value stored before a later write to its slot. Where it can't tell, the decompiler now keeps the load as its own statement.
Follow-up to #2108. A column added later to a SQLite table fills older rows with its default. Two kinds of default were read as empty: a blob written with a plus sign in front (`DEFAULT+X'41'`), which #2108's splitting broke, and a bare word containing accented or other non-ASCII letters or a `$` (`DEFAULT été`, `DEFAULT a$b`). Both are read as SQLite reads them. A test table that SQLite itself would refuse to create is replaced by one it accepts.
Follow-up to #2107. Listing a result's pageable lists looked each list name up from the top of the result again, so a large result with many names took one full walk per name (about 150 ms for 5,000 names in the author's measurement, under 1 ms now). The result is walked once, recording what each name reaches first, in the same order as before. What is listed doesn't change.
Follow-up to #2114. An argument loaded from memory was written into the call that follows it, also when a store in between could have changed that memory: `ldr r0, [r4]; str r1, [r4]; puts(...)` printed `puts(*r4)`, which reads the value after the store. Such a load now stays where it is and the call is shown taking the register, unless the two places can be told apart (the same base with offsets far enough apart, or a stack slot and a fixed address). A store instruction was also recorded as setting the register it reads, which could make the store's own line disappear. And the object of a method-table call is still passed when it was saved to the stack before the call.
Follow-up to #2100. A page script written as a `data:` or `blob:` URL was read as a local path, so `data:text/javascript,0//../../boot.js` became a dependency on the app's own `boot.js`. Anything with a URL scheme is now left alone, while a local path whose query holds a URL stays local. A path written with a `./` in the middle reaches the same file as one without. A dependency's file under `node_modules/` no longer wins over the app's own file of the same name. These lookups now use one index built once per app, where each used to scan every file.
Settings ends with an About tab that shows "Craft Anything" and its version on every system, not
only in macOS's menu bar. A Copy the version button, which the keyboard reaches, copies it. "About"
and "Copy the version" are in all 16 catalogs. The roadmap ticks the item and adds an open line:
Settings doesn't fit a small window at high zoom.
Closes#1300.
Only STR lifted as a store, so the other plain stores recorded the stored register as written, which dropped it from entry-block parameters and other dataflow. Their kind is unchanged.
Follow-up to #2105. While the rebuild ledger was being built, the same piece of evidence was looked up several times. A check result saved in between could fail the first lookup and pass a later one, which left an entry marked proven with no result behind it. Each piece of evidence is now looked up once per build, and an entry is proven only when a passing check's result was actually selected. Two checks that tie no longer give a different explanation depending on the order they were recorded in.
A memory-indirect call's base assigned in the block stays an argument after an earlier read of it. A folded load stays in place when a store before the call may overwrite what it read. A store's source register is no longer recorded as an assignment, which folded the store's statement away.
HTML refs lose interior tabs and newlines before the scheme check, file: is stripped case-insensitively, and a path ending in / resolves to no file in resolve_path or a modulepreload.
A unary plus before X'..' keeps the blob, as SQLite drops the plus. Bare default words take non-ASCII characters and a later dollar sign, as SQLite identifiers do. The comment-after-e fixture uses 0x1e--, which SQLite creates.
Follow-up to #2096 and #2084. A call through a table reached from a register (`mov rdi, obj; call [rdi + 16]`) is usually a method call on that object, with the object as its first argument; since #2096 the pseudo-C showed it with no arguments. The register is passed by name again and its assignment stays visible. A jump to an imported function through its slot (`jmp [slot]`, `ldr pc, …`) is a tail call: it now shows the arguments set up before it and is listed among the function's calls, where it read `return puts();`. And a 32-bit ARM store relative to the program counter keeps its fixed address.
result_lists looked each array name up from the root. It now builds the first match for every name once, in find_result_key's order, and keeps the level-order cap.
Follow-up to #2104. `craft-anything-cli uninstall` named the app whose config blocked it and nothing more; it now prints the reason and what to do. The advice also fits the problem: a folder where the config file should be is called that (Windows reports it as "access denied", which sent people to check permissions), only a real permission error points at permissions, and a config that is badly encoded or malformed is to be backed up and fixed where it is, since moving it aside would also take the other servers it lists out of use. Setup, doctor and uninstall share the wording.
Spaced HTML refs are classified as a browser reads them, only a whole node_modules directory segment marks dependency code, and remote loadURL targets stay URL nodes.
A memory-indirect call's base argument register is passed by name, valid A32 PC-relative stores keep their static address without becoming literal references, and import tail calls through ldr pc or jmp [slot] pass their register arguments and are recorded in Pseudo.calls.