[TooGood007]

Seer links chat answers to Sentry pages using a snapshot of the nav, which Seer
builds by downloading this repo's frontend source and parsing it. The snapshot
only updates when someone reruns that in Seer, so a renamed or moved page leaves
Seer linking to the old route.

Port Seer's parser into tools/seer_nav so the snapshot can be built from this
checkout. It reads the secondary nav, settings nav configs (including gsApp
billing), issue taxonomy and route tree, and records the conditions each page is
shown under (feature flags, deployment, org settings) as data.

python -m tools.seer_nav.generate_snapshot writes the snapshot only when its
pages change; --check writes nothing and exits 1 with the command to update it.
No snapshot is committed yet and nothing runs it. That comes in follow-up PRs
along with the RPC Seer will read it from. On the current frontend it produces
the same 122 pages as Seer's committed snapshot.

[sentry-junior]

The port itself is solid. I ran it against this branch and got the same 122 entries the description claims, and all 21 tests pass under make test-tools. Two things before this leaves draft:

• test_parses_this_checkout parses the real static/ tree, and check_alias_sources raises SystemExit once utils/seer/showNewSeer.ts or orgHasNewSeerPlan.ts changes. But tests/tools only runs in the dev env workflow (make test-tools), and that workflow only triggers on tools/** and a few other paths, not static/**. Backend shards skip it too (IGNORED_DIRS in calculate-backend-test-shards.py). So a frontend PR that changes showNewSeer.ts, or reshapes a nav config the live test depends on, merges green. Then the next unrelated PR that touches tools/** fails on it. I reproduced this by adding a non-comment line to showNewSeer.ts: the test fails with the alias-hash SystemExit. Either add the parsed source paths to the dev env workflow's paths: (secondary nav sections, the settings nav configs, utils/seer/, router/routes.tsx, issueList/taxonomies.tsx, gsApp/overrides/useBillingNavigationConfig.tsx), or hold the live-checkout test until the follow-up adds a --check job that runs on static/ changes.
• Not something this PR made worse, since it matches Seer's current snapshot, but you should know about it before the snapshot starts gating anything: the Insights section (Frontend/Backend/Mobile/Agents/MCP) and the Seer section produce no entries, and nothing reports it. In _secondary_nav_entries, baseUrl is kept raw, so ${DOMAIN_VIEW_BASE_URL} never resolves and _org_relative_path drops the link. The Insights labels are also {FRONTEND_SIDEBAR_LABEL}-style constants, not {t('...')}, so labels is empty. Seer's links use plain variables (to={automationsPath}). The only guard is "zero entries total". A cheap one: fail when a *SecondaryNavigation.tsx with SecondaryNavigation.Links produces zero entries, so silent drops show up in --check instead of as missing Seer links.

[joseph-sentry]

This test parses the real static/ tree, but tests/tools only runs in the dev env workflow, which doesn't trigger on static/**. So a frontend PR that changes showNewSeer.ts (alias hash) or a nav config merges green, and the next unrelated tools/ PR fails here.

Possible fix: skip this test until the follow-up --check job that runs on static/ changes lands, or add the parsed frontend paths to the dev env workflow's paths:.

This comment was generated with Claude Code.