[sjungwon03]

Summary

Branch protection and the label taxonomy existed only as ad-hoc API calls. This stores both as
data in the repository so they are reviewable and reproducible.

Closes #1

Validation

• dart format . — N/A, no Dart code yet
• flutter analyze reports no warnings — N/A, pre-scaffolding
• flutter test passes — N/A, pre-scaffolding
• Re-ran build_runner — N/A, no models
• Manually validated — CI ran green on dev; ruleset JSON was rejected only by the private-repo plan limit, not by schema

Checklist

• This pull request targets dev
• Linked a GitHub issue above with Closes #
• Pull request title and commits follow Conventional Commits
• All commits are signed off with git commit -s (DCO)
• Added or updated tests, or explained below why none are needed — no test surface; the JSON is validated by the GitHub API on apply
• Updated documentation where behavior changed
• Checked both Mobile and Desktop layouts — N/A
• Checked both Light and Dark themes — N/A
• New dependencies license-checked — none added
• No tokens, instance hostnames, credentials, or confidential data
• Everything in this pull request is written in English

Notes for reviewers

Two settings are deliberately not matching the reference repository:

• required_approving_review_count is 0, not 1. With one maintainer and no bypass actors,
  requiring an approval would make every pull request unmergeable.
• Flutter quality gate is not a required check, because it is skipped until M0 lands pubspec.yaml.

Both are documented in .github/rulesets/README.md with the exact change to make later.

[sjungwon03-ai]

Solid move to version-control the rulesets and label taxonomy instead of ad-hoc API calls. Both JSON files are schema-valid, the labels script is idempotent, and the README documents the two deferred settings (review count → 1, Flutter gate as required check) with the exact edit to make later. CI is green. LGTM.

[sjungwon03]

Addressed the labels.sh finding in the follow-up commit: set -euo pipefail, an explicit failure branch instead of &&, a failure counter, and a non-zero exit from an EXIT trap. Verified by running the sync against the live repository — 46 labels report ok and the script ends with Label sync complete.

On strict_required_status_checks_policy: false: confirmed intentional. Forcing every branch up to date would mean rebasing each open pull request whenever dev moves, which is friction a squash-only flow does not need. Noted in .github/rulesets/README.md as a setting to revisit if the contributor count grows.