Skip to content

chore: promote staging to staging-promote/c559a588-24788480958 (2026-04-22 19:05 UTC) - #2864

Merged
henrypark133 merged 1 commit into
mainfrom
staging-promote/d33fecb1-24797241283
Apr 29, 2026
Merged

henrypark133 merged 1 commit into
mainfrom
staging-promote/d33fecb1-24797241283

Conversation

@ironclaw-ci

@ironclaw-ci ironclaw-ci Bot commented Apr 22, 2026 •

Copy link
Copy Markdown
Contributor

Auto-promotion from staging CI

Batch range: 7fb41555a9e55677d1aaea29ca567a5b369c2b05..d33fecb17c3e81404f021ee944aa75673d1b4f97
Promotion branch: staging-promote/d33fecb1-24797241283
Base: staging-promote/c559a588-24788480958
Triggered by: Staging CI batch at 2026-04-22 19:05 UTC

Commits in this batch (80):

Current commits in this promotion (1)

Current base: staging-promote/c559a588-24788480958
Current head: staging-promote/d33fecb1-24797241283
Current range: origin/staging-promote/c559a588-24788480958..origin/staging-promote/d33fecb1-24797241283

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

* Add canonical engine capability status enum

* Add bridge tool surface assignment policy

* fix(engine): tighten scoped surface assignment

* fix(bridge): remove premature approval_gated field, surface ReadyScoped in capabilities

- Remove approval_gated from SurfacePolicyInput (YAGNI until policy uses it)
- Change ReadyScoped fallback from neither() to capabilities_only() so
  scoped subjects remain visible in background context
- Update tests to match new behavior

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix(ci): unblock section 2 policy PR

* engine-v2: add capability projection and two-surface prompt baseline (#2826)

* Add capability projection and two-surface prompt baseline

* Reduce step-context args for clippy-clean two-surface stack

* fix(engine): address two-surface review follow-ups

* fix(engine): normalize alias-aware capability projection

* fix(bridge): share extension fetch between projectors, preserve NeedsAuth in actions

- Fetch list_capability_extensions once in EffectBridgeAdapter and pass
  to both ActionProjector and CapabilityProjector via prefetched_extensions
- Keep NeedsAuth provider tools in available_actions so the LLM can
  trigger auth gates by attempting to call them
- Add unit tests for NeedsAuth preservation and latent tool omission
  at the ActionProjector level where extension maps can be controlled

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: serrrfirat <f@nuff.tech>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: serrrfirat <f@nuff.tech>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added size: XL 500+ changed lines risk: low Changes to docs, tests, or low-risk modules contributor: core 20+ merged PRs labels Apr 22, 2026
@claude

claude Bot commented Apr 22, 2026

Copy link
Copy Markdown

Code review

Found 7 issues:

  1. [HIGH:95] Production code violates CLAUDE.md unwrap() policy in build_step_context()

  2. [MEDIUM:90] Clone-heavy extension cache lookup in hot path

  3. [MEDIUM:75] Module-level dead code suppression masks warnings in production code

  4. [MEDIUM:70] TOCTOU race condition in extension cache validity check

  5. [MEDIUM:68] Extension fetch failures silently degrade to empty capabilities

  6. [MEDIUM:72] CapabilityStatus::Error variant lacks documentation on recovery contract

  7. [LOW:60] Silent error fallback on extension fetch without justification annotation

Non-issues cleared:

  • All trait method signatures correctly updated across 14 call sites and 8 implementations
  • No uninitialized variables, division by zero, or logic errors in diff
  • No .unwrap() panics in async paths
  • No command injection, path traversal, or secrets in logs

Base automatically changed from staging-promote/c559a588-24788480958 to main April 29, 2026 04:09
@henrypark133
henrypark133 merged commit d33fecb into main Apr 29, 2026
327 of 494 checks passed
@henrypark133
henrypark133 deleted the staging-promote/d33fecb1-24797241283 branch April 29, 2026 04:09

This branch had an error being deployed

1 failed and 5 inactive deployments
Ironclaw-QA / production — d33fecb1 Deployed Apr 22, 2026 by railway-app[bot]
cosmose-ironclaw / production — d33fecb1 Deployed Apr 22, 2026 by railway-app[bot]
ironclaw-nearai / production — d33fecb1 Deployed Apr 22, 2026 by railway-app[bot]
humble-cat / staging-cameron — d33fecb1 Deployed Apr 22, 2026 by railway-app[bot]
Near Foundation Ironclaw / production — d33fecb1 Deployed Apr 22, 2026 by railway-app[bot]
venice-ironclaw / production — d33fecb1 Deployed Apr 22, 2026 by railway-app[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor: core 20+ merged PRs risk: low Changes to docs, tests, or low-risk modules size: XL 500+ changed lines staging-promotion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant