v0.6.12
Changed
- Maintenance release with no changes to how the app works.
manufacturing/<design>/drawing/.README.md at the top of the folder as its description, the same file GitHub shows on the repository. The Publish dialog has a Description field for it, and the Read me editor on the project page edits it too. product/README.md stays the agent's requirements document and is no longer shown in the community..work/backup/ first. The build output stays on disk, so the copy only took up space.~/.agents/skills) no longer appear in Replicator's agent.pcb.config.json: a filled shape of one net on one layer, placed over high-current pins. Pads the area touches no longer set the width of the whole net, so a regulator's power net is no longer routed at the width of its narrowest pin. After routing, the run reports how much of each area filled and which other nets cross it. An area over fine-pitch pins can reach them without lowering the net's clearance by hand.~/.codex instead of copied, so the app and your terminal no longer sign each other out.deepseek-v4-flash becomes deepseek-flash.review options on both are gone. Exports and releases recorded by earlier versions are not read; export or release again to replace them..kicad_mod were saved without their extension.high when the model offers it, and the picker shows that effort rather than a blank. Sessions saved before this get the same starting effort. A model that has dropped out of the provider's catalog still offers its efforts, so a session pinned to one keeps its picker.gpt-6-astra reads as GPT 6 Astra. Everything that selects, saves or sends a model still uses the exact id, which the picker keeps in its tooltip.circuit.json — the file the board view actually draws, generated into .work/, which is disposable and never committed. A clone had a board it could not show: the viewer asked for a build that had never travelled and rendered a 404. That file now publishes with the package, outside any delivery section, and even when a section is blocked — a board whose Gerbers failed is still a board somebody should be able to look at. The viewer reads the build first and the newest release second, and says which one it drew.source/lib/footprints/models/ — 77 MB, of which a board that places a single Xiao referenced 3.4 MB, and one unused Raspberry Pi 4 model was 50 MB on its own. Committed and pushed, that was most of the weight of a published project. The models a board actually places are now written when the KiCad stage needs them, read from the compiled circuit, and the ones it does not place are removed from the package.-dirty, releases included. The build id reads git status from inside the Vite config, and Vite bundles that config to a temporary file in the project root while it loads it, so the tree was never clean at the moment it was measured — a marker that exists to say a build came from a modified tree said nothing on every build. It counts tracked changes now, it is left off rather than set when git cannot answer at all, and a release stops on an uncommitted tree so -dirty cannot reach one.no remote connected in grey in the header.main. A forge serves one branch as the repository's head and that is the one the community reads, so pushing whatever branch you happened to be on was not the same as publishing it. Choosing here changes what is pushed and nothing else: no checkout, no touched working tree, and the dialog says so when the branch you are on is not the one going out.project.manifest.json still sitting uncommitted meant registering a listing the community answers with “this repository is not a Replicator project”, discoverable only afterwards from the listing page.project.publish, which pushes the committed history and lists the project in the community through the same flow as the Publish button, creating the GitHub repository first when there is none. Anything the button would refuse on — a missing licence or cover, no sign-in, no GitHub connection — it refuses on too, and tells you what to set.project.manifest.json naming what it is, its licence and its designs; a project's identity is kept out of that shared file so a copied folder is its own project rather than its twin; and the format is published as a specification with JSON Schemas beside it — the same definition the community platform reads, so another tool can read a Replicator project without asking this app.product/bom.json carries the mechanical rows too. The hardware view is about the board and only the board.kicad-cli picked in a file dialog — a KiCad app bundle included, which it resolves to the binary inside. A tool failing for want of a toolchain used to be reported as the tool failing.replicator://open?repo=… link still arrives with its address on screen and an Open button under it.git clone line under the button, and Download zip beside it, are gone from a project's page. The action area is the things you can press; the repository address is still in the footer, where the page says which commit it is showing.cad.look observations, and on the project cards on Home. Renders from before this change keep their old look until the design builds again.assembly-iso.png. A PCB project's card shows that render once the board has been released; before that, its layer plots sit on the same dark ground as the CAD renders rather than on a white card.electronics.search and electronics.detail. Under the old name — parts — the agent read them as the way to find any part at all and sent screws, heat-set inserts, bearings and extrusion to an electronics distributor's catalogue, then read the empty answer as proof the hardware did not exist. Mechanical hardware comes from the CAD catalogue, and always did..work/.web.read_url refuses a search engine's results page and says why: it lists links, returns nothing readable, and was the slowest path to an answer. Searching goes through the provider's own search; a page is read to take facts from a page already known. A host answering 429 or 403 is left alone for ten minutes rather than tried again every turn.rsvg-convert install. Preview images are now rasterized inside the app, so a machine without librsvg finishes routing, DRC, and manufacturing release instead of stopping the whole run at the preview step.Next navigate between every step. Provider and environment readiness still determine whether Finish is available.design.json files, with existing project state migrated automatically.setup, preview, check, and release operations while deterministic routing, KiCad validation, export, and review stages remain encapsulated behind the selected run profile.Blocked review prevents release.Unreleased entries into a dated version section and updating the comparison links.report.completion so the agent reports a natural-language result while the host derives authoritative completion evidence.