Android Worker Platform Tests job was still using 'ff init' which
requires interaction. Updated to use manual .fuzzforge creation like
the fast-workflow-tests job.
This fixes the 'No FuzzForge project found' error in android workflow tests.
The ff init command doesn't have a --non-interactive flag. The command
already runs non-interactively by default, so the flag is not needed.
This was causing initialization to fail with 'No such option' error.
Test projects need to be initialized with 'ff init' to create
.fuzzforge directories before workflows can run. Added initialization
steps to all workflow test jobs:
- Fast workflow tests
- Android platform tests
- Full workflow tests
This ensures projects are properly set up in CI where .fuzzforge
directories don't exist (they're in .gitignore).
The GitHub Actions workflow was failing because the CLI depends on
fuzzforge-sdk and fuzzforge-ai packages which are local to the monorepo
and not available on PyPI.
Updated all jobs to install local dependencies first:
- platform-detection-tests
- fast-workflow-tests
- android-platform-tests
- full-workflow-tests
This ensures pip can resolve all dependencies correctly.