shadowdaoandClaude Opus 5.5
209ed00fdd
Secret Scan / scan (push) Successful in 6s
Build App (Preview) / compute-version (pull_request) Successful in 5s
Secret Scan / scan (pull_request) Successful in 12s
Build App (Preview) / create-release (pull_request) Successful in 1s
Build App (Preview) / build-macos (pull_request) Successful in 3m16s
Build App (Preview) / test (pull_request) Successful in 4m9s
Build App (Preview) / build-windows (pull_request) Successful in 6m46s
Build App (Preview) / build-linux (pull_request) Successful in 10m1s
Build App (Preview) / prune-previews (pull_request) Successful in 2s
get_container_staleness failed on every start/stop of a real container with "OUTPUT_LIMIT: Command output exceeded 8388608 bytes": the manifest's flat `find /workspace` walk alone was 8.6 MB (94k entries of worktrees, node_modules, vendored trees in the writable layer). Pruning node_modules and .git by name was measured on that container and only reached 6.3 MB. - Walk /workspace two levels deep; each non-empty directory at depth 2 is one `S` entry, sized from a new ###SUMMARY section (`du -sbx`). The entry comes from find, so a failed du costs the size, never the dir. Measured on the same container: 8.6 MB -> ~25 kB. - compute_verbatim_paths: summaries count as content (not an empty tree) and are exempt from presence-in-base, since a summary hides which paths are inside; restore's --skip-old-files keeps the per-file guarantee. The verbatim set is unchanged: it already pruned to /workspace/<x>. - manifest_from_container gets its own 32 MiB budget via a new exec_oneshot_as_limited, and an OUTPUT_LIMIT is reported as an actionable sentence (describe_manifest_failure) instead of the buffer message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>