chore: enforce explicit API visibility decisions

[Aniruddha-Shriwant]

Description

Adds a native Redocly configurable rule requiring every OpenAPI Operation Object to explicitly set x-internal to the boolean value true or false.

The Redocly configuration declares all 11 role roots, so local hooks, manual validation, and CI use one command with no custom JavaScript plugin, changed-file wrapper, or repository-owned rule test harness:

npx --yes @redocly/cli@2.51.2 lint --config redocly.visibility.yaml

The tracked dev/githooks/pre-commit hook runs this command when a commit contains staged OpenAPI YAML changes. Developers enable the repository hooks once with:

git config core.hooksPath dev/githooks

Validation

• All 11 configured API roots pass the native Redocly visibility rule
• A real local commit with a staged missing marker was blocked by the pre-commit hook with the exact source location
• A controlled CI probe failed visibility-lint with the same missing-marker error and exit code 1
• The temporary probe commits were removed; the PR branch was restored to its clean validated head
• Missing markers and non-boolean values are rejected by the JSON Schema assertion
• Shell syntax and diff whitespace validation pass
• Net diff against main is limited to the Redocly config, CI workflow, tracked Git hook, and README

Repository follow-up

After this workflow lands and produces its first status on main, add the visibility-lint job to the required status checks.

Clickup

app.clickup.com