[tjXJNOOBIE]

Summary

Apply the org-wide Tavall DI rule to the active tavall-java-utils CustomEnum branch.

tavall-java-utils is a Tavall-owned Java consumer library but is not one of the nine canonical tavall-java-tools implementation repositories, so it receives the universal DI baseline.

Concrete changes:

• adds org.tavall:tavall-di:1.0.0 as an API dependency;
• resolves Tavall DI from the canonical Tavall Studios package repository when credentials are available;
• adds a focused architecture contract explaining that the other eight Tavall tools remain concern-driven and should not be added decoratively.

Boundary

This does not turn the CustomEnum utility into a dependency container or runtime/module scanner. Its existing typed identifier/registry semantics stay focused. Tavall DI is the common first-party composition contract available to the library/consumers.

Relationships

• CHILD_OF Java Utils Added: typed CustomEnum utility foundation #1 / working/custom-enum-foundation
• Added: typed CustomEnum utility foundation #1 itself is a child of repository staging Platform: Staging PR — Tavall Java Utils Mainline Integration #2 / staging/platform
• follows Tavall Java Tools policy PR Refactor CustomEnum to enum semantics #4

Validation truth

Exact Java 25 Gradle/JUnit verification is pending. Keep Draft until validated and then reconcile this child into #1 before repository staging fan-in.

State: IMPLEMENTED_NEEDS_VALIDATION
Owner: chatgpt-interactive
Scope: Java Utils universal Tavall DI consumer baseline
Relationships: CHILD_OF #1; GRANDCHILD_OF #2; FOLLOWS tavall-java-tools#4
Validation: SOURCE_REVIEWED; JAVA25_LOCAL_CI_PENDING
Next Action: run exact-head Java 25 Gradle/JUnit, then reconcile into the CustomEnum foundation branch.