feat: add Ona as a supported platform

[meysholdt]

What

Add Ona as a supported platform in the BMAD installer.

Why

Ona is an AI development environment that supports repository-level skills via .ona/skills/<name>/SKILL.md files. The skill format (YAML frontmatter with name and description, followed by Markdown content) aligns with BMAD's existing skill_format: true output.

Changes

• tools/cli/installers/lib/ide/platform-codes.yaml — Add ona platform entry with installer config (target_dir: .ona/skills, template_type: default, skill_format: true)
• tools/platform-codes.yaml — Add ona metadata entry to keep both config files in sync
• test/test-installation-components.js — Add Test Suite 32 with 16 assertions covering config validation, install, detection, frontmatter format, and reinstall

No JavaScript changes needed — ConfigDrivenIdeSetup and IdeManager pick up the new entry automatically.

Fixes #1967

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR adds Ona as a supported IDE platform in the BMAD installer system, configuring it to generate .ona/skills/<name>/SKILL.md files. It adds the platform entry to two configuration files and includes a comprehensive test suite validating installation behavior, skill detection, and SKILL.md output format.

Changes

Cohort / File(s)	Summary
Platform Configuration tools/cli/installers/lib/ide/platform-codes.yaml, tools/platform-codes.yaml	Added Ona platform entry with target directory .ona/skills, default template type, and skill format enabled. Entry mirrors across both configuration files.
Test Suite test/test-installation-components.js	Added Suite 32 for Ona Native Skills, verifying installer configuration, IDE detection before/after install, SKILL.md frontmatter (name/description) and content validation, and reinstall/upgrade behavior on existing projects.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat: add pi coding agent as supported platform #1854: Adds a different IDE platform entry (codebuddy) using the identical pattern of modifying configuration files and adding a corresponding test suite.
• feat: add CodeBuddy platform support #1483: Modifies the same platform registry files to add a new IDE platform entry (codebuddy), sharing the same configuration-driven approach.

Suggested reviewers

• alexeyv
• bmadcode

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: adding Ona as a supported platform in the BMAD installer.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, explaining the what, why, and changes made to support Ona platform integration.
Linked Issues check	✅ Passed	The PR fully implements the requirements from issue #1967: adds ona entry to platform-codes.yaml with correct installer config, updates both sync files, and includes comprehensive tests.
Out of Scope Changes check	✅ Passed	All changes are directly related to adding Ona as a supported platform; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

You can disable sequence diagrams in the walkthrough.

Disable the reviews.sequence_diagrams setting to disable sequence diagrams in the walkthrough.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@tools/platform-codes.yaml`:
- Around line 130-134: The YAML entry for the `ona` platform currently sets
category: ide but the PR intends `category: cli`; update the `ona` entry's
category field from "ide" to "cli" (i.e., change the value under the `ona:`
block) and confirm with the product owner if the category should instead remain
"ide" before committing; ensure the changed symbol is the `ona` mapping so it
matches other terminal tools like `auggie`, `claude-code`, and `gemini`.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: baacce64-7bf1-4670-abab-53a1c0293bf4

📥 Commits

Reviewing files that changed from the base of the PR and between d2f15ef and df4d53d.

📒 Files selected for processing (3)

• test/test-installation-components.js
• tools/cli/installers/lib/ide/platform-codes.yaml
• tools/platform-codes.yaml

[meysholdt]

Re: CodeRabbit's comment on category: ide vs category: cli — this is intentional. The issue's proposed config was a suggestion; we chose category: ide deliberately since Ona is a full development environment, not a standalone CLI tool. Both YAML files are consistent with each other.