Readers see everything except secrets

Context

Reader access does not confer authority to modify a record.

Decision

Allow integration readers to inspect Library records without secret values. Mutation controls and service authorization use distinct management, credential, execution-operation and staff permissions.

Alternatives Considered

Require the currently unused execution-read permission. No current route requires it; enforcing it would alter the accepted reader experience and needs a product decision.

Consequences

A person holding only read authority does not receive mutation controls.

The Library shows its no-access state when entry authority is missing.

APIs remain authoritative even when console gates differ from their exact permissions.