Found during the ADR-098 fleet task inventory (2026-08-22), verified against the register.
What
In lib/Settings/pipelinq_register.json, the task schema declares:
priority.enum = ["low", "normal", "high"]priority.default = "normaal" ← Dutch spelling, not in the enum
Impact
Any task created without an explicit priority takes a default value the schema itself rejects. Anything that validates the object, or filters/sorts on the declared enum, sees a value that should not exist. It is a one-word typo with a silent blast radius: nothing errors at write time, the wrong value simply propagates.
Fix
Change the default to "normal". Then check existing rows — any task already carrying normaal needs a data fix, since the default has presumably been applied since the field was introduced:
-- illustrative; run through the OR object layer, not raw SQL
SELECT count(*) FROM ... WHERE priority = 'normaal';
Add a schema-level test asserting every default is a member of its enum — this class of typo is worth catching mechanically across the register, not just here.
Context
Scope of ADR-098 (fleet workflow convergence — ConductionNL/hydra#609): task migrates onto a fleet-generic task entity whose priority model normalises four different scales. Fixing the typo before migration avoids carrying it across.
Found during the ADR-098 fleet task inventory (2026-08-22), verified against the register.
What
In
lib/Settings/pipelinq_register.json, thetaskschema declares:priority.enum=["low", "normal", "high"]priority.default="normaal"← Dutch spelling, not in the enumImpact
Any task created without an explicit priority takes a default value the schema itself rejects. Anything that validates the object, or filters/sorts on the declared enum, sees a value that should not exist. It is a one-word typo with a silent blast radius: nothing errors at write time, the wrong value simply propagates.
Fix
Change the default to
"normal". Then check existing rows — any task already carryingnormaalneeds a data fix, since the default has presumably been applied since the field was introduced:Add a schema-level test asserting every
defaultis a member of itsenum— this class of typo is worth catching mechanically across the register, not just here.Context
Scope of ADR-098 (fleet workflow convergence — ConductionNL/hydra#609):
taskmigrates onto a fleet-generic task entity whose priority model normalises four different scales. Fixing the typo before migration avoids carrying it across.