File size: 4,765 Bytes
59db3d1
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
# Sigil computer app

Exported by REA's `export-desktop-application` from a capture of the `sigil` package
(capture Evidence `ev_c456ea9d9da0b493f94341c99f33179939590ab5785330725faac3e2bfadc980`). It was checked against agentenv-framework
0.9.1431.

- `envs/sigil/` is a computer app on the `ubuntu-24.04` base with the `reference` driver, for
  `amd64` and `arm64`. It installs `sigil` from the distribution archive, launches `sh -c cd "$HOME" 2>/dev/null; exec 'sigil' "$HOME"/'Documents/lantern-keeper.epub'` at boot and is ready
  when a window of class `sigil` appears.
- At launch the app opens `~/Documents/lantern-keeper.epub`, the seed's one document.
- Owned paths: `~/.local/share/sigil-ebook/sigil`, `~/Documents`.
  `data/get` returns their files and a typed JSON view of each; `data/reset` restores the seed.
- Seed: 24 file(s) made for the task, as saved at checkpoint `seed`.
  Text files and dconf keys spell the capture host's name as `localhost`, `user@host` as `user@localhost`
  and the home as `/home/user`, which the computer respells to its own at boot.
- Neither owned nor seeded, so the app starts without what it saved there: these files or folders, which changed
  during the capture, `~/.config/QtProject.conf`.
  To own them, capture again naming them with `state_paths` on `start_build_capture`, or `--state-path` on `capture-desktop-application`.
- Seeded as captured, though the app keeps them for its own running, so a stale one can change how it starts:
  WebKit or Chromium storage `~/.local/share/sigil-ebook/sigil/local-storage/Network Persistent State`, `~/.local/share/sigil-ebook/sigil/local-storage/Platform Notifications`, `~/.local/share/sigil-ebook/sigil/local-storage/Visited Links`; caches `~/.local/share/sigil-ebook/sigil/local-storage/GPUCache`.
- Left out of the seed: lock files the app holds while it runs, since a copied one can make it find its profile or document
  in use and keep it from starting: `~/.local/share/sigil-ebook/sigil/local-storage/Platform Notifications/LOCK`.
- Left out of the seed: the app's logs, which record facts about the capture host, such as its kernel, CPU and memory,
  and which it does not need to start: `~/.local/share/sigil-ebook/sigil/local-storage/Platform Notifications/000003.log`.
- `tasks/smoke.json` deploys the app.

Run the task with `agent-env run <this folder>`, or only the deploy with `--task smoke`.

The seed was made for this task, not taken from a user's own data; read `envs/sigil/seed/` before publishing the bundle.

## Task `fix-chapter-title-typo`

`tasks/fix-chapter-title-typo.json` deploys the app, has the agent work through the computer from the prompt below, and grades
the outcome with `artifacts/fix-chapter-title-typo-check/verify.py`, which reads the app's `data/get` views and needs
no model. It grades once the app's files have held for 3 s, so a save the app makes on its own within that
time of the agent stopping counts; each result's `settled` is false when they were still changing 15 s after the
first read. `evals/sigil.toml` names it, so a run of the bundle runs it.

> In Sigil, the title of chapter two in my ebook Documents/lantern-keeper.epub misspells "Mainland" as "Mainlnad". Fix that word in the chapter title and save the book.

Checks, each of which must pass:

- `check-1`: `{"kind":"text_equals","file":"Documents/lantern-keeper.epub","pointer":"/entries/[name=OEBPS~1Text~1Section0001_0001.xhtml]/view/root/children/[name=body]/children/[name=h1]","value":"Chapter Two: A Letter from the Mainland"}`
- `chapter-two-text-kept`: `{"kind":"text_contains","file":"Documents/lantern-keeper.epub","pointer":"/entries/[name=OEBPS~1Text~1Section0001_0001.xhtml]/view/root/children/[name=body]","value":"Her father read it twice by the stove and then put it away without a word."}`
- `chapter-one-title-kept`: `{"kind":"text_equals","file":"Documents/lantern-keeper.epub","pointer":"/entries/[name=OEBPS~1Text~1Section0001.xhtml]/view/root/children/[name=body]/children/[name=h1]","value":"Chapter One: The Lighthouse on Gull Point"}`
- `chapter-three-title-kept`: `{"kind":"text_equals","file":"Documents/lantern-keeper.epub","pointer":"/entries/[name=OEBPS~1Text~1Section0001_0002.xhtml]/view/root/children/[name=body]/children/[name=h1]","value":"Chapter Three: The Night of the Long Tide"}`

REA kept the task because its checks fail on the seed (`check-1`) and all
pass on the captured end state.

To measure a solve rate, run the task k times (3 by default) with the agent and model to measure, and count the runs
whose summary line says `passed`; a run that says `failed` did not finish and is run again rather than counted:

    agent-env run <this folder> --task fix-chapter-title-typo --agent claude-code --model MODEL