You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
0.4.0 - 2026-11-16
Changes
PHP 8 and Laravel: a php adapter for .php and .blade.php files with
Composer PSR-4 classes, Blade, Livewire, Eloquent, events and jobs.
The graph follows the code without wingbox build. In Claude Code a new
PostToolUse hook on Edit and Write, wingbox hook dirty, marks the edited
file in .wingbox/graph-state.json and returns; it never builds. Before the
graph is read (the search hook, every MCP tool, the query commands) the
files changed since the last build are brought in: the marked ones and
those an editor, git or a shell command changed, found by comparing size and
modification time with the snapshot the build wrote. Several edits are
brought in by one refresh; an unchanged project costs one stat per source.
A refresh patches the graph instead of building it: only the changed files
are parsed again, and only the modules that read them, that resolved a name
a created or deleted file could now answer, or that looked up a name the
change added or removed are resolved again. The result is the graph a build
publishes, byte for byte. A changed resolution config (package.json,
tsconfig, pyproject.toml, .gitignore, ...), a language other than Python and
TypeScript, or a change that reaches more than a quarter of the modules
takes the incremental build instead.
The search hook waits up to WINGBOX_HOOK_WAIT seconds (3) for a refresh;
a longer one goes on in the background and publishes later. Meanwhile, after
a failed refresh, or with WINGBOX_AUTO_REFRESH=0, the hook gives no context
from the old graph but (wingbox-graph-stale :reason ...), the MCP tools
start their answer with that line and the query commands warn on stderr. A
failed refresh is not repeated until something changes again.
Builds resolve the modules in parallel (forked processes, same graph): on
fastapi an incremental build after one edit takes 4.4 s instead of 11.2 s
and a cold build 7.0 s instead of 24.1 s. The TypeScript config files are
found in one walk of the tree instead of three.
wingbox install adds the edit hook next to the search hook (timeout 10 s
for the search hook, which may wait for a refresh), without duplicates on
reinstall; wingbox uninstall removes both; the Claude Code plugin carries
both.
The first wingbox usages after a build in which a few files changed reads
and resolves only those files: .code_graph.uses-cache.json keeps the use
walk of each file by content hash and, while no definition, import or file
was added or removed, its resolved uses. A later usages or entity reads
from the graph only the facts that name the symbol asked, and every query
stops reading the path section of the graph once it has it.
Fixes
.wingbox/ and wingbox-out/ are no longer walked by the build: a file
Wingbox wrote there that the repository ignores (a *.log) changed the
cache fingerprint and made the next build parse every file again.