chore: promote staging to staging-promote/e5b82fc6-24240316990 (2026-04-10 14:22 UTC)

[ironclaw-ci]

Auto-promotion from staging CI

Batch range: 13c458e30cff5c437dfe3d19ddee0522f0c6e4fa..a8e6533a1f76502e65ff75b19914af516407a815
Promotion branch: staging-promote/a8e6533a-24247643750
Base: staging-promote/e5b82fc6-24240316990
Triggered by: Staging CI batch at 2026-04-10 14:22 UTC

Commits in this batch (19):

• 980d60e [codex] Stabilize auth readiness and gate flows ([codex] Stabilize auth readiness and gate flows #2050)
• af9b59a feat: unified tool dispatch + schema-validated workspace (feat: unified tool dispatch + schema-validated workspace #2049)
• b819d70 feat(web): add scroll-to-bottom arrow in gateway chat (feat(web): add scroll-to-bottom arrow in gateway chat #2202)
• 9399fcc fix(auth) first-pass Gmail OAuth auth prompt in chat (fix(auth) first-pass Gmail OAuth auth prompt in chat #2038)
• e0bdd74 feat(admin): admin tool policy to disable tools for users (feat(admin): admin tool policy to disable tools for users #2154)
• aaeb904 feat(tui): ship TUI in default binary (feat(tui): ship TUI in default binary #2195)
• 26e5e4c feat(docker): pre-bundle WASM extensions in staging image (feat(docker): pre-bundle WASM extensions in staging image #2210)
• 6a8e581 fix(wasm): upgrade Wasmtime to 43.0.1 and restore CI (fix(wasm): upgrade Wasmtime to 43.0.1 and restore CI #2224)
• 580165c feat(railway): build staging target with pre-bundled WASM extensions (feat(railway): build staging target with pre-bundled WASM extensions #2219)
• 2d8e6e6 fix(ci): resolve 3 staging test failures (fix(ci): resolve 3 staging test failures #2207)
• e0e0fcd fix(agent): stop intercepting bare yes/no/always as approval when nothing pending (fix(agent): stop intercepting bare yes/no/always as approval when nothing pending #2178)
• b9b239e fix(gateway): suppress duplicate text response during auth flow and unify extension config modal (fix(gateway): suppress duplicate auth response and unify extension config modal #2172)
• efdb738 fix(docker): consume CACHE_BUST arg so BuildKit invalidates cache
• bd7f2b7 Create QA Bug Report issue template (Create QA Bug Report issue template #2228)
• 4147c6d feat(gateway): extract gateway frontend into ironclaw_gateway crate with widget system (feat(gateway): extract gateway frontend into ironclaw_gateway crate with widget system #1725)
• 55cdbf2 fix(docs): explain in more details activation block & installation steps for skills (fix(docs): explain in more details activation block & installation steps for skills #2216)
• e5b82fc fix(bridge): sanitize auth_url on engine v2 path (v2 engine: auth_url from tool_activate is not scheme-sanitized #2206) (fix(bridge): sanitize auth_url on engine v2 path (#2206) #2215)
• 494636d docs: add amazon tutorial (docs: add amazon tutorial #2261)
• a8e6533 fix(oauth): use localhost for redirect URI when bound to 0.0.0.0 (fix(oauth): use localhost for redirect URI when bound to 0.0.0.0 #2247)

Current commits in this promotion (0)

Current base: staging-promote/e5b82fc6-24240316990
Current head: staging-promote/a8e6533a-24247643750
Current range: origin/staging-promote/e5b82fc6-24240316990..origin/staging-promote/a8e6533a-24247643750

• (no non-merge commits in range)

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 8 issues:

1. [CRITICAL:85] IPv6 address URL format bug in oauth_base_url() — when called with bare IPv6 address like "::1", returns invalid URL http://::1:3000. Per RFC 3986, IPv6 addresses in URLs must be bracketed: http://[::1]:3000. The test at line 1483 expects the wrong format. This breaks OAuth redirects on IPv6 deployments.

ironclaw/src/main.rs

Lines 1480 to 1484 in a8e6533

	oauth_base_url("my-server.example.com", 8080),
	"http://my-server.example.com:8080"
	);
	assert_eq!(oauth_base_url("::1", 3000), "http://::1:3000");
	}

2. [HIGH:80] Curl pipe-to-shell installation pattern in documentation — Line 133 of amazon.mdx recommends piping untrusted shell script directly to sh. This is a security anti-pattern. Should recommend: download script separately, verify SHA256 hash, review before execution, then run explicitly.

ironclaw/docs/infrastructure/amazon.mdx

Lines 131 to 135 in a8e6533

	```bash
	curl --proto '=https' --tlsv1.2 -LsSf https://github.com/nearai/ironclaw/releases/latest/download/ironclaw-installer.sh | sh
	```

3. [HIGH:85] Documentation content parity violation — Chinese version (docs/zh/infrastructure/amazon.mdx) omits significant sections from English version, particularly the "Configure Your Instance" hardening steps. Chinese version has ~90 lines vs English's 154 lines, creating inconsistent user experience and potentially leaving Chinese-speaking users with incomplete setup guidance.

https://github.com/nearai/ironclaw/blob/a8e6533a1f76502e65ff75b19914af516407a815/docs/zh/infrastructure/amazon.mdx

4. [MEDIUM:75] SSH key management guidance incomplete — Documentation shows chmod 400 but doesn't warn about shell history exposure (key path in bash history) or recommend using ssh-agent/SSH config to avoid exposing keys in process listings.

ironclaw/docs/infrastructure/amazon.mdx

Lines 30 to 35 in a8e6533

	```bash
	# Restrict permissions on the downloaded key (required by SSH)
	chmod 400 ~/.ssh/your-key.pem
	```

5. [MEDIUM:75] Resource guidance for t2.micro incomplete — No documentation of CPU, memory, storage limits. t2 instances have limited burst CPU (5-15% baseline) that could throttle LLM inference. No mention that 8GB default EBS volume may fill quickly with vector embeddings. Free tier only lasts 12 months. Contrast with DigitalOcean docs which specify "$4/month" explicitly.

ironclaw/docs/infrastructure/amazon.mdx

Lines 22 to 25 in a8e6533

	- **Name**: choose a descriptive name (e.g. `ironclaw`)
	- **AMI**: Ubuntu Server 24.04 LTS (free tier eligible)
	- **Instance type**: `t2.micro` or `t3.micro` (free tier eligible) — sufficient for most use cases
	- **Key pair**: click **Create new key pair**, give it a name, choose RSA and `.pem` format, then download the file. Keep it in a safe place — you will not be able to download it again.

6. [MEDIUM:75] Missing integration test for oauth_base_url — Per CLAUDE.md ("Test Through the Caller, Not Just the Helper"), the oauth_base_url() helper gates a side effect (OAuth flow via extension manager). Unit tests on the helper exist (lines 1473-1484), but missing integration test that drives the caller (app startup with mocked config) and verifies correct enable_gateway_mode() behavior. Regression coverage gap.

ironclaw/src/main.rs

Lines 1449 to 1459 in a8e6533

	fn oauth_base_url(host: &str, port: u16) -> String {
	let trimmed = host.trim_start_matches('[').trim_end_matches(']');
	let is_unspecified = trimmed
	.parse::<std::net::IpAddr>()
	.is_ok_and(|ip| ip.is_unspecified());
	if is_unspecified {
	format!("http://localhost:{}", port)
	} else {
	format!("http://{}:{}", host, port)
	}
	}

7. [MEDIUM:70] Insufficient sudo privilege management guidance — Documentation enables passwordless sudo for new user without mentioning security implications. Should recommend configuring sudoers to require password for sensitive operations.

ironclaw/docs/infrastructure/amazon.mdx

Lines 93 to 95 in a8e6533

	sudo adduser ironclaw
	sudo usermod -aG sudo ironclaw
	```

8. [LOW:65] Chinese documentation references missing security guide — Chinese version defers hardening to /zh/security guide (line 76-80) that may not exist or match EC2-specific steps, creating a documentation gap.

ironclaw/docs/zh/infrastructure/amazon.mdx

Lines 76 to 80 in a8e6533

	## 安全加固与安装 IronClaw
	[安全指南](/zh/security) 同样适用于您的 EC2 实例，但有一点不同：由于您已以 `ubuntu`（非 root 的 sudo 用户）身份登录，可以 **跳过"创建新用户"步骤** ——`ubuntu` 已承担了该角色。
	其余所有步骤——更新系统、加固 SSH、安装 Fail2Ban、配置防火墙以及安装 IronClaw——均完全适用。