Thing is Astra integration is not entirely HAL job, that is DRDL Astra group which handle this part, and they outsource it to HAL under strict supervision done by the project team for the process. This is where the khichdi begins.
Since it is to integrate with a completely different software based radar, so drdl has to write the full custom code based software lopp for the test phase (& prove it on a ground test rig setup) because during test there should only be comm with 1553 avionic bus along with kam-500 data acquisition. This is defined process for every test, no other subsystem to interfere.
HAL outsourced work part is to ready the trial jet, charge down the jet & make ready the pylon with the adapter setup , integrate , setup & link with Kam-500 unit etc. Software & linking part done by drdl side people. Since its custom code with rig setup, obviously there would be problem during test phase if they are to do it on their own without ELTA tech people involvement. You won't get it right at first & multiple changes need to be done. this part of work is with project team, not HAL team.
So HAL has to rely on DRDL for the integration & later submit report for QA clearance to RCMA. So far Astra mk1 integration is under a subproject at DRDL & only 1-2 launches from LCA we have seen. Therefore Astra mk1 is not yet cleared for lca mk1a , HAL upon receiving permission from DRDL side that all clear & now fleetwide integration can be done , can only then do the work. This is yet to happen.
Same reason why we see such multi step adapter setup between pylon & launcher, this is done for test mainly to gather required data & keep everything safe. Final config is much more well rounded.