Description
The form-sync tool is not invoked to push the form after a plan is executed. This creates a risk of the local form falling out of sync with the AEM instance — there is no guarantee the agent will push after every change.
Expected Behavior
After a plan is generated and executed, the orchestrator should ask the user whether they want to push the form to AEM. If confirmed, run the push command. This ensures the AEM instance always reflects the latest local changes and avoids discrepancies between local and remote versions.
Suggested Approach
Add a post-plan confirmation step in forms-orchestrator or the relevant domain skill that prompts:
"Plan complete. Push the updated form to AEM now?"
If yes, invoke form-sync push.
Description
The
form-synctool is not invoked to push the form after a plan is executed. This creates a risk of the local form falling out of sync with the AEM instance — there is no guarantee the agent will push after every change.Expected Behavior
After a plan is generated and executed, the orchestrator should ask the user whether they want to push the form to AEM. If confirmed, run the push command. This ensures the AEM instance always reflects the latest local changes and avoids discrepancies between local and remote versions.
Suggested Approach
Add a post-plan confirmation step in
forms-orchestratoror the relevant domain skill that prompts:If yes, invoke
form-sync push.