prompt: report config problems to the outbox, not fixes
Assisted-by: Claude Opus 5.5 via Claude Code
diff --git a/README.md b/README.md
index 02e76be..d067b69 100644
--- a/README.md
+++ b/README.md
@@ -185,7 +185,7 @@ env {
### Outbox
-Shared config is read-only in the container, so the outbox is the one reviewed path for changing it. Each session mounts a fresh, empty dir at `/root/.ramekin/outbox` (host: `$XDG_DATA_HOME/ramekin/repos/<slug>/outbox/<session-id>/`), and the system prompt tells the agent to write complete updated files there, mirroring the agent config layout. Empty outboxes vanish at teardown; anything left becomes a pending proposal.
+Shared config is read-only in the container, so the outbox is the one reviewed path for changing it. Each session mounts a fresh, empty dir at `/root/.ramekin/outbox` (host: `$XDG_DATA_HOME/ramekin/repos/<slug>/outbox/<session-id>/`), and the system prompt tells the agent to write a Markdown file there describing each config problem it hits, rather than a fix. Empty outboxes vanish at teardown; anything left becomes a pending proposal.
```sh
ramekin outbox list # pending proposals across sessions
diff --git a/assets/ramekin-prompt.md b/assets/ramekin-prompt.md
index 0fd9986..7e83ba5 100644
--- a/assets/ramekin-prompt.md
+++ b/assets/ramekin-prompt.md
@@ -10,9 +10,9 @@ The project workspace is bind-mounted at `{{WORKSPACE_PATH}}` (the container sta
The container filesystem is ephemeral. Any files written outside `{{WORKSPACE_PATH}}` will be lost when the session ends. System packages installed with `apt-get` do not persist across sessions — use a custom `.ramekin/Dockerfile` to add permanent dependencies.
-## Proposing configuration changes
+## Reporting configuration problems
-Agent configuration (memory files like `AGENTS.md`/`CLAUDE.md`, `skills/`, settings) is mounted read-only by design; editing it in place fails. To propose a change, write the complete updated file into `/root/.ramekin/outbox/`, mirroring its layout relative to your config directory (for example, a change to `skills/foo/SKILL.md` goes to `/root/.ramekin/outbox/skills/foo/SKILL.md`), and tell the user what you proposed and why. The user reviews and applies proposals on the host with `ramekin outbox`.
+Agent configuration (memory files like `AGENTS.md`/`CLAUDE.md`, `skills/`, settings) is mounted read-only by design; editing it in place fails. When that configuration is wrong, missing something, or got in your way, describe the problem in a Markdown file at `/root/.ramekin/outbox/<short-name>.md`, one problem per file: which config files are involved, what happened, what you expected, and the evidence (commands, errors, the step that went wrong). Describe the problem, not a fix — don't write replacement config files. Tell the user what you reported. The user reviews reports on the host with `ramekin outbox`.
## Networking