fix(cp): remove the tautological API-coverage self-check

[netravnen]

runApiResourceCoverageCheck validated ENTITY_API_RESOURCE_MAP's slugs
against OPENAPI_KNOWN_RESOURCE_SLUGS -- a set built from
ENTITY_API_RESOURCE_MAP itself, so the check could never fire while
reporting green in debug mode. A guard that cannot fire but reports
success is worse than no guard: it manufactures false confidence. A
real coverage check needs an independent source of truth (a fetched
OpenAPI spec); until one exists, no check is honest, and a note on the
map says so. Also removes the dead keeperRowForDelete variable in the
conflict-resolver apply loop, assigned twice and never read.

Changes:

• Delete runApiResourceCoverageCheck, OPENAPI_KNOWN_RESOURCE_SLUGS and
  the runSelfCheck call site.
• Add a note on ENTITY_API_RESOURCE_MAP explaining why there is no
  self-check and what a real one requires.
• Delete the two dead keeperRowForDelete assignments in the IX-F
  conflict-resolver apply loop (the DELETE targets item.doomedRow.id;
  the keeper read-back result was never consumed via this variable).
• Bump CP @Version to 2.0.228 (src + meta); regenerate .user.js.

Security:

• N/A (the removed check never guarded anything -- it was structurally
  unable to fail).

Testing:

• Full suite green: 585 pass, 0 fail (includes the IX-F merge-apply
  suite, which pins the conflict-resolver write path this touches).
• build --check and node --check on the regenerated .user.js: clean.
• Verified by grep that zero references remain to the deleted symbols.

Backwards Compatibility:

• Debug mode no longer logs the meaningless "api resource coverage ok"
  self-check line; no other observable change.

Assisted-by: Claude:claude-opus-5

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}