Changed

Game profiles are now authored and loaded as JSON rather than TOML, conforming to the profile variant of the master schema (issue #76, building on #75). A profile now declares kind and a fidelity tier alongside its game identity, capture defaults, and stages. Profile::parse remains the only constructor, so validation still runs before every capture; loading validates structurally against the master schema (reusing the S025 validator) and semantically for the checks a schema cannot express (acyclic descends_from, a single terminal stage, at least one non-service stage, reachable capture roles, no ambiguous image match, and glob/regex/duration compilation), reporting every problem across both layers in one pass. Profile resolution now finds <ref>.json. The Steam scaffold emits JSON carrying fidelity: heuristic-unverified and a notes string with the warning that its stage classification is heuristic and must be verified against a live capture, so that warning survives as structured data a machine can act on rather than a stripped comment. The toml-span dependency is removed. Capture output is unchanged: an equivalent profile drives byte-identical pcapng and JSON Lines.

The distribution archive now also contains the barebones hint database, placed beside the binary so the first-run bootstrap can seed the writable per-user copy from it. The archive previously held only the binary, the license, and the notice.

The --hint-db option and the FRAGCAP_HINT_DB environment variable now fall back to a per-user default (%APPDATA%\fragcap\hint.db) when neither is set, rather than leaving hint resolution off. A path named explicitly keeps its exact previous semantics: it is used as given and, when absent, is neither created nor an error.

cargo xtask notes now generates a release body from a version's curated Highlights plus a link to the full changelog at the tag, rather than the entire Added/Changed/Fixed list. A version with no Highlights block still falls back to the fuller body, so a release without curated highlights is never empty (issue #53).

The site and README now surface the two external prerequisites up front: npcap (the capture driver, detected but never bundled) and Wireshark (how a capture is read) are named early on the home page, the docs landing, and the getting-started guide, rather than late or in passing. The home page also introduces brand color and styles its links so they read as clickable, and the footer visually separates the "A ShruggieTech project" endorsement from its links.