docs: add repository guidelines for agents

[graycreate]

Summary

• add concise contributor guide tailored for automation agents
• document structure, commands, and expectations in new AGENTS.md

Testing

• not required

[Copilot]

Pull Request Overview

Adds AGENTS.md to document concise repository guidelines for automation agents.

• Introduces project structure summary and common build/test/release commands.
• Provides coding style, testing, and commit/PR conventions targeted at automated contributors.

[Copilot]

[nitpick] The phrase 'file-per-feature modules' is ambiguous (could mean one file per feature or a directory-per-feature). Suggest rewording to clarify intent, e.g., 'keep each feature's views grouped under its existing folder (e.g., place new Feed views in V2er/View/Feed/).'

Suggested change

	- Follow Swift API Design Guidelines: `UpperCamelCase` for types, `lowerCamelCase` for values, and keep file-per-feature modules consistent with existing folders (e.g., add Feed views under `V2er/View/Feed/`).
	- Follow Swift API Design Guidelines: `UpperCamelCase` for types, `lowerCamelCase` for values, and keep each feature's views grouped under its existing folder (e.g., place new Feed views in `V2er/View/Feed/`).

[Copilot]

[nitpick] UI test guidance omits how to name UI test files and whether to use test plans. Consider adding an explicit naming convention (e.g., FeatureNameUITests.swift) and clarifying if a Test Plan is required, improving consistency for automation agents.

Suggested change

	- When adding UI work, include a smoke scenario in `V2erUITests/` or capture simulator screenshots for PR reviewers if automation is impractical.
	- When adding UI work, include a smoke scenario in `V2erUITests/` (name UI test files as `FeatureNameUITests.swift` for consistency) or capture simulator screenshots for PR reviewers if automation is impractical. If automating UI tests, use an Xcode Test Plan (`V2erUITests.xctestplan`) to organize scenarios unless the feature is trivial; this improves CI reliability and agent automation.

[Copilot]

[nitpick] Commit guideline references 'conventional short prefix format' without enumerating allowed prefixes, which can lead to inconsistency. Recommend listing accepted prefixes (e.g., feat, fix, chore, docs, test, refactor, perf, ci) for clarity.

Suggested change

	- Adopt the conventional short prefix format from history, e.g., `chore: bump version to 1.1.18` or `fix(auth): handle MFA token refresh`; keep messages in English and under 72 characters.
	- Adopt the conventional short prefix format (accepted prefixes: `feat`, `fix`, `chore`, `docs`, `test`, `refactor`, `perf`, `ci`) as used in history, e.g., `chore: bump version to 1.1.18` or `fix(auth): handle MFA token refresh`; keep messages in English and under 72 characters.

[github-actions]

Code Coverage Report ❌

Current coverage: 15.06%