Make the first vramfit run legible and CPU-only

## Destination

A first-time user can understand the result, install the base package, and complete one CPU-only run.

The same path states which targets and runtimes have measured support.

## Notes

- #140 owns the PyPI installation correction.
- The first run must keep the base install free of the scan and pack extras.
- Published damage values compare only within one instrument under ADR-0027.
- Reuse shipped artifacts. Do not add a second example artifact without a recorded need.
- The 49B pack has no recorded 16k serve on the 4090 (#501). README text states the 24 GiB budget as the solver target and claims no 16k serve.

## Decisions so far

- [#483 Decide the CPU-only first run](https://github.com/Alberto-Codes/vramfit/issues/483): the first run installs the base package, solves the published 49B map at 24 GiB and 3616 MiB headroom, then reads capacity at fp8 and 16k context. Record: [PR #494](https://github.com/Alberto-Codes/vramfit/pull/494), `docs/tutorials/first-run.md` at `draft` and the README Quick Start.
- [#482 Decide the README's compact evidence summary](https://github.com/Alberto-Codes/vramfit/issues/482): the README gains `## The result`, one table for the 49B publication with the ADR-0027 boundary and one line for the later publications, and Status loses the prose the table replaces. Record: [PR #502](https://github.com/Alberto-Codes/vramfit/pull/502), README `## The result` and the ADR-0003 note dated 2026-09-03.

## Fog

- Whether one compatibility view can cover the CLI and each published artifact.

## Out of scope

- #104 owns deployment of the MkDocs site.
- #148 owns contributor onboarding, issue templates, and support posture.
- #410 and #411 own the publication #2 runtime path.
- New scan, pack, solver, and artifact-schema behavior does not belong to this effort.

Read docs/tutorials/first-run.md at draft, the README Quick Start, and README’s ## The result alongside PRs #494 and #502. Check how the CPU-only run, published 49B map, 24 GiB solver target, ADR-0027 boundary, measured runtimes, and no-16k-serve claim are presented. Done means a first-time user can install the base package and understand the supported CPU-only path without new artifacts.

Written by the indexing model from the issue text.