Explain Value Map with projection rails

[bigboateng]

Summary

• replace the abstract text-only flow with the selected Projection Rails diagram
• keep external source meaning and repository evidence visibly separate until projection
• show existing, partial, and proposed capabilities in one concrete example
• preserve human judgment as the final decision boundary
• normalize repository text files to LF for stable cross-platform manifest checks
• skip only the POSIX-specific Bash file-URI integration test on Windows while retaining Bash validation on Linux and macOS and PowerShell validation on Windows

Why

Value Map needs to be understandable before a reader studies its mechanics. The diagram makes the operator concrete: preserve the sender's meaning, classify what the repository supports, expose what still needs building, and return a testable value hypothesis rather than an automated verdict.

The CI adjustment addresses the initial Windows failure without weakening the distribution contract. Manifest hashes remain deterministic across checkouts, and each installer continues to be validated on its native platform.

Verification

• python3 -m unittest discover -s tests -v
• git diff --check
• rendered the repository-native SVG at 1440×900 and visually checked connector alignment, text boundaries, and reduced-width readability