Clarify README, extract GAQWH implementation, add benchmark, and fix CLI empty-input behavior

[MeridianAlgo-Developer]

Motivation

• Remove misleading "quantum"/signature claims and make project scope explicit as a hashing-only experimental toolkit.
• Surface the full GAQWH implementation as an importable module to improve code visibility and maintainability.
• Provide a simple local benchmark helper so performance of gaqwh can be compared against standard hashes.
• Ensure CLI behavior matches test expectations when stdin is empty.

Description

• Rewrote README.md into a detailed, structured document with table of contents, API reference, CLI usage, benchmarking guide, test scope, security warnings, roadmap, and license, and removed quantum/signature marketing language.
• Extracted the hash engine into astryx/gaqwh.py and simplified astryx/core.py to re-export Astryx and gaqwh, and changed astryx/__init__.py to import gaqwh directly for clarity.
• Added scripts/benchmark_hashes.py to micro-benchmark astryx_gaqwh vs sha3_256 and optionally blake3/kangaroo12 when dependencies are present.
• Fixed cli.py so empty piped stdin prints a guidance message and exits without hashing, and updated setup.py description to reflect the package as an experimental GAQWH toolkit.

Testing

• Ran the test suite with python -m unittest discover -s tests -q, which executed all tests and returned OK (13 tests passed).
• The test run includes CLI tests that validate the empty-stdin guidance behavior.
• No automated benchmark runs were executed in CI as part of this change; the new benchmark helper is available for local performance checks via python scripts/benchmark_hashes.py.

---

Codex Task

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[MeridianAlgo-Developer]

This is what I mean lol now #2 #1 are good