chore: add generated slash command bridge files for Kit repo

[emredursun]

Summary

• Add 75 generated bridge files for Kit repo's own development (25 workflows x 3 IDEs)
• Completes the v5.2.0 bridge generation feature for the Kit repo itself
• These files were generated by kit init --force and are now tracked via the gitignore negation patterns from PR chore: track .claude/commands/ in Kit repo for worktree support #19

Files

Directory	Files	IDE
.claude/commands/	25	Claude Code / Antigravity
.cursor/commands/	25	Cursor
.opencode/commands/	25	OpenCode

Note

These files are not included in the npm package (package.json files field only includes bin/, lib/, .agent/). End users get bridges generated at runtime by lib/command-bridge.js when they run kit init. This PR only affects Kit repo contributors working in worktrees.

Test Plan

• All files have provenance header (<!-- devran-kit-bridge v5.2.0 -->)
• Descriptions extracted from workflow frontmatter
• 982/982 tests passing (no code changes)

[gemini-code-assist]

Code Review

This pull request introduces a series of bridge command files across .claude, .cursor, and .opencode directories to facilitate the execution of Devran AI Kit workflows. The review feedback highlights an opportunity to improve IDE compatibility by ensuring YAML frontmatter is placed at the very beginning of the files and suggests using backticks for file paths to enhance AI recognition.

[gemini-code-assist]

To ensure that IDEs like Claude Code correctly parse the YAML frontmatter, the --- block should be the very first content in the file. Moving the provenance header below the frontmatter improves IDE compatibility. Additionally, consider wrapping the workflow path in backticks (e.g., .agent/workflows/brainstorm.md) to help the AI agent identify it as a file path. This improvement should be applied to all generated bridge files in this directory.

Suggested change

	<!-- devran-kit-bridge v5.2.0 -->
	---
	description: "Structured brainstorming. Explore options before committing to implementation."
	---
	Execute the /brainstorm workflow from the Devran AI Kit.
	Read and follow the full instructions in .agent/workflows/brainstorm.md.
	---
	description: "Structured brainstorming. Explore options before committing to implementation."
	---
	<!-- devran-kit-bridge v5.2.0 -->
	Execute the /brainstorm workflow from the Devran AI Kit.
	Read and follow the full instructions in .agent/workflows/brainstorm.md.

[gemini-code-assist]

The YAML frontmatter should be placed at the top of the file for proper parsing by the IDE. The provenance header should be moved below the frontmatter block. Also, wrapping the workflow file path in backticks is recommended for better AI recognition. This improvement should be applied to all generated bridge files in this directory.

Suggested change

	<!-- devran-kit-bridge v5.2.0 -->
	---
	description: "Structured brainstorming. Explore options before committing to implementation."
	---
	Execute the /brainstorm workflow from the Devran AI Kit.
	Read and follow the full instructions in .agent/workflows/brainstorm.md.
	---
	description: "Structured brainstorming. Explore options before committing to implementation."
	---
	<!-- devran-kit-bridge v5.2.0 -->
	Execute the /brainstorm workflow from the Devran AI Kit.
	Read and follow the full instructions in .agent/workflows/brainstorm.md.