chore: promote staging to staging-promote/86a9d0bd-24396179464 (2026-04-14 14:33 UTC)

[ironclaw-ci]

Auto-promotion from staging CI

Batch range: a53eac5c2dec6b6cd5c08189086093fde64aa9cb..b6f5da88a7bff1c2b2485e6c342787429bdcb056
Promotion branch: staging-promote/b6f5da88-24404973909
Base: staging-promote/86a9d0bd-24396179464
Triggered by: Staging CI batch at 2026-04-14 14:33 UTC

Commits in this batch (30):

• a7401ec fix(gateway): scope chat approvals to the active thread (fix(gateway): scope chat approvals to the active thread #2267)
• 4032f6d Fix paired Telegram owner scope routine visibility (Fix paired Telegram owner scope routine visibility #2258)
• 7d66d83 fix(engine): always append ActionResult for every tool call (fix(engine): always append ActionResult for every tool call #2322)
• 764e586 feat(engine): LLM council via per-call model override in CodeAct (feat(engine): LLM council via per-call model override in CodeAct #2320)
• 70862ed feat(config): default CLI_MODE to TUI instead of REPL (feat(config): default CLI_MODE to TUI #2329)
• 207c4d4 ci: build docker image in release process (ci: build docker image in release process #2321)
• cd9b60c fix: re-apply Telegram UTF-16 splitting and DB MIGRATION label (fix: re-apply Telegram UTF-16 splitting and DB MIGRATION label #2304)
• 88b87c0 feat: user-facing temperature setting (feat: user-facing temperature setting #2275)
• fdb0a13 chore: sync staging and main (chore: sync staging and main #2337)
• 3cb77fe fix: resolve cargo-deny failures (wildcard deps + rand advisory) (fix: resolve cargo-deny failures (wildcard deps + rand advisory) #2370)
• ed2d6dc fix web chat refresh active thread ([codex] Fix web chat refresh active thread #2330)
• 66ccafb chore(engine): update monty to v0.0.11 (chore(engine): update monty to v0.0.11 #2364)
• 4529f00 fix(engine): track consecutive action errors in orchestrator Tier 0 path (Orchestrator: add action error counting to Python execution loop #2325) (fix(engine): track consecutive action errors in orchestrator (#2325) #2340)
• 50fc280 fix(agent): detect and escalate repeated identical failing tool calls (Agent retries same failing tool call up to 50 times with no duplicate detection #2240) (fix(agent): detect and escalate repeated identical failing tool calls #2338)
• 3f6149c feat(cli): add ironclaw profile list subcommand (feat(cli): add ironclaw profile list subcommand #2288)
• 625cd85 Suppress LLM_BACKEND warning when config.toml and .env values match (Suppress LLM_BACKEND warning when config.toml and .env values match #2388)
• a9cea6c fix(ci): skip NearAI URL DNS validation for non-NearAI backends (fix(ci): skip NearAI URL DNS validation for non-NearAI backends #2080)
• 160a75e fix(llm): image detail field + /v1 base URL normalization (fix(llm): image detail field + /v1 base URL normalization #2380)
• 4dbb44c fix(docker): make runtime-staging the default Docker target for Railway (fix(docker): make runtime-staging the default Docker target for Railway #2244)
• 532fc61 feat: admin management panel — web UI for users and usage monitoring (feat: admin management panel — web UI for users and usage monitoring #1963)
• 16b7b06 feat(web): add ironclaw docs link (feat(web): add ironclaw docs link #2398)
• ba81044 fix(mcp): Install NEAR AI MCP server from environment config (fix(mcp): Install NEAR AI MCP server from environment config #2181)
• 57d7b54 Fix Feishu webhook auth refresh and extension card overflow (fix: Feishu webhook auth refresh and extension card overflow #2443)
• 7425dc0 fix(security): harden approval thread safety (TOCTOU + error handling) (fix(security): harden approval thread safety (TOCTOU + error handling) #2366)
• 86a9d0b fix: image generation with nearai models (fix: image generation with nearai models #1819)
• 46ff740 docs(setup): warn that Telegram open mode splits history (docs(setup): warn that Telegram open mode splits history #2427)
• aea2e87 fix(ux): actionable auth errors and improved CLI help for new users (should make it easy to use #1852) (fix(ux): actionable auth errors and improved CLI help for new users (#1852) #2315)
• ab1f279 fix: more strict check for registry to avoid false positives (fix: more strict check for registry to avoid false positives #2222)
• 019c048 refactor(llm): promote decorator chain settings from NearAiConfig to top-level LlmConfig (refactor(llm): promote decorator chain settings from NearAiConfig to top-level LlmConfig #1749)
• b6f5da8 perf(tunnel): reuse HTTP client in CustomTunnel health checks (perf(tunnel): reuse HTTP client in CustomTunnel health checks #1201)

Current commits in this promotion (5)

Current base: staging-promote/86a9d0bd-24396179464
Current head: staging-promote/b6f5da88-24404973909
Current range: origin/staging-promote/86a9d0bd-24396179464..origin/staging-promote/b6f5da88-24404973909

• 46ff740 docs(setup): warn that Telegram open mode splits history (docs(setup): warn that Telegram open mode splits history #2427)
• aea2e87 fix(ux): actionable auth errors and improved CLI help for new users (should make it easy to use #1852) (fix(ux): actionable auth errors and improved CLI help for new users (#1852) #2315)
• ab1f279 fix: more strict check for registry to avoid false positives (fix: more strict check for registry to avoid false positives #2222)
• 019c048 refactor(llm): promote decorator chain settings from NearAiConfig to top-level LlmConfig (refactor(llm): promote decorator chain settings from NearAiConfig to top-level LlmConfig #1749)
• b6f5da8 perf(tunnel): reuse HTTP client in CustomTunnel health checks (perf(tunnel): reuse HTTP client in CustomTunnel health checks #1201)

Auto-updated by staging promotion metadata workflow

Waiting for gates:

• Tests: pending
• E2E: pending
• Claude Code review: pending (will post comments on this PR)

---

Auto-created by staging-ci workflow

[claude]

Code review

Found 3 issues:

1. [MEDIUM:70] LLM Config promotion mixes concerns — decorator chain settings (max_retries, circuit_breaker_threshold, etc.) moved from NearAiConfig to top-level LlmConfig. This conflates provider-specific defaults with global decorator chain configuration. The fallback logic is sound, but this architectural shift could confuse future maintainers about where these settings belong. Consider documenting in CLAUDE.md that these are now global LLM settings, not provider-specific.

https://github.com/anthropics/ironclaw/blob/2d26dfe07af9d7ddb48f772a0cf4c7526e523e24/src/config/llm.rs#L371-L425

2. [MEDIUM:60] Missing integration tests for LLM config fallback behavior — The config code implements fallback from LLM_* to NEARAI_* env vars (e.g., LLM_MAX_RETRIES → NEARAI_MAX_RETRIES → default). Current tests are unit-level only. Per CLAUDE.md testing rules, tests should drive the caller (LlmConfig::resolve) with various env combinations to verify: LLM_MAX_RETRIES overrides NEARAI_MAX_RETRIES, omitting both uses defaults, and invalid values are caught.

https://github.com/anthropics/ironclaw/blob/2d26dfe07af9d7ddb48f772a0cf4c7526e523e24/src/config/llm.rs#L1818-1843

3. [MEDIUM:55] build.rs rerun-if-changed additions may conflict with per-file watches — The PR adds three directory-level watches (registry/tools, registry/channels, registry/mcp-servers). The comment mentions per-file watches are "emitted inside collect_json_files()", but the diff doesn't show that function. If collect_json_files() already watches individual files, these directory watches are correct. If not, per-file granularity is lost. Verify that both mechanisms coexist correctly and document their interaction.

https://github.com/anthropics/ironclaw/blob/2d26dfe07af9d7ddb48f772a0cf4c7526e523e24/build.rs#L129-L132

Note: One pre-existing issue was noted (misleading circuit_breaker_threshold error message for 0 value) but is outside this PR's scope.