facebook search template variables not substituted

[bobdonger]

[Astro-Han]

This is not actually a template-substitution bug.

What is really happening is that the command starts on Facebook home, then inside the same browser script it changes window.location.href to the search page, waits 4 seconds, and tries to read the results.

The problem is that once Facebook navigates to the search page, the original script context is destroyed. At that point Chrome/CDP reports Inspected target navigated or closed, so the later wait and DOM extraction never get a chance to finish.

So the ${{ args.query }} text shown in verbose output is misleading here. That output is just the raw template source being printed for debugging. It does not mean template rendering failed. The real failure is caused by navigation happening inside the same evaluate block.

In plain terms:

1. Open Facebook home
2. Start a script
3. The script redirects the page to search
4. The page reload kills the script itself
5. Result extraction never completes

So the root cause is: navigation and extraction are bundled into one evaluate, not that variables are left unsubstituted.

The fix should be to split this into two steps: first navigate to the search URL, then run a separate extraction step on the loaded search page.