MAX_BW never fires in top-level because cap inputs are tied off

integration_top.sv drives max_bw_valid and max_bw_value to 0 for every port, so the scheduler never emits MAX_BW in the real design. No register block or configuration interface in the repo supplies these values; only the testbenches hard-code them. Searching for a producer of the cap will find nothing outside the testbenches.