# Phase 10 — build and publish release artifacts

## Goal
Build the final release artifact set from the regularized and maintained tree, include the unmodified upstream-derived source for traceability, and emit release metadata suitable for Git tags, Gitea Releases, and package publication.

## Script
`scripts/build-recovered-view.js`

## Outputs
- canonical editable source tree at repo root
- processed source release artifact from the post-Phase-9 tree
- unmodified upstream-derived source artifact for historical and debugging purposes
- release-ready output bundle or package contents when applicable
- `releases/<version>.manifest.json`
- supporting human-readable release notes derived from the pipeline summary and maintained transforms

## Release manifest requirements
- published version `0.y.z`
- upstream snapshot identity
- current and previous run IDs
- processed and unmodified artifact paths and hashes
- transforms included in the release
- compact upstream summary
- packaging outputs and publication targets
- compact pipeline summary metrics such as naming effectiveness, regularization stats, and replay outcomes

## Publishing model
- Git tag + Gitea Release are the canonical published version identity
- package registry publishes installable artifacts for the same version when applicable
- unmodified upstream-derived source may be attached to releases for traceability/debugging without needing to be part of package-registry payloads
- raw upstream bundles stay as release assets, not committed source files
- publication may be retried from existing built artifacts without rebuilding everything

## Verification
- confirm the release tree builds from regularized upstream-derived source plus transforms
- confirm processed and unmodified artifacts correspond to the same upstream snapshot identity
- confirm release manifest is emitted
- confirm manifest-referenced artifacts exist and hash-match
- confirm package contents and release metadata refer to the same version