Task: Generic server-side history dispatch: one subject, per-entity handlers
Table of Contents
This page documents a task in the Consolidate history dialogs onto HistoryDialogBase story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Add the generic history dispatch mechanism: a per-entity field mapper plus the generic NATS subject and server-side registry that consumes it, per History Diff Architecture.
2. Status
| Field | Value |
|---|---|
| State | ABANDONED |
| Parent story | Consolidate history dialogs onto HistoryDialogBase |
| Now | Split into two finer-grained sibling tasks below before implementation started; no code changes. |
| Waiting on | Nothing. |
| Next | Pick up Codegen per-entity history field mapper first. |
| Last touched | 2026-07-11 |
3. Acceptance
4. 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.)
5. Notes
6. 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 |
|---|---|---|
7. PRs
| PR | Title |
|---|---|
8. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
9. Result
Split into two finer-grained sibling tasks, mirroring the earlier
6-way split of template-rollout: this task bundled two genuinely
separable pieces (per-field-type mapping logic vs. subject/registry
wiring), too large to track as one unit of work.
- Codegen per-entity history field mapper
- Generic history.v1.get NATS subject and server-side dispatch registry — blocked on 1.
This task closes with no code changes; its Plan and Acceptance were distributed into the two tasks above.