Kaoru0822 bd8d73ab1d fix(environment): report later bundle write failures as host failures (#5581) ...

* fix(environment): report later bundle write failures as host failures

Only destination admission now refuses the selected directory as invalid
input. A path failure on a nested bundle file after admission, such as a
host pathname-length limit, is reported as an output failure that names the
host cause and the absolute failed path, with recovery guidance for the
partial folder it leaves in place.

Fixes #5522

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(environment): name the host-refused path in export permission failures

A permission failure after earlier bundle files were written was reported
as access denied for the bundle root, so the documented failed path was
lost. The refusal now names the absolute path the host reported, falling
back to the root, and keeps the root as `output_directory`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(environment): attribute pathless bundle write failures to their file

Descriptor operations such as `write` and `fsync` fail without a path, so
a disk-full failure after earlier files named only the bundle root. The
bundle writer now attributes such failures to the file it was writing.
Host-write recovery is applied only to actual host failures; an integrity
refusal keeps its own message without disk-space advice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(environment): attribute package tarball read failures to the tarball

The destination-write attribution also caught failures from reading the
admitted package tarball during the copy, so a source `EIO` named the
destination file and advised freeing disk space. Host failures are now
attributed by direction: tarball reads name the tarball with read
recovery, bundle writes name the file being written.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(environment): state which export failures name a path

The export documentation and host-write message promised a failed path
for every later write failure, but a directory sync at commit time fails
without one. They now promise the failed bundle file or package tarball
when the failure is on one, and only the cause for a folder sync.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-20 22:55:05 -07:00

..

acceptance

fix(artifacts): report a stable symlink loop as a path resolution failure (#5571)

2026-10-20 22:54:28 -07:00

boundary

fix(environment): report later bundle write failures as host failures (#5581)

2026-10-20 22:55:05 -07:00

composition

test(cli): keep IPC trace input under the Linux spawn limit (#5673)

2026-10-21 04:48:33 +08:00

conformance

fix(managed): treat extension-only module scopes as unknown identity (#5674)

2026-10-21 04:35:45 +08:00

evaluation

fix(hopper)!: verify current Linux releases with the publisher key

2026-10-15 12:15:55 +08:00

fixtures

feat(artifacts): inspect and extract PyInstaller archives

2026-10-21 12:48:29 +08:00

process-global

perf(frida): add retained summaries for session status (#5661)

2026-10-21 03:21:30 +08:00

support

perf(test): reuse one compiled CLI for the remaining hot command files (#5784)

2026-10-21 13:34:37 +08:00

ciTestSequencer.ts

perf(ci): keep fast built shards under ten minutes (#5652)

2026-10-21 03:55:40 +08:00

processOwnershipRunner.ts

…