A readable sqlite_schema row could still hold a partial value (an overflow chain that ends
early, loops or leaves the file, or text cut at a schema budget), so a table's column list could
be short while the schema was reported complete. Such records now set schema_truncated and add
a counted integrity note; the object's readable name and metadata are kept.
A squashfs 2.x or 3.x superblock was taken as a filesystem on its magic, version and bytes used
alone. The firmware scan now also requires its block size to match its block_log, from 4 KiB to
1 MiB, as version 4's already must. A superblock cut before those fields is no longer reported.
A note added while an API-backend builder worked waited for its whole turn to end, which can be
hundreds of steps. After each tool step the loop now claims the waiting notes and adds them
after that step's results, in the wording the coding-agent hook uses. Claimed notes are marked
read, so the build shows them in the feed and doesn't send them again after the turn.
An API backend with requests_per_minute set held each request back without a word, so a paced
build looked stuck. A wait of two seconds or more now puts a line in the feed saying how long
it waits and why (#668).
The schema listing dropped its b-tree walk's incomplete flag and notes, so a schema with an
unreadable child page or row was listed as the whole schema, with complete coverage. The
overview now marks such a schema truncated and carries the walk's first notes, and
db_sqlite_show adds a schema_incomplete limitation, partial coverage, and an unknown-table
error that says only the listed part was searched.
The walk listed a folder's files before opening any of its subfolders, so when the file limit stopped it, a file inside an earlier folder was dropped for later ones and the inventory's sort couldn't bring it back. It now opens a subfolder where its name sorts in its parent, and results are sorted folder by folder (`path_order`), so a limit cuts the tree where a listing of it would end. Only the listings of the folders on the current path are held, within the same entry limit. When the entry limit runs out early, fewer entries are reported than before: the honest prefix.
The scan read every squashfs region's block size at offset 12, where only version 4 keeps it;
in 2.x and 3.x that is the uid table's start, and the block size is at offset 51. Older images
now report the block size they declare, and their description no longer names a compression
read from a field those versions don't have.
The build steps filled {editor}, {player} and {ext} with chained replace calls, so an editor
installed under a folder named like a later placeholder reached the builder with a different
path. The one-pass fill moves to platform::text::fill, which both the build steps and i18n::trf
use.
Answers to questions now carry the replaced and replacing AI names as an optional
builder_replacement field (saved, used). The desktop fills them into the same catalog entry
Make and build starts use, so the notice after Just ask follows the UI language. The English
builder_notice is unchanged for CLI and MCP callers.
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.
The check compared .cs files against the sizes its folder walk recorded, then read each one
whole, so a file that grew in between could be read past the 64 MiB source budget. Each read is
now capped at what is left of the budget. When no file could be read, the error keeps the first
read errors and says when the folder walk was cut short.
The notice shown on Make and at build starts when a project's saved AI is off or gone now comes
from the UI catalogs. Turkish has a reviewed translation; the other languages keep the English
wording until a native speaker reviews theirs. Builder names are filled in literally, and the
CLI, MCP and headless notice are unchanged.
The check reports partial coverage, with no total, when a .cs file under the source folder may
have been left unread: the file or size budget stopped the reading, a listed file could not be
read, or the folder walk was cut short. Before, members declared only in an unread file read as
missing in a check marked complete.
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.