DOC GUI: Verify integrated dataset workflows and documentation #2761

Describe the issue linked to the documentation

Essential dataset milestones need a final integrated documentation/journey check, not a deferred testing project. Browsing/media/imports are documented; seeded tests already cover browsing/pagination and text import into a new attack.

Part of #2744. Final prerequisites: #2752 for Chat entry/return and remaining imports, #2756 for provider Load/status/access, and #2759 for exact selected-example Scenarios. Optional #2758 is not required. Keep not ready yet until those milestones complete and this checkpoint is promoted.

Suggest a potential alternative/fix

Extend existing doc/gui/0_gui.md and the real-backend fixture harness only for remaining integrated gaps. Do not duplicate each feature's suites or build a separate guide/demo.

Coverage belongs to delivering milestones:

• FEAT GUI: Add seed-prompt inspiration entry points #2752: contextual entry/return, nonempty drafts, conversations/media and all three import destinations without accidental sending.
• FEAT GUI: Add dataset loading controls and access guidance #2756: default-provider Load, backend credential/access guidance, status/errors/retry and preserved browse/Chat state.
• FEAT GUI: Configure a scenario from selected dataset examples #2759: multi-page exact selections, explicit missing objectives, shared scorer validation, preview/estimate/confirmation/launch and normal results/history.
• FEAT GUI: Add optional per-technique converter composition #2758, if later shipped: its own optional converter tests/documentation. Do not wait for it here.

Check representative journeys connecting completed milestones. The guide must match shipped labels/routes/defaults, counts/unknown metadata, whole conversations, no-send guarantees, shared-memory loading, access limitations, exact-selection freshness and scorer-result meaning. Raw refusal/non-refusal is not automatically task achievement.

Acceptance criteria:

• Earlier milestone tests/docs are present; cover remaining cross-flow gaps without duplicating entire suites.
• A real-backend journey connects provider loading, browsing/media, editable Chat import and exact-example Scenario setup, including cancellation/return and an error or stale-selection path.
• Selections/defaults stay consistent through estimate/launch; navigation neither loses drafts nor sends accidentally.
• Keyboard, focus restoration and narrow viewports are covered at appropriate milestone/integration points.
• The existing guide has runnable controlled-fixture workflows and honest unsupported-shape, credential/shared-memory, retry/status-loss and objective/scorer limitations.
• No privileged Hugging Face access, real secrets or paid calls. E2E uses the real backend with local providers/targets/scorers; only component tests mock API services.

Start with doc/gui, frontend/e2e/datasets.seeded.spec.ts, local fixture/setup helpers and new milestone suites. This is the final essential checkpoint before optional #2758, not a reason to defer focused tests. Scope reorganized November 4, 2026.