[robert3005]

The fuzzer autofix job failed at the Anthropic token exchange with 401. The vortex-claude-write federation rule required job_workflow_ref to be claude-write.yml, so it refused tokens from fuzzer-fix-automation.yml. The comments said that the rule matched only the environment subject.

The rules are now updated outside the repository:

• vortex-claude-write accepts claude-write.yml and fuzzer-fix-automation.yml through a job_workflow_ref condition.
• vortex-claude-ci no longer lists fuzzer-fix-automation.yml. That entry could not match, because the job runs in the claude-automation environment.

This PR changes only comments, so that they agree with the rules.

[codspeed]

Merging this PR will regress 1 benchmark

4 warnings, 1 note

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ Unable to measure the execution of 2 benchmarks

These benchmarks measured no execution time, so their results are not comparable and count as unchanged. This usually happens when the compiler removes the code under test.

Prevent compiler optimizations

See affected benchmarks

⚠️ 18 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ Base and head ran on different runner types

Some benchmarks with significant performance changes were compared across different runner types, so the changes might not come from the code. Run base and head on the same runner type, or use CodSpeed Macro Runners for more stable results.

Learn more about Macro Runners

Open the report in CodSpeed to investigate

ℹ️ 40 benchmarks have no flamegraph

The flamegraph wasn't generated: the symbols of the profiling trace could not be resolved, because no information about the language frames was collected.

See affected benchmarks

⚡ 1 improved benchmark
❌ 1 regressed benchmark
✅ 2437 untouched benchmarks
⏩ 12 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Walltime	starts_with_avx512[64, VarBin]	56.2 µs	62.8 µs	-10.53%
⚡	CPU Simulation	test_scan_filter[int]	3.4 ms	3 ms	+12.96%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing rk/federation-rule-comments (b64c2ce) with develop (a59294e)}

Footnotes

1. 12 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩