docs: policy-aware version, release and installer composition

[pcvantol]

One coordinated documentation increment

POLICY_GOVERNANCE_AND_EFFECTIVE_PROFILES_V1, with Forge #50, EP #103 and Workspace #15.

• Defines Forge Platform policy-aware artifact/runtime/deployment compatibility without moving Forge planning or EP execution policy authority here.
• Documents native Forge version/release operations, product-owned canonical version sources, EP bounded execution/publication and immutable artifact evidence before final composition.
• Distinguishes product/component release, source SHA, artifact digest, protocol/schema and policy/evaluator versions.
• Describes owner API activation receipts, partial cross-product activation, 1/2/3-role installations, restart/update/rollback and preservation of grants/budgets/history.
• Adds the scoped POL-P roadmap/DAG and routes it from the roadmap index and BOOTSTRAP.

Boundary

Four Markdown files only. No installer implementation, manifest schema, helper, workflow, package version, runtime, credential, grant or database changes. Existing #16 artifact composition and #17 SemVer proposals remain untouched and must reconcile with this target before their relevant implementation is adopted. No code-review findings are closed by prose. Full Workspace policy UI is not a new first-canary dependency.

Hosted validation requested on the exact candidate; no full local suite or installed qualification is claimed. Pending until owning merge; no merge, publication or deployment performed.

[pcvantol]

Coordinated documentation-only increment: Forge #50, EP #103, Workspace #15, Forge Platform #18. Full exact-head, DAG and hosted-validation report: pcvantol/forge#50 (comment) .

Platform head 06a7704aee28a7d5ea3446efae856629b57eee73: Foundation validation, CodeQL and TDE observe SUCCESS; Git-mergeable. Four Markdown files only. Existing #16/#17 remain untouched. POL-P requires real policy/release/artifact qualification for the production installer composition, not merely identical product version numbers. No new version allocator, installer implementation, peer SQL, active policy or grant changes. Unmerged; no publication/deployment approval or installed capability is asserted.