fix(app): expose exact visit turn documents in Session

This commit is contained in:
2026-10-24 02:00:18 +01:00
parent 027be68ae7
commit 285392982d
4 changed files with 324 additions and 0 deletions
+31
View File
@@ -0,0 +1,31 @@
# Stage detail debugging fixes
- Stage Summary Input and Output start collapsed (commit `027be68a`). Existing
native section toggles and copy actions remain. Both Material and Cupertino
regression assertions failed before the one-line initial-state fix; all 18
section tests passed afterward.
- Session adds the selected step's inventory-backed input.md, memory.md and
output.md rows through ArtifactDocumentSection. ArtifactViewerPage receives
only those documents from that exact step, so paging cannot escape to an
earlier repeated visit. Its default selectable-text markdown preview exposes
the raw recorded document, not the interpreted Summary maps. Existing safe URL
resolution, same-origin fetch, copy-link and file actions are reused.
- Session export remains external-only with the existing metadata, diagnostics
and export-only repair controls unchanged. Missing documents remain
non-actionable; unavailable capture is distinguished from an empty inventory.
No document URL is constructed or borrowed.
## Verification
- `flutter pub get`: passed using /Users/alan/development/flutter/bin/flutter.
- New exact-visit document tests failed on both hosts before implementation
because Session had no input.md row.
- Six new document tests cover both hosts: repeated visit 2 (sequence 3), exact
inventory and selection, fixture-byte previews and copy-link controls, missing
sibling documents/URLs without borrowing, and unavailable versus empty capture.
- `flutter test test/features/runs test/features/artifacts`: 469 passed.
- Focused `flutter analyze` for the three changed production widgets and two
changed test files: no issues.
- No browser captures, integrated web build, mobile checks, APK build, ADB,
deployment, restart, production data mutation or backend edits performed.
Browser verification and integration/deployment belong to the manager.