feat(nav): add Software Packs to the site navigation

[jbouder]

Reference Issues or PRs

Depends on nebari-dev/starlight#39, released in @nebari/starlight 1.2.0.

What does this implement/fix?

Adds a Software Packs entry to the site nav, pointing at https://packs.nebari.dev. It renders as the last item in the header tabs, the mobile drawer, and the footer's Documentation column, and opens in a new tab.

The theme previously prefixed every nav href with the site base, which turned an absolute URL into /https://packs.nebari.dev. That's fixed upstream in 1.2.0 (isExternalNavHref / navHref), so this branch is just the dependency bump plus one line of config — no local component overrides needed.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

bun run build passes with link validation clean, and bun test test is 6/6 — including the existing check that every internal href resolves, which is what catches a mangled external link. Verified in the built HTML and in a local preview that the header, drawer, and footer all render href="https://packs.nebari.dev" with target="_blank" rel="noopener noreferrer", in the order Docs · Community · Software Packs.

No new tests: the behavior under test lives in the theme package, where nebari-dev/starlight#39 added unit and build coverage for it.

Documentation

No docs change — this is a nav entry, not a documented feature of the site.

Access-centered content checklist

Text styling

• The content is written with plain language (where relevant).
• If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• All links describe where they link to (for example, check the Nebari website).
• This content adheres to the Nebari style guides.

Non-text content

• All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing GIFs or videos.
• If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

The new tab is the theme's behavior for external nav entries, applied uniformly in 1.2.0.

🤖 Generated with Claude Code

[github-actions]

Docs preview for add-software-packs-nav (via the nebari-docs Worker):
https://add-software-packs-nav-nebari-docs.openteams-account.workers.dev