Repository metadata has a page and a proposed ADR

Repository metadata is a new page. It sets catalog-info.yaml at the repository root as the file that holds ownership, hosting, and release data. ADR-0008 records the decision. Its status is proposed.

• Choose each field in this order: Backstage, DevHub, then a new key.
• Add a new key only when Backstage and DevHub have no field for the value. New keys go in spec.kraken.
• The page defines two keys: hosting and release. Each key has a list of allowed values.
• A team proposes a new key in an issue. An Engineering Navigator approves it in the pull request that adds it to the page.
• The link to the repository documents goes in metadata.links. It does not go in an annotation.
• spec.owner names the first owner of the CODEOWNERS rule that matches catalog-info.yaml.
• A production service names its PagerDuty service in pagerduty.com/service-id. The escalation policy of that service names who gets paged.
• Environment URLs, the runbook, and the Slack channel go in metadata.links. Each link has a type from a fixed list: repository, documentation, production, staging, development, runbook, or slack.
• In Claude Code, the /engineering-standards:filling-catalog-info skill writes the file. The page gives the equivalent prompt for Codex, Cursor, and OpenCode.
• The release values are a proposal. After reviewers accept the ADR, each repository that uses the ninjatrader.com/* annotations moves them to spec.kraken.

This page resolves part of issue #26, including the on-call team and the environment URLs. Criticality and data classification stay open.