docs: update bazel-orfs.md with metric update and eqy sections

Add documentation for updating metric thresholds via _update targets
and the EQUIVALENCE_CHECK/RUN_EQY separation. Update status to
reflect all 8 asap7 designs passing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>

Author: oharboe

bazel-orfs.md

@@ -4,7 +4,7 @@ This is an early integration of [bazel-orfs](https://github.com/The-OpenROAD-Pro
 into OpenROAD-flow-scripts. It lets you build ORFS designs with Bazel
 using the same `config.mk` files you already have.
 
-**Status**: beta -- a handful of simple designs work end-to-end.
+**Status**: beta -- all 8 asap7 designs build and pass QoR tests.
 The full patch set lives out-of-tree in `bazel-orfs/orfs/` to minimize
 churn; this PR wires up the minimum needed for developers to kick the
 tires.
@@ -158,6 +158,27 @@ local_path_override(
 - **Parallel**: Independent designs build in parallel automatically.
 - **Reproducible**: Same inputs always produce the same outputs.
 
+## Updating Metric Thresholds
+
+When OpenROAD or flow scripts change, metric thresholds in
+`rules-base.json` may go stale. To update them for a specific design:
+
+```bash
+# Rebuilds the design and writes updated thresholds back to source
+bazelisk run //flow/designs/asap7/aes-block:aes_cipher_top_update
+```
+
+The target name follows the pattern `<design_name>_update` where
+`<design_name>` comes from `DESIGN_NAME` in `config.mk`.
+
+## Equivalence Checking (eqy)
+
+Some designs (e.g. `aes`) set `EQUIVALENCE_CHECK=1` in their
+`config.mk` to enable equivalence checking of repair_timing. The
+actual `eqy` tool invocation is gated by a separate `RUN_EQY`
+variable (default 0), so builds don't fail when eqy is not installed.
+CI sets `RUN_EQY=1` when eqy is available.
+
 ## Known Limitations
 
 - Only asap7 and sky130hd PDKs are wired up (others can be added to