[upstream-sync] Merge current Paradigm Centaur with TipLink compatibility - #76
Merged
Conversation
* refactor: route tool shims through centaur-tools * refactor: keep centaur-tools run as cli runner
feat: log tool shim calls
* fix slackbot best-effort handoff waits * reuse slack API timeout config * centralize slack timeout wrapper
feat: expose tool cli args in analytics
* fix: expose etl toggles under apiRs values * chore: bump chart version to 0.1.80
fix slack event file attachments
Generate a short GPT-backed title when the first user message is appended. Store titles on sessions and expose them in session context responses.
Closes paradigmxyz#640 Co-authored-by: Amp <amp@ampcode.com>
* fix: default sandbox timeout policy * fix: rely on sandbox max lifetime reaping * docs: clarify sandbox lifecycle timers * fix: prune stale warm sandboxes before replenishing * fix: prune stale warm sandboxes across workloads * fix: preserve idle pause deadlines after restart * refactor: simplify idle cleanup candidate query
Co-authored-by: Centaur AI <ai@centaur.local>
…aradigmxyz#862) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* fix: restrict non-observability sandbox egress * fix: whitelist observable cluster egress explicitly * fix: allow in-cluster database egress * fix: tighten restricted sandbox egress review gaps * fix: use configured control plane network peer * fix: keep restricted blocklist observability scoped * fix: allow direct victoria observability egress * fix: configure sandbox observability egress explicitly * fix: derive observability egress from endpoints * fix: avoid hardcoded observability endpoints * fix: allow sandbox egress to api pods
…digmxyz#870) Replayed the summary pipeline over five real threads (stg + prd) and found the deployed prompt produces one vague goal-restating status per thread: it steers the model toward the session goal, and the specific summaries it does write usually land at 46-52 characters, where sanitize_summary silently discards them (19 of 35 attempts). Two prompt changes, validated by replaying the same threads: - Describe the current step or latest finding instead of the overall session goal, with concrete example phrasings. - Target 40 characters and state the 45-character hard limit so the model cuts words instead of overflowing. Published summaries went from 14/35 attempts to 27/35, too-long discards from 19 to 3, and the output narrates actual progress ("I found forge-std is vendored, not submodule", "I'm blocked on tempo-obs metrics 502") instead of repeating "I'm checking X". Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
The authorized drain test permanently fences the API process, so run it after all execution, workflow, and metrics assertions.
Ports the audited TipLink runtime, config, tooling, alias, and Slack-normalization carry-forwards onto the reviewed upstream integration tree.
Make the baked core harness authoritative, prove Fineas overlays retain provider and trust blocks, and probe both real packaged provider routes without network access.
Bind publication to the exact verified PR head and green non-CodeQL checks, serialize package writes, publish by digest, refuse existing tags, and prove descriptors identify this run's runnable arm64 children. CodeQL baseline is unchanged.
Author
|
Retriggering the exact audited head after a transient BuildKit cache miss in the amd64 agent validation job; no source or tree change. CodeQL remains an explicitly ignored inherited baseline. |
Semantic port of approved PR #68 to the current HTTP-secret schema, with exact manifest translation and documentation regressions.
* fix(slackbotv2): resolve trigger bot identities * fix(slackbotv2): match webhook bots by app identity * refactor(slackbotv2): allowlist bot members only
…le (paradigmxyz#984) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Drop upstream-redundant workflow session plumbing, retain the independent cleanup and capability boundaries, align MCP discovery with sandbox shims, and correct runtime access guidance.
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
12 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.
Outcome
Merge current Paradigm Centaur into the TipLink fork while deleting compatibility code that the new upstream architecture supersedes. This is a source-only merge: merging this PR does not publish images or change the live deployment.
Pair this PR with TipLink/fineas-centaur-overlay#311. Do not use #78 except as rollback material.
Frozen source
What was removed
What remains TipLink-specific
These protections are independent of the upstream workflow architecture:
Compatibility verification
The exact core + overlay composition was tested with:
The paired overlay preserves Fineas public Slack RTS search, exact-channel JWT private access, Attio, Notion, Google Workspace, and the existing workflow/tool catalog.
Immutable reviewed artifacts
Tag:
reviewed-images-publish-0fd1735da56d820a4ef12ef525f745f5136fabb1-at-1783968967
Publication:
Each registry image was independently verified as a runnable linux/arm64 child with OCI revision 0fd1735.
Merge boundary