[aliasfoxkde]

Summary

Adds the implementation architecture and phased execution plan for GitForge's CI/storage efficiency initiative.

The plan covers:

• Resource-aware control/fast/standard/heavy/background scheduling, admission control, weighted fairness, resource enforcement and queue observability.
• Immutable content-addressed storage, trust namespaces, manifests/references, managed Git workspaces, optional reflink/OverlayFS/Btrfs providers, and lease-aware two-phase GC.
• Sound incremental test impact and complete test-result fingerprints, reusing and reviewing the existing feat: smart CI + dependency/change-impact graph optimization #322 graph branch rather than merging its stale branch wholesale.
• Shared test-runner integration and a toolchain bake-off covering nextest, sccache, cargo-chef, lust-lang, ts-rust, JS/Python tool alternatives and the supplied server/database benchmark suites.
• Gate 0 remediation for the current compile, cargo-vet and GitForge API polling failures, along with public runner trust and atomic storage validation.

Tracking

Umbrella: #342

Workstreams:

• feat(scheduler): add resource-aware fast, standard, and heavy CI lanes #338 — resource-aware fast/standard/heavy CI lanes
• feat(storage): implement shared content-addressed store, isolated workspaces, and safe GC #339 — CAS, managed workspaces and safe GC
• feat(testing): add sound incremental test-impact graph and reusable test execution cache #340 — incremental test-impact graph and reusable test outcomes
• perf(tooling): benchmark faster compiler, linter, test-runner, and database paths #341 — compiler/linter/test-runner/database benchmarks

Related existing issues: #277, #284, #288, #318, #322, #335, #336, #337 and #258.

Scope and validation

This PR is documentation/design only. It does not change runtime scheduling, storage, test selection, credentials, or runner behavior. The document explicitly records that current main and PR #336 were not fully green at the audit point, and defines exact validation gates before optimization rollout.

Please review the execution order and safety invariants before implementation PRs are opened.

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 96fb1f78-ac9b-4352-b5ba-71f572f8d153

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.