Remove hub/source-control and customize/deep-dives/slash-commands from docs.json

[continue]

This PR removes two sections from the docs.json file:

1. hub/source-control from the Hub section navigation
2. customize/deep-dives/slash-commands from the Deep Dives section navigation

---

This agent session was co-authored by bekah-hawrot-weigel and Continue.

---

Summary by cubic

Removed hub/source-control and customize/deep-dives/slash-commands from docs.json to clean up the sidebar and prevent dead links. This hides these deprecated pages from the Hub and Deep Dives navigation.

^{Written for commit bdd3e4d. Summary will update automatically on new commits.}

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[cubic-dev-ai]

No issues found across 1 file

[continue]

CI Failure Analysis

The failing test should load model from real hub: openai/gpt-5 is experiencing an intermittent HTTP 502: Bad Gateway error when making a real API call to the Hub.

This failure is unrelated to the docs.json changes, which only remove two navigation entries:

• hub/source-control from Hub section
• customize/deep-dives/slash-commands from Deep Dives section

Evidence this is a flaky test:

1. The test makes real HTTP requests to external services
2. Recent main branch runs show the same CLI test failures
3. The 502 error is a server-side issue with the Hub API, not a code issue

Resolution options:

1. Re-run the failed test (maintainer access required)
2. The test should pass on retry if Hub API is healthy
3. This is a documentation-only change with zero impact on CLI functionality

My changes are confined to docs/docs.json and do not touch any code paths related to hub loading or CLI tests.

[sestinj]

🎉 This PR is included in version 1.29.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.34.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀