Pack the job, not the private environment
Include the approved source notes, task boundary, selected context, first brief, separate review finding, corrected final brief, checkpoint history, and a short source index. Use readable formats and stable relative links.
Exclude account identities, credentials, machine descriptions, private locations, raw traces, provider telemetry, and unrelated domain material. The export should explain the job without reproducing the environment that created it.
Open the synthetic bundle somewhere else
The workshop package begins with one source note. The initial brief states “Saturday sessions are available.” Review identifies the unsupported schedule, and the corrected brief removes that sentence.
The export preserves both brief versions, the finding, and the checkpoint. A reader can locate the source for every retained detail and see that schedule and price remain unknown.
The bundle proves only that the synthetic artifacts remain readable and connected after they move. It does not prove a hosted service, universal tool support, or a business result.
Test the move without special access
Copy the bundle into a clean folder. Open the source index first. Follow every relative link, identify the current final brief, locate the rejected claim, and state the next allowed action.
Stop if understanding the result requires a private account, an earlier conversation, or an undocumented location. Add the missing reader-safe artifact before moving the job again.
This export fits work that another person or tool may inspect later. It is excessive for disposable output with no source or correction value.