fix(search): scope developer search guidance and remove github category

[Max17190]

Why

Search help should surface query-relevant highlights and distinguish public developer-index lookup from local code inspection. The search skill description should focus on source discovery. Category guidance and validation should expose supported choices.

Summary

• Surface query-relevant highlights in the search command description and README, preserving existing tool-discovery guidance. Define highlights as page excerpts in the flag help, with defaults and availability details.
• Retain --no-highlights for original snippets and --scrape for full-page content.
• Clarify public developer-index coverage in help, documentation, and the search skill.
• Narrow the developer-index skill's discovery description to public-source lookup for external documentation and upstream evidence. Its body is unchanged.
• Describe highlights as query-relevant excerpts from the page in the search skill.
• Focus the search skill description on source discovery with query-relevant excerpts and optional full-page content. Keep specialized-index links in the search skill body. The scrape skill is unchanged.
• Remove github from category validation, types, and examples. Supported categories are research, pdf, and developer.
• Cover rejection of github and supported categories in built CLI help.
• Keep search execution and response formats unchanged apart from category validation.

Test Plan

• pnpm run build
• pnpm run type-check
• pnpm run format:check
• env -u FIRECRAWL_API_KEY pnpm test: 594 tests passed locally after merging current main.
• Verify highlights and supported categories in built CLI help.
• Validate developer-index and search skill frontmatter and formatting.
• Verify the scrape skill is byte-for-byte identical to the PR base.
• git diff --check

[cubic-dev-ai]

All reported issues were addressed across 6 files

<sub>Shadow auto-approve: would not auto-approve because issues were found.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 5 files (changes from recent commits).

<sub>Shadow auto-approve: would not auto-approve because issues were found.
Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 4 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would not auto-approve. Auto-approval blocked by 1 unresolved issue from previous reviews.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 5 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would not auto-approve. Auto-approval blocked by 1 unresolved issue from previous reviews.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 1 file (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would not auto-approve. Auto-approval blocked by 1 unresolved issue from previous reviews.

Re-trigger cubic</sub>

[Max17190]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@Max17190 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 6 files

<sub>Shadow auto-approve: would not auto-approve because issues were found.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 5 files (changes from recent commits).

<sub>Shadow auto-approve: would not auto-approve because issues were found.
Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 6 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Removes github from accepted search categories (CLI validation/types/tests) and updates search/developer docs. --categories github now errors, so this is a user-visible behavior change that needs product/breaking-change sign-off.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 2 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Removes github from accepted search categories and updates help/docs/tests; existing --categories github calls now error. This is a public CLI contract change justified by the PR description rather than server-side evidence, so product sign-off is needed.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 3 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Removes github from accepted search categories and updates help, docs, types, and tests; existing --categories github calls now fail. This is a public CLI contract change lacking server-side evidence that github was unsupported, so human sign-off is needed.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 2 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Removes github from search categories and updates help, docs, and skill descriptions; existing --categories github calls now error. This public CLI contract change lacks server-side evidence that github was unsupported, so human review is needed.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 2 files (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Removes github from search categories and updates help/docs/skill descriptions; existing --categories github invocations now error. This public CLI contract change lacks server-side evidence that github was unsupported, so human review is needed.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 1 file (changes from recent commits).

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Removes github from search category validation, types, and docs; --categories github now errors. This public CLI contract change lacks server-side evidence that the category was unsupported, so human sign-off is needed.

Re-trigger cubic</sub>

[Max17190]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@Max17190 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 7 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Removes github from search category validation, types, and docs, so existing --categories github calls now error. Docs and tests are updated, but the diff lacks server-side evidence that the category is unsupported, so this public CLI contract change needs human sign-off.

Re-trigger cubic</sub>