# Post-upload website companion sync for TrueTraceShorts

Use this after every AutoShortsBot / TrueTraceShorts private YouTube upload.

## Rule

A successful private upload is not the end of the workflow. Check whether the matching website companion page exists and update/create it immediately when appropriate.

## Privacy-safe website behavior

If the YouTube upload is still `private`:

- Do **not** expose the private YouTube URL as a visitor-facing `videoUrl`, watch button, or homepage link.
- Store the YouTube video ID / Shorts URL only in candidate/source metadata.
- Mark `website_link_allowed: false` or equivalent source metadata.
- Build the companion page as a useful guide without a broken/private video button.

When the video later becomes public or intentionally website-linkable:

- Sync `videoUrl: https://www.youtube.com/shorts/<id>` into both the candidate JSON and red-flag markdown.
- Rebuild and QA before pushing.

## Minimal post-upload checklist

1. Read the review package and YouTube upload audit.
2. Confirm `privacyStatus: private`, `upload_status: success`, and upload-only scope.
3. Create/update the website candidate JSON with:
   - source candidate/version;
   - video SHA;
   - YouTube video ID / Shorts URL;
   - `youtube_privacy: private`;
   - `website_link_allowed: false`.
4. Generate the companion page and start-frame thumbnail from the approved preview.
5. Run website build / production QA.
6. Browser-check the new red-flag route and console.
7. Confirm the private YouTube ID does not appear in built visitor HTML.
8. Commit/push website changes.

## Pitfall

If the user asks “did you update the website?” after a private upload, verify filesystem/build state before answering. If missing, update it immediately. Do not claim the site was updated from the upload alone.