[Initiative] Hydrated Catalog View in ScyllaDB with Lossless YAML Export

[juliuskrah]

Summary

Add a hydrated resource view that materializes merged spec + computed status, and provide faithful YAML export from the CLI with Markdown preserved in block scalar form.

In Scope

• Define hydrated persistence model in ScyllaDB for catalog resources (spec, status, metadata)
• Persist Markdown body as spec.content during parse/hydration
• Materialize status fields produced by controller logic into hydrated records
• Implement CLI -o yaml export path that reassembles Kubernetes-style resource output from hydrated storage
• Render spec.content as YAML block scalar (|) to preserve Markdown formatting
• Add round-trip fidelity tests for import -> hydrate -> export

Out of Scope

• Markdown rendering/sanitization rules in UI
• Mutating admission behavior
• Query language redesign

Acceptance Criteria

• Hydrated records store both spec and status in ScyllaDB with documented schema
• spec.content is populated from Markdown body for applicable resource kinds
• CLI YAML export emits valid Kubernetes-style documents
• Exported Markdown content is preserved using block scalar style with no lossy folding
• Round-trip tests verify semantic equivalence for representative resources
• Performance baseline exists for hydration and export at catalog scale

Implementation Notes

Hydration separates author intent (spec) from machine observations (status) while keeping both queryable. YAML export must be user-trustworthy: if Markdown formatting is rewritten or folded unexpectedly, authoring workflows degrade and diff noise increases. Preserving spec.content with block scalars keeps Git history legible and aligns with declarative UX expectations.

Dependencies

• Depends on: [Initiative] Datastore Backend: ScyllaDB with Migrations #102 (ScyllaDB backend), [Initiative] Separate Markdown Parsing Layer from Catalog Validation #134 (parsing separation)
• Related: [Initiative] Dual-Mode Admin: Shopify and GitHub Views #121 (dual-mode admin), [Initiative] CLI-First Platform Management (Admin Optional) #120 (CLI-first management), [Initiative] Controller Watch API with resourceVersion Resume #131 (watch API)