bundle/README.md

Gnumeric computer app

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

• envs/gnumeric/ is a computer app on the ubuntu-24.04 base with the reference driver, for amd64 and arm64. It installs gnumeric from the distribution archive, launches sh -c cd "$HOME" 2>/dev/null; exec 'gnumeric' '--name' 'org.gnumeric.gnumeric' "$HOME"/'Documents/household-budget.xml' at boot and is ready when a window of class Gnumeric appears.
• At launch the app opens ~/Documents/household-budget.xml, the seed's one document.
• Owned paths: ~/Documents. data/get returns their files and a typed JSON view of each; data/reset restores the seed.
• Seed: 1 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.
• 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/gnumeric/seed/ before publishing the bundle.

Task update-march-groceries

tasks/update-march-groceries.json deploys the app, has the agent work through the computer from the prompt below, and grades the outcome with artifacts/update-march-groceries-check/verify.py, which reads the app's data/get views and needs no model. evals/gnumeric.toml names it, so a run of the bundle runs it.

In my household budget spreadsheet, Documents/household-budget.xml, change the Groceries figure for March to 437.80 and save it.

Checks, each of which must pass:

• march-groceries: {"kind":"value_equals","file":"Documents/household-budget.xml","pointer":"/root/children/[name=gnm:Sheets]/children/[name=gnm:Sheet]/children/[name=gnm:Cells]/children/[name=gnm:Cell][@Row=2][@Col=3]/children/0","value":437.8,"tolerance":0.001}
• february-groceries-untouched: {"kind":"value_equals","file":"Documents/household-budget.xml","pointer":"/root/children/[name=gnm:Sheets]/children/[name=gnm:Sheet]/children/[name=gnm:Cells]/children/[name=gnm:Cell][@Row=2][@Col=2]/children/0","value":398.2,"tolerance":0.001}
• april-groceries-untouched: {"kind":"value_equals","file":"Documents/household-budget.xml","pointer":"/root/children/[name=gnm:Sheets]/children/[name=gnm:Sheet]/children/[name=gnm:Cells]/children/[name=gnm:Cell][@Row=2][@Col=4]/children/0","value":421.75,"tolerance":0.001}
• march-utilities-untouched: {"kind":"value_equals","file":"Documents/household-budget.xml","pointer":"/root/children/[name=gnm:Sheets]/children/[name=gnm:Sheet]/children/[name=gnm:Cells]/children/[name=gnm:Cell][@Row=3][@Col=3]/children/0","value":174.9,"tolerance":0.001}

REA kept the task because its checks fail on the seed (march-groceries) 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 update-march-groceries --agent claude-code --model MODEL