CAIBI project benchmark: Gridfinity Rebuilt Prompt version 1.0 Help me build Gridfinity Rebuilt using the existing creator project at https://github.com/kennetek/gridfinity-rebuilt-openscad. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI. Project context: - A parametric OpenSCAD implementation of Gridfinity bins with configurable sizes, compartments, tabs, bases and print options. - Build context: OpenSCAD; 3D printer; Filament; Optional magnets, screws or labels depending on generated bin. - Where AI helps: Parameter changes, OpenSCAD edits, Customisation. - Physical work: Measure, Print, Test fit. - Main limitation: The design work is easy compared with print time. Large storage systems consume more filament and machine hours than the first few bins suggest. Read the source first. Use its published design, files, dimensions and parts as the baseline; do not redesign it unless a missing detail requires a clearly labelled proposal. If you cannot access a source or verify a revision, say so. Provide one practical build package: 1. Design and files: explain the source design, link the original editable files, and identify missing files or modifications. 2. Parts and fabrication: give quantities, exact variants and compatibility, plus a cutting or printing list where applicable. Preserve source dimensions; flag anything unconfirmed. 3. UK and US purchasing: direct product links, checked dates, stock, pack sizes, taxes, delivery and regional costs. Mark unverifiable details as unknown; do not invent links, prices or availability. 4. Assembly: an ordered guide covering fabrication, fitting, wiring or software as applicable, setup, checks and troubleshooting. 5. Cost and time: separate parts, fabrication, delivery, hands-on time and machine time, with assumptions and exclusions. 6. Function and ease: a test plan for the project's stated purpose, likely difficulties, required skills and any corrections or limitations. Keep source facts, your proposals and items needing physical verification distinct. An estimate is not a measured build result. Do not claim to have built or tested hardware. Include failed attempts and omissions. If a section does not apply, say why. Use the source as accessed during this run and record its revision or access date. The prompt is fixed; the linked source can change.