feat(time): the planned time entry is a satellite, not a third timeEntry

[rubenvdlinde]

Why

Three apps declared a timeEntry. A schema slug is global per organisation and SchemaMapper::find() matches LOWER(slug), so whichever row was reached first answered for all three: humaniq's HR booking, pipelinq's billing record, and this app's project booking.

humaniq is the agreed owner of the hours. This app's record is the planning side of one — the task it was booked against, the contractor, the hourly rate — so it is named for what it is: plannedTimeEntry, carrying a timeEntry property naming the humaniq booking.

That reference is a plain uuid, not a $ref — humaniq's register is a different register, and ADR-062 rule 7 gives a cross-register target no $ref.

The migration

RenameTimeEntrySchemaSlug renames the row before InitializeSettings, modelled on pipelinq's step for the same collision (ConductionNL/pipelinq#1805). Without it the descriptor change renames nothing: the import matches by (application, slug) and its not-found branch creates a second schema, orphaning every existing entry silently while the app reads an empty list.

Registered in both <post-migration> and <install> — the install block is the one that actually runs here, for the reason info.xml already documents about the planix → planninq app-id change.

Eighteen sites move together

The register's schema list, its key and slug, six seedData "schema" references across the register and the mock, four manifest widget sources plus a schemaSlug, two stores, and the portal contribution provider.

Six existing tests asserted the old slug and now assert the new one — they are what caught the manifest and portal sites.

What this does not do yet, deliberately

date, duration, user and description stay here rather than moving onto the humaniq booking, because four dashboard widgets read duration, user and date straight off this schema. Moving them would make all four render nothing on an instance without humaniq — blank, with no explanation.

The fleet already has the pattern: a requiredApp widget, which gate-55 supports and which hides rather than rendering empty when the backing app is absent — and pipelinq already reads this app's project that way. Applying it here is the next change, recorded in #572, and it is what makes the hours live once.

The collision is cleared either way, which is what this change is for.

Testing

• 186 tests green: 4 new, 6 updated.
• phpcs, phpmd, psalm and phpstan clean via composer check:strict.
• All 73 applicable hydra gates pass — after composer update conduction/hydra-gates (v1.14.0 → v1.15.0). The stale vendored copy invented two manifest failures; worth updating before diagnosing one.

🤖 Generated with Claude Code

[github-actions]

Quality Report — ConductionNL/planninq @ 9862245

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
check-l10n-js		✅
check-schema-l10n		❌
composer			✅	✅ 104/104
npm			✅	✅ 536/536
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-05 13:00 UTC

Download the full PDF report from the workflow artifacts.