Export and inspect reports

Choose an existing local Output directory, run a review, inspect its status and findings, then choose Export changes. SaveTether creates a new report folder containing Report.json, Changes.csv, and Report.html; it never replaces an existing report. Open all three locally and confirm the reported status and coverage before sharing.

JSON preserves typed identities and exact strings, mapping decisions, findings, run and version details, status, coverage, and fingerprints. CSV includes coverage even when there are no changes and protects spreadsheet formulas. HTML escapes project text and links only to companion local JSON/CSV; it does not load remote assets.

Partial or cancelled export is a separate action that requires explicit user approval and preserves that status. Failed reviews cannot be exported. Release capture has stricter eligibility; see release capture. Inputs are revalidated and staged files read back before the folder is published. If another process changes staged output, publication is refused; a remaining SaveTetherStage_ directory is incomplete staging, not a delivered report. Inspect it and resolve the interference before retrying. Do not delete staging blindly, because it may contain another process’s changes.

Reports can contain project names, identifiers, and local paths. Review them for confidential data before forwarding them to support.