Skip to content

chore(nav): drop the Sandbox concept - #358

Open
jirhiker wants to merge 1 commit into
stagingfrom
chore/remove-sandbox-concept
Open

chore(nav): drop the Sandbox concept#358
jirhiker wants to merge 1 commit into
stagingfrom
chore/remove-sandbox-concept

Conversation

@jirhiker

@jirhiker jirhiker commented Aug 22, 2026

Copy link
Copy Markdown
Member

What

Removes the Sandbox concept from the app and the docs. No replacement nav group in this PR — the geothermal nav group lands separately.

Why

The Sandbox group mixed a typography specimen with three WIP geothermal grids, and its visibility flag treated staging as a place to try things out. Preview deploys are the sandbox — a PR preview can run against an ephemeral API nobody else shares. staging is a pre-production release branch: what lands there is a candidate for production.

Changes

Nav

  • Removed the Sandbox nav group (ExampleNavItem) and the SHOW_EXAMPLE_NAV flag it was gated on.
  • The pages it linked stay routable by URL: /example/typography, /geothermal/wells/records-grid, /geothermal/wells/inventory, /geothermal/wells/temp-depth. Routes and pages are untouched.

Sandbox resource

  • Removed the Sandbox access-control resource and its branch in the resource switch.
  • ocotillo.hydrograph-correction no longer sets parent: 'Sandbox' — it was nested under a group that no longer exists, and it is already top-level in RESOURCE_NAV.
  • Removed the name === 'Sandbox' label special-case in the Refine sider.
  • Removed the two Sandbox access-control test cases and the isResourceListAdminOnly('Sandbox') assertion.

Docs

  • AGENTS.md: new "Where unfinished work gets exercised" section — previews are the sandbox, staging is a pre-production release branch, and WIP gates key off dev or preview only (as recordsGridLogic.ts already does). Do not add a staging arm.
  • access-control-ruleset.md, geothermal-well-inventory.md, geothermal-well-search-contract.md, and the picker doc comments updated.
  • preview-deployments.md keeps its "sandbox" wording — there it means preview-as-sandbox, which is the point.

Follow-up

A Geothermal nav group for Records / Inventory / Temp-Depth is deliberately left out of this PR.

Verification

  • npm run typecheck clean.
  • Biome diagnostic counts on the touched files are unchanged from the base (AppShell.tsx carries pre-existing format debt; unrelated lines were not reformatted).
  • accessControl.test.ts 36/36 pass. The 12 failing files repo-wide are the ECONNREFUSED 127.0.0.1:4010 contract tests that need the Prism mock (npm run mock:server:cypress); they are untouched by this change.
  • Checked live on the dev server: sidebar ends at Hydrograph Correction, no Sandbox entry, /geothermal/wells/records-grid still loads by URL, no console errors.

🤖 Generated with Claude Code

The Sandbox nav group mixed a typography specimen with three WIP geothermal
grids, and its visibility flag treated staging as a place to try things out.
Previews are the sandbox now: a PR preview can run against an ephemeral API
nobody else shares, while staging is a pre-production release branch.

- Remove the Sandbox nav group and its SHOW_EXAMPLE_NAV flag. The pages it
  linked (/example/typography and the three geothermal grids) stay routable by
  URL; a geothermal nav group lands separately.
- Remove the Sandbox access-control resource, the 'Sandbox' parent on
  ocotillo.hydrograph-correction, and the Sandbox label case in the Refine
  sider.
- Document the staging-vs-preview rule in AGENTS.md and update the docs that
  described nav placement as Sandbox.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@jirhiker
jirhiker force-pushed the chore/remove-sandbox-concept branch from 482705b to 1e7b505 Compare August 22, 2026 18:09
@jirhiker jirhiker changed the title chore(nav): drop the Sandbox concept for a Geothermal nav group chore(nav): drop the Sandbox concept Aug 22, 2026
@github-actions

Copy link
Copy Markdown

1 similar comment
@github-actions

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant