Commit Graph
1309 Commits
Author SHA1 Message Date
RRFZ 65fe6484e0 Claim Match HTML script types against complete JavaScript MIME names and the exact module keyword. 2026-11-16 09:00:47 -05:00
Fadlalla-ai d1949b0987 Record the two Ghidra file-setting cases from #1949's review 2026-11-16 17:56:39 +04:00
Fadlalla-ai 5aec366273 Keep a wrapper in Ghidra's folder, and follow a link a start script names 2026-11-16 17:56:39 +04:00
Justin John 997b89ce4c Keep Settings → AI's tool list from showing an older choice (R5.4) (#1950)
Each change to an AI's tool list runs as its own job, and jobs can finish in any order, so two quick changes could leave Settings showing the first while the second was saved. The row now waits for its save, as the request-rate row does. Also escapes the `|` characters that split the STATUS table row.
2026-11-16 20:52:04 +07:00
Fadlalla-ai b4b51bc300 Find the Java that Ghidra's setup brings as the Java runtime, where Vineflower and the listing look 2026-11-16 17:48:58 +04:00
Fadlalla-ai 3fc9dc0695 Claim finding the Java that Ghidra's setup brings as the Java runtime 2026-11-16 17:48:46 +04:00
FredApps 239dc0536a Take target file signatures from the shared craft-sniff table (R3.12) (#1948)
* Take target file signatures from the shared craft-sniff table

* Pin craft-sniff to the craft-libs #1841 merge and record the cutover

The shared table is on main at 070005125f0af1a5ae4a59002270e5849505bfc0.

* Keep named-but-unsupported formats as Unknown

A CPIO file starting 070701 was identified by craft-sniff, then fell
through to the unsigned path and was called text. Identified kinds this
app does not inspect stay Unknown; the unsigned fallback is only for
files with no signature.
2026-11-16 14:40:58 +01:00
BFlat b8d31ff4b4 Merge pull request #1949 from Fadlalla-ai/bugfix/r5.7-ghidra-setting-names-a-file
A Ghidra folder setting that named a file was run as the headless launcher whatever it was. A start script for Ghidra's window (as Linux packages put on PATH) was listed as found, failed as a launcher, and Deep mode quietly used the built-in decompiler. A file is now run only when it is the headless launcher or a script that runs it; a link or start script is followed to its Ghidra folder; any other file isn't listed as Ghidra.
2026-11-16 20:32:08 +07:00
Fadlalla-ai 610fff4896 Follow a Ghidra setting that names a file to its Ghidra folder, and never run anything else as Ghidra 2026-11-16 16:56:00 +04:00
BFlat 6d0fa34750 Merge pull request #1947 from Fadlalla-ai/fix/cargo-target-dir-at-start
Follow-up to #1941. Where a program is about to start or be checked (Play, making a pin, the build's run and screenshot checks), Cargo itself is asked for its target directory, which also covers CARGO_BUILD_TARGET_DIR, the Cargo home's config and a parent workspace's target folder. The Project screen keeps the file lookup, so it starts no process; without Cargo the result is the file lookup. Outside the project only a program the manifests name is taken.
2026-11-16 19:50:55 +07:00
Fadlalla-ai c413f99d87 Claim following a Ghidra setting that names a file to its Ghidra folder 2026-11-16 16:45:56 +04:00
Justin John a897fff072 Choose each AI's builder tool list in Settings → AI and with ai tools (R5.4) (#1946)
An API backend's `tools` setting (auto, lean or full) could only be changed by editing config.toml. Settings → AI now has a "Builder's tools" choice per API backend, with a caption saying what Auto works out to for that AI, and `ai tools <name> [auto|lean|full]` shows or sets it from the CLI. Auto is saved as no setting; agent apps are refused, as they choose their own tools.
2026-11-16 19:41:14 +07:00
BFlat 8d8fbc7daa Merge pull request #1945 from Fadlalla-ai/test/ghidra-setup-linux
Docs only: the guided install was tried on a clean Debian 13 and a Debian 13 desktop, followed by a Deep-mode decompile. macOS stays open, and a new roadmap line records that a Ghidra folder setting naming a file is listed as found while Deep mode quietly uses the built-in engine.
2026-11-16 19:29:37 +07:00
Justin John 5538adbc58 Tell a builder why a build refused a tool that needs consent, instead of "the user said no" (R5.5) (#1944)
A build on an API model refuses every tool that needs consent outside the Build tools without asking anyone, and the model was told "The user said no", so it made up a reason (#1938). The model is now told that nobody was asked and that a plugin's `consent` setting decides; the journal records the case as `refused`. Whether such a build should ask the person is left as a decision line in the roadmap.
2026-11-16 19:29:30 +07:00
Fadlalla-ai 131b1ef49d Keep old pins on their own copy, and a linked project's build inside it
A pin from before programs were recorded starts what its copy holds again (file
lookup), not where Cargo builds the project now. Cargo prints real paths, so its
target folder for a project opened through a link is put back under the path
the project was given as, and a pin doesn't take the project's own build for an
outside one.
2026-11-16 16:28:57 +04:00
Fadlalla-ai 7037414257 Ask Cargo where a Rust build went when its program starts
The file lookup from #1941 stays for frequent reads (the Project screen). Where a
program is about to start or be checked (Play, pins, the build's run and
screenshot checks), launch_now also runs cargo metadata from the project and
looks in its target_directory first, which covers what the files don't:
$CARGO_HOME/config.toml, CARGO_BUILD_TARGET_DIR and a parent workspace's
target/. Outside the project, only a program the manifests name is taken.
2026-11-16 16:21:23 +04:00
Fadlalla-ai b09e136435 Claim asking Cargo for its target directory where a program starts 2026-11-16 16:17:31 +04:00
BFlat 7b113213da Merge pull request #1941 from AlexJoaquimPereira/bugfix/r5.7-cargo-target-dir
Play, pins and the build checks looked only in app/target, so a project whose Cargo settings move the output (CARGO_TARGET_DIR, or build.target-dir in a .cargo config in the project or above it) built but could not be started. The lookup now reads those settings without starting a program. A target directory outside the app supplies only a program the manifests name, and a pin copies such a program into its own folder.
2026-11-16 19:15:30 +07:00
Fadlalla-ai 3a59e1c1f7 Record Ghidra setup tried on Linux, and a Ghidra setting that names a file
The guided install (Ghidra 12.1.4 and its Java, through engines_install) on a
clean Debian 13 and a Debian 13 desktop, then a Deep-mode decompile from Ghidra.
Ghidra laid out as Arch-based packages install it is found (#85). New open line:
a Ghidra folder setting naming the /usr/bin/ghidra start script is listed as
found, but Deep mode quietly uses the built-in lifter.
2026-11-16 15:58:51 +04:00
AlexJoaquimPereira 2ce8d31311 Record the R5.7 review fixes and the Cargo-answer follow-up
Name the final commits, the named-only rule for target directories outside the app, the pin copy, and the follow-up PR #1942's author offered.
2026-11-16 17:24:38 +05:30
AlexJoaquimPereira 216295fdcd Keep shared target programs out of unnamed projects, and copy pins (R5.7)
A shared or ancestor target directory outside app now supplies only a program the manifests name. Without a name, only target directories inside app are searched, so another project's executable isn't started. built_program_in(app, env) makes the tests independent of the process's CARGO_TARGET_DIR.

The ancestor walk starts from a normalized absolute app, so a relative app reaches a config above the working directory; normalized paths also keep .. out of selected programs. Cargo's legacy config wins over config.toml when it exists, and a config without the key or with invalid TOML doesn't fall through.

A pin copies a program built outside app into pin-program/ and records that relative path; other executables in a shared folder are not copied, and the frozen pin keeps working when the external build is removed.
2026-11-16 17:24:07 +05:30
AlexJoaquimPereira c77ab58fe5 Tick the R5.7 Cargo target-directory line
Record commit efff13a2 and the remaining global CARGO_HOME and parent-workspace cases.
2026-11-16 17:24:07 +05:30
AlexJoaquimPereira 842f011ae0 Find a Rust build's program under Cargo's target directory (R5.7)
A project whose Cargo settings move the build output (build.target-dir in .cargo/config.toml, or CARGO_TARGET_DIR) built, but Play and the screenshot/self-test checks only looked in app/target, so they could not start the program. built_program now looks under CARGO_TARGET_DIR, then the closest project or ancestor .cargo setting, then the default target/ as a fallback, and starts the first target directory that has the named program.

The new AI regression uses a project with target-dir = "out" and fails before the fix; engine tests cover the environment path (relative and absolute), a project setting, an ancestor setting, the environment coming first, and the default fallback.
2026-11-16 17:24:06 +05:30
AlexJoaquimPereira 9aadbde82d Claim R5.7: find a Rust build's program under Cargo's target directory 2026-11-16 17:24:06 +05:30
Fadlalla-ai 20647658fa Claim trying Ghidra setup for real on Linux 2026-11-16 15:47:02 +04:00
BFlat 8dec78492d Merge pull request #367 from oliver-mee/bugfix/policy-gates
The process and UI source-policy gates stopped at a file's first test attribute, so production code below an interleaved test module escaped them. They now read Rust paths through the whole file, follow import aliases, ignore comments and string examples, and exempt only items that can't exist outside tests. The lock gate uses the same scope, and module files named by a path attribute are checked wherever they live.
2026-11-16 18:04:55 +07:00
BFlat 3ef118107e Merge pull request #1940 from scks1/bugfix/r5.5-api-failure-log-service-text
A failed API-backend turn wrote the error's message to its log, and that message repeats what the service, or a proxy in front of it, answered, which can include the key or words from the request. The log now keeps our own code for the error, the HTTP status, the context window and request size, and the service's error code only when it is one of a known list. The error shown in the app and the CLI still has the service's message.
2026-11-16 17:59:57 +07:00
Oliver Mee 41397fa761 Include explicitly referenced production module files in policy checks 2026-11-16 18:44:09 +08:00
Oliver Mee 59941e75af Check hidden source and report unscannable directory links 2026-11-16 18:44:09 +08:00
Oliver Mee 40442a78d5 Limit policy exclusions to manifest crate boundaries 2026-11-16 18:44:09 +08:00
Oliver Mee 518b8be76b Keep production source directories in policy checks 2026-11-16 18:44:09 +08:00
Oliver Mee 3df6b38e40 Check complete Rust items in source policy gates (R0.5) 2026-11-16 18:44:09 +08:00
BFlat 7aebf09ae3 Merge pull request #1937 from Fadlalla-ai/test/r5.7-linux-window-and-rebuild
On a clean Ubuntu 24.04 under X11 the app stopped before its window because the package list left out the X11 half of xkbcommon. The package line in the README and its translations now includes libxkbcommon-x11-0. STATUS records the window opening on a clean container and the README's snake-game rebuild reaching Ready with Claude Code. A new roadmap line notes that the first build check didn't find the program when Cargo's target directory pointed elsewhere.
2026-11-16 17:38:43 +07:00
Simon Koch-Sultan 352848bfb6 Leave the service's words out of an API backend's failure log (R5.5)
write_failure_log wrote the error's message, which repeats what the
service or a proxy in front of it answered (up to 1,000 characters of an
HTTP error, all of a stream's error message), so a key or words from the
request repeated there were kept in logs/. The log now keeps Craft
Anything's code for the error, the HTTP status, the context window and
request size, and the service's error code only when it is one of
failure::KNOWN_PROVIDER_ERRORS, written from that list.
2026-11-16 05:26:42 -05:00
Simon Koch-Sultan 777ef76170 Claim leaving the service's words out of an API failure log (R5.5) 2026-11-16 05:23:08 -05:00
Fadlalla-ai 752ccd5e6f Keep the rest of the Linux quick start open on the roadmap (R5.7)
The ticked line covered only what ran: the window on a clean Ubuntu 24.04 and
the snake rebuild on a desktop. The website rebuild examples, a rebuild on a
clean machine, a real screen and Wayland get their own open line.
2026-11-16 14:16:21 +04:00
Fadlalla-ai 946f2522db Add libxkbcommon-x11-0 to the Linux quick start and record the window and rebuild checked (R5.7)
On a clean Ubuntu 24.04 under X11 the app stopped before its window:
"Library libxkbcommon-x11.so could not be loaded". With libxkbcommon-x11-0
installed it opened on its welcome screen. The README's snake-game rebuild
reached Ready with Claude Code. Also notes, as an open line, that the first
build check didn't find the program when Cargo's target-dir pointed elsewhere.
2026-11-16 14:01:18 +04:00
Fadlalla-ai a00aedbff1 Claim the rest of the Linux quick start live check (R5.7) 2026-11-16 13:53:30 +04:00
BFlat 090188d705 Merge pull request #1936 from Fadlalla-ai/test/r5.7-linux-quick-start
On a clean Debian or Ubuntu system the README's package list left out a C compiler, so the first build stopped with "linker cc not found". The package line in the README and its translations now starts with build-essential. STATUS records the install steps followed as written on clean Ubuntu 24.04 and Debian 13 containers; the window on a clean machine with a screen and the README's rebuild commands stay open in the roadmap.
2026-11-16 16:15:08 +07:00
Fadlalla-ai 11607a91b2 Keep the window and rebuild steps of the Linux quick start open, and say what wasn't run (R5.7) 2026-11-16 12:49:20 +04:00
Fadlalla-ai efe7d74f11 Add build-essential to the Linux quick start and record it checked on clean Ubuntu and Debian (R5.7) 2026-11-16 12:39:42 +04:00
Fadlalla-ai af627b5419 Claim the Linux quick start live check in the roadmap (R5.7) 2026-11-16 12:24:44 +04:00
Trần Quang Đãng 9460af211f Let Claude Code use the model its own settings name by default (#921)
* Let Claude Code use the model its own settings name by default

Claude Code runs are no longer passed a hardcoded --model: with no choice
saved, the agent uses whatever its own settings name (a custom model, an
alias, opusplan…), and `ai model --default` clears a saved override back
to that. The Settings → AI picker lists "Default (its own settings)" first
for Claude Code (saved as `claude-code` or `claude`), choosing it clears
the saved model, and the typed "Another model" field is gone since the
list carries the choice. effort_levels detects Claude Code by adapter id
so the `claude` agent id gets every effort level too.

* Translate "Default (its own settings)" in the remaining eight catalogs

The i18n gate requires every catalog to carry the same key set; the
first commit only added the new picker label to six of them.
2026-11-16 08:59:20 +01:00
BFlat 21ffa656ca Merge pull request #1914 from Plastic-time/bugfix/r3.12-js-line-index-1115
Line numbers in JavaScript facts counted only LF, so anything after a bare CR, U+2028 or U+2029 was reported on the previous line. The line index now counts every ECMAScript line terminator, and CRLF once.
2026-11-16 14:12:01 +07:00
RRFZ 7a452424e9 Merge main into bugfix/r3.12-js-line-index-1115 2026-11-16 01:48:57 -05:00
Justin John 5a3fba9286 Keep the plan-limit advice on the turn's closing error (R5.3) (#1933)
A turn refused by a used-up Claude plan limit ends with a closing result error, which is the one the run keeps, and it carried the generic advice, so "which limit, and when it resets" was lost. The closing error now carries the same plan-limit advice as the error before it. Follow-up to #1931.
2026-11-16 13:46:01 +07:00
Justin John 15972b4fbb Stop the build at a used-up Claude Code plan limit instead of retrying it (R5.3) (#1931)
When a Claude plan's 5-hour or weekly limit was used up, Claude Code's rate_limit error was read as a per-minute rate limit, so the build waited and tried again and failed the same way each time. Claude Code's stream reports each turn's plan limits; when that report says the turn was rejected, the failure is now a usage limit, which isn't retried, and the fix names which limit is used up and roughly when it resets. A rate limit on a turn the plan allowed is still waited for and retried. Fixes #1919.
2026-11-16 13:24:16 +07:00
FredApps 51b000e23a Merge pull request #1922 from storytold/refactor/shared-xml-plist
Use the shared XML property-list reader
2026-11-16 06:42:58 +01:00
Justin John d2d52137ea Use the Windows manual proxy for engine downloads when no proxy variable is set (R2.9) (#1930)
Engine downloads (Ghidra and its JDK, Godot, pinned installs) used only the proxy environment variables, so behind a VPN that sets only the Windows system proxy they went direct and timed out. When no proxy variable is set, they now use the person's manual proxy from Windows' settings, read from the registry once per download; this computer and Windows' own exceptions go direct, and a NO_PROXY the person set replaces those exceptions. Settings with credentials, SOCKS only or no port are ignored. AI clients are unchanged. Not run behind a real system proxy. Fixes #1827, #1787.
2026-11-16 12:37:41 +07:00
BFlat 0e32cd474c Merge pull request #1812 from htcom-code/bugfix/r3.13-body-outline-cap
A walkthrough asked to keep response bodies keeps them for the first 200 requests and said nothing about the rest, so a request without a body read as a response that had none. The result now counts how many requests kept a body, were past the cap, came after the deadline or couldn't be read, and the evidence carries a limitation when some were left out.
2026-11-16 08:29:11 +07:00