release: ship v1.8.0 founding validation docs

[sergeliatko]

Summary

• Reframe the README around repository sprawl, value preservation, and portfolio-level judgment.
• Document the confirmed 340-project founding use case and three-implementation lineage without implying external adoption.
• Align architecture, provenance, roadmap, and quickstart guidance with the founding evidence boundary.
• Synchronize package and plugin identity for v1.8.0 while leaving the installable runtime and fixtures unchanged.

Verification

• npm.cmd run validate
• npm.cmd run package -- v1.8.0
• npm.cmd run release:verify-assets -- v1.8.0
• Manual inventory review of all three ZIP files and SHA-256 comparison with SHA256SUMS
• Runtime tree identity check against v1.7.0
• npm.cmd run release:preflight -- v1.8.0

Final preflight result: pass.

Candidate tree SHA-256: 81196cfed25d998f87c2dfc54ab5403a21e9b350c54017f3aeb11b05f36507de.

Checksum manifest SHA-256: ed43473a6737ff551b551fee1bea62e34769d7537c4187214f34e9834988406e.

Privacy and Compatibility

Private intake remains ignored, uncommitted, and excluded from every package. The release publishes only generalized, maintainer-approved founding facts and leaves skills/coordinate-github-repositories/, fixtures, activation, output behavior, package formats, and installation paths unchanged.