docs: reorder mission-control sections in docs.json

[continue]

Summary

Moved the Integrations section to appear directly after Workflows in the Mission Control navigation menu for better logical flow and user experience.

Changes

• Reordered the Mission Control pages in docs/docs.json
• New order: tasks → workflows → integrations → metrics → sharing → governance → secrets → configs

This makes the navigation more intuitive as users typically configure workflows before setting up integrations.

---

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

---

Summary by cubic

Reordered Mission Control navigation so Integrations appears directly after Workflows for a clearer setup flow and easier discovery.

• Refactors
  • Updated docs/docs.json to set order: tasks → workflows → integrations → metrics → sharing → governance → secrets.

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

[cubic-dev-ai]

No issues found across 1 file

[continue]

CI Test Failures - Not Related to Changes

The failing macOS tests are infrastructure issues unrelated to the docs.json changes:

Root Causes:

1. macOS Node 18/20: Sharp library download failed with 503 Service Unavailable from GitHub (transient network error)
2. macOS Node 24: Flaky UI test in TUIChat.editMessage.test.tsx

Evidence:

• Recent main branch runs also show CLI PR Check failures
• No code changes were made - only JSON reordering in docs/docs.json
• All other 50+ checks passed successfully including:
  • ✅ Mintlify Deployment & Validation
  • ✅ All Ubuntu & Windows tests
  • ✅ macOS Node 22 tests
  • ✅ All e2e tests
  • ✅ Security & compliance checks

Retriggering CI by pushing empty commit to retry the flaky macOS tests.

[continue]

Request for Maintainer Review

The macOS CLI tests continue to fail due to infrastructure issues unrelated to this docs-only PR:

Issue Details:

• Change: Only reordered JSON in docs/docs.json (no code changes)
• Problem: Sharp library fails to download on macOS runners (503 Service Unavailable)
• Impact: Blocks PR merge despite all relevant checks passing

Successful Checks (50+):

✅ Mintlify Deployment - Docs build and deploy successful
✅ Mintlify Validation - Link rot & content validation passed
✅ All Ubuntu tests - Node 18, 20, 22, 24
✅ All Windows tests - Node 18, 20, 22, 24
✅ macOS Node 22 - Passed
✅ All e2e tests - Passed
✅ Security & compliance - All passed

Failed Checks:

❌ macOS Node 18 - Sharp download 503 error
❌ macOS Node 20 - Sharp download 503 error

Comparison:

Recent docs PR #8797 passed all checks. The difference is timing - GitHub/npm registry had intermittent availability issues.

Recommended Action:

Since this is a docs-only change with Mintlify validation passing, could a maintainer either:

1. Approve and merge despite flaky macOS tests, or
2. Re-run the failed jobs manually, or
3. Add path filtering to skip CLI tests for docs/** changes

cc @maintainers

[continue]

Root Cause Analysis & Solution

Current Situation

This PR modifies only docs/docs.json but triggers full CLI test suite including macOS builds that are currently experiencing infrastructure failures.

Problem

The cli-pr-checks.yml workflow runs for all PRs without path filtering:

on:
  pull_request:
    branches: [main]

This causes unnecessary test runs for docs-only changes and blocks PRs when unrelated infrastructure fails.

Proposed Solution

Add path filtering to cli-pr-checks.yml:

on:
  pull_request:
    branches: [main]
    paths-ignore:
      - 'docs/**'
      - '*.md'
      - '.github/workflows/preview.yaml'

Benefits

1. Faster CI - Docs PRs don't wait for 24 CLI test matrix jobs
2. Reduced failures - Docs PRs won't be blocked by unrelated infrastructure issues
3. Cost savings - Fewer unnecessary compute minutes
4. Better DX - Docs contributors get faster feedback

Immediate Action Needed

For this PR specifically:

• ✅ Mintlify validation passed (the relevant check for docs)
• ✅ All other 50+ checks passed
• ❌ Only macOS CLI tests failing (infrastructure issue, not code)

Recommendation: Merge this PR and create a follow-up to add path filtering to the workflow.

Would a maintainer be able to approve/merge despite the flaky macOS tests?

[sestinj]

🎉 This PR is included in version 1.6.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.36.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀