Document training role in creative ecosystem

[ibloud]

Summary

• identify Training as the ecosystem's contributor on-ramp
• map demonstrated skills to possible scoped next contributions
• preserve the repository's noncanonical status
• clarify academic, compensation, privacy, and access boundaries

Verification

• TypeScript typecheck passed
• failing tests remain the intentional candidate starting state; no exercise behavior changed

Boundaries

• development lineage is not treated as one literal continuity
• historical material does not override repository canon
• third-party expression is not transferred into original IP
• no private benefit, housing, medical, or financial records are included