#1001 brought back the old open copy of the packaged Deep-build checklist line next to the ticked one and cut the ticked one off after "from the"; the cut-off line is removed and the full line ticked again, since docs/releasing.md has the check. The open line about the macOS remote-query test is removed too: its fix (#949) is already ticked.
The source-map parser read the whole JSON into a value and then copied every sources, sourcesContent and names entry, so a 64 MiB map of empty strings built about 21 million strings twice before anything was checked. It now reads only the fields it uses, straight from the JSON, and counts every sources, sourcesContent, names and ignore-list entry against one limit (2,000,000 by default) shared across sections; a map with more is refused with TooManyEntries as soon as the limit is passed, without reading the rest.
A project placed by a relative path gave engines and programs relative paths, but the child already runs inside app/, so Unity's -projectPath, Godot's --path, Unreal's -project and -archivedirectory, option runs (--screenshot, --self-test), console run checks and Play pointed inside app/ a second time. They now resolve the project path first; a program named by a bare PATH command is left as it is.
The source-map parser bounds the inventory it builds, but source recovery's manifest repeated every expanded source path in its outputs, so a long shared sourceRoot could still retain tens of megabytes of paths. Recovery now charges each original's source path and output path to the inventory's entry and byte budget, shared across inputs; once it's reached, further originals are left out, and the manifest, result, summary, a limitation and partial coverage say so. A pitfalls entry records the rule.
Craft Anything runs OpenCode 2 (opencode run --standalone). OpenCode 1.x has no --standalone, so the flag check saw it was missing, said "trying it anyway", and the build sat on OpenCode's usage text (#1111, #1693). When OpenCode's help was read and lacks the flags, the turn now stops at once saying the opencode found looks like 1.x, with how to install OpenCode 2 or choose it in Settings -> AI. A help that couldn't be read still lets the run go on, and a refused program is checked again next turn, so an updated OpenCode is seen. Other agents keep "trying it anyway".
oid_text, which names certificate fields and policies in decoded code requirements, showed malformed OID content as a different, valid-looking OID: an unterminated last subidentifier was dropped, a subidentifier padded with a leading 0x80 octet was accepted, empty content was an empty string, and more than 64 arcs were cut short. These now read "invalid", and a first subidentifier longer than eight octets is split into its two arcs like a short one.
Four open lines in the roadmap repeated a nearby line that is already ticked (the folder a build command ran in, what usage.json left out of a local build, a flaky helper test, and OpenCode's MCP server over SSH), so cargo xtask pending listed work the code already does. They are removed; each outcome stays in its ticked line.
What a builder gets from each coding agent (our tool server, our approval policy, resume, notes during a turn, a message longer than the command line) was spread over each adapter's arguments, environment and ACP session. cli_agents::grants now states it per adapter, takes resume and long messages from the adapter itself, and tests hold every row to what the adapter actually hands a builder; an adapter without a row fails them, and unchecked cells say NotYet with the gap in words.
When a source map's inventory was cut by its limits, the source-to-bundle comparison searched only the retained names and reported an omitted source as confirmed unmatched. Sources with no observed match now go in a separate uncertain_sources list with the reason source_map_inventory_truncated, the result says the inventory was truncated, and the evidence carries a limitation and partial coverage; positive matches are unchanged.
Distinct source identities such as src//main.js and src/main.js normalize to the same recovery path, so recovery kept the first and dropped the rest; a file and a folder of the same name, and separate inputs with the same name, lost sources the same way. Ordinary paths are unchanged; a source whose path would collide now goes to its own sources-collisions/<input>/<source>/ folder, and the manifest records each one's input and source-map index. A pitfalls entry records the rule.
A small source map could expand to gigabytes when its sourceRoot was copied into every source name, and the full list was built before the application analyzer kept 5,000 of them. Source lists are now built within an entry and byte budget shared across sections and an application's maps, checking each expanded path's length before allocating it; when only a prefix fits, the result says it was truncated and the analysis notes it as a limitation. A pitfalls entry records the rule.
Word likeness ignores one-character words, so an output made only of numbers had no words on either side and bare 4.5 against 9.0 passed as identical. When both outputs are only numbers and there is no second observation of the original, the check now compares the numbers in order and says which differ; output with words beside its numbers is compared as before.
When a program printed more than its output cap, its error said "what it printed last" from the first bytes kept and never said the rest was dropped. The process runner now also keeps the last 16 KiB of a stream once it passes its cap; failure messages, ssh diagnosis and build checks quote that end and say the output was cut, while tools that parse output still get its start.
After #1682, a run on a reattached project still used the builder picked on Make instead of the project's own, replaced the live conversation of a project already building, and cleared the Make draft even when the run didn't start. It now uses the saved builder (asking for one if it's gone), shows the running build's conversation and says it's already building, and clears the draft only once the request is running or queued. The run remains the only writer of the project's feed.
Since #987, picking a folder that already holds a project attaches to it, but the create path then overwrote its saved builder, asset budget, generated-assets choice and stack, replaced its conversation, and dropped the typed request. An attached project now keeps everything the person set and its saved conversation, and the request is added as its follow-up, in the app and the CLI; the CLI refuses --build-with, --generate-assets and --existing for such a folder with a fix to use instead.
The console run check compared words after dropping one-character tokens, so bare results like 4.5 and 9.0 looked empty and 12 matched -12. Study now runs the original twice per input; the check requires the numbers that were the same in both runs to match in order (keeping signs, decimals, exponents, radix and large integers), ignores numbers that varied between them, such as timings and PIDs, and says so in its note. Without a second observation it compares words only. Program names are replaced only as whole words, so they can't eat into numbers.
The roadmap asked for #1030's parent/descendant and startup-timeout cleanup tests to be run on Windows. They passed five runs in a row on Windows 11, and no processes they started were left running afterwards; the line is ticked with what was checked.
Source lookups and recovered source lists dropped sourceRoot when a source started with / or contained ://, giving the wrong original source. A non-empty root is now prefixed to every source before it is read as a URL, as ECMA-426 describes; an empty root still means no root, since generators commonly write "" for that.
Files reaching the third level of classic block pointers (above about 64 MiB with 1 KiB blocks) were left unrecovered. The reader now follows the triple-indirect pointer, keeps the full logical span of sparse subtrees at every level, and still refuses files whose mapping blocks are unavailable.
Method fingerprints wrote float constants as JSON numbers, which can't hold NaN or infinity, so methods differing only in such constants got the same fingerprint. Nonfinite constants are now written as their IEEE-754 bits, and single-precision NaNs keep their original operand bits, which widening to double could change.
SquashFS reads one XZ stream per block, but the block decoder refused a complete first stream whenever bytes followed its footer, so the file's data was lost. It now checks the stream the decoder consumed as a complete XZ stream on its own and returns it, ignoring what follows, and still never returns output from a stream that failed to decode.
The sBPF inspector capped symbols and relocations at 400,000 records, but reaching the cap only ended the current table, so each further SYMTAB/DYNSYM or REL/RELA table could add another record past it. It now stops visiting further tables of that kind once the cap is reached, keeping the earlier records and their order.
A cramfs file whose block-pointer table lay outside the available filesystem bytes was left without contents, but nothing said so, and the image still counted as completely recovered. Such a file now gives a warning and marks the image incomplete, keeping the file listed.
Big-endian JFFS2 images were detected and then refused. The reader now takes the byte order from the first node's magic, after any erased space, and reads node, inode and directory integers in it, so the same tree and contents come out in either order; a node in the other byte order stops the scan with a warning.
newarray accepted any element-type byte and multianewarray accepted zero dimensions, both of which the JVM refuses. The decoder now stops at a newarray whose type isn't one of the eight primitive array types or a multianewarray with zero dimensions, as for other invalid instructions.
Any object that was the string "$null" was read as the archive's nil marker, so a real string with that text disappeared. Only the archive's first object, where the marker lives, is now read as nil; a "$null" string anywhere else stays a string.
DNS labels showed dots, backslashes and unprintable bytes as they came, so different wire names could look the same; they're now escaped (\. \\ \DDD). HTTP is reported only for a complete start line: a request with a known method, a target without control characters and an HTTP/1.x version, or a response with an HTTP/1.x version, a three-digit status and an optional reason phrase. The packet tools' warning about unreadable parts now says what may be missing.
In a ZIP64 archive with data in front of it, the locator's stored offset can miss the end record, and the classic fallback then counted the ZIP64 record and locator as prefix bytes and lost the central directory. Before falling back, the reader now looks for the record within 64 KiB before the locator, and takes it only when it is single-volume, agrees with the classic record and has a central directory right before it; a warning says it was recovered.
Small ext4 inline files had their contents read as block addresses, so they failed to recover or came out as zeros, and a filesystem with only the inline-data feature was labelled ext2. Regular inline files of up to 60 bytes are now read from the inode, within the usual byte budget; longer inline files and inline directories are still reported as not recovered.
After a bad extent header or an unreadable child block, the extent walker returned a partly filled map, and recovery showed the missing ranges as zeros. Extent nodes now have to be complete and consistent (magic, entry counts, child depths, non-empty extents), within a shared work budget, or the file is left unrecovered with a warning.
LZ4 SquashFS images were refused although the project has a bounded raw LZ4 decoder. SquashFS metadata, data blocks and tail fragments now decode with it, treating the size as an upper limit, while Unity bundles keep requiring the exact decoded size.
Data blocks were concatenated whatever their length and the result trimmed at the end, so a short or corrupt first block could shift the bytes after it while the file looked complete. Each raw or decoded block, sparse blocks and the last partial block included, must now cover exactly its part of the file, or the file is left unrecovered with a warning.
The application graph is built from the assembly's inventory, members and native boundaries but only passed on the members' warnings, so a warning only the inventory or the native mappings raised (such as trailing bytes in an attribute's signature) disappeared from it. The graph now combines all three, keeps each view's first warning in view, and removes repeats before its 20-warning limit.
Directory and file pointers in a version-two cramfs image could reach bytes appended after the filesystem, so unrelated trailing data could fill in recovered contents. The size recorded in a version-two header now bounds every read, in either byte order; an image shorter than that size is read as far as it goes and marked incomplete, and version-one images are read as before.
Any ext inode that wasn't a directory or symlink was read as a regular file, so device, socket and FIFO fields could be taken as block pointers. The inode's mode now decides its kind: special and unknown inodes are listed as other entries without reading their fields as data, and a directory entry's type hint can't override the inode.
The certificate reader took any [0] field inside SignedData, kept non-X.509 certificate choices, and applied the certificate limit per field. It now reads the certificates field only in its declared place after the version, digest algorithms and content, returns only X.509 (SEQUENCE) choices, and applies the limit once.
#1644 sent an earlier run's waiting notes as the new run's message and deleted their files, so a run that stopped during setup lost them, and a note file that couldn't be read was dropped silently. Such notes now become the new run's own waiting notes, kept on disk until the builder takes them or handed to the next run like any note; a notes folder that can't be read is moved aside instead of deleted.
The ZIP64 end record's declared size wasn't checked. A record smaller than its fixed fields, an extent that overflows, or fixed fields that run into the locator now make the archive corrupt; a declared extent that doesn't end at the locator, or a locator that doesn't point to a record (as in archives with a stub in front), keeps reading the directory with a warning, as before.
The XML plist reader already decodes UTF-16 after either byte-order mark, but the check that decides a file is a plist only looked for ASCII <plist, so UTF-16 NIB archives were turned away first. The check now also finds the UTF-16LE and UTF-16BE marker after its byte-order mark, on code-unit boundaries, within the same 1 KiB probe.
A type chunk whose entry data started inside its offset table or past the chunk was still read, and a bag entry with a short header, or more values than fit in the chunk, read past its data. The type is now skipped with a warning in the first case; in the second the entry is kept without its parent and values, the table is marked truncated, and a warning says why. A bag with more values than the reader keeps is marked truncated too.
Binary plist dates and keyed-archive NSDate values were shown floored to whole seconds, so events within one second looked the same. They now keep their fraction, rounded to microseconds (finer would only show the float's noise for present-day dates), with a rounded-up second carried into the date; whole seconds still show without a fraction.
A data node that failed to inflate, used an unsupported compression or decoded to a length other than its declared size was skipped, leaving zeros or older bytes in the file while it looked recovered, and an overlong raw node could overwrite the next extent. Such nodes now mark their extent damaged; a newer valid node can still replace it, and a file is left unrecovered only if a damaged extent survives into its final contents.
The DER reader accepted redundant length encodings (a long form under 128, or a leading zero length byte) without saying so. Each element now records whether its length is minimal; certificate, CMS, Authenticode and certificate-chain views keep everything they read and add one note that an element is not strict DER, and signatures over those bytes are checked as before.
Lossy decoding turned different malformed name values into the same replacement characters, and UniversalString values weren't decoded. Name values are now decoded by their string type (UTF-8; Printable, IA5, Visible and Numeric as ASCII; T61 as Latin-1; BMP and UniversalString as UTF-16 and UTF-32), and a value that is malformed or of another type is shown as its hex DER encoding.
Signature readers returned the decoded signature and silently accepted bytes after it. Complete method, field, local, TypeSpec and instantiation signatures now note when their blob carries extra bytes: the decoded types are kept, as the runtime uses them, and the inventory, member and native-boundary views say once that some signatures have trailing data that wasn't interpreted.
Godot reads --path as UTF-8, and the path was passed through a lossy conversion, so a project folder whose name isn't valid UTF-8 could open a different project with a similar name. Such a project now isn't launched instead.
Resource configurations that differed only in grammatical gender, round screens, wide colour gamut, HDR, or keyboard and navigation visibility got the same qualifier string, and MNC 00 was shown as 65535. Those qualifiers are now named as Android names them.
The contract dispatcher patterns accepted instructions a few positions apart, so unrelated code could be read as selector extraction, a Vyper selector comparison or a short-calldata check. Each pattern now needs its exact instruction sequence and operands, and a dispatch to something that isn't a JUMPDEST reports its mutability as unknown.
ZIP entries made on macOS (host 19) now keep their Unix mode, so their directories and symlinks are recognised, and VFAT entries (host 14) are recognised as directories by their DOS attribute, as MS-DOS and NTFS entries already were.