record that images are done and were never fork-gated

Bucket 1 lists them as No, and phase 4 put them behind the migration. opencode run takes
--file, so the path we already use carries them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-10 16:49:52 +01:00
co-authored by Claude Opus 5
parent 73b8111216
commit f0aa6dbf4b
+7
View File
@@ -102,6 +102,13 @@ passed that one model.
Until the model question is answered, turns stay on `opencode run --dir`, which is verified working on Until the model question is answered, turns stay on `opencode run --dir`, which is verified working on
1.18.16. 1.18.16.
**Images are done, and they never needed the fork** (bucket 1 lists them as "No — see B4", and Phase 4
put them behind the migration). `opencode run` takes attachments with `--file`, so the subprocess path
carries them today: the sidecar spills each image to a temp file for the turn and removes it in
`settle`. Verified end to end — a red PNG over the chat socket to `opencode/claude-sonnet-4-6` came back
"Red". `list-models` now reports each model's own `capabilities.input.image` instead of a hardcoded
`false`, so the composer gate became load-bearing in the right direction.
--- ---
## Bucket 1 — Claude has it, OpenCode does not ## Bucket 1 — Claude has it, OpenCode does not