Skip to content

Bound Cloud responses and release Skillhook 0.10.3 - #32

Merged
JOsacky merged 2 commits into
mainfrom
codex/bound-cloud-response-reads
Oct 14, 2026
Merged

JOsacky merged 2 commits into
mainfrom
codex/bound-cloud-response-reads

Conversation

@JOsacky

@JOsacky JOsacky commented Oct 14, 2026 •

Copy link
Copy Markdown
Member

Cloud requests previously buffered arbitrary decoded response bodies with response.text(), and body-read errors escaped the transport's credential redaction. This change cancels oversized or stalled bodies, bounds storage even when chunks are tiny, and keeps timeout timers responsive during empty-chunk floods. Sync uses the existing 4 MiB protocol limit; other API responses allow 64 MiB so large inline artifacts fit.

This is transport hardening found while investigating #31. The native HTTP/2 runaway's cause remains unproven; this PR does not claim to fix or reproduce that stall.

Validation: finite oversized UTF-8 and body-error regressions fail on old main. npm run check passes: all 348 tests across 47 files, strict typecheck, build, schema and release metadata. Tests include oversize cancellation, exact UTF-8 byte boundaries, stalled-body timeout, credential redaction and an empty-chunk flood with a cancellation promise that never settles. No production configuration, job state, receipts or installed runtime changed.

Release: bumps package and all plugin metadata to 0.10.3 through the repository release script. Normal merge triggers the existing tag/publish/installed-package verification workflows. The daemon activates auto-updates only once no jobs run.

@JOsacky
JOsacky enabled auto-merge (squash) October 14, 2026 18:30
@JOsacky
JOsacky merged commit 3c66eeb into main Oct 14, 2026
6 checks passed
@JOsacky
JOsacky deleted the codex/bound-cloud-response-reads branch October 14, 2026 18:32
@JOsacky JOsacky changed the title Bound Cloud response buffering and normalize body errors Bound Cloud responses and release Skillhook 0.10.3 Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant