chore(release): prepare v1.14.2

[seakee]

Summary

Prepare the v1.14.2 stability release from frozen dev SHA 57616ad8b26020f1b713b1d2ad77e7b622918b57.

This patch release contains only 1.x maintenance fixes already merged to dev: CPA v8 client API key loading compatibility, retained-history pricing rebuild after supported usage cleanup, account-history degradation when exact pricing is unrecoverable, and the release update-index retry hardening already present in the release delta.

Community and 1.x maintenance PRs must target dev. Approved v2 implementation
PRs target v2. Repository automation retargets other pull requests to dev;
this can change the diff and make existing review comments outdated. main
accepts only a promotion PR whose source is this repository's dev branch.

Scope

• Frontend panel
• Manager Server
• CPA panel mode
• Full Docker mode
• Native packages / release
• Docs / Wiki
• CI / build / tooling

Changes

• Add Chinese and English v1.14.2 release notes with the reviewed cpamp-update metadata block.
• Add the reviewed Telegram release post.
• Record the established release statistics: 21 commits, 25 files changed, +1096 / -171.
• Acknowledge @camy-x for the external CPA v8 compatibility contribution in all required release surfaces.

User Impact

v1.14.2 restores expected API Key display on CPA v8 and makes post-cleanup pricing/history behavior resilient without inventing deleted historical pricing data.

When exact pricing cannot be proven for one account, only that account's cost is unavailable; the rest of its trusted history and healthy accounts in the same batch remain usable.

Compatibility / Runtime Notes

• No schema migration or configuration change.
• Full Muse / Meta compatibility baseline remains CPA v7.3.4+.
• Supported usage cleanup does not restore deleted raw events; retained projection data is reused only when exact coverage is provable.
• This release does not add new 1.x feature scope.

Data / Security Notes

No new secrets, schema changes, or persisted application data are introduced by the release content.

The underlying fixes preserve fail-closed pricing semantics for genuinely incomplete legacy history and do not synthesize deleted request details.

Risk / Rollback

Risk level: Medium, driven by the Manager Server historical-pricing paths already reviewed in #893 and #894.

Before publication, the standard release topology, content validation, full dry-run build, and exact candidate SHA checks remain mandatory. After publication, the immutable tag/Release must not be moved or recreated.

Verification

• Release scope frozen at 57616ad8b26020f1b713b1d2ad77e7b622918b57
• Release statistics reproduced from previous release source 37b7eccf4e3d2d377a2224ada347ff5051e14e46 to frozen dev
• Three versioned release files only
• Release Content CI
• Required checks
• Build and Release dry-run
• Publish

Screenshots / Recordings

Not applicable; this is a patch release packaging already-reviewed fixes.

Docs

The versioned release notes and Telegram post are the required documentation changes for this patch release.

Related

Refs #879
Refs #887
Refs #893
Refs #894