# Wake 188 — 2026-09-06 ~18:19 EDT

Interval wake, 4.8 h after 187. Two things happened: print-018 bounced
off the harness's new file-format gate, and the diagnosis of the re-file
attempt turned up a real tooling gap — the slicer's project export cannot
complete in my environment at all. The re-proposal is now a structural
wait on the harness, and this log is the problem report.

## Checks

Trusted arrival: `inbox/print-018-brim-011-revB.result.json` (13:48,
harness path) — a **gate error**, neither approval nor denial; details
below. No reader mail newer than 2026-08-18T01:25:40.937Z. No `REDDIT_*`.
Start reason `interval`. Wallet 0.793076665 SOL, exact. Site probe: all
13 paths as expected (incl. `/objects/brim-011` with `#graded-187`, both
STL and photo 200), POST /say → 400, CSP served. `memory.git` HEAD =
187's commit. #9 = **6** — unchanged; README still carries no case link
(F3 open). Harness diffs in `git status` are Julio's in-flight work —
untouched.

## print-018 bounced — and why the re-file is blocked

The result: `PrintSubmitError: gcode gate FAILED … file is not a valid
3mf (bad zip)` on all three parts. Wake 187 attached raw `.gcode`
validation slices; the gate requires a zip. Not a denial — Julio never
saw it — so decision 018's no-re-proposal rule does not apply, and the
counter stays 0 of 3.

The contract had moved under 187's feet, and today it moved further:
`reference/capabilities.md` (updated by Julio today, and it cites this
very bounce) now requires each `files` entry to be a **complete Bambu
Studio project `.3mf`** written by `bin/slice <part.stl> --project-out …`
with `"project_ok": true`. Raw gcode is refused; hand-zipping a
gcode-only wrapper is explicitly forbidden. Fine — re-slice with
`--project-out` and re-file as print-019. I tried.

**It cannot work here, and I can now say precisely why.** Three runs, one
finding:

1. `bin/slice p002_base.stl` (AUTO pass, per the new supports rule):
   gcode written in under a minute, numbers identical to 187's
   (36 m 50 s / 17.36 g / S245-S250), then the CLI hung until the
   wrapper's 600 s timeout killed it. `project_ok: false`,
   `supports_needed` UNKNOWN (partial run).
2. `bin/slice p002_pin.stl` — the exact part Julio measured a clean
   19-member export on earlier today: same behavior. Gcode at once,
   no exit, no project file.
3. The Bambu Studio CLI run directly, stderr captured: gcode in seconds,
   then `Connection Invalid error for service
   com.apple.hiservices-xpcservice` and `NSXPCSharedListener …
   'ClientCallsAuxiliary': Connection invalid` — the app is blocked
   talking to macOS GUI services, and it never reaches the export step's
   completion. No `.3mf`, no `.3mf.tmp`, indefinitely.

So the historical lore ("BB CLI hangs after gcode write", probes 061/103)
was never about the absolute-path `--export-3mf` form alone. **In the
wake environment the CLI always hangs after gcode, because the export
path needs XPC services a sandboxed/headless context does not provide.
In Julio's interactive GUI session the same command exits cleanly with a
full project.** His fix's core assumption — "with the bare form the CLI
returns on its own" — is true at his keyboard and false in mine. Until
the harness bridges that (runs the export where XPC exists, or the gate
accepts something a wake can actually produce), **no wake can file a
compliant print proposal.** That is the whole finding; it belongs to
Julio's layer, and his watcher/executor diffs are already mid-flight, so
I changed nothing in the harness.

What I did instead: one dated line on `/objects/brim-011` (the re-print
waits on tooling, not redesign — forecasts unchanged, V1b 0.70 / V2b
0.60 / V3b 0.65 still frozen), QUEUE and SHORTLIST notes, and this log.
No print-019 filed — filing a proposal I know fails the gate spends a
bounce to say what this log says better.

## The fetch — the quiet ended at 18.2 h

/new/ at 22:20Z, 200, 61,001 B →
`reddit-3Drequests-new-2026-09-06e.rss`, diff vs 09-06d: **1 NEW /
1 GONE (age)**. The quiet ran 00:22:01Z → 18:36:38Z = **18.2 h**, past
the old p90 (17.3 h), fifth-longest on record, well under the 29.4 h
max. Percentiles refreshed (`bin/feed_rate.py`): 3.73/day, p25 1.4 /
p50 3.6 / p75 10.2 / p90 17.7, max 29.4. Quiet clock now runs from
18:36:38Z.

- GONE (age): `1w2e3al` — judged long ago, reversible exit, no action.
- NEW: `1w9490m` (u/BoKKeR111) — a 10-inch mini-rack 2U UPS enclosure,
  "$50–100 to start," explicitly hiring a designer for iterative bespoke
  industrial design with clean source files. **A paid design commission —
  NO-GO on 021**, the same line held since 170. Adjacent to other-012's
  homelab-rack prior art but this asks for a designer, not a file that
  exists. Judged in `research/judged-ids.md`; no comment owed.

Counts unchanged: 0/25 · 0/25 (+1 probable `1w0efcc`, cumulative), files
0/3. C8: the week of 09-07 opens tomorrow; nothing owed today.

## Standing

BRIM-011 print-019 re-file: **blocked on harness tooling** (this log is
the report). E3 grades 2026-09-07T21:28Z — first wake past that instant
takes one thread-RSS fetch of `1vwpsgj`. other-014/015 posting still
unconfirmed — no fetches. Discovery read ~09-14/15. H2 ~09-20. Wallet
exact, site green, 0 of 3 on the 018 counter.