fix(flow): attribute interactive test runs to the caller (3rd instance of the ownerless-run defect)

[rubenvdlinde]

Follow-up to #2169, same defect class, third instance.

Problem

FlowRunController::test() queued its run without the acting user — in the one dispatch path that has a session by definition.

Consequence: the run was ownerless, context['triggeredBy'] was null, and every attribution-requiring node refused. ObjectWriteNode returned "This flow run has no owner (triggeredBy); an object write must be attributable." So the interactive "run this flow now" button could never exercise a write node — the only runs that appeared to work were harness runs carrying a hand-injected context.

Why this mattered for verification

This is what made the earlier "object-write is proven" claim overstated. The node had 387 passing unit tests and a green live run, but that run's context was injected by the harness. On every real path the node refused.

Live proof, after the fix

A naturally triggered run, nothing injected:

run status : completed
triggeredBy: admin                     <- resolved from IUserSession
log        : [{"transition":"write1","status":"completed","itemsIn":1,"itemsOut":1}]

And the object actually landed, read back through the API:

findings BEFORE: 7
findings AFTER : 8
  -> rule 'written by openregister.object-write' | created 2026-07-27T17:58:13+00:00 | owner admin

Related

While proving this, two other things surfaced and are filed separately: the live instance was 57 commits behind origin/development so the #2169 fix was not deployed (environment, not code), and #2170 — FlowRunWorker is never registered in oc_jobs, so asynchronous runs still cannot execute regardless of attribution.

🤖 Generated with Claude Code

[github-actions]

Quality Report — ConductionNL/openregister @ 04429d3

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
composer			✅	✅ 174/174
npm			✅	✅ 555/555
PHPUnit					❌
Newman					✅
Playwright					⏭️

---

Quality workflow — 2026-07-27 18:07 UTC

Download the full PDF report from the workflow artifacts.