bazel: Blacksmith remote cache enablement and cold/warm performance gates

Context

Implements step 8 of #1: enable/observe Blacksmith Bazel caching and measure cold/warm performance against the accepted baseline.

Work

Ensure org-admin has enabled Bazel Build Caching for this repository; verify no competing --remote_cache overrides Blacksmith.
Capture remote-cache hits/misses, action counts, wall time, CPU time, and storage for cold and warm runs.
Compare Bazel path to the accepted Blacksmith/Cargo baseline from bazel: freeze migration inventory and Cargo/Blacksmith baseline #12.
Prove cache disablement/eviction still yields a correct cold build without repository changes.
Meet build: migrate CI builds and tests to Bazel with Blacksmith caching #1 thresholds across ≥10 paired representative runs: warm PR build/test p50 ≥30% faster; total build compute ≥25% lower; cold p50 regression ≤10%.

Acceptance criteria

Given parity evidence from #6 and the baseline from #12
When cold and warm Blacksmith Bazel runs are measured over the defined paired sample
Then remote cache hits appear on repeated identical-SHA builds
And a source change reruns only actions whose declared inputs changed
And the #1 performance gates pass (or a checked-in waiver documents failure with maintainer approval — prefer pass)
And cache-unavailable cold builds remain correct

Out of scope

Sole CI Gate cutover and sticky-disk removal (bazel: cut over CI Gate, retain rollback, retire Cargo sticky disks #4).
Changing product code for speed unrelated to build graph.
Mobile bindings.

Evidence

Machine-readable benchmark evidence + Blacksmith dashboard links + exact SHA in closure notes.
Ordinary AGENTS.md close.

Relationships

Parent / blocks: M2 gate: implement #1 Bazel migration via sub-agents #2
Blocked by: bazel: cross-platform release targets and Cargo/Bazel parity evidence #6
Blocks: bazel: cut over CI Gate, retain rollback, retire Cargo sticky disks #4
Canonical spec: build: migrate CI builds and tests to Bazel with Blacksmith caching #1 (Blacksmith integration; performance AC)

ci: force synchronize for Test Suite (#5)

Status after org-admin enablement (#1 done)

Harness fix + verification PR opened: #426

Changes in that PR:

observe-warm now primes/warms across distinct --output_base dirs (same-base re-runs were satisfied by the local action cache and reported zero processes / zero remote hits even when remote caching could be active).
collect-pairs mode + Bazel Bootstrap wiring to gather ≥10 cold/warm pairs once hits are observed.
Still no in-repo --remote_cache.

Current blocker (not org-admin)

GitHub Actions is in a major outage (https://www.githubstatus.com — Actions major_outage). PR #426 has no github-actions check suite / Test Suite run yet, so we cannot observe remote cache hit on Blacksmith or collect the paired sample.

#5 stays OPEN. Do not start #4 until hits are observed, perf-sample.json is complete, and strict evaluate passes without --allow-pending.

Will retrigger #426 when Actions recovers.

Status after org-admin enablement (#1 done)

Harness fix + verification PR opened: #426

Changes in that PR:

observe-warm now primes/warms across distinct --output_base dirs (same-base re-runs were satisfied by the local action cache and reported zero processes / zero remote hits even when remote caching could be active).
collect-pairs mode + Bazel Bootstrap wiring to gather ≥10 cold/warm pairs once hits are observed.
Still no in-repo --remote_cache.

Current blocker (not org-admin)

GitHub Actions is in a major outage (https://www.githubstatus.com — Actions major_outage). PR #426 has no github-actions check suite / Test Suite run yet, so we cannot observe remote cache hit on Blacksmith or collect the paired sample.

#5 stays OPEN. Do not start #4 until hits are observed, perf-sample.json is complete, and strict evaluate passes without --allow-pending.

Will retrigger #426 when Actions recovers.

ci: retrigger Test Suite after Actions recovery (#5)

ci: active retrigger for Test Suite (#5)

ci: second active retrigger for Test Suite (#5)

ci: add workflow_dispatch to Test Suite for outage retrigger (#5)

fix(bazel): affected-inputs under remote cache + CI policy (#5)

build(bazel): check in Blacksmith cold/warm cache evidence (#5)

fix(bazel): restore same-base affected-inputs isolation probe (#5)

fix(bazel): run affected-inputs on default output base (#5)

fix(bazel): unique affected-inputs mutation avoids remote hit (#5)

build(bazel): verify Blacksmith remote cache hits and collect perf pa…

build(bazel): cut over CI Gate, retain rollback, retire PR Cargo stic…

Navigation Menu

Repository navigation

bazel: Blacksmith remote cache enablement and cold/warm performance gates #5

Context

Work

Acceptance criteria

Out of scope

Evidence

Relationships

10 remaining items

Status after org-admin enablement (#1 done)

Current blocker (not org-admin)

Status after org-admin enablement (#1 done)

Current blocker (not org-admin)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

bazel: Blacksmith remote cache enablement and cold/warm performance gates #5

Description

Context

Work

Acceptance criteria

Out of scope

Evidence

Relationships

Activity

10 remaining items

DecisionNerd commented on Aug 6, 2026

Status after org-admin enablement (#1 done)

Current blocker (not org-admin)

DecisionNerd commented on Aug 6, 2026

Status after org-admin enablement (#1 done)

Current blocker (not org-admin)

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions