Setup Snapshot
Setup Snapshot is the frozen record of how the project was configured at cutover. When the Go Live finalize step completes, GSS captures a point-in-time snapshot of every resource binding, every profile_config field, and every check_run row across all setup stages. That snapshot is what the Snapshot page renders.
When the page is available
Post-live only. Before cutover finalizes, the Setup Snapshot sidebar item is hidden and navigating directly to the URL redirects to the active Setup page. The item becomes visible as a sub-item under Overview once the project's Go Live state is completed.
What the page shows
- Header — "Setup Snapshot" with a subtitle showing when the snapshot was captured at Go Live and when setup completed.
- Stages status panel — a six-node stepper (Audit, Build, Cloud, Connect, Publish, Go Live) showing each stage's frozen verification state at finalize. Each node anchor-links into the matching section below.
- Frozen detail sections, in order:
- Audit — audit captured timestamp, web container scanned, tags scanned, events scanned.
- Connect — GCP project, GTM web + server containers, GA4 properties (browser + server).
- Server — Cloud Run tagging + preview services, custom server domain, container image.
- Tagging — container config (masked), web + server mirror-pipeline workspaces, DNS check status.
- Validate — publish confirmed timestamp, plus any legacy verify checks captured (pre-Phase-4 archives only).
- Publish — published-at timestamp, web/server container published versions, web/server prior versions.
- Go Live — cutover completed timestamp, pre-cutover snippet target, post-cutover web + server live versions.
Section labels group artifacts by what shipped (resources, infrastructure, configuration) rather than by the setup pipeline's stage names — e.g. GCP project lives under "Connect", Cloud Run services under "Server".
How it differs from /setup
The live Setup pipeline (/p/{slug}/setup) renders the project's current state. Setup Snapshot renders the project's frozen state. If you have re-bound a resource post-live or accepted a binding change, the live Setup page reflects the new value; Setup Snapshot still shows the value at cutover. Pair this with Changes to see what has drifted.
When to use Setup Snapshot
- Compliance review — what configuration shipped to production?
- Engineering handoff — what bindings should I expect to see on this project?
- Forensics after a change — what did the configuration look like before the drift?
- Re-running a similar project — copy the snapshot's choices into a new project.