docs(sonar): resolve stale org comment contradicting its own values

[hyperpolymath]

Summary

sonar-project.properties contradicted itself. Comment-only fix — sonar.organization and sonar.projectKey are unchanged.

PR #35 added a comment block recording the SonarCloud organisation as an unverified assumption, with metadatastician as the guess. PR #42 then decided the organisation as hyperpolymath and changed the values — but not the comment. The two have disagreed on main since 2026-07-23.

Two concrete defects:

1. Line 3 pointed at id=metadatastician_IDApTIK while line 16 declares sonar.projectKey=hyperpolymath_IDApTIK. The header URL led to the wrong project.
2. Lines 6–14 still said ORG IS ASSUMED, NOT VERIFIED -- maintainer to confirm before provisioning, and argued that "if the estate in fact consolidates under the hyperpolymath SonarCloud org, this should read hyperpolymath / hyperpolymath_IDApTIK instead" — describing as a hypothetical the exact two values printed immediately below it. Anyone reading the file was told the question was open when it had been settled four days earlier.

Both were mine, from #33/#35. Sorry for the noise.

What the comment says now

• The organisation is hyperpolymath, decided in Worktree idaptik governance alignment #42, closing Decide the SonarCloud organisation for metadatastician-org repos #38 — stated as fact, with the reasoning that the GitHub-org boundary deliberately does not mirror the SonarCloud one (the thing I originally got wrong).
• The two durable estate warnings are kept: the stale hyperpolymath_rsr-template-repo key in template-derived repos, and the ordering rule — fix a wrong projectKey before adding SONAR_TOKEN, because without the token a scan fails at authentication and submits nothing, whereas with the token and a wrong key it silently reports into another project.

A deliberate choice about wording

The original comment rotted because it recorded transient status ("assumed, not verified", "confirm before provisioning") in a committed file, where it then outlived the decision. So this version deliberately records only durable facts.

Notably, it does not say the project is unprovisioned or the token unset — both true right now (verified: hyperpolymath_IDApTIK returns not-found, no SONAR_TOKEN on this repo), and both things that stop being true the moment you set them up. Those belong in #38 and the dev-note, not here. The file states the requirement instead, which stays accurate either way.

Test plan

• git diff confirms no sonar.* value line changed — comments only
• Header project URL now matches the declared sonar.projectKey
• No remaining claim that the organisation is undecided
• Branch is based on current main (9e86676)

Unrelated and still outstanding: metadatastician/cadastra declares hyperpolymath_rsr-template-repo while its README badge says metadatastician_cadastra. Now that the org is settled, its config org is right, its key is wrong, and the badge should become hyperpolymath_cadastra. Happy to do that separately.

🤖 Generated with Claude Code