playwright_manager already takes a browser_type and references firefox, so the seam is there. for runs that get filtered on fingerprint rather than behavior, would it be useful to point the firefox branch at a build that keeps a realistic, consistent fingerprint (deterministic per session)? it's a python playwright wrapper with the standard browser/context/page api, so it slots in where chromium.launch is today without touching the skills layer. happy to prototype it against playwright_manager if there's interest, otherwise no worries.
playwright_manager already takes a browser_type and references firefox, so the seam is there. for runs that get filtered on fingerprint rather than behavior, would it be useful to point the firefox branch at a build that keeps a realistic, consistent fingerprint (deterministic per session)? it's a python playwright wrapper with the standard browser/context/page api, so it slots in where chromium.launch is today without touching the skills layer. happy to prototype it against playwright_manager if there's interest, otherwise no worries.