Desktop footer context limit ignores effective ModelConfig (GOOSE_CONTEXT_LIMIT), disagrees with compaction

🤖

**Describe the bug**

Split from #10893. The footer denominator comes from static metadata with a hardcoded 128000 fallback (ui/desktop/src/components/ChatInput.tsx:596-627, :83) and never reads the session's effective ModelConfig, which compaction uses and which honors GOOSE_CONTEXT_LIMIT.

---

**To Reproduce**

Set GOOSE_CONTEXT_LIMIT: 1048576, start a session on a model whose static metadata says 128k: footer shows x / 128k while compaction triggers relative to 1M. Provider-agnostic.

---

**Expected behavior**

Footer and compaction read the same effective limit. Direction: expose the session's effective context_limit over ACP next to the existing usage updates; ChatInput prefers it, static chain as fallback.

Verification: with an override, footer and compaction agree; without, known models keep canonical limits.

The bug is in ui/desktop/src/components/ChatInput.tsx around lines 596-627 and 83, where the footer denominator uses a hardcoded fallback. The session's effective ModelConfig, which respects the GOOSE_CONTEXT_LIMIT environment variable, is used by compaction. Start by finding where the session's context_limit is exposed via ACP (Agent Communication Protocol). Update ChatInput to read this value, falling back to static metadata. Verify by setting GOOSE_CONTEXT_LIMIT to a different value and checking that the footer and compaction agree.

索引モデルが issue の本文から書いたものです。