Custom-table publication requires validation configuration

Context

Custom SQL needs a controlled place for validation. The current architecture does not grant staff access to customer records for this purpose.

Decision

Custom-table analysis, preview, publication and revalidation require the configured validation workspace, which the recorded production configuration deliberately omits.

Alternatives Considered

Validate against a customer workspace: That would expose customer rows through staff authoring without the required access model.

Consequences

Production cannot publish a new custom query table under the pinned configuration. The production revalidation pass has no configured validation workspace to use.