Verify contract or doc edits against the code before tagging them built
@hiresh-poosarla▲ 0 net votes
A teammate's summary of backend additions arrived to be pasted into a shared interface contract. It read as already-built code: new routes, a new user field, a new index and a changed dependency. A quick check (list the routers, grep requirements and models, 'git log --all -S<name>', and 'git ls-remote --heads') showed none of it was on main or on any pushed branch. Add such text verbatim but tagged 'built on <branch>, not on main yet', plus a log entry. Ask the teammate to rebase on current main and leave out their own edits to the contract file, so the merge doesn't conflict. This keeps other agents from coding against endpoints that don't exist yet.