[P3 carryover] Qualify v0.8.0 HTML artifact release copy

[project820]

Carryover from PR #59

PR #59 (75a4124, merged) refreshed the v0.8.0 release copy.

Residual issue

The release wording says an HTML artifact is produced “always” / for every generation. That overstates the implemented contract: the renderer transitions to error on AI_ERROR, and the generation orchestrator exposes explicit failed outcomes.

Affected copy

• CHANGELOG.md:12
• README.md:12
• README.md:52
• docs/releases/v0.8.0.md:7

Desired fix

Qualify the claim to successful HTML generation (or clearly describe the failure path). Keep release documentation consistent with the renderer and orchestrator behavior.

Evidence

• Source PR: docs: v0.8.0 changelog, what's new, README refresh + version bump #59
• Final review: docs: v0.8.0 changelog, what's new, README refresh + version bump #59 (review)

[project820]

🤖 Psycho-842 [BOT] triage

ℹ️ TRIAGE — The release copy promises a saved HTML artifact for every generation, while the current implementation explicitly models failed outcomes.

Summary

The v0.8.0 documentation says HTML output is always produced after unsafe content is cleaned.
Current renderer and main-process code allow a generation to fail or be cancelled without a finalized artifact, so the copy should be qualified to successful generation.

Reproducibility & Evidence

Measured on default-branch commit 7b7065082d487a9c8c3c9576cf2283a9f88e0ec3: CHANGELOG.md:12, README.md:12 and :52, and docs/releases/v0.8.0.md:5-7 retain unconditional wording.
src/renderer/html-export-state.ts:241-243 maps AI_ERROR to step: 'error' and clears finalized; src/renderer/html-export-wizard.ts:493-504 routes partial, failed, cancelled, and rejected requests to that error path. src/main/html-export-generation-orchestrator.ts:93-143, 204-214 declares and returns explicit failed and cancelled results.
The current main CI run for this commit completed successfully. No runtime generation was executed because this issue concerns release-documentation accuracy, not a new runtime defect.

Impact & Priority Suggestion

• 🟡 P3 Low — Public release wording can set an incorrect expectation for unsuccessful generation attempts; it does not alter runtime behavior or create a data-safety regression.

Duplicates & Related

No separate duplicate found. This is the carryover from PR #59; the related sanitizer behavior landed in PR #56.

Next Evidence Needed

• Update all four release-copy locations to say that a finalized HTML artifact is produced after a successful generation, or explicitly describe the failure/retry path.
• Add the documentation PR and the exact revised wording here for final consistency checking.

ℹ️ TRIAGE

🦀 Triaged by Hermes agent BOT 🦞