fix: revive the inert Feature test suite, drop the dead behat Mink block

[tuxpiper]

Stacked on #5053 — base is chore/devops-cleanup, so the diff here is just the fixes. Retarget to develop once #5053 merges.

Four real defects surfaced while auditing the devops config. Unlike #5053 these change behaviour, hence the separate PR.

1. The tests/Feature phpunit suite matched zero tests

phpunit.xml.dist selects ./tests/Feature with suffix="Test.php", but the two files there were named ExportJobAPI.php and WebhooksPostsUpdateAPI.php. Nothing in that suite has run since 2022.

They could not simply be renamed — both had rotted since the Lumen → Laravel migration:

• ExportJobAPI imported Laravel\Lumen\Testing\DatabaseTransactions; Lumen is no longer installed
• WebhooksPostsUpdateAPI declared setUp()/tearDown() without the : void return types PHPUnit 9 requires
• both used the Lumen assertion API (seeStatusCode / seeJson / seeJsonStructure / expectsJobs), none of which exists on Laravel's TestCase
• ExportJobAPI referenced \Ushahidi\Modules\Auth\GenericUser, which does not exist (the real class is \Ushahidi\Authzn\GenericUser)

Ported both to Laravel 8 + PHPUnit 9 and renamed them so the suite collects them:

• seeStatusCode/seeJson/seeJsonStructure → assertStatus/assertJson/assertJsonStructure on the returned TestResponse
• expectsJobs(ExportPostsJob::class) → Bus::fake() + Bus::assertDispatched()

ExportJobAPITest now creates its own admin user in setUp() rather than assuming user id 2. Ushahidi\Authzn\Session::getUser() loads the acting user from the database, and id 2 is only an admin in the behat fixture (tests/datasets/ushahidi/Base.yml) — which phpunit never loads, and which rewrites the users table when behat does load it. Owning the user keeps the suite independent of run order.

phpunit goes from 172 → 176 tests, 534 → 552 assertions.

2. behat.yml.dist declared a Mink extension that Behat silently ignored

The extensions: block was indented as a child of suites.default instead of at profile level, so Behat never activated it.

That misindentation was load-bearing. mink appears zero times in composer.lock — it is not installed. Anyone "fixing" the indentation to hoist extensions: to where it looks like it belongs would instantly break all 738 scenarios with an extension-not-found error.

So the block is deleted, not re-indented. The three contexts use no Mink. Behat still passes 738/738.

3. .editorconfig used an invalid value

indent_style = spaces — the spec only accepts tab or space, so editors silently ignored it and indent style was unenforced. Now space.

4. The Vagrantfile could not find the Homestead.yml that ships with the repo

Vagrantfile only looked for Homestead.yaml or Homestead.json, but the repo ships Homestead.yml — and .gitignore ignores the two names it did look for. Following the setup docs ("the Vagrant and Homestead.yml files that ship with Ushahidi", then vagrant up) aborted with Homestead settings file not found. Broken since Homestead.yml was re-added in 2023.

Homestead.yml is now added to the lookup chain, after Homestead.yaml/.json so a developer's local override still wins. Preferred over renaming the tracked file, which would land it under a gitignored name. The abort message now points at the directory it actually searches, rather than confDir (the vendor Homestead install).

⚠️ Statically validated, not boot-tested. Vagrantfile parses (ruby -c), Homestead.yml parses as YAML, and the lookup chain now resolves Homestead.yml where it previously aborted. But Homestead.yml pins provider: virtualbox, and VirtualBox on Apple Silicon cannot run the x86_64 Homestead box — so vagrant up needs an Intel Mac or a Linux host to confirm end-to-end.

Verification

Against a throwaway mariadb:10.11 stack mirroring the CI job:

Check	Result
composer lint	✅ all 3 rulesets
phpunit	✅ 176 tests, 552 assertions (was 172/534)
phpspec	✅ 10 specs, 42 examples
behat	✅ 738 scenarios, 6339 steps

🤖 Generated with Claude Code