Clarify self-hosting claim scope to CodBoot experimentation

[Copilot]

The issue was ambiguity around whether Coderive is now fully self-hosting project-wide (Java-like) or only within the CodBoot effort. This update clarifies that current self-hosting completion applies to the CodBoot experimentation track, not the entire repository/runtime stack.

• Scope clarification

  • Tightened wording so “100% self-hosting” is explicitly scoped to experimentations/codboot.
  • Removed room for interpreting this as a full project-wide/bootstrap-chain replacement claim.

• Boundary statement

  • Explicitly calls out that experimentations/ is isolated from production runtime paths.
  • Preserves clear separation between experimental self-hosting status and broader repo/toolchain dependencies.

• Terminology consistency

  • Aligned language across self-hosting docs so status, scope, and boundaries use the same framing.

**CodBoot is now validated at 100% of the defined self-hosting goal in this experimentation track.**
...
Everything in `experimentations/` is intentionally separated from production runtime paths.