Task: Backfill missing Qt drawer for 5 hand-authored dq Qt entities

Table of Contents

This page documents a task in the Calendar follow-ups: remaining hand-written list pagination cleanup story. It captures the goal, current status, acceptance, and any notes or results.

Goal

Backfill a ** Qt drawer into each of catalog, change_reason_category, change_reason, data_domain, and subject_area's (all ores.dq) codegen entity .org models, reverse-engineered from their existing hand-authored Qt files so regenerating produces byte-identical (or intentionally reconciled) output – bringing these five under normal codegen maintenance instead of permanent hand-authorship drift risk. Not calendar-specific – filed under this story only because it was discovered while scoping the has_pagination pagination-truncation task, which needs a Qt drawer to exist before :has_pagination: true can do anything for these five.

Status

Field Value
State BACKLOG
Parent story Calendar follow-ups: remaining hand-written list pagination cleanup
Now Not yet started.
Waiting on Nothing.
Next Begin implementation.
Last touched 2026-07-30

Acceptance

  • [ ] Each of the 5 entities' .org model gains a ** Qt drawer whose properties/detail-fields/columns accurately describe the existing hand-authored Qt files.
  • [ ] Regenerating each entity's ores.cpp.qt facet either produces byte-identical output to what's committed (ideal), or a reviewed, intentional diff that's then committed as the new baseline (e.g. fixing genuine drift the hand-authored version had accumulated).
  • [ ] :has_pagination: true added at the same time if these entities also exhibit the misleading-pagination-controls bug (check each for a PaginationWidget first).
  • [ ] Full local build green; ctest green.

Plan

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Notes

Test Scenarios

Manual QA scenarios (scaffolded via compass add test_scenario, run through the QA Validation Runner panel) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

Scenario State Notes
     

PRs

PR Title
   

Review

Comment summary File Decision Notes
       

Result

Emacs 29.3 (Org mode 9.6.15)