Why: backend adopts upstream main (role-policy/HITL fixes) and the parallel scratch-session work while keeping the M5 nested pin, so the followups composition stays current with main. Evidence: integration transport (gitlinkb7-run.json); pins checks and combination targets re-run below. Impact: one component gitlink. Refs: feature/audit-followups-pin-gate-m5
ui
@ fadabceade