[rhiever]

FM27 build 27.0.0+2486695 now opens through the normal library, CLI, and app reader. Other FM27 builds and unregistered layouts reject. This prepares version 0.8.0 without tagging or publishing it.

The implementation keeps strict FM27 checks and conservative edition-specific budgets while preserving FM26's existing budget. Unsupported tables reject, unavailable fields stay explicit, and FM27 validation field statuses remain unconfirmed. Populated per-match histories are still unsupported; the raw span API remains separate from semantic fixture and rules tables.

The app and documentation now describe both editions, stored money units, and coverage limits. The app identifies the reader version required for FM27, so an older published reader does not advertise support it lacks. Local browser verification used the built 0.8.0 wheel; no package was uploaded. The branch includes the main fixes from PR32 and the workflow instructions from PR33. Version metadata and the changelog prepare 0.8.0.

Validation so far:

• 3,364 non-corpus tests passed; Ruff and Pyright passed.
• Documentation built with warnings treated as errors; wheel/sdist content checks passed.
• Private in-game observation tests and isolated browser checks passed with real FM26 and FM27 saves. Save bytes, screenshots, extracted values, and test evidence remain ignored and local; public fixtures are synthetic.
• All 43 fresh canonical FM26 corpus tests passed. All 12 CI checks passed on the current head. The earlier largest-save history memory limit remains an explicit coverage limitation, not a regression claim.

The staged and commit-message privacy hooks passed. A full local scan retains an existing MIT-license overlap with a private dependency; it is not represented as a clean full scan.

Independent integration review passed on the exact current head, including 182 focused public tests, 4 private tests, and real-save browser checks. Package publication remains deferred for the maintainer's explicit release decision.

Provenance and checks

• Tests cover the changed behavior.
• No private save data, screenshots, names, identities, or extracted values are committed.
• Format work uses authorized local saves and in-game observations; no decompilation, leaked material, NDA material, or unlicensed parser code.
• Final required checks and independent review completed.