Claudeagent and ClaudeagentA line of a job's log no longer shows twice when the runner sends its batch again. The runner numbers each batch of a job's log (1 for the first, counting up through the job) and a batch keeps its number when a report whose answer was lost is sent again; g1t keeps that number in the log's new `chunk` column (migration 0016), under a unique index on the job and the number, and a batch whose number it already has is left out in the same statement that takes the next `seq`. A runner that numbers nothing has every batch kept, as before, and a job run again starts its numbers afresh, its earlier log having moved aside. The service's tests run the statement against the migrations in SQLite, and the runner's against a server that fails the first report. The Actions guide says so.0f6ef54History
- ..
- backup.test.ts
- backup.ts
- bump.test.ts
- bump.ts
- computer-shape.ts
- computer.test.ts
- computer.ts
- credentials.test.ts
- credentials.ts
- delegate.test.ts
- delegate.ts
- egress.test.ts
- egress.ts
- gate.test.ts
- guard.ts
- hosted.test.ts
- hosted.ts
- hub.ts
- index.ts
- instructions.test.ts
- instructions.ts
- lifecycle.test.ts
- lifecycle.ts
- mentions.test.ts
- mentions.ts
- model-defaults.test.ts
- model-env.test.ts
- model-env.ts
- repo-instructions.ts
- self-hosted.test.ts
- self-hosted.ts
- workflow-hosts.test.ts