Launch MagicQuant: preserve history, publishable CLI, AGPL and unified docs

[magiccodingman]

Result

Make the renamed MagicQuant repository the home of both the application and its research, with a NuGet-installed CLI, AGPL-3.0-only licensing, and release-branch trusted publishing.

Merge this PR with a merge commit. Do not squash or rebase: it imports the complete MagicQuant-Pipeline main history without rewriting original commits. Both source histories are ancestors of the launch branch. Subsequent commits organize the tree and implement launch features. The old destination README is retained as wiki/overview.md.

Changes

• Move application projects into src/, tests into tests/, and retain operational docs in docs/, research in wiki/, and historical research in archival/.
• Rewrite the README as a briefing and NuGet quick start, with badges, config examples, scratch-disk performance guidance, optional Unsloth learning, accurate Linux/Windows support statements, and early support links. Add the requested GitHub/Sayou/PayPal funding configuration.
• Package MagicQuant as the magicquant .NET tool, including config, Python helper, native assets, package icon/readme, AGPL license and third-party notices. Add init-config (never overwrites) and --version.
• Make starter settings model-neutral: no selected provider, model, machine paths or model license. Move the external configuration walkthrough to an opt-in template and document same-model upstream links versus local rebuilding for variants, including the limits of tensor-only copying.
• Point generated discovery and clone READMEs directly to https://github.com/magiccodingman/MagicQuant, covered by output tests.
• Add .github/workflows/publish-nuget.yml with environment: release, NuGet/login@v1, and secrets.NUGET_USER. A push/merge to release validates first, reserves an automatic patch version with an immutable tag, tests the exact package, and publishes. Same-commit retries reuse the version. release-version.txt supports deliberate minor/major increases.
• Extend Linux/Windows Debug/Release CI with actual package installation tests, documentation/config checks, and version-reservation tests. Add a checksum-pinned secret scan covering history and the final tree, and IDE/local-artifact ignore rules.

Numerical formulas, existing database formats, and runtime artifact contracts are preserved. Starter/typed confirmed-anomaly expansion defaults now use built-in Q6_K/Q5_K candidates only; explicit external expansion names belong in the opt-in provider template. Existing user configs are not rewritten. No real release is published by this PR.

Validation

• Local strict Release build: zero warnings/errors; 171 tests passed, one explicitly opt-in model smoke skipped.
• Eight Python checks passed, including real isolated bare-remote version reservation/retry and documentation links.
• The actual nupkg installs from a local-only feed into a clean directory; checks bundled native/config/Python assets, help/version, config generation/no-overwrite, spaces in paths, and read-only preflight outside the checkout.
• Secret review: Gitleaks scanned the complete imported history plus the final tree. The only initial matches were two exact tensor-name test fixtures; an exact-line/path exception documents those false positives. No credentials detected after review. Historical machine paths and author email metadata are intentionally retained with faithful history.
• GitHub Actions validates all four Linux/Windows Debug/Release builds, test suites and package installations, plus the separate history/tree secret scan. All five checks passed on the initial launch revision (CI run); the PR check panel shows validation for subsequent documentation/default-profile updates.
• Full model numerical parity and end-to-end Windows campaigns are not established by these checks. The prior Pipeline cleanup's Linux Qwen smoke remains the model-level evidence.

Maintainer release setup

Configure NuGet trusted publishing for owner magiccodingman, repository MagicQuant, workflow filename publish-nuget.yml, environment release, package MagicQuant; add NUGET_USER as the NuGet profile username. Configure the GitHub release environment/branch policy and required checks as described in docs/releases.md. First publication is 0.1.0. NuGet badges resolve after that first publication.

The original destination checkout's uncommitted wiki/docs/Imatrix-Dataset.md edit is untouched and is not silently included here.