What you would like to be added?
Implement AI Scaffolding Tier 3 checks 3.1 and 3.3 for the distributed-workloads repo:
Check 3.1 - Component-level context files
Add .claude/rules/ with path-scoped rules for component-specific conventions:
tests/trainer/ - mandatory tag declaration, test structure, import boundariestests/common/support/ - shared infrastructure conventions, environment variable patterns, file organizationtests/** - namespace isolation, resource naming, cleanup, cross-cutting import boundary rules
Check 3.3 - Architectural boundary lint rules
Enable depguard in .golangci.yml with per-suite boundary rules preventing cross-suite imports:
tests/kfto/ must not import from tests/trainer/, tests/fms/, tests/odh/tests/trainer/ must not import from tests/kfto/, tests/fms/, tests/odh/tests/fms/ must not import from tests/kfto/, tests/trainer/, tests/odh/tests/odh/ must not import from tests/kfto/, tests/trainer/, tests/fms/
Move shared image helpers (GetAlpacaDatasetImage, GetBloomModelImage) from tests/kfto/ to tests/common/support/environment.go to resolve existing cross-suite import violations.
Why is this needed?
The AI Scaffolding Tier 3 report identified gaps in the distributed-workloads repo: no component-level context files (634 files with only root-level CLAUDE.md) and no architectural boundary enforcement via linting. Adding these improves AI agent effectiveness and prevents unintended coupling between test suites.
What you would like to be added?
Implement AI Scaffolding Tier 3 checks 3.1 and 3.3 for the distributed-workloads repo:
Check 3.1 - Component-level context files
Add
.claude/rules/with path-scoped rules for component-specific conventions:tests/trainer/- mandatory tag declaration, test structure, import boundariestests/common/support/- shared infrastructure conventions, environment variable patterns, file organizationtests/**- namespace isolation, resource naming, cleanup, cross-cutting import boundary rulesCheck 3.3 - Architectural boundary lint rules
Enable
depguardin.golangci.ymlwith per-suite boundary rules preventing cross-suite imports:tests/kfto/must not import fromtests/trainer/,tests/fms/,tests/odh/tests/trainer/must not import fromtests/kfto/,tests/fms/,tests/odh/tests/fms/must not import fromtests/kfto/,tests/trainer/,tests/odh/tests/odh/must not import fromtests/kfto/,tests/trainer/,tests/fms/Move shared image helpers (
GetAlpacaDatasetImage,GetBloomModelImage) fromtests/kfto/totests/common/support/environment.goto resolve existing cross-suite import violations.Why is this needed?
The AI Scaffolding Tier 3 report identified gaps in the distributed-workloads repo: no component-level context files (634 files with only root-level CLAUDE.md) and no architectural boundary enforcement via linting. Adding these improves AI agent effectiveness and prevents unintended coupling between test suites.