Repository navigation
Foundry 0.2.0
Foundry 0.2.0
简体中文
Foundry 0.2.0 在 Go 工作流上加入 JavaScript、TypeScript 和 Python：从已提交的单包仓库生成计划、修改独立候选、在内置 VM 中测试和修复，再导出 patch 与报告。模型上下文、计划执行、测试和交付继续独立审批，原仓库不会被自动修改。
下载
| 平台 | 安装包 | 运行要求 |
|---|---|---|
| Apple Silicon Mac | DMG | 硬件虚拟化；无需 Docker 或宿主机语言工具链 |
| Windows x64 | EXE | 已启用硬件虚拟化及 Windows Hypervisor Platform |
SHA256SUMS · 安装与输入约定 · 验收回执
Mac 为 ad-hoc 完整性签名，未作 Developer ID 签名或公证；Windows 安装包未签名。SHA-256 只校验文件完整性，不证明发布者身份。保留系统安全检查，不要求关闭 Gatekeeper、SmartScreen 或杀毒软件。
支持范围
- Go 1.27.3 标准库项目；Node 24.22.1 的
node:test；TypeScript 5.9.3 类型检查后运行node:test；Python 3.13.5 的unittest。 - JS/TS 依赖限于预先准备的纯 JS npm lock v3 目录；Python 限于精确锁定的纯 wheel。导入依赖另行同意，测试、配置、锁文件和依赖受保护。VM 无网络，不运行安装脚本。
- API Key / 兼容 Responses 为主要接入方式。任务固定账户、地址、模型与次数上限，不自动重试或切换收费 API。ChatGPT 订阅登录仍属实验性功能。
- 交付为本地 patch 和报告；不自动 apply、提交、推送、部署。原生扩展、monorepo、任意命令及其他测试框架不在本版范围。
证据与版本对应
源码提交：e53ece42ff9f26e99a7d39a62b0fab4b790dc30a。
- Mac 原生 Go v1 与 12 项 v2 验收已完成：Node/TS/Python 的基线、明确注入失败、修复复验在真实 VM 运行；角色回复使用协议 fixture。边界测试分别验证类型检查、初始化/发现、资源、超时、信号和后代进程/输出流处理；不能把预期阻断写成业务测试通过。
- 单独的 Mac TypeScript 真实 API 验收完成 6 次角色调用：Researcher、Planner、Worker、Debugger、QA、Auditor 各一次。通过用户选择的本地 Responses 网关请求
grok-4.6，上游模型身份未独立验证。使用真实类型依赖与 4 项测试，明确注入的首候选错误被检出，Debugger 修复后封存补丁和报告。记录 19,791 输入、13,390 输出 token；这不是金额上限或自然模型出错的证明。 - 最终提交的 Mac DMG 已重新完成真实 Go v1 与全部 12 项 v2 VM 验收、安装与完整性检查、原生窗口及重启记录保留验收。Alpha.3 和 v0.1.0 的升级、重启、恢复、回滚与卸载保留测试均重新完成。封存的运行时及完整源码输入仍归属组件提交
6e60138；上述真实供应商调用也在该组件完成，未在最终宿主程序重复调用。 - Windows 在同一提交的原生托管 CI 中通过安装、实际窗口绘制与可访问性检查、重启、双版本升级、卸载保留数据以及 13 项 WHPX 验收。模型使用 fixture，未宣称 Windows 真实供应商调用，也未宣称人工交互或断电测试认证。
更新不重置任务预算或改写历史证据；旧任务依赖精确保留的运行时。升级前备份数据，缺失/损坏的旧运行时会阻断。v0.1.0 下载及其原始验收仍保留。
English
Foundry 0.2.0 adds bounded single-package JavaScript, TypeScript and Python delivery to its Go workbench. Research and planning lead to isolated candidate changes, real guest tests, confirmed-failure repair, and a local patch/report. Context sharing, execution, tests and delivery retain separate approvals. The source repository is never automatically modified.
Use the Mac DMG or Windows x64 EXE above and verify SHA256SUMS. Mac packages use ad-hoc integrity signing without Developer ID/notarization; Windows packages are unsigned. Do not disable OS security controls. Windows requires enabled hardware virtualization and Windows Hypervisor Platform; neither platform falls back to host execution.
Supported contracts are standard-library Go, Node node:test, TypeScript typecheck plus node:test, and Python unittest. Import already prepared pure-JS npm lock-v3 trees or exact locked pure wheels with separate consent. Tests, configuration, locks and dependencies remain protected. Guests have no network and run no package-install scripts. Native extensions, monorepos and other frameworks are outside this release.
API Key / explicitly selected compatible Responses endpoints are the primary model route. No automatic model retry or paid-API fallback occurs. Subscription login remains experimental. Delivery stops at a reviewed patch and report; automatic apply, Git writes and deployment are not included.
Evidence distinguishes actual tests from model fixtures. Mac Go v1 and all 12 v2 native checks completed, including three real baseline/fault/repair workflows and expected boundary rejection cases. A separate Mac TypeScript run made six successful real gateway calls, one per role, requesting grok-4.6; upstream identity was not independently verified. Its four tests detected an intentionally injected first-candidate fault, followed by real Debugger repair and sealed delivery. Recorded usage was 19,791 input and 13,390 output tokens, not a monetary cap.
The final Mac package at e53ece42ff9f26e99a7d39a62b0fab4b790dc30a passed fresh Go v1 and all 12 v2 native VM checks, physical installation and integrity checks, actual native-window inspection, restart retention, and both Alpha.3 and stable-0.1.0 upgrade/recovery/rollback/data-preserving uninstall paths. Sealed runtime/full-source inputs and the separate real-provider run retain component attribution to 6e60138; real-provider calls were not repeated on the final host. Windows native CI passed for this exact source, including installation, OS window paint/accessibility checks, restart, both upgrades, data-preserving uninstall and 13 WHPX cases. Model replies are fixtures; these checks do not establish real-provider access or human interactive acceptance on Windows, or power-loss certification.
The seven attached files include both installers, a clean Foundry source archive, complete corresponding-source archives for both platforms, scoped public evidence, and checksums. Platform source archives contain runtime/installer sources and both sandbox source trees. Private task records, account data, raw provider transcripts and private Git history are excluded. Historical v0.1.0 assets remain unchanged.
Foundry source is Apache-2.0; bundled third-party components retain their licenses and corresponding-source requirements. Existing task budgets and evidence persist across upgrades. Keep a backup and retain required old runtimes; missing or tampered runtime inputs stop execution.