Sharpen README for GitHub

[GeoGeekLab]

Summary

• make the first screen signal-first with CI/release/Python/typing status
• lead with the geospatial correctness problem rather than generic project prose
• add a real operation-aware terminal example
• surface dataset / relation / operation semantics as the project mental model
• make CLI, adapters, rule families, policy, schemas, and release contracts easier to scan
• preserve current v0.1.0 behavior and distribution details
• carry the GeoGeekLab identity without turning the README into marketing copy