desktop: the payload fixed — 7.4GB→144MB, dev keys out, boot-smoke gate
- desktop:dist cleans dist/ + .next/standalone before next build: the trace sweep was shipping the PREVIOUS build's DMG inside every new one (standalone/dist = 8.0GB inside the app; measured 7.4GB DMG → 144MB). - the same sweep shipped the repo-root auth.json (dev BYOK keys, byte-identical) in every DMG ever built — excluded in the trace and REFUSED by a new build-server.mjs guard (.env* belt-and-braces). - WARNING (next.config.ts): dir-style trace excludes (dist/** etc., "./"-anchored or not) strip server-external packages to bare package.jsons — pi-ai/pi-agent-core lost their dist/, the packaged server 500'd on ERR_MODULE_NOT_FOUND. Only the three verified-safe entries stay. - new scripts/smoke-server.mjs gates desktop:dist between payload curation and packaging: boots the standalone exactly as the Electron shell does (temp LH_DATA_DIR, empty auth) and requires 200s on / + graph/models/settings. Caught both defects above on its first day. - entitlements: allow-unsigned-executable-memory dropped (2019-era relic per current electron-builder docs; weakens hardened runtime). - pi-ai + pi-agent-core pinned exact 1.0.2 — persisted chat records carry their wire shapes; post-release a bump is a migration event. Gates: typecheck, lint, 1459/1459 tests, full desktop:dist + smoke PASS.
This commit is contained in:
@@ -11,9 +11,33 @@ const nextConfig: NextConfig = {
|
||||
// tracing sweeps the repo's real data/ — chat records, graph ledgers —
|
||||
// INTO the standalone bundle. A shipped desktop app would carry the
|
||||
// developer's session data inside it.
|
||||
//
|
||||
// SECRETS (2026-10-08, caught in the payload audit): the same sweep
|
||||
// ships the repo-root auth.json — the DEV BYOK key store — byte-identical
|
||||
// into the DMG (the packaged app never reads it: the shell passes
|
||||
// LH_AUTH_FILE → userData). Excluded here; build-server.mjs also REFUSES
|
||||
// to package any standalone still containing it. .env* belt-and-braces
|
||||
// the same class (not observed swept, same seam).
|
||||
//
|
||||
// ⚠ EXCLUDE PATTERNS ARE LOAD-BEARING IN WAYS THE DOCS DON'T DESCRIBE
|
||||
// (empirically established 2026-10-08): adding dir excludes like
|
||||
// "dist/**/*" / "./dist/**/*" for repo-root output dirs STRIPPED THE
|
||||
// server-external packages (pi-ai / pi-agent-core lost everything
|
||||
// under their dist/ — the traced copy collapsed to a bare package.json
|
||||
// and the packaged server died on ERR_MODULE_NOT_FOUND; openai/
|
||||
// @anthropic-ai — pi-ai's deps — vanished from the trace entirely).
|
||||
// Anchored "./"-prefixed forms behave the same. Only the three entries
|
||||
// below are verified safe (complete externals trace + clean payload).
|
||||
// The 7.4 GB recursive-DMG payload (repo dist/ swept into the bundle,
|
||||
// shipping the previous build inside the next) is instead prevented by
|
||||
// the `rm -rf dist .next/standalone` clean step in desktop:dist —
|
||||
// verified sufficient, since the sweep can only copy what exists at
|
||||
// trace time. scripts/build-server.mjs guards the rest.
|
||||
outputFileTracingExcludes: {
|
||||
"*": [
|
||||
"data/**/*",
|
||||
"auth.json",
|
||||
".env*",
|
||||
],
|
||||
},
|
||||
// Empirically verified gaps (2026-09-17 standalone smoke): the tracer
|
||||
|
||||
Reference in New Issue
Block a user