feat: move gh-pages on this current repo to a new repo AztecPackages/ben

.claude/skills/adding-benchmarks/SKILL.md

@@ -20,7 +20,7 @@ Benchmarks flow through the system as follows:
 3. **Upload**: CI caches the merged JSON and GitHub Action uploads to the benchmark dashboard
 4. **Display**: Results appear at the dashboard with historical tracking
 
-**Live dashboard:** https://aztecprotocol.github.io/aztec-packages/bench/?branch=next
+**Live dashboard:** https://aztecprotocol.github.io/benchmark-page-data/bench/?branch=next
 
 ## How Benchmark Names Work
 

.github/workflows/ci3.yml

@@ -111,6 +111,7 @@ jobs:
           benchmark-data-dir-path: "bench/${{ env.TARGET_BRANCH }}"
           tool: "customSmallerIsBetter"
           output-file-path: ./bench-out/bench.json
+          gh-repository: AztecProtocol/benchmark-page-data
           github-token: ${{ secrets.AZTEC_BOT_GITHUB_TOKEN }}
           auto-push: true
           ref: ${{ github.event.pull_request.head.sha || github.sha }}

ci3/dashboard/rk.py

@@ -138,9 +138,9 @@ def root() -> str:
         f"\n"
         f"Benchmarks:\n"
         f"\n{YELLOW}"
-        f"{hyperlink('https://aztecprotocol.github.io/aztec-packages/bench?branch=master', 'master')}\n"
-        f"{hyperlink('https://aztecprotocol.github.io/aztec-packages/bench?branch=staging', 'staging')}\n"
-        f"{hyperlink('https://aztecprotocol.github.io/aztec-packages/bench?branch=next', 'next')}\n"
+        f"{hyperlink('https://aztecprotocol.github.io/benchmark-page-data/bench?branch=master', 'master')}\n"
+        f"{hyperlink('https://aztecprotocol.github.io/benchmark-page-data/bench?branch=staging', 'staging')}\n"
+        f"{hyperlink('https://aztecprotocol.github.io/benchmark-page-data/bench?branch=next', 'next')}\n"
         f"{hyperlink('/chonk-breakdowns', 'chonk breakdowns')}\n"
         f"{RESET}"
     )

l1-contracts/README.md

@@ -36,7 +36,7 @@ We use `forge fmt` to format. But follow a few general guidelines beyond the sta
 
 You can run `./bootstrap.sh gas_report` to generate a detailed gas report for the current state and update the gas_report.md file.
 
-If you want something more manageble you should be using the `./boostrap.sh gas_benchmark` which will give you some "happy path" gas numbers for set with and without validators in a format that might be slightly simpler to figure out. The values outputted from this can also be seen over time at https://aztecprotocol.github.io/aztec-packages/dev/l1-gas-bench/.
+If you want something more manageble you should be using the `./boostrap.sh gas_benchmark` which will give you some "happy path" gas numbers for set with and without validators in a format that might be slightly simpler to figure out. The values outputted from this can also be seen over time at https://aztecprotocol.github.io/benchmark-page-data/dev/l1-gas-bench/.
 
 When running CI or tests with `./bootstrap.sh test`, the script will automatically check if gas usage has changed by running `./bootstrap.sh gas_report check`. If gas usage has changed, the test will fail and show a diff of the changes.