What: Add an adapter.ts template that power users can edit to map their trace format to the internal Trace shape, alongside the wizard.
Why: The wizard (#2) covers non-coders. Power users with non-trivial transforms (custom field renames, computed fields, multi-source merges) need a code-level escape hatch. Pulled out of #2 to keep v1 focused.
Acceptance criteria:
adapter.ts template at the project root with commented examples- Loader uses
adapter.ts if present, otherwise falls back to wizard
- Reference link to the internal Trace type in the repo
Out of scope: changes to the wizard.
Depends on: #2
What: Add an
adapter.tstemplate that power users can edit to map their trace format to the internal Trace shape, alongside the wizard.Why: The wizard (#2) covers non-coders. Power users with non-trivial transforms (custom field renames, computed fields, multi-source merges) need a code-level escape hatch. Pulled out of #2 to keep v1 focused.
Acceptance criteria:
adapter.tstemplate at the project root with commented examplesadapter.tsif present, otherwise falls back to wizardOut of scope: changes to the wizard.
Depends on: #2