governance: onboard observatory to organization repository policy

[zoeyrose]

Summary

atrinik/observatory is an active default-stack repository, but it is absent from the GitHub settings desired-state inventories. It therefore retains GitHub repository-creation defaults instead of the Atrinik repository policy.

Live evidence

Checked on 2026-08-24 with gh:

Setting	atrinik/observatory	Atrinik baseline
Merge commits	allowed	disabled
Rebase merges	allowed	disabled
Squash commit title	COMMIT_OR_PR_TITLE	PR_TITLE
Squash commit message	COMMIT_MESSAGES	PR_BODY
Delete head branch after merge	disabled	enabled
Applicable governance rulesets	default-branch integrity and linear history only	also pull-request gate and repository required CI
Repository properties	unclassified, seed, none	explicit active replacement classification

The COMMIT_MESSAGES setting explains why squash merges do not include the pull request description. The repository is otherwise active, public, on main, and its baseline security features currently report enabled.

Required follow-up

1. Add observatory to config/repositories.json under pull_request_gate and required_ci, using the workflow job context Validate dashboard and Workers plus Conventional PR title.
2. Add an explicit observatory record to config/repository-properties.json. Based on the workspace manifest, the likely values are component role service, provider set replacement, lifecycle active, and release policy none; confirm the role with the Observatory owner.
3. Run bin/validate and a reviewed bin/publish plan, then apply the repository defaults and governance rules through the normal authorized publisher flow.
4. Decide separately whether Observatory will ever publish immutable releases; do not add the release-tag rule until that release contract exists.

Acceptance criteria

• Observatory has squash-only merges with PR_TITLE and PR_BODY, and merged head branches are deleted.
• Direct changes are covered by the pull-request ruleset and the required CI ruleset includes the current validation job and Conventional PR title check.
• Repository custom properties are explicit and no longer unclassified/seed.
• The live result is re-read after publication and matches the desired-state files.

References: repository defaults, repository inventory, repository properties, and Observatory validation workflow.

[github-actions]

🎉 This issue has been resolved in version 2.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀