system stringlengths 1.23k 1.54k | user stringlengths 861 9.59k | think stringlengths 63 3.06k | answer stringlengths 21 6.29k |
|---|---|---|---|
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required specs and checking the existing seed catalog.
Now let me read the Wave 6 catalog and its wave-wide laws.
Clean results: `-NonInteractive` mandatory-miss gives exit 1, empty stdout, one stderr line; parameter-set ambiguity reproduces for both call shapes. Next: switch semantics and `... | Wave 6, chunk 6P1 complete — all 6 catalog items authored, all gates green. These are the first PowerShell seeds in the repo (no `ps-*` collisions existed; pwsh 7.6.3 and the `powershell→pwsh` preflight mapping were already in place).
**ps-windowcast** — build-cli — `[CmdletBinding()]`/`param()` maintenance-window car... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-8 enterprise-integration seed authoring preamble
You are the sole seed author for one Wave-8 chunk. Repo root is the current
directory. These instructions are mandatory and supplement `tasks/SEED_SPEC.md`.
## Read before writing
1. Read all of `tasks/SEED_SPEC.md`.
2. Read the Wave-8 laws, evidence map, and a... | I'll start by reading the spec and catalog, then check for existing 8D seeds.
The layout is clear. Now the research phase — I'll search for the current official Confluent docs for all four interfaces.
Research is complete for all four seeds. Now let me inspect the existing Wave-8 C# seed for the xunit project layout ... | All gates are green. Wave-8 chunk 8D is complete — final report:
## Chunk 8D — 4/4 seeds authored, all gates passed
Every seed follows the Wave-8 laws: research-driven protected contract (`docs/contract.json` + `docs/official_sources.json` in `test_files`), hermetic loopback mocks with dummy credentials, injected sle... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-8 enterprise-integration seed authoring preamble
You are the sole seed author for one Wave-8 chunk. Repo root is the current
directory. These instructions are mandatory and supplement `tasks/SEED_SPEC.md`.
## Read before writing
1. Read all of `tasks/SEED_SPEC.md`.
2. Read the Wave-8 laws, evidence map, and a... | I'm the Wave-8 chunk 8A seed author. Let me start by reading the spec, the Wave-8 catalog, and checking the existing seeds.
Now let me check if any other Wave-8 seeds have already been authored (to see a wave-8-style layout), and look at existing project seed structure.
I'm the first Wave-8 author. Let me inspect one... | All four Wave-8 chunk 8A seeds are authored, audited `[complete]`, smoke-failing on baseline, and `[valid]` under `validate_seeds.py` (reference patch applies, verify passes, protected files untouched). No pre-existing seeds were modified; the only repo additions are the four new seed directories and their workspaces.
... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required specs and checking the current state of the seed catalog.
Deprecation and generics lints behave as expected. Now checking Thread.stop availability, fallthrough/finally/serial lint texts, and this-escape triggers:
CS1998 didn't fire even in isolation — that's unexpected and matters f... | All 6 catalog items for chunk 5W4 are authored, self-checked, and gated. Final report:
**java-woolbale** — warnfix-java (5W4 #1): `-Xlint:all -Werror` generics retrofit of a wool-bale intake registry — raw-type sites ×5, unchecked casts/conversions, and a generic-varargs heap-pollution declaration whose three frozen c... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required specs and checking the existing seed catalog.
Let me check the wave-4 Part I chunk details and the go-dashfeed example for how networked go seeds are structured.
Writing the go-lifegrid fixtures and reference implementation:
Now the task.json with the user-voice prompt:
go-lifegri... | Final report — wave 7, chunk 7G2, all 6 catalog items authored:
**go-lifegrid** — build-game — Conway's Life package with bounded and toroidal modes, `.cells` fixture loading, N-step evolution, and exact pinned ASCII frames (blinker/toad oscillation, glider torus lap in 24 steps, glider dying against a bounded corner ... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-8 enterprise-integration seed authoring preamble
You are the sole seed author for one Wave-8 chunk. Repo root is the current
directory. These instructions are mandatory and supplement `tasks/SEED_SPEC.md`.
## Read before writing
1. Read all of `tasks/SEED_SPEC.md`.
2. Read the Wave-8 laws, evidence map, and a... | I'm the Wave-8 chunk 8L author. Let me start by reading the spec, the catalog, and checking the existing seed IDs.
No existing jira seeds — all 4 items are missing. Now let me read the Wave-8 laws and chunk 8L catalog.
Now let me inspect a recently-authored Wave-8 seed for layout conventions.
The pattern is clear. L... | All four Wave-8 chunk 8L seeds are authored, validated, and gated. Final report:
## Chunk 8L — Atlassian Jira Cloud integrations (4/4 complete)
**Research.** No `jira-*` ID collisions existed; all catalog IDs used as-is. The Atlassian api-group reference pages are too large for WebFetch (truncated), so exact operatio... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required specs and checking the existing seed catalog.
All six target ids are new. Now let me read the wave constraints and an example C++ seed.
Now let me look at an existing wave-7 C++ build seed as the formatting example.
Cribbage oracle values verified by hand-checking several. Now writ... | All six chunk-7G8 seeds are authored, self-checked, and gated.
**cpp-chessperft** — build-game — full-rules chess move generator (FEN load, sorted UCI legal-move lists, castling/EP/promotion/pins) verified by pinned perft counts at depths 1–4 over six fixture positions.
Smoke: `[ok ] cpp-chessperft: pre-fix verify fa... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-8 enterprise-integration seed authoring preamble
You are the sole seed author for one Wave-8 chunk. Repo root is the current
directory. These instructions are mandatory and supplement `tasks/SEED_SPEC.md`.
## Read before writing
1. Read all of `tasks/SEED_SPEC.md`.
2. Read the Wave-8 laws, evidence map, and a... | I'll start by reading the required spec and catalog files, then check existing seed IDs.
No ID collisions. Now reading the Wave-8 laws and chunk 8Z catalog.
Now I'll inspect exactly one existing Wave-8 seed for layout.
Let me look at the docs fixtures and a bit of the test harness in this same seed to understand the... | All gates pass. The other modified/untracked paths in git status belong to parallel authors and pre-existing work — my changes are confined to the four seed directories and their workspaces (which `validate_seeds.py` reset to baseline after proving the patches). No probes or temp artifacts remain, and per the integrity... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required specs and checking the current state of the seed catalog.
Deprecation and generics lints behave as expected. Now checking Thread.stop availability, fallthrough/finally/serial lint texts, and this-escape triggers:
CS1998 didn't fire even in isolation — that's unexpected and matters f... | All 6 catalog items for chunk 5W4 are authored, self-checked, and gated. Final report:
**java-woolbale** — warnfix-java (5W4 #1): `-Xlint:all -Werror` generics retrofit of a wool-bale intake registry — raw-type sites ×5, unchecked casts/conversions, and a generic-varargs heap-pollution declaration whose three frozen c... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-8 enterprise-integration seed authoring preamble
You are the sole seed author for one Wave-8 chunk. Repo root is the current
directory. These instructions are mandatory and supplement `tasks/SEED_SPEC.md`.
## Read before writing
1. Read all of `tasks/SEED_SPEC.md`.
2. Read the Wave-8 laws, evidence map, and a... | I'll start by reading the required spec and catalog files, and checking existing seed IDs.
No ID collisions — none of the four Meraki IDs exist. Now let me read the Wave-8 catalog and laws.
Now I'll inspect exactly one existing Wave-8 seed for layout (a Go project one, relevant to my chunk).
Let me look at the rest ... | All gates are green. Final report:
# Wave-8 chunk 8Y — Cisco Meraki integrations: 4/4 seeds authored
All four catalog items are authored, smoke-checked, reference-proven, and validated (`validate_seeds.py --only …` run exactly once: **4 valid, 0 invalid**). No pre-existing seeds, pipeline code, catalogs, or traces we... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required specs and checking the existing seed catalog.
All six target ids are new. Now let me read the wave constraints and an example C++ seed.
Now let me look at an existing wave-7 C++ build seed as the formatting example.
Cribbage oracle values verified by hand-checking several. Now writ... | All six chunk-7G8 seeds are authored, self-checked, and gated.
**cpp-chessperft** — build-game — full-rules chess move generator (FEN load, sorted UCI legal-move lists, castling/EP/promotion/pins) verified by pinned perft counts at depths 1–4 over six fixture positions.
Smoke: `[ok ] cpp-chessperft: pre-fix verify fa... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'm authoring the 6 x86-64 assembly seeds for wave 7 chunk 7A1. First, let me read the required docs and survey existing seeds.
The pipeline already supports `asm` (preflight checks gcc). Let me look at a recent wave-7 C build seed for format conventions.
Blackjack pins done (order-sensitive rollhash noted). Now the ... | All six seeds audit `[complete]`. Work is done — final report below.
## Wave 7 / Chunk 7A1 — final report
| id | kind-category | description | smoke | reference verify |
|---|---|---|---|---|
| asm-lifestep | build-game | One Life generation over a row-major byte grid, toroidal wrap with the multi-count tiny-grid law... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required specs and checking the existing seed catalog.
Let me check the wave-4 Part I chunk details and the go-dashfeed example for how networked go seeds are structured.
Writing the go-lifegrid fixtures and reference implementation:
Now the task.json with the user-voice prompt:
go-lifegri... | Final report — wave 7, chunk 7G2, all 6 catalog items authored:
**go-lifegrid** — build-game — Conway's Life package with bounded and toroidal modes, `.cells` fixture loading, N-step evolution, and exact pinned ASCII frames (blinker/toad oscillation, glider torus lap in 24 steps, glider dying against a bounded corner ... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | # Wave-4 authoring-agent preamble (read this first, follow exactly)
You are authoring seeds for the fable-code training-data pipeline. Repo root:
this directory. Everything below is mandatory.
## Read before writing anything
1. `tasks/SEED_SPEC.md` — the seed spec, quality bar, and mandatory
self-check. It is the... | I'll start by reading the required docs and checking the existing seed catalog.
JDK 26 is available. Let me set up task tracking and look at examples of java build seeds and a full wave-7 game prompt.
Now the test contract:
One correction — my "landing in opponent's empty pit" test needs 4 stones in pit 6 (store + b... | All 6 catalog items for chunk 7G6 are authored, self-checked, and round-trip verified.
**Final report — wave 7, chunk 7G6 (java ×6, all `build-game`)**
| id | idx | description | smoke | reference verify |
|---|---|---|---|---|
| java-adventure | 1 | OO text-adventure engine: plain-text room-graph format, typed Room/... |
You are an autonomous coding agent running on the user's machine.
You work in the current directory of a real repository. Use your tools to read, search, create, and edit files and to run shell commands (tests, builds, type-checkers). Some tools are deferred: only their names are known until you load their schemas wit... | Data-platform ticket. Our telemetry archiver pushes nightly rollup blobs to S3 with a single put_object call, and last night a 3.4 GB rollup timed out four times and the job gave up — we resend the whole object every time anything hiccups. I want a proper multipart uploader package, `s3mpu`, built on the official AWS S... | I'll start by reading the workspace fixtures and tests, then do the required official-docs research before writing any code.
Fixtures and tests reviewed. Now the required research — loading WebSearch/WebFetch and reading the current official AWS docs before writing any code.
The live docs check out against the fixtur... | Done — `bash run_verify.sh` is green (14 passed), and the review finding that caused the last rejection is fixed and verified with an adversarial probe.
**What was built.** A new `s3mpu/` package, split into `constants.py` (the pinned documented values), `planning.py` (`select_strategy` and `plan_parts` with the 1-bas... |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- -