issue-804: ADR for devui editor roundtrip test

[domhanak]

Description

This is an ADR for a test to validate Dev UI Workflow Editor Rendering Round-Trip

ADR for #804

Updated with:
Added PoC test suite with cases
Update the ADR based on PoC

Changes

Adds ADR for #804

Checklist

Before submitting this PR, please ensure:

• I ran the full build with integration tests locally: ./mvnw clean install -DskipITs=false
• Code follows the project's code conventions
• Tests have been added/updated to cover the changes
• Documentation has been updated (if user-facing changes)
• Commit messages are clear and follow conventional commits style
• I have read and followed the Contributing Guide
• I have read and comply with the LLM Usage Policy (if applicable)

Additional Notes

[fantonangeli]

LGTM, for the parts which I can understand.
Thanks @domhanak

[lornakelly]

@domhanak Thanks for the ADR, my knowledge of quarkus flow internals is limited but looks like a great start. Just one small comment:

EchoNameWorkflow covers a single flat set task but, from my understanding, each construct serialises to a different JSON shape from Java and the editor's own tests only cover hand-written YAML, so nothing checks that shape.

So can we run the same check across the other types:call, for, fork, tryCatch, listen, emit, raise, run, switch, wait? Happy to have this in a phase 2 section if we just want to get the simple example up and running first?

[domhanak]

@lornakelly yea, so I initially did not include this when prompting, so it is not there. Wanted to keep the focus narrow to limit hallucinations and inaccuracies. So this ADR covers the MVP, the expansion to broader coverage can be done in multiple ways, but we need one where we reuse existing example workflows so it is a bit tricky.

I have since theorized a way to reuse what we have in docs cookbook and working on PoC locally.
Once I validate it is ok and works well, Ill update the PR with some extra analysis output from Bob tool.

Ultimately we could do one big workflow that has everything here, but that is something I did not think through yet.

[lornakelly]

@lornakelly yea, so I initially did not include this when prompting, so it is not there. Wanted to keep the focus narrow to limit hallucinations and inaccuracies. So this ADR covers the MVP, the expansion to broader coverage can be done in multiple ways, but we need one where we reuse existing example workflows so it is a bit tricky.

I have since theorized a way to reuse what we have in docs cookbook and working on PoC locally. Once I validate it is ok and works well, Ill update the PR with some extra analysis output from Bob tool.

Sounds good, thanks

[lornakelly]

LGTM

[ricardozanini]

Are these exclusions because of the inclusion of docs sources in builder-helper-maven-plugin? If so, can you please add a comment here explaining this?

[domhanak]

Sure, I ll add comment explaining