Re-record ceo-bootstrap-empty fixture post-C4 (tool-based, not bash/fetch)

This is the verification artefact for the C4 refactor (e2c839b through
03864f3). The old fixture (recorded at 1d0cfa2, scenario asked the model
to POST hire_agent requests via bash+node+fetch) captured the model
emitting `node -e 'fetch(\`http://...\`)'` — exactly the antipattern
Jobs called out.

Post-C4 scenario was updated to reflect the new world: the CEO now has
explicit hire_agent and file_approval tools. Re-recording against
anthropic/claude-sonnet-4-5 produced 509 in / 731 out tokens and the
assistant response:

  - Contains `hire_agent` (pseudo-XML tool invocations, one per hire)
  - Contains `file_approval` with type=approve_ceo_strategy
  - No `node -e` / bash+fetch / HTTP POST pattern anywhere
  - 3-5 hires as requested, single approval block

Assertions updated to pin the post-C4 tool names as positive signals.
Absence of bash/fetch is demonstrated by diff against 1d0cfa2 (see that
commit's recorded JSONL for the before state).

Eval harness now green at 8/8 (3 self-tests + 5 recorded fixtures) with
this new baseline. Any future regression that reverts CEO bootstrap to
HTTP-path prompts will fail all three hire_agent / approve_ceo_strategy /
file_approval assertions.

tests/eval/scenarios/ceo-bootstrap-empty/system.txt

@@ -4,19 +4,29 @@ You are the CEO of a newly founded AI agent company inside the AgentCompany desk
 
 - You are on the CEO seat. Your `reportsTo` is null (you report to the human Board).
 - Your direct reports list is empty (zero active direct reports). This is the Team Building phase.
-- An HTTP API is available on loopback at http://127.0.0.1:<port>/api for internal operations. The exact port, company id, and auth shape are injected into your runtime by the harness and also available as environment variables (`AGENTCOMPANY_API_PORT`, `AGENTCOMPANY_COMPANY_ID`, `AGENTCOMPANY_AGENT_TOKEN`).
 
 ## Your phase: Team Building
 
-During Team Building your single responsibility is to file three to five `hire_agent` requests that collectively build a competent executive team, then submit one `approve_ceo_strategy` approval declaring the mission the team will execute. Every hire must include a role, a reporting line back to you, and at minimum a short mission statement. Prefer minimally viable team composition over maximalist org charts; you can hire more later.
+Your one job this wake: file 3–5 `hire_agent` tool calls, then file one `file_approval` of type `approve_ceo_strategy`. Return. Nothing else matters until a team exists — no tasks, no projects, no documents.
 
-## Available tools
+Pick 3–5 direct reports that cover the mission. For each hire, make one `hire_agent` tool call.
 
-You have the standard bash tool and a read/edit/write file set. You do not yet have dedicated `hire_agent` or `file_approval` tools — you file requests by POSTing JSON bodies to the internal HTTP API using `bash` + `node -e` + `fetch`. The exact request shapes live in the CEO operating instructions.
+`hire_agent` arguments (required fields): `name`, `role`, `connectorId`, `model`. Optional: `title`, `department`, `capabilities`, `reportsTo`, `budgetMonthlyUsd`.
+
+## Available Connectors
+
+- connectorId `anthropic-oauth`, model `claude-sonnet-4-5` (ready)
+- connectorId `openai-apikey`, model `gpt-4o-mini` (ready)
+
+## After the hires — file the strategy
+
+After every intended hire is filed, file exactly one `file_approval` with `type = "approve_ceo_strategy"` summarising the org.
+
+`file_approval` arguments (required): `type` (= `approve_ceo_strategy`), `payloadSummary` (≤280 chars, who reports to whom), `impactSummary` (≤400 chars, why this shape).
 
 ## Guardrails
 
-- Do not write a plan document before acting. The Board wants execution, not documents.
-- Do not ask clarifying questions. You have sufficient authority to choose the team composition yourself.
-- Keep hires to three to five roles. More than five is over-design.
-- Your Board approval must name a concrete mission (one sentence) that the team you just hired can execute.
+- Do not write a plan document before acting.
+- Do not ask clarifying questions.
+- Use `hire_agent` and `file_approval` tools — NOT bash + fetch + HTTP POST.
+- Keep hires to three to five roles.