Code references on components
A component can point at code: a repository, a path, and a branch or a commit. When the flight computer's specification changes, the firmware referencing it is visible from the same page, so the question of whether the software knows about this yet has an answer instead of a meeting. This is the same problem the rest of the product exists to solve, applied to the boundary teams get wrong most often, because the mechanical side and the software side keep their records in different tools and neither notices when the other moves.
References pin to a commit on publish
A reference to a branch is a reference to a moving target. When a component version is published, every branch reference on it snapshots to the exact commit it pointed at, so the record says this version was built against this commit and keeps saying it after the branch has moved on twenty times. That is the difference between a link and a record: a year later, looking at a flown board, you can get back the code that was actually on it rather than whatever is on the branch today. It happens automatically at publish and never blocks the publish if the connection to the repository is down.
Boards render in the browser
Electronics designs in a linked repository are detected and rendered in the browser, schematics and boards alike, with pan, zoom and per-layer visibility. Nothing is installed and nothing is exported. The practical blocker to getting electronics reviewed by more than one person has always been that reviewing meant installing the toolchain, matching the version, and pulling the branch, which is enough friction that boards get reviewed by whoever drew them. A monorepo with several designs in it is handled as several boards rather than one.
Assembly view
Alongside the design view there is an assembly screen: the parts list grouped into line items by value and footprint, next to a map of the board with every part drawn in its real position and outline. Pick a line item and the parts light up where they physically go, and each line can be checked off as it is populated. Hand-assembling a board from a flat parts list is how components end up in the wrong place, and this is the view that stops it.