Sync upstream paradigmxyz/centaur main → darkmatter/centaur main - #60
Open
darkmatter[bot] wants to merge 24 commits into
Open
Sync upstream paradigmxyz/centaur main → darkmatter/centaur main#60darkmatter[bot] wants to merge 24 commits into
darkmatter[bot] wants to merge 24 commits into
Conversation
…z#1613) Bumps the github-actions group with 2 updates: [actions/checkout](https://github.com/actions/checkout) and [actions/setup-python](https://github.com/actions/setup-python). Updates `actions/checkout` from 4 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v4...v7) Updates `actions/setup-python` from 5 to 7 - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v5...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: actions/setup-python dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ith 3 updates (paradigmxyz#1612) chore(deps): bump the api-rs-dependencies group Bumps the api-rs-dependencies group in /services/api-rs with 3 updates: [aws-smithy-types](https://github.com/smithy-lang/smithy-rs), [toml](https://github.com/toml-rs/toml) and [tower-http](https://github.com/tower-rs/tower-http). Updates `aws-smithy-types` from 1.6.2 to 1.6.3 - [Release notes](https://github.com/smithy-lang/smithy-rs/releases) - [Changelog](https://github.com/smithy-lang/smithy-rs/blob/main/CHANGELOG.md) - [Commits](https://github.com/smithy-lang/smithy-rs/commits) Updates `toml` from 1.1.4+spec-1.1.0 to 1.1.5+spec-1.1.0 - [Commits](toml-rs/toml@toml-v1.1.4...toml-v1.1.5) Updates `tower-http` from 0.7.0 to 0.7.1 - [Release notes](https://github.com/tower-rs/tower-http/releases) - [Commits](tower-rs/tower-http@tower-http-0.7.0...tower-http-0.7.1) --- updated-dependencies: - dependency-name: aws-smithy-types dependency-version: 1.6.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: api-rs-dependencies - dependency-name: toml dependency-version: 1.1.5+spec-1.1.0 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: api-rs-dependencies - dependency-name: tower-http dependency-version: 0.7.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: api-rs-dependencies ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…th 4 updates (paradigmxyz#1611) chore(deps): bump the ruby-dependencies group Bumps the ruby-dependencies group in /services/console with 4 updates: [sentry-ruby](https://github.com/getsentry/sentry-ruby), [sentry-rails](https://github.com/getsentry/sentry-ruby), [bootsnap](https://github.com/rails/bootsnap) and [image_processing](https://github.com/janko/image_processing). Updates `sentry-ruby` from 6.7.0 to 7.0.0 - [Release notes](https://github.com/getsentry/sentry-ruby/releases) - [Changelog](https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md) - [Commits](getsentry/sentry-ruby@6.7.0...7.0.0) Updates `sentry-rails` from 6.7.0 to 7.0.0 - [Release notes](https://github.com/getsentry/sentry-ruby/releases) - [Changelog](https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md) - [Commits](getsentry/sentry-ruby@6.7.0...7.0.0) Updates `sentry-rails` from 6.7.0 to 7.0.0 - [Release notes](https://github.com/getsentry/sentry-ruby/releases) - [Changelog](https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md) - [Commits](getsentry/sentry-ruby@6.7.0...7.0.0) Updates `bootsnap` from 1.25.0 to 1.26.0 - [Release notes](https://github.com/rails/bootsnap/releases) - [Changelog](https://github.com/rails/bootsnap/blob/main/CHANGELOG.md) - [Commits](rails/bootsnap@v1.25.0...v1.26.0) Updates `image_processing` from 2.0.3 to 2.1.0 - [Changelog](https://github.com/janko/image_processing/blob/master/CHANGELOG.md) - [Commits](janko/image_processing@v2.0.3...v2.1.0) --- updated-dependencies: - dependency-name: sentry-ruby dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: ruby-dependencies - dependency-name: sentry-rails dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: ruby-dependencies - dependency-name: sentry-rails dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: ruby-dependencies - dependency-name: bootsnap dependency-version: 1.26.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: ruby-dependencies - dependency-name: image_processing dependency-version: 2.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: ruby-dependencies ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* chore(slackbotv2): upgrade Chat SDK to 4.40.0 * docs: remove Chat SDK upgrade notes * fix(slackbotv2): preserve delivery state and stream batching
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 8, 2026 03:01
b5a40a2 to
0715475
Compare
darkmatter
Bot
changed the title
* feat(api-rs): retention for session_events Every event the control plane records lands in session_events, including one row per harness stdout line, and nothing ever removed them: no TTL, no partitioning, and no delete anywhere in api-rs. Rows only went via the cascade from sessions, and sessions are not deleted in normal operation, so the table grew monotonically for the life of the deployment -- order 1.1M rows and 450MB a day on a modest single node, against a 20Gi default volume. SESSION_EVENTS_RETENTION_DAYS deletes events past the window on the existing cleanup sweep. Off by default: session_events is durable history and dropping it is not something to start doing to an existing deployment unasked. Events of a queued or running execution are never deleted, whatever their age. A long-running turn's early output is still needed to replay it, and age alone does not distinguish old from still-in-use. Deletes are batched and each sweep is bounded at 100k rows. Switching retention on for the first time can face millions of rows, and one unbounded delete would hold locks and bloat the table for the duration; successive sweeps drain the backlog instead. Migration 0054 adds the created_at index the sweep needs -- the table had only (thread_key, event_id) and (execution_id, event_type), so an age-keyed delete would seq-scan the largest table in the schema on every pass. * refactor(api-rs): separate session event retention cleanup * fix: limit session event retention to stdout rows * chore: bump chart version to 0.1.137 * fix: expire stdout after execution retention window * refactor: return retention deletion count directly * fix: install retention index outside startup migrations --------- Co-authored-by: Matthew Slipper <me@matthewslipper.com>
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 8, 2026 16:01
a106e21 to
59ffe5e
Compare
darkmatter
Bot
changed the title
darkmatter
Bot
changed the title
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 8, 2026 17:02
272f5eb to
59ffe5e
Compare
…1616) * feat(slackbotv2): add toggleable Slack agent experience * fix(slackbotv2): make native agent stops recoverable * chore(chart): bump version to 0.1.138 * refactor(slackbotv2): defer native stop support
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 8, 2026 18:01
d10382d to
160baf5
Compare
darkmatter
Bot
changed the title
* feat: add durable Slack button callbacks to workflows * refactor: simplify workflow button lifecycle * refactor: start a workflow for each Slack button click * feat: support Slack workflow button styles * fix: authenticate workflow button targets before invocation * docs: clarify Slack button replay semantics
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 8, 2026 20:01
e2c4440 to
b3fd35e
Compare
darkmatter
Bot
changed the title
darkmatter
Bot
changed the title
* fix: show workflow button processing state * docs: remove workflow button documentation changes * refactor: simplify workflow button feedback lifecycle * fix: keep workflow button feedback best effort * refactor: clarify workflow button feedback lifecycle
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 9, 2026 04:45
c9376bb to
2c23d3e
Compare
darkmatter
Bot
changed the title
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 10, 2026 01:18
b250035 to
0c97b1a
Compare
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 10, 2026 06:01
0c97b1a to
33228fe
Compare
darkmatter
Bot
changed the title
* feat: add info command to centaur MCP tool * fix: preserve legacy MCP skill guidance * refactor: remove centaur info cache * fix: correct centaur info command discovery * fix: reject non-typer info entrypoints clearly * fix: complete centaur info discovery metadata * docs: fix centaur run example * refactor: use CLI help for tool discovery
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 10, 2026 19:02
948d99e to
33228fe
Compare
darkmatter
Bot
changed the title
darkmatter
Bot
changed the title
darkmatter
Bot
changed the title
darkmatter
Bot
force-pushed
the
sync/upstream-main
branch
from
September 10, 2026 21:02
a40eb04 to
22a94df
Compare
darkmatter
Bot
changed the title
* feat: default company context output to JSON * test: remove broad company context output test
* feat: advertise tool skill associations * feat: merge repository and console skill catalogs * fix: tolerate malformed tool skill metadata * chore: restore sandbox system prompt * fix: preserve shadowed console skills * refactor: simplify merged skill catalog * refactor: move skill guidance into tool help * feat: add skill lookup guidance to MCP instructions * docs: link tool help to relevant skills * docs: leave vlogs help unchanged
feat: add batch read to gsuite tool
* fix: steer active codex block turns * test: reuse codex app-server fixture * test: cover queued codex block turns
* fix: require MCP catalog search * refactor: split MCP v2 bootstrap tools * refactor: make MCP builtin dispatch explicit
* fix: clarify MCP catalog discovery guidance * test: remove MCP catalog guidance test
* feat: default Granola output to JSON * test: remove unrelated Granola raw output coverage * test: remove Granola CLI coverage
![darkmatter[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upstream sync conflict repair completed in place on
sync/upstream-main.dc84e632cf7f909b5f36c6f5508e3f63143da107e5d3cb71f8de619e7e26905ecfb10df487ca459eb6d9b91aa7c188dc14d808cb274a46d5d21c2fa0sync/upstream-main--no-ffthree-way merge completed cleanly.Validation:
git diff --check HEAD^1..HEAD: passedcargo +stable check --workspace --lockedinservices/api-rs: passedcargo +stable check --lockedincrates/harness-server: passedbun test: 753 passed, 1 skipped, 0 failedSource:
paradigmxyz/centaur:main→sync/upstream-main. This PR is updated in place; it must be merged by a human only.