legal: release GraphForge v0.5.0 under Apache-2.0 #218

Objective

Release the entire current GraphForge repository and every v0.5.0 first-party package under Apache License 2.0 before publication.

Acceptance criteria

• Root and packaged LICENSE/NOTICE files use Apache-2.0 consistently.
• Rust, Python, npm, fuzz, test, CLI, binding, docs-tooling, and agent-skills manifests report Apache-2.0.
• BUSL terms, Additional Use Grant, Change Date/AGPL conversion, commercial-use restrictions, and release-specific license generation are removed.
• Contributions are accepted under Apache-2.0 terms without the proprietary-relicensing CLA.
• Static and packaged-artifact gates verify Apache metadata, LICENSE/NOTICE inclusion, and third-party attribution.
• Current product, contributor, legal, release, and artifact documentation describes Apache-2.0.
• v0.4.0 and earlier published artifacts remain correctly described as MIT.
• Live v0.5.0 release issues cannot reintroduce BUSL or the removed CLA.

Evidence

• Merged: legal: release GraphForge under Apache-2.0 #221
• Squash commit: ead5e8b1ce5b0e7b627b3d54c7bcb0e46e81f9b1
• Exact-head CI Gate and every required Test Suite lane passed.
• Local coverage: Rust 86.56%, Python 100% (79 tests), Node 100% (214 tests).
• Apache compliance, package-license, cargo-deny, and generated third-party notice checks passed.

Non-goals

• Rewriting Git history or previously published v0.4.x artifacts.
• Adding commercial extensions to this repository.
• Changing runtime APIs, storage formats, or product behavior.

Relationships

• Completed prerequisite and native sub-issue of release: ship GraphForge v0.5.1 with fast-fail recovery #192.
• Updated the licensing assumptions in legal(dx): re-point published Apache-2.0 package metadata at the canonical repository #191, release: final metadata check (consolidated into #192) #199, and docs(legal): make Apache licensing and contribution terms reachable from public docs #200.