RFC-0089: Catalog-assisted Ossie Authoring

[meaningforger]

Summary

Refine RFC-0089 as a Core developer-tool proposal: bounded exact-object catalog inspection, a versioned source-bound snapshot, and deterministic Ossie candidate generation. All commands and contracts remain proposed, not implemented.

Review decisions

• Core owns the reusable inspector, snapshot, generator, and local CLI; managed hosts such as Metis Cloud own authoring UI, permissions, Draft/Candidate/Release, and activation.
• Authorize before consulting Project registration or DataSource/Backend state. Host-specific physical metadata permissions remain in force.
• Bind selector IDs, structured physical names, Project, and logical DataSource in the snapshot; reject mismatched authoring maps and unrepresentable identifiers.
• Emit only explicitly selected dimensions and optional technical row count. Never infer business metrics, semantic keys, or joins from catalog metadata.
• Keep offline generation separate from online validation and authorized execution. Catalog visibility does not establish SELECT permission.

Verification

• Documentation link check passed on the updated branch.
• Whitespace and diff checks passed.
• No runtime behavior or implementation tests changed.