Triage Codacy's 55 new issues on the bootstrap PR and set the gate baseline

[amondnet]

Context

Codacy Static Code Analysis reports ACTION_REQUIRED on PR #5:

55 new issues (0 max.) of at least severity.

The gate is configured to allow 0 new issues, so any finding fails it. The detail lives only on the Codacy pull-request dashboard — it is not in the check output, which carries an empty summary.

Deliberately left unaddressed on PR #5: the repository has no branch protection and the active pleaseai-oss ruleset enforces only repository visibility, so this is not a required check and does not block the merge. Deferring it keeps the review-fix commits scoped to findings we could actually read and verify.

What has to be decided

1. Are the 55 findings real? PR feat: implement the AsciiDoc to Markdown conversion pipeline #5 is the project bootstrap — it introduces the whole scripts/ tree at once, so every finding in it is "new" by definition. A count this size on a bootstrap PR may reflect the gate's baseline rather than 55 distinct defects.
2. Is 0 max. the right policy for this repository? It is a reasonable steady-state target and a poor one for an initial import. If it stays, the baseline needs setting deliberately.
3. Which of Codacy's tools overlap with what CI already runs? The repo already gates on eslint --max-warnings 0 (bun run lint) and tsc --noEmit. Findings that duplicate those are noise; findings that do not are the ones worth acting on.

Next step

Someone with Codacy dashboard access exports the 55 findings, groups them by tool and rule, and this issue records which are actionable. Then either fix them or set the gate's baseline with a stated rationale.

Reference

• PR feat: implement the AsciiDoc to Markdown conversion pipeline #5 head at time of filing: b40d0f0
• Check: Codacy Static Code Analysis → action_required