fix(quality): name the four steps of the references audit

[rubenvdlinde]

phpmd measured execute() at cyclomatic complexity 22 against a threshold of
10 and refused it. shillinq hit the same wall on the same generated shape and
was fixed in shillinq#1517; this is the equivalent, so the four apps keep one
audit shape rather than drifting apart.

The branching was never incidental. It is a five-way classification plus a
write decision, and naming the parts is what lets execute() read as "read,
index, audit, report":

method	responsibility
ownerIndex()	index owners by the identity key, and survive an unreadable owner
auditRows()	classify every row, writing the unambiguous ones when allowed
classifyRow()	the five-way verdict
backfill()	one patch write
report()	the one-line summary

Behaviour is unchanged, including the order the cases are tested in, which
matters: a row already carrying a reference is never a backfill candidate,
regardless of what its identity key would have matched.

Why this exists at all

I did not run phpmd before pushing the first version. composer phpmd over all
of lib/ is OOM-killed on this machine and reports a false pass, so it was run
per file this time — and the exit code was read rather than tail's, which had
already masked one result earlier in this work.

check	result
phpmd, per file	0 findings, exit 0
PHPCS / Psalm / PHPStan	0
PHPUnit	green

humaniq's command was re-run on the rig after the refactor and reports the same
tally as before it.

🤖 Generated with Claude Code

[github-actions]

Quality Report — ConductionNL/stackiq @ 830db1c

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
check-vue-demi		✅
test-l10n		✅
format		✅
check-schema-l10n		✅
check-l10n-js		✅
composer			✅	✅ 130/130
npm			✅	✅ 714/714
app:check-code	⏭️
info.xml	✅
REUSE	❌
PHPUnit					✅
Newman					⏭️
Playwright					⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development
Hydra gates					❌

---

Quality workflow — 2026-09-06 18:39 UTC

Download the full PDF report from the workflow artifacts.