Repository Resource Contract: Kubernetes-style Declarative Markdown Schema

[juliuskrah]

Summary

Define the canonical Repository resource contract as a declarative markdown file using the Kubernetes-style frontmatter schema (apiVersion, kind, metadata, spec, status). Repositories should be expressible as tracked markdown files in git, consistent with how Products, Collections, and CategoryTaxonomies are managed.

Parent initiative: #40

Scope

• Define apiVersion, kind, metadata, spec, and status schema for a Repository resource.
• Define RepositorySpec fields: name, default branch, description, visibility, tier, and any relevant settings.
• Define validation rules and error semantics for required/optional fields.
• Define RepositoryStatus conditions (e.g. Ready, AdmissionAccepted) and resolved fields.
• Provide a copy-pasteable example Repository markdown document that passes all validation rules.

Acceptance Criteria

• Repository frontmatter schema is fully specified (all spec and status fields documented with types, constraints, and examples).
• Validation rules and rejection error messages are documented for each field.
• At least one valid example document and one invalid example document are included.
• Schema is consistent with ObjectMeta, LabelSelector, and ObjectReference conventions defined in [Initiative] Kubernetes-style Catalog Frontmatter #40.

Dependencies

• Parent: [Initiative] Kubernetes-style Catalog Frontmatter #40