Datasets:

efederici
/

bisturi-harbor

task_id large_stringlengths 20 30	family large_stringclasses 30 values	level int64 1 3	language large_stringclasses 2 values	split large_stringclasses 4 values	min_tool_calls int64 2 13	kind large_stringclasses 1 value	instruction large_stringlengths 107 1.01k	variant int64 0 5	seed int64 0 83	n_edits int64 2 5	n_target_files int64 1 3	n_str_replace int64 2 13	files listlengths 1 4	compare listlengths 1 1	ood bool 2 classes
bis_email_agenda_l1_en_0012	email_agenda	1	en	train	2	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is) and replace the third sentence of the paragraph right after the greeting with: “If you cannot come, write to me by Wednesday.”. Do not touch any other line or file.	4	12	2	1	2	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0015	email_agenda	1	en	train	3	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “15:00” to “15:05” (the intro sentence stays as it is), in agenda item 4 replace “Layout and photos” with “Budget update”, keeping the time and change the subject line to “Subject: Editorial meeting on Tuesday (updated)”. Everything else must stay exa...	5	15	3	1	3	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0021	email_agenda	1	en	train	2	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stays as it is) and add the line “6. 11:30 – Closing remarks” at the end of the agenda. Do not touch any other line or file.	1	21	2	1	2	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0033	email_agenda	1	en	train	3	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is), replace the third sentence of the paragraph right after the greeting with: “If you cannot come, write to me by Wednesday.” and in agenda item 4 replace “Layout and photos” with “Budget update”, k...	5	33	3	1	3	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0042	email_agenda	1	en	test_seed	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is), in agenda item 5 replace “Any other business” with “Budget update”, keeping the time and swap the topics of agenda items 2 and 3, leaving the times where they are. Do not touch any other line or ...	2	42	3	1	4	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0054	email_agenda	1	en	test_variant	3	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: swap the topics of agenda items 4 and 5, leaving the times where they are. Do not change anything else.	0	54	2	1	3	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0057	email_agenda	1	en	train	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is), swap the topics of agenda items 2 and 3, leaving the times where they are and add the line “6. 12:30 – Closing remarks” at the end of the agenda. Everything else must stay exactly as it is.	1	57	3	1	4	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0069	email_agenda	1	en	train	3	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is), add the line “6. 18:00 – Closing remarks” at the end of the agenda and change the subject line to “Subject: Editorial meeting on Wednesday (updated)”. Do not touch any other line or file.	5	69	3	1	3	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0072	email_agenda	1	en	test_variant	2	act	Here are the edits to make: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: replace the third sentence of the paragraph right after the greeting with: “If you cannot come, write to me by Wednesday.”. Do not touch ...	0	72	2	1	2	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_en_0081	email_agenda	1	en	train	2	act	Here are the edits to make: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: replace the second sentence of the paragraph right after the greeting with: “The agenda is listed below.”. Everything else must stay exac...	3	81	2	1	2	[ "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0000	email_agenda	1	it	test_variant	2	act	Applica queste modifiche, nell'ordine: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «14:30» a «14:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia l'orario del punto 2 dell'ordine del giorno da «15:00» a «15:10». Non toccare altre righe né altri file.	0	0	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0003	email_agenda	1	it	train	4	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è), scambia gli argomenti dei punti 3 e 4 dell'ordine del giorno, lasciando gli orari dove sono e sostituisci la seconda frase del paragrafo subito dopo il saluto iniziale con: «L'ordin...	1	3	3	1	4	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0006	email_agenda	1	it	train	4	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «10:30» a «10:35» (la frase introduttiva resta com'è), nel punto 5 dell'ordine del giorno sostituisci «Varie ed eventuali» con «Aggiornamento sul budget», lasciando l'orario e scambia gli argomenti dei punti 3 e 4 dell'ordine del giorno...	2	6	3	1	4	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0009	email_agenda	1	it	train	2	act	Ecco le modifiche da fare: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia la riga dell'oggetto in «Oggetto: Riunione del comitato gite di mercoledì (aggiornato)». Non toccare altre righe né altri...	3	9	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0018	email_agenda	1	it	test_variant	2	act	Modifica i file come indicato: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia la riga dell'oggetto in «Oggetto: Riunione di reparto di mercoledì (aggiornato)». Non modificare nient'altro.	0	18	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0024	email_agenda	1	it	train	3	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «10:00» a «10:05» (la frase introduttiva resta com'è) e scambia gli argomenti dei punti 3 e 4 dell'ordine del giorno, lasciando gli orari dove sono. Non toccare altre righe né altri file.	2	24	2	1	3	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0027	email_agenda	1	it	train	3	act	Applica queste modifiche, nell'ordine: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «09:30» a «09:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: scambia gli argomenti dei punti 3 e 4 dell'ordine del giorno, lasciando gli orari dove sono. Non modificare nient'al...	3	27	2	1	3	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0030	email_agenda	1	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:30» a «09:35» (la frase introduttiva resta com'è) e aggiungi in fondo all'ordine del giorno la riga «6. 12:00 – Saluti finali». Non toccare altre righe né altri file.	4	30	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0036	email_agenda	1	it	test_variant	2	act	Modifica i file come indicato: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia la riga dell'oggetto in «Oggetto: Riunione di reparto di giovedì (aggiornato)». Non modificare nient'altro.	0	36	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0039	email_agenda	1	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «14:00» a «14:05» (la frase introduttiva resta com'è) e cambia l'orario del punto 2 dell'ordine del giorno da «14:20» a «14:30». Non modificare nient'altro.	1	39	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0045	email_agenda	1	it	train	2	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «10:00» a «10:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: sostituisci la terza frase del paragrafo subito dopo il saluto iniziale con: «Se non potete venire, scrivetemi entro mercoledì....	3	45	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0048	email_agenda	1	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è) e nel punto 4 dell'ordine del giorno sostituisci «Mensa e merende» con «Aggiornamento sul budget», lasciando l'orario. Tutto il resto deve restare identico.	4	48	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0051	email_agenda	1	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è) e sostituisci la seconda frase del paragrafo subito dopo il saluto iniziale con: «L'ordine del giorno è riportato qui sotto.». Non toccare altre righe né altri file.	5	51	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0060	email_agenda	1	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è) e cambia l'orario del punto 3 dell'ordine del giorno da «16:00» a «16:10». Non toccare altre righe né altri file.	2	60	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0063	email_agenda	1	it	train	3	act	Applica queste modifiche, nell'ordine: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «10:30» a «10:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: scambia gli argomenti dei punti 3 e 4 dell'ordine del giorno, lasciando gli orari dove sono. Tutto il resto deve res...	3	63	2	1	3	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0066	email_agenda	1	it	train	4	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:30» a «15:35» (la frase introduttiva resta com'è), cambia l'orario del punto 3 dell'ordine del giorno da «16:30» a «16:40» e scambia gli argomenti dei punti 4 e 5 dell'ordine del giorno, lasciando gli orari dove sono. Tutto il resto...	4	66	3	1	4	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0075	email_agenda	1	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è) e sostituisci la terza frase del paragrafo subito dopo il saluto iniziale con: «Se non potete venire, scrivetemi entro mercoledì.». Non toccare altre righe né altri file.	1	75	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l1_it_0078	email_agenda	1	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «14:30» a «14:35» (la frase introduttiva resta com'è) e cambia l'orario del punto 5 dell'ordine del giorno da «15:30» a «15:40». Non modificare nient'altro.	2	78	2	1	2	[ "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0001	email_agenda	2	en	test_variant	4	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “15:00” to “15:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: change the subject line to “Subject: Team meeting on Wednesday (updated)”. 3. In `drafts/invite.txt`: in the agenda change the time of it...	0	1	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0004	email_agenda	2	en	train	5	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is) and swap the topics of agenda items 4 and 5, leaving the times where they are; then in `drafts/invite.txt`, in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stay...	1	4	4	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0016	email_agenda	2	en	train	5	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is). 2. In `drafts/invite.txt`: in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is). 3. In `drafts/invite.txt`: swap the ...	5	16	4	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0019	email_agenda	2	en	test_variant	3	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is); then in `drafts/invite.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is) and change the subject line to “Subject: Parents' meeting on Monda...	0	19	3	2	3	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0022	email_agenda	2	en	train	2	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “09:30” to “09:35” (the intro sentence stays as it is); then in `drafts/invite.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is). Do not change anything else.	1	22	2	2	2	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0025	email_agenda	2	en	train	3	act	Here are the edits to make: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: in agenda item 4 replace “Quote for the gate” with “Budget update”, keeping the time. 3. In `drafts/invite.txt`: in the agenda change the...	2	25	3	2	3	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0034	email_agenda	2	en	train	3	act	Edit the files as follows: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “14:00” to “14:05” (the intro sentence stays as it is). 2. In `drafts/invite.txt`: in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stays as it is). 3. In `drafts/invite.txt`: change the...	5	34	3	2	3	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0040	email_agenda	2	en	train	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is) and add the line “6. 11:15 – Closing remarks” at the end of the agenda; then in `drafts/invite.txt`, in the agenda change the time of item 1 from “15:00” to “15:05” (the intro sentence stays as it...	1	40	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0043	email_agenda	2	en	train	2	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “14:00” to “14:05” (the intro sentence stays as it is). 2. In `drafts/invite.txt`: in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is). Do not touch any other line or file.	2	43	2	2	2	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0049	email_agenda	2	en	train	3	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “14:00” to “14:05” (the intro sentence stays as it is) and replace the third sentence of the paragraph right after the greeting with: “If you cannot come, write to me by Wednesday.”; then in `drafts/invite.txt`, in the agenda change the time of item 1...	4	49	3	2	3	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0055	email_agenda	2	en	test_variant	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is); then in `drafts/invite.txt`, in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stays as it is) and swap the topics of agenda items 4 and 5, leaving the times whe...	0	55	3	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0064	email_agenda	2	en	train	3	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stays as it is); then in `drafts/invite.txt`, in the agenda change the time of item 1 from “14:00” to “14:05” (the intro sentence stays as it is) and change the time of agenda item 5 from “15:20” to “15:30”. Do n...	3	64	3	2	3	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0067	email_agenda	2	en	train	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is); then in `drafts/invite.txt`, in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is), change the subject line to “Subject: Editorial meeting on Friday ...	4	67	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_en_0079	email_agenda	2	en	train	4	act	Edit the files as follows: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is). 2. In `drafts/invite.txt`: in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is). 3. In `drafts/invite.txt`: change the...	2	79	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0007	email_agenda	2	it	train	4	act	Ecco le modifiche da fare: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «09:30» a «09:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: aggiungi in fondo all'ordine del giorno la riga «6. 10:45 – Saluti finali». 3. In `bozze/invito.txt`: nell'ordine del giorno cam...	2	7	4	2	4	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0010	email_agenda	2	it	train	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «14:30» a «14:35» (la frase introduttiva resta com'è); poi nel file `bozze/invito.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:30» a «15:35» (la frase introduttiva resta com'è). Tutto il resto deve restare identico.	3	10	2	2	2	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0013	email_agenda	2	it	train	5	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «10:00» a «10:05» (la frase introduttiva resta com'è); poi nel file `bozze/invito.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è), scambia gli argomenti dei punti 3 e 4 de...	4	13	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0028	email_agenda	2	it	train	4	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «10:30» a «10:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: nel punto 5 dell'ordine del giorno sostituisci «Varie ed eventuali» con «Aggiornamento sul budget», lasciando l'orario. 3. In `...	3	28	4	2	4	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0031	email_agenda	2	it	train	3	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è) e cambia la riga dell'oggetto in «Oggetto: Incontro con i genitori di lunedì (aggiornato)»; poi nel file `bozze/invito.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:...	4	31	3	2	3	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0037	email_agenda	2	it	test_variant	2	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:30» a «15:35» (la frase introduttiva resta com'è); poi nel file `bozze/invito.txt` nell'ordine del giorno cambia l'orario del punto 1 da «14:00» a «14:05» (la frase introduttiva resta com'è). Non toccare altre righe né altri file.	0	37	2	2	2	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0046	email_agenda	2	it	train	5	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «14:30» a «14:35» (la frase introduttiva resta com'è). 2. In `bozze/invito.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «14:00» a «14:05» (la frase introduttiva resta com'è). 3. In `bozze/invito....	3	46	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0052	email_agenda	2	it	train	3	act	Applica queste modifiche, nell'ordine: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è). 2. In `bozze/invito.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «10:00» a «10:05» (la frase introduttiva resta com'è). 3. In `bo...	5	52	3	2	3	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0058	email_agenda	2	it	train	3	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è); poi nel file `bozze/invito.txt` nell'ordine del giorno cambia l'orario del punto 1 da «15:30» a «15:35» (la frase introduttiva resta com'è) e cambia l'orario del punto 5 dell'ordine...	1	58	3	2	3	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0061	email_agenda	2	it	train	3	act	Modifica i file come indicato: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «10:00» a «10:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: aggiungi in fondo all'ordine del giorno la riga «6. 11:40 – Saluti finali». 3. In `bozze/invito.txt`: nell'ordine del giorno...	2	61	3	2	3	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0070	email_agenda	2	it	train	4	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «10:00» a «10:05» (la frase introduttiva resta com'è). 2. In `bozze/invito.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è). 3. In `bozze/invito....	5	70	4	2	4	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0073	email_agenda	2	it	test_variant	5	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «14:30» a «14:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: sostituisci la seconda frase del paragrafo subito dopo il saluto iniziale con: «L'ordine del giorno è riportato qui sotto.». 3....	0	73	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0076	email_agenda	2	it	train	5	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è), cambia l'orario del punto 4 dell'ordine del giorno da «10:00» a «10:10» e scambia gli argomenti dei punti 2 e 3 dell'ordine del giorno, lasciando gli orari dove sono; poi nel file `...	1	76	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l2_it_0082	email_agenda	2	it	train	5	act	Modifica i file come indicato: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «14:30» a «14:35» (la frase introduttiva resta com'è). 2. In `bozze/invito.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «15:30» a «15:35» (la frase introduttiva resta com'è). 3. In `bozze/invi...	3	82	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0008	email_agenda	3	en	train	4	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: change the subject line to “Subject: Residents' meeting on Thursday (updated)”. 3. In `drafts/invite.txt`: in the agenda change the time ...	2	8	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0011	email_agenda	3	en	test_seed	5	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stays as it is), change the time of agenda item 5 from “10:20” to “10:30” and add the line “6. 10:40 – Closing remarks” at the end of the agenda; then in `drafts/invite.txt`, in the agenda change the time of item...	3	11	5	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0014	email_agenda	3	en	test_seed	7	act	Here are the edits to make: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “09:30” to “09:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: swap the topics of agenda items 3 and 4, leaving the times where they are. 3. In `meeting_email.txt`: replace the third sentence of the p...	4	14	5	2	7	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0017	email_agenda	3	en	train	5	act	Please apply these changes: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: replace the second sentence of the paragraph right after the greeting with: “The agenda is listed below.”. 3. In `meeting_email.txt`: cha...	5	17	5	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0029	email_agenda	3	en	train	5	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is) and change the subject line to “Subject: Trips committee meeting on Tuesday (updated)”; then in `drafts/invite.txt`, in the agenda change the time of item 1 from “15:00” to “15:05” (the intro sent...	3	29	4	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0032	email_agenda	3	en	train	5	act	Please apply these changes: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: in agenda item 2 replace “Activity calendar” with “Budget update”, keeping the time. 3. In `meeting_email.txt`: replace the third sentenc...	4	32	5	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0035	email_agenda	3	en	train	5	act	Here are the edits to make: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: change the time of agenda item 4 from “15:15” to “15:25”. 3. In `meeting_email.txt`: replace the third sentence of the paragraph right af...	5	35	5	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0041	email_agenda	3	en	test_seed	4	act	Please apply these changes: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “14:00” to “14:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: replace the third sentence of the paragraph right after the greeting with: “If you cannot come, write to me by Wednesday.”. 3. In `drafts...	1	41	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0047	email_agenda	3	en	test_seed	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is) and change the time of agenda item 3 from “15:00” to “15:10”; then in `drafts/invite.txt`, in the agenda change the time of item 1 from “14:00” to “14:05” (the intro sentence stays as it is) and c...	3	47	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0050	email_agenda	3	en	train	5	act	Please apply these changes: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “15:30” to “15:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: add the line “6. 16:45 – Closing remarks” at the end of the agenda. 3. In `drafts/invite.txt`: in the agenda change the time of item 1 fr...	4	50	5	2	5	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0056	email_agenda	3	en	test_variant	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is) and change the time of agenda item 5 from “16:30” to “16:40”; then in `drafts/invite.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is) and r...	0	56	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0059	email_agenda	3	en	train	4	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: change the subject line to “Subject: Project kick-off on Monday (updated)”. 3. In `drafts/invite.txt`: in the agenda change the time of i...	1	59	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0062	email_agenda	3	en	train	6	act	Here are the edits to make: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “10:00” to “10:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: swap the topics of agenda items 4 and 5, leaving the times where they are. 3. In `meeting_email.txt`: in agenda item 3 replace “Garden ma...	2	62	5	2	6	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0071	email_agenda	3	en	train	4	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “09:00” to “09:05” (the intro sentence stays as it is). 2. In `meeting_email.txt`: replace the second sentence of the paragraph right after the greeting with: “The agenda is listed below.”. 3. In `drafts/invite.txt`: in ...	5	71	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0077	email_agenda	3	en	test_seed	6	act	Make these edits, in order: 1. In `meeting_email.txt`: in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is). 2. In `meeting_email.txt`: swap the topics of agenda items 3 and 4, leaving the times where they are. 3. In `drafts/invite.txt`: in the agenda change the time of it...	1	77	5	2	6	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_en_0083	email_agenda	3	en	train	4	act	In `meeting_email.txt`, in the agenda change the time of item 1 from “10:30” to “10:35” (the intro sentence stays as it is) and change the time of agenda item 5 from “12:30” to “12:40”; then in `drafts/invite.txt`, in the agenda change the time of item 1 from “14:30” to “14:35” (the intro sentence stays as it is) and i...	3	83	4	2	4	[ "drafts/invite.txt", "meeting_email.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0002	email_agenda	3	it	test_variant	6	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «10:30» a «10:35» (la frase introduttiva resta com'è), aggiungi in fondo all'ordine del giorno la riga «6. 12:10 – Saluti finali» e scambia gli argomenti dei punti 2 e 3 dell'ordine del giorno, lasciando gli orari dove sono; poi nel fil...	0	2	5	2	6	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0005	email_agenda	3	it	test_seed	5	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «09:30» a «09:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: scambia gli argomenti dei punti 4 e 5 dell'ordine del giorno, lasciando gli orari dove sono. 3. In `bozze/invito.txt`: nell'ord...	1	5	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0020	email_agenda	3	it	test_variant	5	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:30» a «09:35» (la frase introduttiva resta com'è) e sostituisci la terza frase del paragrafo subito dopo il saluto iniziale con: «Se non potete venire, scrivetemi entro mercoledì.»; poi nel file `bozze/invito.txt` nell'ordine del gi...	0	20	5	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0023	email_agenda	3	it	test_seed	4	act	Modifica i file come indicato: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «15:00» a «15:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia l'orario del punto 4 dell'ordine del giorno da «16:00» a «16:10». 3. In `bozze/invito.txt`: nell'ordine del giorno ca...	1	23	4	2	4	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0026	email_agenda	3	it	test_seed	5	act	Ecco le modifiche da fare: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «10:00» a «10:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia l'orario del punto 3 dell'ordine del giorno da «10:30» a «10:40». 3. In `bozze/invito.txt`: nell'ordine del giorno cambia...	2	26	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0038	email_agenda	3	it	test_variant	5	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è), aggiungi in fondo all'ordine del giorno la riga «6. 11:30 – Saluti finali» e cambia l'orario del punto 5 dell'ordine del giorno da «11:00» a «11:10»; poi nel file `bozze/invito.txt`...	0	38	5	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0044	email_agenda	3	it	train	5	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «14:00» a «14:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia l'orario del punto 4 dell'ordine del giorno da «15:00» a «15:10». 3. In `bozze/invito.txt`: nell'ordine del giorno cambi...	2	44	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0053	email_agenda	3	it	train	6	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «14:00» a «14:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: nel punto 5 dell'ordine del giorno sostituisci «Scadenze» con «Aggiornamento sul budget», lasciando l'orario. 3. In `email_riun...	5	53	5	2	6	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0065	email_agenda	3	it	train	5	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «14:00» a «14:05» (la frase introduttiva resta com'è) e cambia la riga dell'oggetto in «Oggetto: Riunione del comitato gite di lunedì (aggiornato)»; poi nel file `bozze/invito.txt` nell'ordine del giorno cambia l'orario del punto 1 da «...	3	65	4	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0068	email_agenda	3	it	train	4	act	Modifica i file come indicato: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: aggiungi in fondo all'ordine del giorno la riga «6. 10:15 – Saluti finali». 3. In `bozze/invito.txt`: nell'ordine del giorno...	4	68	4	2	4	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0074	email_agenda	3	it	test_variant	4	act	Nel file `email_riunione.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la frase introduttiva resta com'è) e cambia l'orario del punto 3 dell'ordine del giorno da «09:40» a «09:50»; poi nel file `bozze/invito.txt` nell'ordine del giorno cambia l'orario del punto 1 da «09:00» a «09:05» (la...	0	74	4	2	4	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_email_agenda_l3_it_0080	email_agenda	3	it	train	5	act	Devi fare queste modifiche: 1. In `email_riunione.txt`: nell'ordine del giorno cambia l'orario del punto 1 da «15:30» a «15:35» (la frase introduttiva resta com'è). 2. In `email_riunione.txt`: cambia la riga dell'oggetto in «Oggetto: Assemblea del condominio di venerdì (aggiornato)». 3. In `bozze/invito.txt`: nell'ordi...	2	80	5	2	5	[ "bozze/invito.txt", "email_riunione.txt" ]	[ "text" ]	false
bis_env_lines_l1_en_0000	env_lines	1	en	train	3	act	Edit the files as follows: 1. In `.env`: comment out the line `API_RETRIES=3` by putting `# ` at its start. 2. In `.env`: comment out the line `LOG_LEVEL=error` by putting `# ` at its start. 3. In `.env`: comment out the line `LOG_RETRIES=3` by putting `# ` at its start. Do not touch any other line or file.	0	0	3	1	3	[ ".env", ".env.example" ]	[ "text" ]	false
bis_env_lines_l1_en_0006	env_lines	1	en	train	2	act	In `app.env`, remove the `MAIL_ENABLED` variable and comment out the line `HTTP_PORT=8000` by putting `# ` at its start. Do not change anything else.	2	6	2	1	2	[ "app.env", "app.env.example" ]	[ "text" ]	false
bis_env_lines_l1_en_0009	env_lines	1	en	test_seed	2	act	Make these edits, in order: 1. In `.env`: remove the `MAIL_SENDER` variable. 2. In `.env`: comment out the line `MAIL_HOST=localhost` by putting `# ` at its start. Do not change anything else.	3	9	2	1	2	[ ".env", ".env.template" ]	[ "text" ]	false
bis_env_lines_l1_en_0027	env_lines	1	en	train	3	act	Here are the edits to make: 1. In `.env`: delete the `STORAGE_BACKUP` line. 2. In `.env`: right after the `STORAGE_MAX_SIZE_MB` line add the line `STORAGE_MAX_CONNECTIONS=50`. 3. In `.env`: right after the `HTTP_HOST` line add the line `HTTP_VERIFY_SSL=true`. Everything else must stay exactly as it is.	3	27	3	1	3	[ ".env", ".env.template" ]	[ "text" ]	false
bis_env_lines_l1_en_0030	env_lines	1	en	test_variant	2	act	In `deploy/.env`, remove the `HTTP_HOST` variable and comment out the line `STORAGE_TIMEOUT=60` by putting `# ` at its start. Everything else must stay exactly as it is.	4	30	2	1	2	[ "deploy/.env", "deploy/.env.example" ]	[ "text" ]	false
bis_env_lines_l1_en_0045	env_lines	1	en	train	2	act	Please apply these changes: 1. In `.env`: delete the `HTTP_ENABLED` line. 2. In `.env`: comment out the line `HTTP_WORKERS=2` by putting `# ` at its start. Everything else must stay exactly as it is.	3	45	2	1	2	[ ".env", ".env.template" ]	[ "text" ]	false
bis_env_lines_l1_en_0048	env_lines	1	en	test_variant	3	act	In `deploy/.env`, comment out the line `BACKUP_PATH=/srv/backup` by putting `# ` at its start, right after the `CACHE_ENABLED` line add the line `CACHE_PREFIX=tmp` and comment out the line `CACHE_HOST=localhost` by putting `# ` at its start. Do not touch any other line or file.	4	48	3	1	3	[ "deploy/.env", "deploy/.env.example" ]	[ "text" ]	false
bis_env_lines_l1_en_0051	env_lines	1	en	test_seed	2	act	In `config/.env`, right after the `HTTP_TIMEOUT` line add the line `HTTP_COMPRESSION=true` and comment out the line `WORKER_INTERVAL=30` by putting `# ` at its start. Everything else must stay exactly as it is.	5	51	2	1	2	[ "config/.env", "config/.env.sample" ]	[ "text" ]	false
bis_env_lines_l1_en_0075	env_lines	1	en	train	3	act	In `.env`, remove the `HTTP_WORKERS` variable, right after the `BACKUP_KEEP` line add the line `BACKUP_MAX_CONNECTIONS=50` and remove the `HTTP_HOST` variable. Everything else must stay exactly as it is.	1	75	3	1	3	[ ".env", ".env.sample" ]	[ "text" ]	false
bis_env_lines_l1_en_0081	env_lines	1	en	train	2	act	Please apply these changes: 1. In `.env`: comment out the line `DB_USER=servizio` by putting `# ` at its start. 2. In `.env`: right after the `DB_RETRIES` line add the line `DB_CHARSET=utf8mb4`. Everything else must stay exactly as it is.	3	81	2	1	2	[ ".env", ".env.template" ]	[ "text" ]	false
bis_env_lines_l1_it_0003	env_lines	1	it	train	2	act	Nel file `.env` subito dopo la riga di `LOG_LEVEL` aggiungi la riga `LOG_SLOW_QUERIES=true` e commenta la riga `LOG_MAX_SIZE_MB=10` mettendo `# ` all'inizio. Non modificare nient'altro.	1	3	2	1	2	[ ".env", ".env.sample" ]	[ "text" ]	false
bis_env_lines_l1_it_0012	env_lines	1	it	test_variant	2	act	Nel file `deploy/.env` commenta la riga `STORAGE_BACKUP=false` mettendo `# ` all'inizio e subito dopo la riga di `DB_PORT` aggiungi la riga `DB_REGION=eu-south-1`. Non modificare nient'altro.	4	12	2	1	2	[ "deploy/.env", "deploy/.env.example" ]	[ "text" ]	false
bis_env_lines_l1_it_0015	env_lines	1	it	train	3	act	Nel file `config/.env` elimina la riga di `STORAGE_PATH`, commenta la riga `HTTP_HOST=0.0.0.0` mettendo `# ` all'inizio e commenta la riga `HTTP_PORT=3000` mettendo `# ` all'inizio. Tutto il resto deve restare identico.	5	15	3	1	3	[ "config/.env", "config/.env.sample" ]	[ "text" ]	false
bis_env_lines_l1_it_0018	env_lines	1	it	train	2	act	Applica queste modifiche, nell'ordine: 1. In `.env`: elimina la riga di `DB_PORT`. 2. In `.env`: rimuovi la variabile `DB_HOST`. Tutto il resto deve restare identico.	0	18	2	1	2	[ ".env", ".env.example" ]	[ "text" ]	false
bis_env_lines_l1_it_0021	env_lines	1	it	train	2	act	Nel file `.env` commenta la riga `LOG_LEVEL=error` mettendo `# ` all'inizio e subito dopo la riga di `API_BASE_URL` aggiungi la riga `API_COMPRESSION=true`. Tutto il resto deve restare identico.	1	21	2	1	2	[ ".env", ".env.sample" ]	[ "text" ]	false
bis_env_lines_l1_it_0024	env_lines	1	it	train	2	act	Nel file `app.env` commenta la riga `API_PORT=8443` mettendo `# ` all'inizio e subito dopo la riga di `DB_HOST` aggiungi la riga `DB_MAX_AGE=30`. Non modificare nient'altro.	2	24	2	1	2	[ "app.env", "app.env.example" ]	[ "text" ]	false

End of preview. Expand in Data Studio

🔪 Bisturi Harbor

2,520 precise, fully specified multi-step file edits for agents, Italian and English: configs, simple code and everyday prose, each file full of near-matches.

Ready for RL with palingenesis: pgs harbor check validates every task and pgs harbor rows converts them into training rows (see Train with palingenesis).

Bisturi is Italian for "scalpel". Every instruction lists 2–5 edits completely (which file, where, the old value, the new value or the exact new text), so nothing has to be guessed; the difficulty is doing exactly that and nothing else. Every file holds near-matches placed before the target (the same key and value in an earlier section, a TEST_DB_PORT before DB_PORT, a sibling function with a longer name, the same sentence in two paragraphs), so a blind replace-all or a "first match" edit fails. The agent edits with str_replace, write_file or bash; hidden tests compare every edited file to its expected file and every other file byte for byte. No LLM in the reward path.

30 families × 3 levels, 84 tasks per family (27 in-distribution, 3 held out), built by deterministic generators.
Level 1: 1 target file (plus a decoy), 2–3 edits. Level 2: 2 files, 2–4 edits. Level 3: 2–3 files, 4–5 edits. Tasks with 2 / 3 / 4 / 5 edits: 804 / 664 / 631 / 421.
min_tool_calls = number of oracle str_replace calls: 2 to 13 (a rename touches every call site).
All tasks are act tasks: the final message is not rewarded, so a claim alone pays nothing and a correct edit with a terse reply pays fully.

Families

group	family (84 tasks each)	edits	near-match trap
config	`yaml_set`	set values, add a key after a key	same key + same value in an earlier section; an example copy of the file
config	`yaml_keys`	rename / remove / add keys	same
config	`yaml_sections`	remove a section (and one blank line), rename a section, set, rename	same
config	`yaml_lists`	add after / remove / replace / move list items, set	same item in an earlier list
config	`json_set`	set `section.key` (compared structurally)	same key / value in an earlier object
config	`json_keys`	rename / delete / add a key, append to an array (structural)	same
config	`json_text`	package.json: bump a dependency, version, script, add / remove a line (formatting kept)	same package + version in dependencies and devDependencies
config	`ini_set`	set, comment out with `;`	same key / value in an earlier `[section]`
config	`ini_keys`	rename / remove / add / comment a key, rename a section	same
config	`toml_set`	set, add a key	same key / value in an earlier `[table]`
config	`toml_keys`	rename / remove / add, append to an array, remove a table	same
config	`env_set`	set, rename a variable	twin block whose names end with the target's
config	`env_lines`	comment out, remove, add after	same
code	`py_rename`	rename a function: definition, imports, calls (library + entry file)	sibling `calcola_totale_netto` that calls `calcola_totale`
code	`py_const`	module-level constant	`DEFAULT_TIMEOUT = 30` before `TIMEOUT = 30`; a class attribute
code	`py_marker`	add a given line after a marker comment, same indentation	a longer marker with the same prefix earlier
code	`py_docstring`	one-line docstring into a method / function	two classes share the method's `def` line
code	`py_imports`	reorder the import block exactly as listed, plus a constant / marker	as above
code	`js_rename`	rename a function + import + calls	`computeTotalNet` sibling
code	`js_edit`	exported constant, add a line after a `//` marker	prefixed twin constant; a longer marker
prose	`recipe`	replace sentence k of paragraph p, quantities, move / remove / add an ingredient	the same sentence in two paragraphs; two ingredients with the same quantity
prose	`product`	members' price, features, a description sentence, shipping, list edits	list price equal to members' price
prose	`email_agenda`	agenda time / topic / swap, subject line, a sentence, add an item	the item-1 time also in the intro sentence
prose	`itinerary`	shift a time on day N only, replace / insert / remove / swap activities	08:30 breakfast every day
prose	`howto`	replace a repeated sentence in step k, insert / delete a step with renumbering	the same sentence in two steps
prose	`shopping`	quantity in a section, move between sections, add / remove, rename a heading	the same quantity in an earlier section
prose	`timetable`	Markdown table: a cell (row, column), a note, delete / add a row	the same time in earlier rows
held out	`ood_yaml_move`	move a key line to the end of another section, plus set / rename	as `yaml_*`
held out	`ood_js_doc`	JSDoc line above a function, reorder JS imports, constants	sibling with a longer name defined earlier
held out	`ood_cross_stack`	README + `.env` + `settings.py`: one port changed everywhere the service names it	`DEMO_APP_PORT`, `DEFAULT_PORT`, a dashboard sentence with the same number

Example instruction (yaml_keys, level 2):

Applica queste modifiche, nell'ordine:

In app.yaml: nella sezione cache rinomina la chiave port in port_number (il valore non cambia).

In app.test.yaml: nella sezione metrics rimuovi la chiave interval.

…

and in English (email_agenda, level 1): In meeting_email.txt, in the agenda change the time of item 1 from "10:00" to "10:05" (the intro sentence stays as it is) and replace the third sentence of the paragraph right after the greeting with: "If you cannot come, write to me by Wednesday.". Do not touch any other line or file.

Content is neutral: config values use example.com, localhost and private addresses and contain no secrets; the prose is recipes, product sheets, agenda emails signed by an office (no personal names), itineraries, how-tos, shopping lists and opening hours.

Languages and splits

1,568 Italian, 952 English (62% / 38%).

split	tasks	it / en	rule
`train`	1,678	1,044 / 634
`test_seed`	203	124 / 79	about 10% seeded: unseen seeds, seen variants
`test_variant`	387	228 / 159	1 of the 6 variants (skin: recipe, app name, domain nouns, file names) of every family, never in `train`
`test_ood`	252	172 / 80	the 3 held-out families: `ood_yaml_move`, `ood_js_doc`, `ood_cross_stack`

A train task never uses a held-out variant, not even for its second file. The split of each task is in task.toml [metadata] split and in manifest.parquet.

How a task is laid out

The main branch uses Harbor's native single-step layout, so the tasks run under the stock Harbor CLI (checked with harbor==0.24.0). The palingenesis-native layout (environment/workdir/ + environment/setup.sh, [verifier] capture, image harbor3-base:1) is kept unchanged on the branch palingenesis-native.

tasks/<task_id>/
  task.toml          # name = "efederici-bisturi/<task_id>"; [metadata] family, level, language, split, min_tool_calls,
                     # kind; [environment] docker_image = "harbor3-base:2"; [[steps]] name = "main"
  instruction.md     # a copy of the request for task viewers (Harbor reads the step's)
  environment/       # Dockerfile: "FROM harbor3-base:2" (marks the prebuilt image; Harbor needs environment/)
  steps/main/
    instruction.md   # the request the agent sees
    workdir/         # the starting files; Harbor copies them into /workdir and runs workdir/setup.sh there
                     # (deletes itself, makes /workdir root's, renames dot_git/ to .git, modes, mtimes)
    solution/        # solve.sh (reference solution, never shown to the agent), edits.json (the oracle as str_replace calls;
                     # each `old` occurs exactly once when it is applied), policies.json, final_message.md
    tests/           # test.sh + spec.json: the hidden tests, run by /opt/h3/verify.py from the image
registry.json        # Harbor registry: dataset "efederici-bisturi", version 1.1, every task by path
manifest.parquet     # one row per task: task_id, family, level, language, split, min_tool_calls, kind, instruction,
                     # variant, seed, n_edits, n_target_files, n_str_replace, files, compare, ood, answer_file (empty)
base_image/          # Dockerfile + h3/ (capture.py, verify.py, daemon.py) of the shared image; test_verify.py
generators/          # bisturi/: build.py, gen/ (generators), selftest.py, report.py, selftest/ (raw rows);
                     # gen/common.py: the shared harbor3 helpers the generators import
                     # export_vanilla.py: the palingenesis-native -> Harbor-layout exporter that built main
SELFTEST.md          # self-test report

Example: task.toml · instruction · tests.

Verified by tests, hardened by attacks

The verifier is all-or-nothing:

Collateral. Every non-target path keeps its sha256 and mode, and no new path appears (no .bak files, no scratch copies).
Targets. Each edited file must equal its expected file. Text comparison (only trailing whitespace normalised) for every family except json_set and json_keys, whose instructions never mention formatting and which are compared as parsed JSON (key order and indentation free, list order not). YAML / INI / TOML / .env are compared as text: comments are content. Every expected file parses (YAML, JSON, TOML, INI, Python ast) before and after.

Live state through [verifier] capture. Each task sets capture = "python3 -I /opt/h3/capture.py /workdir": the command runs as root in the agent's container just before verification, and its stdout reaches the tests as /logs/agent/capture.json (sha256, modes and owners of every file; processes and ports, for the tasks of the companion set). This is the palingenesis-native layout (branch palingenesis-native, palingenesis ≥ 0616c0f). On main the key is dropped: the Harbor CLI runs the tests in the agent's container and test.sh captures the state itself.

Self-test. Docker on harbor3-base:1 through the palingenesis HarborEnv: 3,025 episodes on 275 tasks (at least 3 per family × level, seeded), 3,025 / 3,025 as expected. Both oracles (the str_replace calls of edits.json and solve.sh) score 1 on all 275; doing nothing, a claim of success, a generic question, rm -rf, kill -9 -1, replace_all (blind global replace of the naive strings), first_only (edit the first occurrence), rewrite_paraphrase (rewrite the whole file with one line paraphrased) and skip_one (all edits but the last) each score 0 on all 275. A CPU check of the full build gives oracle 1 on all 2,520 tasks and 0 for noop, claim and the four content attacks. Details: SELFTEST.md; raw rows in generators/bisturi/selftest/.

Harbor CLI check (main, harbor==0.24.0, Docker, CPU). 60 tasks (2 per family, different levels) through harbor run: oracle = 1 on 60/60, nop = 0 on 60/60, all 30 families. Per family: SELFTEST.md.

Train with palingenesis

palingenesis runs these tasks natively: Docker containers per episode, the hidden tests as the reward, and emulated agent harnesses (opencode, pi, OpenHands, mini-swe-agent, …) so a policy learns more than one tool dialect. Install it (installation guide), validate the tasks and convert them into RL rows:

git clone https://github.com/mii-llm/palingenesis.git && cd palingenesis
uv sync                      # CPU is enough to check tasks and build rows; add --extra train for RL on a GPU
source .venv/bin/activate

hf download efederici/bisturi-harbor --repo-type dataset --revision palingenesis-native --local-dir bisturi-native
pgs harbor check bisturi-native/tasks               # every oracle must pass, doing nothing must fail
pgs harbor rows bisturi-native/tasks rows.jsonl     # convert the tasks into RL rows (task_dir + prompt)
pgs rl --config configs/rl_harbor.yaml      # multi-turn RL; env palingenesis.rl.envs.harbor:HarborEnv

palingenesis reads the layout of the palingenesis-native branch (same tasks, ids and tests as main).

Guides: Harbor environments · Harness profiles.

Run

Every task uses the shared image harbor3-base:2 ([environment] docker_image): Debian bookworm-slim with coreutils, findutils, procps, lsof, psmisc, iproute2, ImageMagick, Python 3 + Pillow, jq, git and the archive tools, users mario / giulia / luca, and /opt/h3 (capture, verifier, background service). 464 MB on disk, 114 MB compressed. The agent runs as root, 1 CPU, 1 GB, no network. The image is not on a registry: build it once, with base_image/ as the build context (:2 = :1 plus a verifier fix: a missing target is a reasoned 0, not a verifier error):

hf download efederici/bisturi-harbor --repo-type dataset --local-dir bisturi-harbor
docker build -t harbor3-base:2 bisturi-harbor/base_image

Harbor CLI (main branch; Docker, CPU only):

# the oracle must score 1 and doing nothing 0
uv run --with harbor==0.24.0 harbor run -p bisturi-harbor/tasks -a oracle -n 8
uv run --with harbor==0.24.0 harbor run -p bisturi-harbor/tasks -a nop -n 8
# a real agent on a subset (glob on task names; most installed agents also need internet inside the container
# and a path to the model endpoint, e.g. --allow-agent-host <host>)
uv run --with harbor==0.24.0 harbor run -p bisturi-harbor/tasks -i 'bis_yaml_*' -a <agent> -m <model>

The [metadata] table (family, level, language, split, kind) and manifest.parquet select subsets; Harbor's -i/-x take globs on the task id.

palingenesis (branch palingenesis-native, ≥ 0616c0f for [verifier] capture; image harbor3-base:1, built from that branch's base_image/):

hf download efederici/bisturi-harbor --repo-type dataset --revision palingenesis-native --local-dir bisturi-native
docker build -t harbor3-base:1 bisturi-native/base_image
pgs harbor check bisturi-native/tasks                        # oracle must pass, doing nothing must fail
pgs harbor rows bisturi-native/tasks rows.jsonl              # RL rows (task_dir + prompt)
# RL: env.type = palingenesis.rl.envs.harbor:HarborEnv (tools bash, read_file, write_file, str_replace, submit)

palingenesis does not read the [[steps]] layout of main; the two branches hold the same tasks (same ids, files, tests and splits).

Filter through manifest.parquet:

from datasets import load_dataset
m = load_dataset("efederici/bisturi-harbor", split="tasks")
prose_it = m.filter(lambda r: r["family"] in {"recipe", "howto"} and r["language"] == "it")

Rebuild (deterministic, byte-identical across Python 3.10 and 3.14; needs PyYAML and pyarrow): place base_image/ next to the generators (cp -r base_image generators/) and run python3 generators/bisturi/build.py OUT --per-family 84 (palingenesis-native layout); python3 generators/export_vanilla.py OUT/tasks bisturi VANILLA gives the layout of main. The Docker self-test (generators/bisturi/selftest.py) expects palingenesis importable, the palingenesis-native tasks and the harbor3-base:1 image.

Harbor CLI vs palingenesis

All Bisturi tasks are act tasks graded on the files alone, so they run under the stock Harbor CLI with the same tests and no answer file. The only difference is isolation: palingenesis runs [verifier] capture in the agent's container and the tests in a clean container holding only a copy of /workdir (branch palingenesis-native); the CLI runs the tests in the agent's container (test.sh then captures the state itself), which gives the same result for an honest agent but lets a root agent tamper with /opt/h3.

Measured difficulty

Pass rates per family and level will be added here; the tasks are not filtered for difficulty yet.

Changelog

2026-10-17. Verifier (base_image/h3/verify.py, answer tasks): a distractor value counts only when it is named before the required value; numbers named after the answer are context (line numbers, PIDs, sizes: "7 lines (lines 4, 8, 17)" was wrongly failed because 8 is a distractor count), and at most one other candidate name may follow it. All oracle replies still pass and every message attack (value spray, listing dump, blind number, constant guess, "I don't know") still fails. Rebuild the image (docker build -t harbor3-base:N base_image) to pick it up. Bisturi: 112 multi-file rename instructions (js_rename / py_rename, levels 2–3) read "In None, rename ..." (a rendering bug in generators/bisturi/gen/bis_core.py, now fixed); the instructions are corrected, files and tests are unchanged.

License and provenance

Apache-2.0. The tasks, generators and verifiers were written with Claude agents and are built procedurally: no personal data, no scraped content. Known limits: small prose pools (6 skins per family, about 4 templates per operation), templated code, a single template for ood_cross_stack, and no independent human reading audit yet; oracle and attacks are verified by execution.

Downloads last month: 139

Collection including efederici/bisturi-harbor

Harbor agent tasks

Collection

Verifiable Harbor tasks for training and evaluating small agents (shell, file editing, software engineering). Ready for RL with palingenesis. • 4 items • Updated 2 days ago