fix: include missing tool-specific fields in RulesyncRule.fromFile

[yhorikawa]

Summary

• Fix RulesyncRule.fromFile to include claudecode, copilot, and antigravity tool-specific fields when constructing the frontmatter object
• cursor and agentsmd were already included, but the other tool-specific fields were missing
• Add tests to verify copilot and claudecode frontmatter loading

Background

When tool-specific configuration (e.g., copilot.excludeAgent, claudecode.paths) was defined in a rule file's frontmatter, these fields were not copied during the fromFile object construction, so they were silently dropped and never reflected in the generated output.

Related: #1259

Test plan

• Add test for copilot frontmatter configuration loading
• Add test for claudecode frontmatter configuration loading
• Run pnpm cicheck to verify quality

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Fixes RulesyncRule.fromFile so tool-specific frontmatter (claudecode, copilot, antigravity) is preserved when loading Rulesync rule files, preventing configuration from being silently dropped during generation.

Changes:

• Include claudecode, copilot, and antigravity in the validated frontmatter object constructed by RulesyncRule.fromFile.
• Add unit tests to verify copilot and claudecode frontmatter loading from disk.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/features/rules/rulesync-rule.ts	Ensures additional tool-specific frontmatter keys are carried through fromFile parsing/validation.
src/features/rules/rulesync-rule.test.ts	Adds regression tests for copilot and claudecode frontmatter loading behavior.

[Copilot]

validatedFrontmatter is still built by manually enumerating fields from result.data, which is easy to regress (this PR is fixing an omission). Consider constructing it by spreading result.data and then overriding only the fields that need defaults (e.g., root/localRoot/targets/globs) so newly-added frontmatter keys aren’t accidentally dropped again.

[yhorikawa]

This is a good suggestion, but the scope of this change would be significantly larger. I'd like to keep this PR focused on the bug fix.

[Copilot]

This change fixes antigravity frontmatter being dropped, but there’s no unit test here covering antigravity loading via RulesyncRule.fromFile. Adding a focused test (similar to the new copilot/claudecode cases) would prevent regressions and directly covers issue #1259.

[yhorikawa]

fix: ba15674

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

validatedFrontmatter is built with an object literal that explicitly assigns optional fields (agentsmd/cursor/claudecode/copilot/antigravity). When those keys are absent in the file, this forces them to exist as properties with undefined values in getFrontmatter(), which breaks existing strict toEqual assertions in this test suite and can also change the observable shape of the API. Consider constructing validatedFrontmatter by starting from result.data (so absent keys stay absent) and then overriding only the fields that need defaults (root/localRoot/targets/globs).

[dyoshikawa]

@yhorikawa Thank you!