Skip to content

Add deterministic traverse-starter UI flow#26

Merged
enricopiovesan merged 1 commit into
mainfrom
claude/issue-4-deterministic-ui-flow
Jun 30, 2026
Merged

Add deterministic traverse-starter UI flow#26
enricopiovesan merged 1 commit into
mainfrom
claude/issue-4-deterministic-ui-flow

Conversation

@enricopiovesan

Copy link
Copy Markdown
Contributor

Summary

  • Adds `src/client/traverseOutput.ts` — `parseOutput()` validates and type-narrows the execution envelope into typed `TraverseStarterOutput` fields
  • Updates `App.tsx` output panel to render `title`, `tags`, `noteType`, `suggestedNextAction`, `status` from runtime output — no local computation
  • Falls back to raw JSON if the output shape doesn't match (forward-compatible)
  • 6 new unit tests for `parseOutput`; 17 total

Closes #4

Definition of Done

  • User can enter a short note
  • UI sends input to Traverse runtime
  • UI renders runtime-provided fields: title, tags, noteType, suggestedNextAction, status
  • UI does not compute these fields locally
  • Feature is deterministic — no live AI/model access required

Validation

npm run typecheck  # pass
npm run lint       # pass
npm run test       # 17 tests pass (4 files)

Renders runtime-provided structured output fields — title, tags, noteType,
suggestedNextAction, status — without computing any business fields in the UI.
Adds parseOutput() to validate and type-narrow the execution envelope, with
6 unit tests. Total: 17 tests across 4 files.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@enricopiovesan enricopiovesan merged commit 2353184 into main Jun 30, 2026
4 checks passed
@enricopiovesan enricopiovesan deleted the claude/issue-4-deterministic-ui-flow branch June 30, 2026 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add deterministic traverse-starter UI flow

1 participant