Add blume-search extension

[olavblj]

Description

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Greptile Summary

This PR adds a macOS Raycast extension that launches Blume’s bundled local search helper and presents projects, conversations, messages, setup artifacts, and suggestions in a searchable list.

• Adds helper discovery, process lifecycle management, protocol parsing, deep-link generation, and category filtering.
• Adds focused tests, extension assets, package configuration, documentation, and initial release notes.

Confidence Score: 4/5

The preferred-application validation defect should be fixed before merging because the unrestricted picker can route helper startup through a non-Blume application; the remaining findings are submission and configuration issues.

The automatic discovery path restricts applications to supported Blume bundle IDs, but the preferred path bypasses that guard and passes the selected application directly into executable discovery and spawning.

Files Needing Attention: extensions/blume-search/src/blumeSearchClient.ts, extensions/blume-search/package.json, extensions/blume-search/CHANGELOG.md, extensions/blume-search/eslint.config.cjs, extensions/blume-search/src/search.tsx

Important Files Changed

Filename	Overview
extensions/blume-search/src/blumeSearchClient.ts	Resolves stable or canary Blume installations and creates the helper client, but trusts a preferred appPicker value without validating its bundle ID.
extensions/blume-search/src/helperProcessClient.ts	Implements helper process startup, handshake fallback, request supersession, response limits, timeouts, parsing, and cleanup.
extensions/blume-search/src/protocol.ts	Defines protocol-v1 request and result DTOs and validates helper response frames, with partial validation of category-specific fields.
extensions/blume-search/src/search.tsx	Implements the searchable Raycast list, category filter, helper lifecycle, result actions, and error states while manually duplicating preference typing.
extensions/blume-search/src/searchModel.ts	Maps result categories to assets, subtitles, filters, and stable or canary Blume deep links.
extensions/blume-search/package.json	Declares the macOS view command, app picker, dependencies, and scripts but omits the required schema and screenshot metadata.
extensions/blume-search/CHANGELOG.md	Adds initial release notes with a hardcoded date instead of the required merge-date placeholder.
extensions/blume-search/eslint.config.cjs	Adds an ESLint v9 flat configuration without the repository-required defineConfig wrapper.

Prompt To Fix All With AI

### Issue 1
extensions/blume-search/src/blumeSearchClient.ts:12
**Preferred app bypasses validation**

When a user selects a non-Blume application in the app picker, `resolveBlumeApplication` returns it without validating its bundle ID, so its path is used to locate and launch an executable under `ELECTRON_RUN_AS_NODE`, causing the wrong application to be launched or a misleading update error.

```suggestion
  if (preferred) {
    if (!preferred.bundleId || !BLUME_BUNDLE_IDS.includes(preferred.bundleId)) {
      throw new Error("Choose Blume or Blume Canary in extension preferences.");
    }
    return preferred;
  }
```

### Issue 2
extensions/blume-search/package.json:27
**View command lacks screenshots**

The new view-type command has no `metadata` folder containing Raycast-styled screenshots, leaving the extension without the Store presentation assets required for view commands.

### Issue 3
extensions/blume-search/CHANGELOG.md:1
**Changelog hardcodes release date**

The Initial Release heading hardcodes `2026-08-14` instead of `{PR_MERGE_DATE}`, preventing release automation from inserting the actual merge date.

```suggestion
## [Initial Release] - {PR_MERGE_DATE}
```

### Issue 4
extensions/blume-search/package.json:1-2
**Manifest omits schema declaration**

The new extension manifest omits the Raycast `$schema` reference, so contributors lose manifest-specific autocomplete and schema validation.

```suggestion
{
  "$schema": "https://www.raycast.com/schemas/extension.json",
  "name": "blume-search",
```

### Issue 5
extensions/blume-search/eslint.config.cjs:1-8
**ESLint config skips defineConfig**

This ESLint v9 flat configuration exports its array directly instead of using `defineConfig` from `eslint/config`, bypassing the repository’s supported normalization pattern for nested preset arrays.

```suggestion
const { defineConfig } = require("eslint/config");
const raycastConfig = require("@raycast/eslint-config");

module.exports = defineConfig([
  {
    files: ["src/**/*.{js,jsx,ts,tsx}"],
  },
  ...raycastConfig.flat(),
]);
```

### Issue 6
extensions/blume-search/src/search.tsx:25-30
**Preferences type is duplicated**

The command manually declares `Preferences` even though Raycast generates that type from the manifest, creating a second preference contract that can drift when the application preference changes.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Add blume-search extension" | Re-trigger Greptile}

[greptile-apps]

Preferred app bypasses validation

When a user selects a non-Blume application in the app picker, resolveBlumeApplication returns it without validating its bundle ID, so its path is used to locate and launch an executable under ELECTRON_RUN_AS_NODE, causing the wrong application to be launched or a misleading update error.

Suggested change

	if (preferred) return preferred;
	if (preferred) {
	if (!preferred.bundleId || !BLUME_BUNDLE_IDS.includes(preferred.bundleId)) {
	throw new Error("Choose Blume or Blume Canary in extension preferences.");
	}
	return preferred;
	}

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/blume-search/src/blumeSearchClient.ts
Line: 12

Comment:
**Preferred app bypasses validation**

When a user selects a non-Blume application in the app picker, `resolveBlumeApplication` returns it without validating its bundle ID, so its path is used to locate and launch an executable under `ELECTRON_RUN_AS_NODE`, causing the wrong application to be launched or a misleading update error.

```suggestion
  if (preferred) {
    if (!preferred.bundleId || !BLUME_BUNDLE_IDS.includes(preferred.bundleId)) {
      throw new Error("Choose Blume or Blume Canary in extension preferences.");
    }
    return preferred;
  }
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[greptile-apps]

View command lacks screenshots

The new view-type command has no metadata folder containing Raycast-styled screenshots, leaving the extension without the Store presentation assets required for view commands.

Rule Used: What: Extensions with view-type commands must incl... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/blume-search/package.json
Line: 27

Comment:
**View command lacks screenshots**

The new view-type command has no `metadata` folder containing Raycast-styled screenshots, leaving the extension without the Store presentation assets required for view commands.

**Rule Used:** What: Extensions with view-type commands must incl... ([source](https://app.greptile.com/raycast/-/custom-context?memory=87059ac1-c601-487f-9f1c-bce8a3cb6209))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Changelog hardcodes release date

The Initial Release heading hardcodes 2026-08-14 instead of {PR_MERGE_DATE}, preventing release automation from inserting the actual merge date.

Suggested change

	## [Initial Release] - 2026-08-14
	## [Initial Release] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE}... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/blume-search/CHANGELOG.md
Line: 1

Comment:
**Changelog hardcodes release date**

The Initial Release heading hardcodes `2026-08-14` instead of `{PR_MERGE_DATE}`, preventing release automation from inserting the actual merge date.

```suggestion
## [Initial Release] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}`... ([source](https://app.greptile.com/raycast/-/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[greptile-apps]

Manifest omits schema declaration

The new extension manifest omits the Raycast $schema reference, so contributors lose manifest-specific autocomplete and schema validation.

Suggested change

	{
	"name": "blume-search",
	{
	"$schema": "https://www.raycast.com/schemas/extension.json",
	"name": "blume-search",

Rule Used: What: Require Raycast extension projects to includ... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/blume-search/package.json
Line: 1-2

Comment:
**Manifest omits schema declaration**

The new extension manifest omits the Raycast `$schema` reference, so contributors lose manifest-specific autocomplete and schema validation.

```suggestion
{
  "$schema": "https://www.raycast.com/schemas/extension.json",
  "name": "blume-search",
```

**Rule Used:** What: Require Raycast extension projects to includ... ([source](https://app.greptile.com/raycast/-/custom-context?memory=9c275ba8-ead2-4952-b909-12275352b16b))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

ESLint config skips defineConfig

This ESLint v9 flat configuration exports its array directly instead of using defineConfig from eslint/config, bypassing the repository’s supported normalization pattern for nested preset arrays.

Suggested change

	const raycastConfig = require("@raycast/eslint-config");
	module.exports = [
	{
	files: ["src/**/*.{js,jsx,ts,tsx}"],
	},
	...raycastConfig.flat(),
	];
	const { defineConfig } = require("eslint/config");
	const raycastConfig = require("@raycast/eslint-config");
	module.exports = defineConfig([
	{
	files: ["src/**/*.{js,jsx,ts,tsx}"],
	},
	...raycastConfig.flat(),
	]);

Rule Used: What: In ESLint v9+, defineConfig is exported fr... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/blume-search/eslint.config.cjs
Line: 1-8

Comment:
**ESLint config skips defineConfig**

This ESLint v9 flat configuration exports its array directly instead of using `defineConfig` from `eslint/config`, bypassing the repository’s supported normalization pattern for nested preset arrays.

```suggestion
const { defineConfig } = require("eslint/config");
const raycastConfig = require("@raycast/eslint-config");

module.exports = defineConfig([
  {
    files: ["src/**/*.{js,jsx,ts,tsx}"],
  },
  ...raycastConfig.flat(),
]);
```

**Rule Used:** What: In ESLint v9+, `defineConfig` is exported fr... ([source](https://app.greptile.com/raycast/github/raycast/extensions/-/custom-context?memory=ded2e079-95d0-44a7-80b5-83bbe04916f5))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Preferences type is duplicated

The command manually declares Preferences even though Raycast generates that type from the manifest, creating a second preference contract that can drift when the application preference changes.

Rule Used: What: Don't manually type getPreferenceValues() ... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/blume-search/src/search.tsx
Line: 25-30

Comment:
**Preferences type is duplicated**

The command manually declares `Preferences` even though Raycast generates that type from the manifest, creating a second preference contract that can drift when the application preference changes.

**Rule Used:** What: Don't manually type `getPreferenceValues()` ... ([source](https://app.greptile.com/raycast/-/custom-context?memory=61aa4fa9-b8e8-41b4-8b27-f888b95b75af))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!