Release: publish uImposition 0.7.0-alpha.5

[sunpole]

Цель

Опубликовать уже проверенный M7.5 как immutable prerelease uImposition 0.7.0-alpha.5 без кода M7.6 и без нового solver.

Release boundary

• starting main for this PR: 195d6496a291095a69cc9089a64154561ffbb1fa;
• functional M7.5 baseline: 009451cce94d5cde05ee72305f30447aa65a646c;
• version checkpoint / release commit: 195d6496a291095a69cc9089a64154561ffbb1fa;
• exact focused screenshot source: a8db529c29e7b71a7809bb5f857d48cfde115597;
• final publication head: 32ffe5ea58f4dd44e74d37e15727bf389b43ec85.

The existing publish workflow must create recovery branch release/v0.7.0-alpha.5 and immutable tag v0.7.0-alpha.5 at the version checkpoint commit, not at this later publication commit.

Publication files

• factual RU patchnote with short Telegram text;
• real Playwright focused PNG for m7-objective-priority-editor;
• permanent evidence ZIP with six M7.5 Chromium scenarios;
• embedded exact-head Quality and full Chromium/PDF Action archives;
• release manifest with separate sourceCommit and releaseCommit;
• evidence README;
• internal hashes for image, patchnote, manifest and README;
• external SHA-256 records for release PNG and evidence ZIP.

Automation repairs

The release preparation workflow exposed an old manifest-format mismatch: capture writes manifest.ndjson, while the generator expected manifest.json. This PR fixes that exact contract, validates a full 40-character release commit, records exact workflow provenance, embeds README/internal hashes into the ZIP, and writes final asset hashes.

Initial diagnostic runs 30236369867 and 30236370923 failed at that stale manifest path after successful Chromium capture. The corrected packaging runs 30236462228 and final run 30236703966 succeeded.

Exact evidence already available

• Quality: run 30236119913, 173/173 tests;
• Quality artifact 8641678651, digest sha256:7570c0a0c529d9994ea416d28cfefdbcfd688c8701fed09213b9c12642315f27;
• full Chromium/PDF: run 30236119914, 16/16 scenarios;
• screenshots artifact 8641691735, digest sha256:1cf047532caf18e7d49a6464a8f4b339dcc2ea15c37eb6f6ca0581491b0d33df;
• final focused evidence: run 30236703966;
• release PNG SHA-256: bb5686efa1d0f75990885b6f5e8736c1c4c93233eae181c3ae68f81397cf5a6e;
• evidence ZIP SHA-256: 9ac0cfb4c01c34e530b4f734e499e6184cf2d6ab78f2157ea1216e6ee5742ec9.

Visual review

The desktop and mobile focused images are readable without clipping/overflow. Estimated cost is first; four plans are reused and zero regenerated; uniform-r90-dedicated-pairs is visibly a recommendation, not an operator selection. No secrets/private data are present.

Required merge gate

• exact-head Quality success;
• exact-head complete Chromium/PDF success;
• uNews validation success;
• release publication paths are wired into the full Chromium gate;
• no unresolved review threads;
• merge only the immutable head named above.

Final publication-head checks

• Quality: run 30236853803, 173/173, artifact 8641905253, digest sha256:564e8f8901a8ac480b7f2819a301132081982f82f07005acccf555bdfe9f4a59;
• Chromium/PDF: run 30236853835, 16/16, artifact 8641922460, digest sha256:6cbd9c09f1ead8b96e5b69bfa76b43a165c4c1c55fe15230c47b4f5899e4b5f0;
• uNews validation: run 30236853818, success;
• no-marker prepare validation: run 30236853801, success.

Scope and claims

No underproduction, no zero substitution for missing prices, no merging of layout forms with color plates, no loss of feasible catalog variants, and no recommendation-over-selection behavior. The documented bounded search is not described as globally complete, and machine compatibility remains an operator check.

M7.6 is not included.