Prepare the 1.0.0 GA release surface

Add the repo-side pieces for milestone 5: MIT licensing, real maintainer and forge metadata, a public support doc, 1.0.0 release notes, release-prep tooling, and CI uploads for the full candidate artifact set.

Keep source-tree version surfaces honest by reading the local project version in the CLI and About dialog, and cover the new release-prep plus version-fallback behavior with focused tests.

Document where raw validation evidence belongs, add the GA validation rollup, and archive the latest readiness review. Milestone 5 remains open until the forge release page is published and the milestone 2 and 3 matrices are filled with linked manual evidence.

Validation: PYTHONPATH=src python3 -m unittest discover -s tests -p 'test_*.py'; PYTHONPATH=src python3 -m unittest tests.test_release_prep tests.test_portable_bundle tests.test_aman_cli tests.test_config_ui; python3 -m py_compile src/*.py tests/*.py; PYTHONPATH=src python3 -m aman version

docs/developer-workflows.md

@@ -13,14 +13,21 @@ make package-deb
 make package-arch
 make runtime-check
 make release-check
+make release-prep
 ```
 
 - `make package-portable` builds `dist/aman-x11-linux-<version>.tar.gz` plus
   its `.sha256` file.
+- `make release-prep` runs `make release-check`, builds the packaged artifacts,
+  and writes `dist/SHA256SUMS` for the release page upload set.
 - `make package-deb` installs Python dependencies while creating the package.
 - For offline Debian packaging, set `AMAN_WHEELHOUSE_DIR` to a directory
   containing the required wheels.
 
+For `1.0.0`, the manual publication target is the forge release page at
+`https://git.thaloco.com/thaloco/aman/releases`, using
+[`docs/releases/1.0.0.md`](./releases/1.0.0.md) as the release-notes source.
+
 ## Developer setup
 
 `uv` workflow: