busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

feat(ui): add chat-driven dataset review flow

Browse Source 
Move dataset review clarification into the assistant workspace and
rework the review page into a chat-centric layout with execution rails.

Add session-scoped assistant actions for mappings, semantic fields,
and SQL preview generation. Introduce optimistic locking for dataset
review mutations, propagate session versions through API responses,
and mask imported filter values before assistant exposure.

Refresh tests, i18n, and spec artifacts to match the new workflow.

BREAKING CHANGE: dataset review mutation endpoints now require the
X-Session-Version header, and clarification is no longer handled
through ClarificationDialog-based flows
This commit is contained in:
busya
2026-03-26 13:33:12 +03:00
parent d7911fb2f1
commit 7c85552132
74 changed files with 6122 additions and 2970 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
specs/027-dataset-llm-orchestration/checklists/requirements.md
View File

@@ -38,6 +38,7 @@
## Notes
- Validation completed against [spec.md](../spec.md) and [ux_reference.md](../ux_reference.md).
- Automatic documentation, guided clarification, and Superset-derived dataset execution are all represented as independently testable user journeys.
- Error recovery is aligned between the UX reference and the functional requirements, especially for partial filter import, missing run-time values, and conflicting metadata.
- The specification is ready for the next phase.
- Automatic documentation, guided clarification, Superset-derived dataset execution, and manual fallback review are represented as independently testable user journeys.
- Chat-centric workflow, collapsible completed phases, multi-dataset tabbed review scope, and per-dataset exclusion behavior are reflected in both the specification and UX reference.
- Error recovery is aligned between the UX reference and the functional requirements, especially for partial filter import, missing run-time values, conflicting metadata, and unavailable LLM assistance.
- The specification is ready for the next phase.