feat(jobs): ten minutes as well as ten messages #743

Merged

coilyco-ops merged 1 commit from feat/ten-minutes-or-ten-messages into main

2026-08-13 22:01:46 +00:00

coilyco-ops commented

2026-08-13 22:00:05 +00:00

Member

The other half of the ceiling Kai decided on issue 236:

10 messages or 10 minutes, whichever we hit first

Issue 356 landed the message half and the seam under it. This adds the time half, which was not buildable before the counter existed.

What ships

maxJobContentWindow = 10 * time.Minute, and ErrJobContentWindowClosed separate from ErrJobContentExhausted. Two ceilings, two errors, so an executor and an operator can tell a job that said too much from one that took too long. The refusal reason also reaches telemetry as ceiling.

The decision inside it

The window opens on the first message, not at submission. A job that sat in the queue for an hour still gets its full ten minutes to answer. Queue time is not answer time, and a job punished for waiting would be a bound on the runner's backlog wearing a content ceiling's name.

That is the one judgement here and it is asserted directly by TestTheWindowOpensOnTheFirstMessage.

Verification

ward exec gate PASS on all six steps.

Two mutations, both in runs where the package compiles:

the window never closing: fails TestTheAnswerWindowClosesOnTime
the window opening at submission: fails that test plus TestTheWindowOpensOnTheFirstMessage, TestTheBoundIsPerJob, TestContentAndProgressDoNotShareABound

My first attempt at the first mutation was a build failure rather than a test failure - setting the condition to false left opened unused. That is issue 653's trap, where a non-compiling package reads as "caught". Redone as a comparison that still uses the variable.

Not in this change

Threading. Kai said both conditions should trigger it. Neither ceiling threads yet; they refuse. That is the next slice and it needs the thread binding in jobthread.go, which is its own piece of work.

File upload, the third output mode.

closes #742

The other half of the ceiling Kai decided on [issue 236](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/236): > 10 messages or 10 minutes, whichever we hit first [Issue 356](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/356) landed the message half and the seam under it. This adds the time half, which was not buildable before the counter existed. ## What ships `maxJobContentWindow = 10 * time.Minute`, and `ErrJobContentWindowClosed` **separate from** `ErrJobContentExhausted`. Two ceilings, two errors, so an executor and an operator can tell a job that said too much from one that took too long. The refusal reason also reaches telemetry as `ceiling`. ## The decision inside it **The window opens on the first message, not at submission.** A job that sat in the queue for an hour still gets its full ten minutes to answer. Queue time is not answer time, and a job punished for waiting would be a bound on the runner's backlog wearing a content ceiling's name. That is the one judgement here and it is asserted directly by `TestTheWindowOpensOnTheFirstMessage`. ## Verification `ward exec gate` PASS on all six steps. Two mutations, both in runs where the package compiles: - the window never closing: fails `TestTheAnswerWindowClosesOnTime` - the window opening at submission: fails that test plus `TestTheWindowOpensOnTheFirstMessage`, `TestTheBoundIsPerJob`, `TestContentAndProgressDoNotShareABound` **My first attempt at the first mutation was a build failure rather than a test failure** - setting the condition to `false` left `opened` unused. That is [issue 653](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/653)'s trap, where a non-compiling package reads as "caught". Redone as a comparison that still uses the variable. ## Not in this change **Threading.** Kai said both conditions should trigger it. Neither ceiling threads yet; they refuse. That is the next slice and it needs the thread binding in `jobthread.go`, which is its own piece of work. **File upload**, the third output mode. closes #742

coilyco-ops added 1 commit

2026-08-13 22:00:05 +00:00

feat(jobs): ten minutes as well as ten messages

ci / image-build (pull_request) Successful in 23s

Details

ci / test (pull_request) Successful in 37s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

8a8064d916

356 landed the message half of the ceiling Kai decided on 236. This adds the
time half, which was not buildable before the counter existed.

Two ceilings, two errors: ErrJobContentWindowClosed is separate from
ErrJobContentExhausted, so an executor and an operator can tell a job that said
too much from one that took too long. The reason reaches telemetry as ceiling.

The window opens on the first message rather than at submission. A job that sat
in the queue for an hour still gets its full ten minutes, because queue time is
not answer time and a bound on the backlog should not wear a content ceiling's
name.

closes #742

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-13 22:00:05 +00:00

coilyco-ops referenced this pull request

2026-08-13 22:01:43 +00:00

Model did not response to long form multi turn message request #236

coilyco-ops merged commit 5ffd7dc0da into main

2026-08-13 22:01:46 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 22:01:48 +00:00

Merge pull request 'feat(jobs): ten minutes as well as ten messages' (#743) from feat/ten-minutes-or-ten-messages into main