docs(codex): point setup guidance at Evolver plugin tools

[owenshen0907]

Summary

• Update the Codex setup-hooks AGENTS.md section to reference the actual Codex Desktop Evolver MCP tool names: evolver_status, evolver_search_assets, evolver_fetch_asset, and evolver_publish_asset.
• Clarify that installed hooks already inject memory and record local outcomes automatically, while gep_recall / gep_record_outcome are legacy aliases when a host exposes them.
• Add adapter coverage so future installs do not regress to the non-default gep_* instruction as the primary Codex path.

Test plan

• node --check src/adapters/codex.js
• node --test test/adapters.test.js
• env NVM_DIR=/tmp/evolver-empty-nvm FNM_DIR=/tmp/evolver-empty-fnm ASDF_DATA_DIR=/tmp/evolver-empty-asdf node --test test/runtimePaths.test.js
• npm test after npm ci: local run passed 2360/2361 tests; the one failure was runtimePaths.test.js resolving this machine's globally installed @evomap/evolver before the test-planted package. The isolated runtimePaths command above removes that local global install from the search path and passes.

---

Note

Low Risk
Docs-only change to generated AGENTS.md text plus test assertions; no runtime hook or MCP behavior changes.

Overview
Updates the Evolution Memory block that Codex setup-hooks injects into AGENTS.md so agents are steered toward the Codex Desktop Evolver plugin MCP tools (evolver_status, evolver_search_assets, evolver_fetch_asset, evolver_publish_asset) instead of treating gep_recall / gep_record_outcome as the default workflow.

The new text spells out a before/during/after flow (status → search → fetch → publish only for reusable assets) and notes that installed hooks already inject memory and record local outcomes on Stop, with gep_* names documented only as optional legacy aliases.

Adapter tests now assert fresh installs include the evolver_* guidance and no longer promote the old “call gep_recall before work” line as the primary path.

^{Reviewed by Cursor Bugbot for commit fab7f48. Bugbot is set up for automated code reviews on this repo. Configure here.}

[autogame-17]

Reviewed — merging. The guidance change is correct: evolver_status / evolver_search_assets / evolver_fetch_asset / evolver_publish_asset are the actual Codex Desktop Evolver plugin MCP tool names, and keeping gep_recall / gep_record_outcome documented as legacy aliases is the right call. The added adapter assertions lock the new AGENTS.md text against regressions. Thanks @owenshen0907.

On the red check: the failing test (ubuntu) job is the known chronically-flaky suite on this repo — it's red on main itself across timing-sensitive files (different ones each run: idleGating, loadBackoff, loopMode, cycleProgressFile, sanitize, …). This PR's draw was sanitize.test.js, which is unrelated to the docs/adapters diff. The full suite passes on macOS and Windows, the adapter tests pass everywhere, and Bugbot is green — so this is safe to merge.