fix: complete 0.3.6 runtime and research reliability - #192
Merged
Advait Paliwal (advaitpaliwal) merged 16 commits intoJul 28, 2026
Conversation
Node's parseArgs throws a bare 'Unknown option' error for any unrecognized flag (e.g. feynman update --extensions), with no pointer to feynman help. Catch ERR_PARSE_ARGS_UNKNOWN_OPTION and append a hint to run feynman help. (cherry picked from commit e50ccad)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
For what is worth, was struggling with alphaxiv login, and simply replaced my local |
This was referenced Jul 26, 2026
Advait Paliwal (advaitpaliwal)
marked this pull request as ready for review
July 28, 2026 12:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/thinking [level]command with supported-level filtering andmaxfetch_contentscratch data into the active project, fix active-org atomicity, package the required source modules, and retain the bundled research package stack0.82.1ModelRuntime, pin the complete runtime graph, repair current Pi/MCP consumer advisories, and verify source plus installed runtime artifactsContributor PR #189 remains included as commit
79aa7b2with its original authorship and cherry-pick provenance.PR #200 independently proposed the same user-facing
/thinkingcapability after this branch's implementation was already prepared. This candidate supersedes it with Pi 0.82.1 model-aware levels, direct arguments, completions, non-UI status, and clamp reporting; no co-author attribution is claimed for the independently prepared implementation.PR #191 and PR #197 remain intentionally excluded because generic extension inventory and hard-coded provider catalog lanes are broader than the owning research-loop defects.
Exact candidate
93779a97d0138851ccd5c514204fafd8a3d70787@companion-ai/feynman@0.3.60.82.154d965608f6b3f7ec228a9aee84edd22b691c790841c5715937787962a70efb3546fc45b7d46cbe1b8898c0a5d2bd3553ba9a7de073adfeedd277094b50d9de6The fresh Daytona tarball from the release-impacting installer head and the final GitHub PR artifact are byte-identical. The final commit changes only the PR verifier, its regression, and the lab notebook; none are shipped in the npm package.
Verification
24.18.0: focused Windows/native/workflow regressions9/9; fullnpm test650/650; typecheck; build; architecture check; website lint/typecheck/build; root and website production audits; package freshness review;git diff --check; dry pack and package budgetb098c3809b9b148a4bea2829c16faa07bf464015on Node24.18.0: full650/650tests, source, website, package, clean-consumer, five production audits, source/installed artifact verification, version/help/package/search flows, and Pi RPC extension loading (112commands, includingweb-results) passed; the sandbox was deleted after receipts were retained25.9.0withPATHempty: installed package artifact verification passed without a hosttarexecutable22.22.0/24.18.0/25, macOS Node24.18.0, Windows Node24.18.0/25, native Windows build, Windows PowerShell 5.1 installer, and PowerShell Core installer all passedTracked issues will be closed with the published
0.3.6install/release receipt rather than at merge time: #182, #185, #186, #187, #188, #190, #193, #196.