update metrics for bp_single and bp_quad

[eder-matheus]

designs/gf12/bp_quad/rules-base.json updates:

Metric	Old	New	Type
cts__timing__setup__tns	-247000.0	-638000.0	Failing
globalroute__timing__setup__tns	-702.0	-8020.0	Failing
detailedroute__route__drc_errors	1	0	Tighten
finish__timing__setup__ws	-219.0	-208.0	Tighten
finish__timing__setup__tns	-1620.0	-1420.0	Tighten

designs/gf12/bp_single/rules-base.json updates:

Metric	Old	New	Type
cts__timing__setup__tns	-517000.0	-474000.0	Tighten
cts__timing__hold__tns	-4250.0	-4700.0	Failing
globalroute__timing__setup__ws	-615.0	-556.0	Tighten
globalroute__timing__setup__tns	-106000.0	-79400.0	Tighten

[gemini-code-assist]

Code Review

This pull request updates the regression baseline metrics in rules-base.json for the bp_quad and bp_single designs. While some metrics show improvements, the reviewer highlighted significant timing degradations in the bp_quad design for both cts__timing__setup__tns and globalroute__timing__setup__tns. The reviewer requested clarification or a tracking issue to address these regressions before merging.

[gemini-code-assist]

The cts__timing__setup__tns metric shows a significant degradation (from -247000.0 to -638000.0). Please provide the explicit agreement or tracking issue to address this timing degradation later, or clarify if this is caused by parasitics estimation bug fixes.

References

1. It is acceptable to merge updates to regression baselines that show significant degradation, provided there is an explicit agreement to address the underlying issue later.

[gemini-code-assist]

The globalroute__timing__setup__tns metric shows a significant degradation (from -702.0 to -8020.0). Please provide the explicit agreement or tracking issue to address this timing degradation later, or clarify if this is caused by parasitics estimation bug fixes.

References

1. It is acceptable to merge updates to regression baselines that show significant degradation, provided there is an explicit agreement to address the underlying issue later.