[steve-calvert-glean]

Problem

Some deployments serve Glean's document search tool as enterprise_search instead of search. The bundled skills and the Cursor rule only say search, so on those deployments they name a tool that isn't in the tool list. using-glean also says tool names are "always consistent across deployments", which is no longer true.

Change

• Add a pluginpack partial, partials/search-tool-name.md, that says both names are the same tool with the same parameters, and to use whichever one the tool list shows.
• Set source.partials in pluginpack.config.ts.
• Include {{> search-tool-name}} once in each skill and rule that names the tool: using-glean (and its reference/search.md), plan-prep, project-awareness, project-handoff, using-glean-code, using-glean-productivity, search, skill-creation-guide (shared and the Codex override), and the Cursor glean-tool-selection rule.
• Correct the "always consistent" sentence in using-glean.

Inline mentions of search stay as they are. One note per file covers them, and the source stays readable. When every deployment serves one name, we update the partial and rebuild.

This complements #32, which handles the tool name in the local MCP server.

Testing

• npm test (build + pluginpack validate for claude, cursor, and codex) passes.
• Diffed dist/ against a build of main: 28 files changed (9 skill files × 3 targets, plus the Cursor rule). Every change adds the note, except the one corrected sentence in using-glean. No unresolved {{> tags remain in dist/.

[steve-calvert-glean]

Closing because this is now obsolete. Since 1024d08, the plugin lists Glean search as search on every deployment, including deployments that serve it as enterprise_search. Skills can always say search.