stack

mosaicstack/stack

Fork 0

Author	SHA1	Message	Date
Jarvis	af7dd3fa7c	ci: re-trigger pipeline (flaky pglite WASM OOM in packages/db, unrelated) All checks were successful ci/woodpecker/pr/ci Pipeline was successful Details ci/woodpecker/push/ci Pipeline was successful Details The push/ci run for the prior commit failed only in packages/db's src/migrate.test.ts with 'memory access out of bounds' inside the pglite WASM module — a known-flaky in-memory-Postgres crash under CI memory pressure. The pr/ci pipeline passed on the identical tree, and this PR changes only a bash launcher script (no TS / no db package), so the failure cannot originate here. Empty commit to re-run CI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-24 00:04:41 -05:00
Jarvis	644d2805d2	fix(fleet): pre-trust claude agent workdir to clear the folder-trust gate (#644 ) Fleet-launched Claude agents stall forever at Claude Code's one-time "Is this a project you trust?" folder-trust prompt: there is no human in the pane to answer it, yet the heartbeat keeps reporting "healthy" because the pane process is alive — it's just blocked. This is the most common fleet outage (F1 / premature stop). --dangerously-skip-permissions does NOT bypass this gate, and neither does `trustedProjectDirectories` in settings.json (both verified empirically on 2026-06-24). The only record the gate honors is the per-project entry in ~/.claude.json: projects["<dir>"].hasTrustDialogAccepted == true — exactly what answering the prompt writes. start-agent-session.sh now pre-seeds that record for the claude runtime before launching the pane. The seeding is: - claude-only (codex/pi have no such gate), - idempotent (no-op when already trusted), - atomic (tempfile + os.replace; never corrupts a partial/unreadable file), - flock-serialized across concurrent agent launches sharing ~/.claude.json, - best-effort (any failure is non-fatal — the agent still launches, worst case it falls back to the pre-fix behavior). Verified end-to-end: with /home/jarvis untrusted, the modified launcher flips hasTrustDialogAccepted to true and Claude boots straight to the ready prompt with no gate. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-24 00:04:41 -05:00

Author

SHA1

Message

Date

Jarvis

af7dd3fa7c

ci: re-trigger pipeline (flaky pglite WASM OOM in packages/db, unrelated)

ci/woodpecker/pr/ci Pipeline was successful

Details

ci/woodpecker/push/ci Pipeline was successful

Details

The push/ci run for the prior commit failed only in packages/db's
src/migrate.test.ts with 'memory access out of bounds' inside the pglite
WASM module — a known-flaky in-memory-Postgres crash under CI memory
pressure. The pr/ci pipeline passed on the identical tree, and this PR
changes only a bash launcher script (no TS / no db package), so the
failure cannot originate here. Empty commit to re-run CI.

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

2026-06-24 00:04:41 -05:00

Jarvis

644d2805d2

fix(fleet): pre-trust claude agent workdir to clear the folder-trust gate (#644 )

Fleet-launched Claude agents stall forever at Claude Code's one-time
"Is this a project you trust?" folder-trust prompt: there is no human in
the pane to answer it, yet the heartbeat keeps reporting "healthy" because
the pane process is alive — it's just blocked. This is the most common
fleet outage (F1 / premature stop).

--dangerously-skip-permissions does NOT bypass this gate, and neither does
`trustedProjectDirectories` in settings.json (both verified empirically on
2026-06-24). The only record the gate honors is the per-project entry in
~/.claude.json: projects["<dir>"].hasTrustDialogAccepted == true — exactly
what answering the prompt writes.

start-agent-session.sh now pre-seeds that record for the claude runtime
before launching the pane. The seeding is:
- claude-only (codex/pi have no such gate),
- idempotent (no-op when already trusted),
- atomic (tempfile + os.replace; never corrupts a partial/unreadable file),
- flock-serialized across concurrent agent launches sharing ~/.claude.json,
- best-effort (any failure is non-fatal — the agent still launches, worst
  case it falls back to the pre-fix behavior).

Verified end-to-end: with /home/jarvis untrusted, the modified launcher
flips hasTrustDialogAccepted to true and Claude boots straight to the ready
prompt with no gate.

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

2026-06-24 00:04:41 -05:00

1 changed files with 1 additions and 1 deletions

									
										2

packages/mosaic/package.json
									
												View File
												
					@@ -1,6 +1,6 @@

					{

					{

					  "name": "@mosaicstack/mosaic",

					  "name": "@mosaicstack/mosaic",

					  "version": "0.0.42",

					  "version": "0.0.41",

					  "repository": {

					  "repository": {

					    "type": "git",

					    "type": "git",

					    "url": "https://git.mosaicstack.dev/mosaicstack/stack.git",

					    "url": "https://git.mosaicstack.dev/mosaicstack/stack.git",

Compare commits

2 Commits

release/mo ... fix/fleet-

2

packages/mosaic/package.json

View File

Compare commits

2 Commits release/mo ... fix/fleet-

2 packages/mosaic/package.json Unescape Escape View File

2 Commits

release/mo ... fix/fleet-

2

packages/mosaic/package.json

View File